[arch-general] cups not starting on boot after last 2 kernel updates? -- where to put it in the DAEMONS line?
Guys, Cups has been working like clockwork for the past year - up until the last 2 kernel updates. Now after boot, a manual '/etc/rc.d/cupsd restart' is required to get it working again. Would moving it in the DAEMONS line make sense? Currently I have: DAEMONS=(hwclock syslog-ng network named @netfs @ntpd @sshd @dhcp4 @crond @mysqld @postfix @dovecot @httpd @samba @cups @vsftpd @sensors @spamd) When cups fails to start, I get the following warnings and errors: W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "[v1.::1]" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "127.0.0.1" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "[v1.::1]" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "127.0.0.1" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "192.168.7.15" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "192.168.7.15" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "192.168.7.15" ignored! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3225! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3235! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3245! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3255! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3265! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3275! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3285! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3295! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3305! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3315! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3325! E [08/Aug/2011:10:53:39 -0500] Unable to bind socket for address [v1.::1]:631 - Address already in use. E [08/Aug/2011:10:53:39 -0500] Unable to bind socket for address 127.0.0.1:631 - Address already in use. E [08/Aug/2011:10:53:39 -0500] Unable to bind socket for address 192.168.7.15:631 - Address already in use. E [08/Aug/2011:10:53:39 -0500] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported I have no idea what the Bad File number errors are, but the warnings are just from the multiple explicit listen designations in the cupsd.conf for client access: # Only listen for connections from the local machine. Listen localhost:631 Listen phoenix.rlfpllc.com:631 Listen phoenix:631 Listen www.rlfpllc.com:631 Listen 192.168.7.15:631 I think the real issue is the 'Address already in use' errors, but that doesn't explain why it cups starts just fine with a manual '/etc/rc.d/cupsd restart'. If the address/port was actually already taken, then I would expect the restart to fail as well. The the ACL error is fine - cups isn't using acls on my box and I don't want to set the acl mount option in fstab, so I can live with that error. I've been through the forums, google and bug tracker task/22895, but still no solution. Should I move cupsd earlier in the DAEMONS line? Anybody else seeing cups fail to start on boot, but starting fine on a manual restart? Thanks for any thoughts or help you can give. -- David C. Rankin, J.D.,P.E.
On 11:31 Mon 08 Aug , David C. Rankin wrote:
Guys,
Cups has been working like clockwork for the past year - up until the last 2 kernel updates. Now after boot, a manual '/etc/rc.d/cupsd restart' is required to get it working again. Would moving it in the DAEMONS line make sense? Currently I have:
DAEMONS=(hwclock syslog-ng network named @netfs @ntpd @sshd @dhcp4 @crond @mysqld @postfix @dovecot @httpd @samba @cups @vsftpd @sensors @spamd)
You have @cups in DAEMONS ... probably need @cupsd? -- Peter Bui
On 08/08/11 at 11:31am, David C. Rankin wrote:
Guys,
Cups has been working like clockwork for the past year - up until the last 2 kernel updates. Now after boot, a manual '/etc/rc.d/cupsd restart' is required to get it working again. Would moving it in the DAEMONS line make sense? Currently I have:
DAEMONS=(hwclock syslog-ng network named @netfs @ntpd @sshd @dhcp4 @crond @mysqld @postfix @dovecot @httpd @samba @cups @vsftpd @sensors @spamd)
When cups fails to start, I get the following warnings and errors:
W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "[v1.::1]" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "127.0.0.1" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "[v1.::1]" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "127.0.0.1" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "192.168.7.15" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "192.168.7.15" ignored! W [08/Aug/2011:10:53:39 -0500] Duplicate listen address "192.168.7.15" ignored! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3225! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3235! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3245! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3255! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3265! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3275! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3285! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3295! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3305! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3315! E [08/Aug/2011:10:53:39 -0500] Bad File number 1 on line 3325! E [08/Aug/2011:10:53:39 -0500] Unable to bind socket for address [v1.::1]:631 - Address already in use. E [08/Aug/2011:10:53:39 -0500] Unable to bind socket for address 127.0.0.1:631 - Address already in use. E [08/Aug/2011:10:53:39 -0500] Unable to bind socket for address 192.168.7.15:631 - Address already in use. E [08/Aug/2011:10:53:39 -0500] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported
I have no idea what the Bad File number errors are, but the warnings are just from the multiple explicit listen designations in the cupsd.conf for client access:
# Only listen for connections from the local machine. Listen localhost:631 Listen phoenix.rlfpllc.com:631 Listen phoenix:631 Listen www.rlfpllc.com:631 Listen 192.168.7.15:631
I think the real issue is the 'Address already in use' errors, but that doesn't explain why it cups starts just fine with a manual '/etc/rc.d/cupsd restart'. If the address/port was actually already taken, then I would expect the restart to fail as well. The the ACL error is fine - cups isn't using acls on my box and I don't want to set the acl mount option in fstab, so I can live with that error.
I've been through the forums, google and bug tracker task/22895, but still no solution. Should I move cupsd earlier in the DAEMONS line? Anybody else seeing cups fail to start on boot, but starting fine on a manual restart? Thanks for any thoughts or help you can give.
-- David C. Rankin, J.D.,P.E.
You need to start cupsd in rc.conf daemons... not cups
On 08/08/2011 06:18 PM, J. W. Birdsong wrote:
You need to start cupsd in rc.conf daemons... not cups
Peter, J.W. -- thank you. (slaps self for stupidity) That is a 'forest-for-the-trees' issue it would have taken days to see! -- David C. Rankin, J.D.,P.E.
It would appear that on Aug 8, Peter Bui did say:
You have @cups in DAEMONS ... probably need @cupsd?
It would appear that on Aug 8, J. W. Birdsong did say:
You need to start cupsd in rc.conf daemons... not cups
It would appear that on Aug 8, David C. Rankin did say:
Peter, J.W. -- thank you. (slaps self for stupidity) That is a 'forest-for-the-trees' issue it would have taken days to see!
Hmmmnnn. Now I'm confused... According to my console login prompt, I'm currently using 2.6.39-ARCH And after a recent pacman -Syu cups stopped loading for me until I changed my Daemons line to say cups rather than cupsd. There had, if I remember right, been a {is it 'rc.confpacnew' or 'rc.conf.pacnew'?} that didn't have cups listed in the daemons line. Anyway I remember putting "cupsd" the new rc.conf first, and when that didn't work I edited it to just say "cups". I didn't think much about it at the time. All I cared was that my printer worked again. But why would one Arch Linux installation need "cups" in the daemons line while another needs "cupsd"??? -- | ~^~ ~^~ | <?> <?> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>>
On Tue, Aug 9, 2011 at 5:25 PM, Joe(theWordy)Philbrook <jtwdyp@ttlc.net> wrote:
It would appear that on Aug 8, Peter Bui did say:
You have @cups in DAEMONS ... probably need @cupsd?
It would appear that on Aug 8, J. W. Birdsong did say:
You need to start cupsd in rc.conf daemons... not cups
It would appear that on Aug 8, David C. Rankin did say:
Peter, J.W. -- thank you. (slaps self for stupidity) That is a 'forest-for-the-trees' issue it would have taken days to see!
Hmmmnnn. Now I'm confused... According to my console login prompt, I'm currently using 2.6.39-ARCH And after a recent pacman -Syu cups stopped loading for me until I changed my Daemons line to say cups rather than cupsd.
There had, if I remember right, been a {is it 'rc.confpacnew' or 'rc.conf.pacnew'?} that didn't have cups listed in the daemons line. Anyway I remember putting "cupsd" the new rc.conf first, and when that didn't work I edited it to just say "cups". I didn't think much about it at the time. All I cared was that my printer worked again.
But why would one Arch Linux installation need "cups" in the daemons line while another needs "cupsd"???
-- | ~^~ ~^~ | <?> <?> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>>
Which version of cups needs 'cups' in the DAEMONS array?
Karol Blazewicz [2011.08.09 1744 +0200]:
On Tue, Aug 9, 2011 at 5:25 PM, Joe(theWordy)Philbrook <jtwdyp@ttlc.net> wrote:
It would appear that on Aug 8, Peter Bui did say:
You have @cups in DAEMONS ... probably need @cupsd?
It would appear that on Aug 8, J. W. Birdsong did say:
You need to start cupsd in rc.conf daemons... not cups
It would appear that on Aug 8, David C. Rankin did say:
Peter, J.W. -- thank you. (slaps self for stupidity) That is a 'forest-for-the-trees' issue it would have taken days to see!
Hmmmnnn. Now I'm confused... According to my console login prompt, I'm currently using 2.6.39-ARCH And after a recent pacman -Syu cups stopped loading for me until I changed my Daemons line to say cups rather than cupsd.
There had, if I remember right, been a {is it 'rc.confpacnew' or 'rc.conf.pacnew'?} that didn't have cups listed in the daemons line. Anyway I remember putting "cupsd" the new rc.conf first, and when that didn't work I edited it to just say "cups". I didn't think much about it at the time. All I cared was that my printer worked again.
But why would one Arch Linux installation need "cups" in the daemons line while another needs "cupsd"???
-- | ~^~ ~^~ | <?> <?> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>>
Which version of cups needs 'cups' in the DAEMONS array?
It seems that older versions of the cups package installed /etc/rc.d/cups and not /etc/rc.d/cupsd. At least I had cups in the DAEMONS array, and it always worked until I did some pacman -Suy. It didn't take long to figure out, though, that the name of the script was now changed to cupsd. Cheers, Norbert
On Tue, Aug 9, 2011 at 10:25 PM, Norbert Zeh <nzeh@cs.dal.ca> wrote:
It seems that older versions of the cups package installed /etc/rc.d/cups and not /etc/rc.d/cupsd. At least I had cups in the DAEMONS array, and it always worked until I did some pacman -Suy. It didn't take long to figure out, though, that the name of the script was now changed to cupsd.
Cheers, Norbert
If I'm reading this [1] right, daemon name change occurred on 2011-07-14 on cups version update to 1.4.7-2. [1] http://projects.archlinux.org/svntogit/packages.git/commit/cups/trunk/PKGBUI...
participants (6)
-
David C. Rankin
-
J. W. Birdsong
-
Joe(theWordy)Philbrook
-
Karol Blazewicz
-
Norbert Zeh
-
Peter Bui