Home > Cups Unable > Cups Unable To Bind Broadcast Socket

Cups Unable To Bind Broadcast Socket

Thanks. And as I can reach web pages both in apache through port 80 and in Tomcat through port 8080 I should be able to reach CUPS through port 631 as far Offline #3 2014-01-25 15:21:34 Luckiboy Member Registered: 2013-11-22 Posts: 15 Re: [Solved] Cups error (/etc/hosts corrupt?) The log file says localhost:631 is an invalid host? If you do not have a password on your root account then you won't be able to add printers remotely or via the web interface!To disable password authentication you need to check over here

I don't dare do anything with GUI's, they tend to corrupt/change my text-based config settings, so I've made no changes. Till Kamppeter (till-kamppeter) wrote on 2009-01-10: #15 So Alvin and Trapanator, you should be able to print. The 1.7.1 version was pushed out sometime last month, which might explain these posts only coming up now (there's at least three). Hopefully, you can get on with managing the printers w/o further issue. http://www.linuxproblem.org/art_13.html

D [30/Dec/2004:11:10:31 -0500] LoadAllPrinters: Loading printer HP-Deskjet... I'm holding on to this for reference as I'm sure to use it in the future. When I try I get the error message: Firefox can't establish a connection to the server at 10.0.0.201:631 Trapanator (trapanator) wrote on 2009-01-11: #25 I upgraded to 1.3.9-2ubuntu6, but I cannot

Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ Till Kamppeter (till-kamppeter) wrote on 2009-01-10: #7 Alex, cups 1.3.9-2ubuntu5 is completel;y broken, please update to cups 1.3.9-2ubuntu6 (if not yet in -updates from -proposed). 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). As of yesterday, /var/log/samba/smbd.log shows this error: printing/print_cups.c:cups_printer_fn(110) Unable to connect to CUPS server localhost - Connection refused There were no entries in smbd.log today.

it should make a list of things listed in /etc/services and avoid those ports.) Robie Basak (racb) on 2015-10-08 summary: - cups: 127.0.0.1:631 - Address already in use.+ rpcbind grabs ports I'll remove .mozilla after I synced my config, I'll notice you when that solved it.What log is that you shared in post #8?/var/log/cups/error_log Offline #11 2014-01-26 17:34:21 Luckiboy Member Registered: 2013-11-22 Get 1:1 Help Now Advertise Here Enjoyed your answer? http://www.linuxquestions.org/questions/linux-general-1/unable-to-bind-socket-address-already-in-use-202099/ The printer works as advertised when connected locally to either machine.

April 2011 13:34 -.- Tats├Ąchlich... Can you kill all the listed processes, check whether no new processes come up and then start CUPS with sudo /etc/init.d/cups start Does CUPS start up, are you able to print? ramz View Public Profile View LQ Blog View Review Entries View HCL Entries Visit ramz's homepage! Join Now For immediate help use Live now!

Weird. https://www.experts-exchange.com/questions/21255770/cups-daemon-error-unable-to-bind-socket-address-in-use.html Bug189144 - rpc.statd sometimes binds to cups port 631 Summary: rpc.statd sometimes binds to cups port 631 Status: CLOSED DUPLICATE of bug 103401 Aliases: None Product: Fedora Classification: Fedora Component: nfs-utils Can it be that my problem is a different one? I think there is where the problem reside: ServerName xcaret.mydomain ServerAdmin [email protected] AccessLog /var/log/cups/access_log DataDir /usr/share/cups DefaultCharset utf-8 DefaultLanguage en DocumentRoot /usr/share/doc/cups ErrorLog /var/log/cups/error_log LogLevel debug MaxLogSize 1048576 PageLog /var/log/cups/page_log PreserveJobFiles

I feel like it would be best to write them as different threads since they don't seem to be related issues. check my blog Please let me know if you need more info. Please let me know if any additional info is needed. I added links to the three pertinent threads there and will be following along.

Allow From 10.* Order Deny,Allow Deny From All Allow From 127.0.0.1 <---------check here!!!! spangler View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by spangler View Blog 06-21-2008, 11:20 AM #7 Clemens.K LQ Newbie Registered: Jun Connect both servers S1 and S2 on the second network slots respectively. http://popupjammer.com/cups-unable/cups-unable-to-bind-socket-for-address-v1-1-631.html Listen localhost:631 Listen /var/run/cups/cups.sock Port 631 # Show shared printers on the local network.

I [07/Apr/2011:23:39:35 +0200] Using policy "default" as the default! For details and our forum data attribution, retention and privacy policy, see here Affecting: rpcbind (Ubuntu) Filed here by: D J Gardner When: 2015-10-07 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu

Samba works fine in terms of file sharing, only the print share failed.

Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. In your case it assigned unfortunately the port number 631. If not, your problem is something else.

Yves Dorfsman (dorfsmay) wrote on 2012-06-14: #32 The problem is that other daemon grab this port before cupsd gets a chance, typcally rpc. cupsd 1556 root 5u IPv6 10054 0t0 TCP ip6-localhost:ipp (LISTEN) cupsd 1556 root 6u IPv4 10055 0t0 TCP localhost:ipp (LISTEN) cupsd 1556 root 8u IPv4 10058 0t0 TCP crashserv.local:ipp (LISTEN) cupsd Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We http://popupjammer.com/cups-unable/cups-unable-to-bind-socket-for-address.html Here is the output from the "nmap 10.0.0.145" command: Starting Nmap 4.62 ( http://nmap.org ) at 2009-01-11 13:18 CET Interesting ports on sveinung1 (10.0.0.145): Not shown: 1712 closed ports PORT STATE

I still don't see the print share in any GUI on either RH9 or in XP Testparm shows up ok for print shares, but when I type smbclient -L xpclient, I Hopefully, you can get on with managing the printers w/o further issue. Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael FaradayYou assume people are rational and influenced by evidence. Password Linux - General This Linux forum is for general Linux questions and discussion.

If you want to # create dirs. D [07/Apr/2011:23:39:36 +0200] Report: clients=0 D [07/Apr/2011:23:39:36 +0200] Report: jobs=0 D [07/Apr/2011:23:39:36 +0200] Report: jobs-active=0 D [07/Apr/2011:23:39:36 +0200] Report: printers=0 D [07/Apr/2011:23:39:36 +0200] Report: printers-implicit=0 D [07/Apr/2011:23:39:36 +0200] Report: stringpool-string-count=127 D 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 svsig (svsig) wrote on 2009-01-11: #22 error_log Edit (2.3 KiB, text/plain) My problem is that I can't access the CUPS web interface on the server from a client.

Affecting: cups (Ubuntu) Filed here by: Alvin When: 2008-12-02 Confirmed: 2008-12-25 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu I commented out the bottom two copies, resaved cupsd.conf, did an /etc/init.d/cups restart, and I'm back in business. 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. I think there is where the problem reside: ServerName xcaret.mydomain ServerAdmin [email protected] AccessLog /var/log/cups/access_log DataDir /usr/share/cups Go to Solution 7 3 2 +1 4 Participants klukac(7 comments) Gabriel Orozco(3 comments) LVL

Till Kamppeter (till-kamppeter) wrote on 2009-01-10: #8 If you reboot your machine, does it really not start up CUPS? I commented out the only reference to 631 that was un-commented and it is working fine. Of course, your mileage may vary. Before rebooting, please edit /etc/cups/cupsd.conf, so that it has a line LogLevel debug and no other "LogLevel" line.

delete your previous configuration files in /etc/cups.d (clean the directory). 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 I get the error when i use at the same time: Port 631 Listen on x.x.x.x:631 Clemens.K View Public Profile View LQ Blog View Review Entries View HCL Entries Find