LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 07-07-2004, 06:24 AM   #1
engineerwell
LQ Newbie
 
Registered: Feb 2004
Distribution: SuSE Linux 9.0
Posts: 12

Rep: Reputation: 0
"unable to bind socket - Address already in use"


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?
 
Old 07-07-2004, 07:21 AM   #2
linuxxed
Member
 
Registered: Feb 2004
Posts: 273

Rep: Reputation: 30
Re: "unable to bind socket - Address already in use"

Quote:
Originally posted by engineerwell
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.
 
Old 08-02-2004, 01:49 AM   #3
jdsalmonson
LQ Newbie
 
Registered: Aug 2004
Posts: 1

Rep: Reputation: 0
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
 
Old 08-25-2004, 10:02 AM   #4
ramz
LQ Newbie
 
Registered: Aug 2004
Location: Fairfax, VA
Distribution: SUSE LINUX Professional 9.1
Posts: 6

Rep: Reputation: 0
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.
 
Old 09-01-2004, 01:36 PM   #5
scottmacphee
LQ Newbie
 
Registered: Sep 2004
Posts: 1

Rep: Reputation: 0
Lightbulb

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
 
Old 06-17-2008, 03:36 PM   #6
spangler
Member
 
Registered: Apr 2007
Posts: 45
Blog Entries: 1

Rep: Reputation: 15
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.
 
Old 06-21-2008, 10:20 AM   #7
Clemens.K
LQ Newbie
 
Registered: Jun 2008
Posts: 9

Rep: Reputation: 0
Quote:
Originally Posted by spangler View Post
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
 
Old 05-12-2010, 02:46 AM   #8
bayvista
LQ Newbie
 
Registered: Jul 2005
Location: Sydney, Australia
Distribution: Ubuntu Breezy Badger 5.10
Posts: 24

Rep: Reputation: 15
CUPS - Unable to bind socket

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???
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
"Unable to establish ICE Listeners: Cannot Socket..." Error!!! cqmyg5 Slackware 6 04-15-2012 12:37 AM
dhcpd error "Can't bind to dhcp address" msjenkins Linux - Networking 4 10-06-2010 05:16 PM
bind error on high ports "address already in use" DCalabrese Linux - Networking 2 05-25-2005 09:21 AM
difference between "Web server local URL" and "IPv4 address"? kpachopoulos Linux - General 2 09-17-2004 01:30 PM
Quagga "Can't bind socket: Invalid argument" JJX Linux - Networking 0 04-29-2004 10:21 AM


All times are GMT -5. The time now is 09:05 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration