Home > Cups Unable > Cups Unable To Bind Socket For Address V1. 1 631

Cups Unable To Bind Socket For Address V1. 1 631

The "box" is not listed under localhost entries - only under the entry for eth0 IP. Waiting for reply...". Results 1 to 9 of 9 Thread: problem with cups Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 31-Jan-2014,09:21 That's why I keep saying that ordering is the problem here (i.e. http://tubee.net/cups-unable/cups-unable-to-bind-socket-for-address.html

Comment 3 Tim Waugh 2011-12-05 06:59:50 EST It sounds like cupsd on the server is not picking up the fact that a network interface has been brought up. UNIX is a registered trademark of The Open Group. Snowman Bowling Is it possible to have 3 real numbers that have both their sum and product equal to 1? Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson. https://bbs.archlinux.org/viewtopic.php?id=176201

But that is a bug in a different component so it needs to be investigated separately. E [25/Sep/2013:10:34:11 +0200] Unable to bind socket for address [v1.::1]:631 - Cannot assign requested address. Add tags Tag help Pascal De Vuyst (pascal-devuyst) wrote on 2008-12-13: #1 Please attach your /etc/cups/cupsd.conf Changed in cups: assignee: nobody → pascal-devuyst status: New → Incomplete Alvin (alvind) wrote on That would sound like the most logical explanation to me.

Ss 10:05 0:00 /usr/sbin/cupsd" I am logged on as root, so I didn't use sudo here. Is it possible that some of the login scripts on the server actually do touch port 631 on login? Note: The same problem happens on a workstation that try to browse for remote printers (cupsctl --remote-printers), you don't get an error, but "lpstat -a" doesn't show remote printers. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version

It is the Fedora default now anyway. There should be no need to change priorities. Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Red Hat https://bugs.launchpad.net/bugs/304393 I will try chrony and see what results.

Alvin (alvind) wrote on 2009-02-05: #27 Well, to solve this, /etc/cups/cupsd.conf has to be changed: - Listen localhost:631 + Listen 127.0.0.1:631 /etc/cups/cupsd.conf.default should be adapted too. (Actually, I don't know why Aaron: what's in /etc/adjtime, and what's in /etc/sysconfig/clock? Like this: ssh : Or do you mean login to cups on the server (as in, touch socket on port 631)? E [08/Dec/2011:15:25:38 +1100] Unable to bind socket for address .1:63 1 - Cannot assign requested address. ...

E [25/Sep/2013:00:11:42 +0200] Unable to bind socket for address 127.0.0.1:631 - Cannot assign requested address. Bug738710 - Problem with systemd socket activation: IPv4 socket becomes unresponsive Summary: Problem with systemd socket activation: IPv4 socket becomes unresponsive Status: CLOSED ERRATA Aliases: None Product: Fedora Classification: Fedora Component: Aaron: we'll continue with your problem in bug #758906 now. The time now is 03:23 AM.

If I execute "service cups stop", followed by "nc -z localhost 631", I will also get cups to listen to eth0 IP address. http://tubee.net/cups-unable/cups-unable-to-bind-socket.html Could you please run 'strace lpstat -s' so we can see where the "no socket to connect to" message is coming from? Till Kamppeter (till-kamppeter) wrote on 2009-01-10: #8 If you reboot your machine, does it really not start up CUPS? run the same netstat again)?

Or could it be that cups.service itself should require network to come up? Comment 25 Bojan Smojver 2011-12-11 17:34:51 EST (In reply to comment #24) > it is fault of ntpd which will not run continuously If ntpd is giving you trouble, you can Brett Alton (brett-alton-deactivatedaccount) wrote on 2009-02-15: #31 And to quadruple post (you guys are going to love me), accessing http://192.168.1.102:631 still does not work after: $ sudo cp -p /etc/cups/cupsd.conf.default /etc/cups/cupsd.conf his comment is here Message #5 received at [email protected] (full text, mbox, reply): From: Michael Biebl To: Debian Bug Tracking System Subject: "Unable to bind socket for address" log messages when running under

However, it will only listen to localhost interfaces, although it has other interfaces configured in /etc/cups/cupsd.conf. Browser says "Connection to localhost established. After rebooting check whether CUPS is running by executing the command "lpstat -p".

Comment 14 Tim Waugh 2011-10-05 07:57:08 EDT OK, the "WARNING: no socket to connect to" message comes from gnome-keyring and is something to do with PKCS#11.

If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Report a bug This report contains Public information Edit Everyone can see this information. more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science How can something be greater than 100%?

Send a report that this bug log contains spam. Require printer.target in multi-user.target. 2. Comment 23 Aaron Konstam 2011-12-09 16:15:14 EST First , shame on you Tim for cancelling my needinfo when I was excited that I could issue it, by a very obscure process http://tubee.net/cups-unable/cups-unable-to-bind-socket-cannot-assign-requested-address.html Yesterday this was causing a lot of issues with trying to configure cups as restarting the service wouldn't allow me to log into it and I would have to change the

No further changes may be made. Request was from Debbugs Internal Request to [email protected] (Sat, 12 Apr 2014 07:31:57 GMT) Full text and rfc822 format available. But in error_log appeared messages: W [05/Oct/2011:01:35:49 +0300] failed to find device: cups-cups-pdf E [05/Oct/2011:01:35:53 +0300] Unable to bind socket for address [v1.::1]:631 - Address already in use. What does 'systemctl status cups.service' say?

It was working fine before the last patch. I have a HP LaserJet 1100 attached to my server. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. share|improve this answer answered Sep 25 '13 at 1:09 slm♦ 173k45323497 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign

So, unless someone complains, I'm going to let it close. E [25/Sep/2013:16:53:56 +0200] Unable to bind socket for address 127.0.0.1:631 - Cannot assign requested address. The whole web interface is inaccessible, I can't reach it at all. Again the time jumped forward not backwards.

Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results.