Following installation of printer CUPS fails with: "CUPS daemon died during initialization" error.

Having run rccups restart and investigate the error_log the following seems to be the only error reported:

"StartListening: Unable to bind socket - Address already in use."

How can I fix this?

Check the port CUPS is listening (/etc/services).

Check who is using that port using ( lsof -i:[PORT] or netstat -na |grep LISTEN|grep [PORT])

Move that app to a different port if it is using cups port.

I just confronted this very problem. I am trying to configure printing with SuSE 9.1. I came across this exact error. Looking at /var/log/messages
I realized that when I tried to start cupsd it was trying to read /etc/cups/cupsd.conf - which did not exist. Thru some error during my attempting to
configure printing thru YAST, the /etc/cups directory was completely removed (!) I reinstalled the cups rpms and this directory was replaced and
now cupsd will start without a problem.

However I still have not been able to print to my Canon S820 via a printserver. So eventhough I was able to overcome this particular hurdle, I'm
having a hard time printing to a printserver w/ SuSE 9.1 (while I had no problem w/ SuSE 8.1).

Best of luck,
-Jay

Well, I managed to finally solve this problem. Apparently, if you do something to uninstall/reinstall CUPS (like in my case thinking that I couldn't do LPD print services with CUPS and would need LRPng...oops...) and you already have SAMBA installed, CUPS will give you the Error 98 or "StartListening: Unable to bind socket - Address already in use." or "CUPS daemon died during initialization" error. I believe this is because of the linkages that exist between SAMBA-shared printers and CUPS that break and cause CUPS to detect a conflict (even though one CLEARLY doesn't exist). To finally fix the problem, I uninstalled all CUPS and UNIX printing related stuff (except for cups-libs and libgimpprint, because they broke too many other things) and all of the SAMBA related stuff. When I opened the yast2 printer control, the system prompted me for what kind of print system I wanted to install (I picked CUPS Server) and installed all the applicable RPMs. CUPS then started right up. Though I haven't as of yet, I'll next reinstall SAMBA and see what happens. Hopefully this helps one of the hundred+ people that I see with this problem in various groups/messageboards and think the only recourse is a reinstall.

I wedged my system in the same way. SuSE 9.1, using the YAST print manager interface trying to add a new USB printer.

I'm not sure exactly how I got where I did, but I think I ended up starting multiple copies of the print manager interface.

What ended up happening was the system concatenated three copies of /etc/cups/cupsd.conf into a single entry. Therefore, there were three binds to socket 631, causing cupsd to barf and die.

I commented out the bottom two copies, resaved cupsd.conf, did an /etc/init.d/cups restart, and I'm back in business.

Of course, your mileage may vary.

Have a good day.

Scott
scott@macphees.org

Scottmacphee, I just wanted to let you know that I was getting the same error on SLES 9 and did a search for 631 in cupsd.conf. I commented out the only reference to 631 that was un-commented and it is working fine.

Thanks for the tip.

I get the error when i use at the same time:
Port 631
Listen on x.x.x.x:631

I had a lot of trouble with a Canon LBP3100, although I now know that the problem is CUPS. Although I have added CCPD to my startup, I always need to run sudo /etc/init.d/ccpd start to make my printer work. I'd really like to know why???