[Bug 864312] New: cups needs to be restarted after every reboot - not listening properly?
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c0 Summary: cups needs to be restarted after every reboot - not listening properly? Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix@suse.com ReportedBy: jnelson-suse@jamponi.net QAContact: jsmeix@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Lately, I've had to restart cups after every reboot. It doesn't appear to be listening the same before vs. after each restart. Example: turnip:~ # netstat -planetu | grep 631 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 11507 725/cupsd tcp 0 0 ::1:631 :::* LISTEN 0 11506 725/cupsd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 11510 725/cupsd turnip:~ # rccups restart redirecting to systemctl restart cups.service turnip:~ # netstat -planetu | grep 631 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 29394 5017/cupsd tcp 0 0 192.168.1.2:631 0.0.0.0:* LISTEN 0 29392 5017/cupsd tcp 0 0 ::1:631 :::* LISTEN 0 29393 5017/cupsd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 29397 5017/cupsd turnip:~ # You'll notice that the 192.168.1.2 address is not present. This is the address of br0 (bridge zero). Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jnelson-suse@jamponi.net Platform|Other |All Found By|--- |Community User OS/Version|Other |openSUSE 13.1 --- Comment #1 from Johannes Meixner <jsmeix@suse.com> 2014-02-18 09:44:03 CET --- The bug's subject "cups needs to be restarted after every reboot" makes it look like a duplicate of bnc#802132 see in particular https://bugzilla.novell.com/show_bug.cgi?id=802132#c8 All cupsd starting issues that I noticed up to now are somehow related to bnc#857372. I assume your particular issue is also related to bnc#857372. To exclude issues that are related to bnc#857372 I would appreciate it if you try out the cups packages (at least cups-libs, cups-client, and cups) from the OBS project "Printing" on your system and provide feedback whether or not it works for you, see https://bugzilla.novell.com/show_bug.cgi?id=857372#c75 for instructions - in particular note ----------------------------------------------------------------------- To make systemd using only that cups.service file one may have to do # systemctl disable cups.service # systemctl enable cups.service ----------------------------------------------------------------------- Alternatively your issue could be related to your network setup because you wrote "192.168.1.2 address is not present This is the address of br0 (bridge zero)." A precondition for further analysis regarding network setup is that you use CUPS from the OBS project "Printing" because that packages use only "the real thing" /usr/sbin/cupsd directly via cups.service, cf. https://bugzilla.novell.com/show_bug.cgi?id=857372#c57 Where the cupsd is listening is specified by the "Listen" directive in /etc/cups/cupsd.conf, see "Configuring CUPS <= 1.5 in the Network" at http://en.opensuse.org/SDB:CUPS_in_a_Nutshell When you have an advanced network setup, you may have to specify the right values for your particular network setup manually for the "Listen" directive in /etc/cups/cupsd.conf Jon Nelson, please provide feedback whether or not it works for you with CUPS from the OBS project "Printing". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c2 --- Comment #2 from Johannes Meixner <jsmeix@suse.com> 2014-02-20 17:39:49 CET --- See https://bugzilla.novell.com/show_bug.cgi?id=857372#c122 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c3 Gerhard Roland <gerhard.roland@groland.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gerhard.roland@groland.de --- Comment #3 from Gerhard Roland <gerhard.roland@groland.de> 2014-03-05 15:13:58 UTC --- i have the same issue. it can be overcome if one adds in /usr/lib/systemd/system/cups.services the line After=network.service in the unit section (3rd line) This and other errors are due to a general design error in systemd:: we do not need speed in bringing a system up but reliability and predictiveness. We cannot afford time race conditions (like this one). And obviously there are other things to wait for but sockets. In this case we must wait for an IP being up. I suggest to rebuild _all_ waiting conditions and dependences we had in system V init in systemd or to return to sysinitV. Will there be such an option in 13.2 (to me 13.1 is much to instable for a productive installation)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c4 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|jnelson-suse@jamponi.net |gerhard.roland@groland.de --- Comment #4 from Johannes Meixner <jsmeix@suse.com> 2014-03-11 11:01:02 CET --- Gerhard Roland, do you already use the cups packages (at least cups-libs, cups-client, and cups) from the OBS project "Printing" on your system and you need "After=network.service" in cups.service in addition to "After=network.target"? I ask because cups.service in CUPS from "Printing" already contains "After=network.target", see https://bugzilla.novell.com/show_bug.cgi?id=857372#c61 "man systemd.special" reads ---------------------------------------------------------------------------- network.target This unit is supposed to indicate when network functionality is available, but it is only very weakly defined what that is supposed to mean .. Also see network-online.target described above. ---------------------------------------------------------------------------- network-online.target Units that strictly require a configured network connection should pull in network-online.target (via a Wants= type dependency) and order themselves after it. This target unit is intended to pull in a service that delays further execution until the network is sufficiently set up. What precisely this requires is left to the implementation of the network managing service. ---------------------------------------------------------------------------- but I am not at all a sufficient systemd expert to know what the right thing is and I cannot guess what "weakly defined" and "left to the implementation" actually results in reality. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c5 --- Comment #5 from Gerhard Roland <gerhard.roland@groland.de> 2014-03-11 11:49:29 UTC --- I just rechecked. I had tried to reinstall cups before I checked the systemd script due to no effect of the reinstall. As far as yast tells me under lxde there should be SUSE packages (licence SUSE GPL), version 1.5.4-12.4.1 installed. I have installed cups-client, cups.libs, cups-libs-32bit, cups-pk-helper, gutenprint, hplip, python-cups, python-cupshelper, To be honest, I never changed before the standard packages since...(I don't know 9.x or even earlier), -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c6 --- Comment #6 from Gerhard Roland <gerhard.roland@groland.de> 2014-03-11 13:12:35 UTC --- 1. OS is opensuse 13.1, all patches updated. 2. The printer I cannot install due to the missing admistration functions, is a HP photosmart D5460 on USB. lsusb finds the printer.. A samsung SCX4633FD is installed and working on network (socket, ipp is not reponding) – but since the first reboot after the first attempt to install the HP printer no adminstration nor maintaince is possible. 3. HP: USB Samsung (working) network, socket. 4. hp none (not possible to install Samsung the universal driver provides by Samsung (sorry no direct link, only http://www.samsung.com/uk/support/model/SCX-4833FD/SEE-downloads#, select Linux driuver V1.00.06) 5.1 trying to set pu the pronter with yast fails. The connection wizzard cannot find the HP printer. Setting up with hp-setup (within yasr) the printer type cannot be selected automatically. When filled in manually, the dialog repotrts an error and adds no printer. 5.2 no installation – no printing ;o Samung works, but no maitaince nor from yast nos via cups web interface. 5.3 command line see 5.2 6. I will provide any file you need – but I do not find any hint even in ei cups error log when cupsa log level is debug. It simply says: no permission. Pleaser tell which file you need. 8. in netstat -nl the ports for die used interface an loopback are reported( presumingly otherwise the samsung printe could not work). Everything wokred fine for a couple of releases up to opensuse 12.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c7 --- Comment #7 from Gerhard Roland <gerhard.roland@groland.de> 2014-03-14 16:08:30 UTC --- The last patch (not to start cups on boot but only on demand) may work on workstations but not on print servers. as nothing will start up cups on port 631 if it is not running there. xinetd will not help either, if at boot time the IP address of the particular interface is not up when xinetd starts... What does prevent the maintainers to put in solutions that worked for decades until they have working their new ones? This systemd ideology is driving me crazy. The basic assumptions are obviously simply insufficient as proven by these examples. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c8 --- Comment #8 from Johannes Meixner <jsmeix@suse.com> 2014-03-14 17:29:13 CET --- I fully agree. Therefore I really recommend to use the cups packages (at least cups-libs, cups-client, and cups) from the OBS project "Printing" on your system. E.g. for openSUSE 13.1 32-bit i586 for direct manual download from http://download.opensuse.org/repositories/Printing/openSUSE_13.1/i586/ and for openSUSE 13.1 64-bit x86_64 from http://download.opensuse.org/repositories/Printing/openSUSE_13.1/x86_64/ CUPS from the OBS project "Printing" does no longer have systemd socket activation enabled by default. Instead it activates the cupsd directly via cups.service which "just works" as it worked all the time in the past. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c9 Gerhard Roland <gerhard.roland@groland.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|gerhard.roland@groland.de | --- Comment #9 from Gerhard Roland <gerhard.roland@groland.de> 2014-03-16 03:05:28 UTC --- Coming up on system reboot works for me with the OBS "Printing" packages. Thank you! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=864312 https://bugzilla.novell.com/show_bug.cgi?id=864312#c10 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #10 from Johannes Meixner <jsmeix@suse.com> 2014-03-18 08:49:22 CET --- This proves what I wrote in comment#1: "All cupsd starting issues that I noticed up to now are somehow related to bnc#857372". *** This bug has been marked as a duplicate of bug 857372 *** http://bugzilla.novell.com/show_bug.cgi?id=857372 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com