Cups starts and then stops after 15 seconds

[Debian Bug Importer]

Automatically imported from Debian bug report #340314 http://bugs.debian.org/340314

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #340314 http://bugs.debian.org/340314

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 22 Nov 2005 16:59:06 +0000
From: Richard Ibbotson <email address hidden>
To: <email address hidden>
Subject: Cups starts and then stops after 15 seconds

Subject: cups starts and then stops after 15 seconds
Package: Cupsys
Version: 1.1.23-12
Severity: grave
Justification: renders package unusable

*** Please type your report below this line ***

Cupsys 1.1.23-12. Tried to use an earlier version of cupsys and that
didn't work. A version from Feb 2005 works fine. Printer goes
offline after 15 seconds of being configured with the 1.1.23-12
version. Samsung ML-1510. kcmprintmgr 3.4.2 detects the printer.
USB is working fine. USB scanner working on the same system. No
logs due to failure of cupsys to initialise. Also, get this more
often than cups starting in the firt place..

Get:1 http://ftp.debian.org testing/main cupsys-client 1.1.23-12
[109kB]
Get:2 http://ftp.debian.org testing/main cupsys-bsd 1.1.23-12 [47.8kB]
Fetched 157kB in 3s (40.0kB/s)
Preconfiguring packages ...
Selecting previously deselected package cupsys.
(Reading database ... 257703 files and directories currently
installed.)
Unpacking cupsys (from .../cupsys_1.1.23-12_i386.deb) ...
Selecting previously deselected package cupsys-client.
Unpacking cupsys-client
(from .../cupsys-client_1.1.23-12_i386.deb) ...
Selecting previously deselected package cupsys-bsd.
Unpacking cupsys-bsd (from .../cupsys-bsd_1.1.23-12_i386.deb) ...
Setting up cupsys (1.1.23-12) ...
Starting Common Unix Printing System: cupsdcupsd: Child exited with
status 98!
invoke-rc.d: initscript cupsys, action "start" failed.

Setting up cupsys-client (1.1.23-12) ...

Setting up cupsys-bsd (1.1.23-12) ...

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-1-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Output of.. /var/log/cups/error_log ... no other logs produced due to
the nature of the failureto start..

I [22/Nov/2005:14:36:23 +0000] Full reload complete.
E [22/Nov/2005:14:36:23 +0000] StartListening: Unable to bind socket
for address c0a80102:631 - A
I [22/Nov/2005:15:28:49 +0000] Loaded configuration file
"/etc/cups/cupsd.conf"
I [22/Nov/2005:15:28:49 +0000] Configured for up to 100 clients.
I [22/Nov/2005:15:28:49 +0000] Allowing up to 100 client connections
per host.
I [22/Nov/2005:15:28:49 +0000] Full reload is required.
I [22/Nov/2005:15:28:51 +0000] LoadPPDs: Read
"/var/lib/cups/ppds.dat", 3277 PPDs...
I [22/Nov/2005:15:28:52 +0000] LoadPPDs: No new or changed PPDs...
I [22/Nov/2005:15:28:53 +0000] Full reload complete.
E [22/Nov/2005:15:28:53 +0000] StartListening: Unable to bind socket
for address c0a80102:631 - A
I [22/Nov/2005:15:29:41 +0000] Loaded configuration file
"/etc/cups/cupsd.conf"
I [22/Nov/2005:15:29:41 +0000] Configured for up to 100 clients.
I [22/Nov/2005:15:29:41 +0000] Allowing up to 100 client connections
per host.
I [22/Nov/2005:15:29:41 +0000] Full reload is required.
I [22/Nov/2005:15:29:41 +0000] LoadPPDs: Read
"/var/lib/cups/ppds....

[Kenshi Muto (kmuto)]

severity 340314 important
thanks

At Tue, 22 Nov 2005 16:59:06 +0000,
Richard Ibbotson wrote:
> Subject: cups starts and then stops after 15 seconds
> Package: Cupsys
> Version: 1.1.23-12
> Severity: grave
> Justification: renders package unusable
>
> *** Please type your report below this line ***
>
> Cupsys 1.1.23-12. Tried to use an earlier version of cupsys and that
> didn't work. A version from Feb 2005 works fine. Printer goes
> offline after 15 seconds of being configured with the 1.1.23-12
> version. Samsung ML-1510. kcmprintmgr 3.4.2 detects the printer.
> USB is working fine. USB scanner working on the same system. No
> logs due to failure of cupsys to initialise. Also, get this more
> often than cups starting in the firt place..

> E [22/Nov/2005:15:29:42 +0000] StartListening: Unable to bind socket
> for address c0a80102:631 - A

It looks IPP port 631 for CUPS is bound by other application or cupsd
couldn't be stopped correctly.
Please check who binds a port by using lsof, such as 'lsof -i TCP:631'.

Thanks,
--
Kenshi Muto
<email address hidden>

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 23 Nov 2005 13:45:12 +0900
From: Kenshi Muto <email address hidden>
To: Richard Ibbotson <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: [Pkg-cups-devel] Bug#340314: Cups starts and then stops after 15 seconds

severity 340314 important
thanks

At Tue, 22 Nov 2005 16:59:06 +0000,
Richard Ibbotson wrote:
> Subject: cups starts and then stops after 15 seconds
> Package: Cupsys
> Version: 1.1.23-12
> Severity: grave
> Justification: renders package unusable
>
> *** Please type your report below this line ***
>
> Cupsys 1.1.23-12. Tried to use an earlier version of cupsys and that
> didn't work. A version from Feb 2005 works fine. Printer goes
> offline after 15 seconds of being configured with the 1.1.23-12
> version. Samsung ML-1510. kcmprintmgr 3.4.2 detects the printer.
> USB is working fine. USB scanner working on the same system. No
> logs due to failure of cupsys to initialise. Also, get this more
> often than cups starting in the firt place..

> E [22/Nov/2005:15:29:42 +0000] StartListening: Unable to bind socket
> for address c0a80102:631 - A

It looks IPP port 631 for CUPS is bound by other application or cupsd
couldn't be stopped correctly.
Please check who binds a port by using lsof, such as 'lsof -i TCP:631'.

Thanks,
--
Kenshi Muto
<email address hidden>

[Richard Ibbotson (richard-sheflug)]

" It looks IPP port 631 for CUPS is bound by other application or
cupsd couldn't be stopped correctly. Please check who binds a port by
using lsof, such as 'lsof -i TCP:631'. "

# /etc/init.d/cups restart
cupsd: Child exited with status 98!
cups: unable to restart scheduler.
# lsof -i TCP:631
#
^^^^^^^^
nothing happens !

Nothing happens. I have also tried to compile and install cups 1.2.2
from source and the same error message comes up on the screen.

# /etc/init.d/cupsys restart
Restarting Common Unix Printing System: cupsdcupsd: Child exited with
status 98!
#

Richard

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 30 Nov 2005 11:16:43 +0000
From: Richard Ibbotson <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Bug#340314: [Pkg-cups-devel] Bug#340314: Cups starts and thenstops after 15 seconds

" It looks IPP port 631 for CUPS is bound by other application or
cupsd couldn't be stopped correctly. Please check who binds a port by
using lsof, such as 'lsof -i TCP:631'. "

# /etc/init.d/cups restart
cupsd: Child exited with status 98!
cups: unable to restart scheduler.
# lsof -i TCP:631
#
^^^^^^^^
nothing happens !

Nothing happens. I have also tried to compile and install cups 1.2.2
from source and the same error message comes up on the screen.

# /etc/init.d/cupsys restart
Restarting Common Unix Printing System: cupsdcupsd: Child exited with
status 98!
#

Richard

[Jonathan Guthrie (jguthrie)]

I get the same symptoms after the update I just installed. (1.1.23-13)
I used the lsof command to check for other listeners on the socket and
found nothing. Before I searched for the defect, I also tried to use
netstat to check for that (because I assumed that the socket was in
close-wait-state, actually, and I wanted to see if that state had been
cleared before trying it again) and also found nothing. There is no
process listening on that socket.

I also assumed that it was because I specified only the socket number
to listen on and used dpkg-reconfigure to use both "localhost" and the
ip address of eth0, then just the address of eth0, then just localhost.
That did not alter the behavior. I also turned off the polling for
pinters, and that did not alter the behavior. I also altered the
configuration to allow printing only from localhost, but that did not
alter the behavior.

I also checked for print jobs that had been spooled, but hadn't been
printed (thinking that there was perhaps a problem with startup when
spool files existed) and found none.

On whim, I checked /etc/cupsd.conf and found that there was still an
active "Ports" line. Commenting-it out fixes the problem. It appears
to me to be the result of duplicating the ports line in /etc/cupsd.conf
and /etc/cups/cups.d/ports.conf
--
Jonathan Guthrie (<email address hidden>)
Sto pro veritate

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 13 Dec 2005 19:05:48 -0600
From: Jonathan Guthrie <email address hidden>
To: <email address hidden>
Subject: Bug#340313: Cups starts and then stops

I get the same symptoms after the update I just installed. (1.1.23-13)
I used the lsof command to check for other listeners on the socket and
found nothing. Before I searched for the defect, I also tried to use
netstat to check for that (because I assumed that the socket was in
close-wait-state, actually, and I wanted to see if that state had been
cleared before trying it again) and also found nothing. There is no
process listening on that socket.

I also assumed that it was because I specified only the socket number
to listen on and used dpkg-reconfigure to use both "localhost" and the
ip address of eth0, then just the address of eth0, then just localhost.
That did not alter the behavior. I also turned off the polling for
pinters, and that did not alter the behavior. I also altered the
configuration to allow printing only from localhost, but that did not
alter the behavior.

I also checked for print jobs that had been spooled, but hadn't been
printed (thinking that there was perhaps a problem with startup when
spool files existed) and found none.

On whim, I checked /etc/cupsd.conf and found that there was still an
active "Ports" line. Commenting-it out fixes the problem. It appears
to me to be the result of duplicating the ports line in /etc/cupsd.conf
and /etc/cups/cups.d/ports.conf
--
Jonathan Guthrie (<email address hidden>)
Sto pro veritate

[Matt Zimmerman (mdz)]

Martin, perhaps your improvements to the init script would have addressed this problem?

[Martin Pitt (pitti)]

cups 1.2rc2 no longer stumbles over duplicate Ports entries in the configuration.

[Kenshi Muto (kmuto)]

# Automatically generated email from bts, devscripts version 2.9.20
merge 319602 340314

[Kenshi Muto (kmuto)]

Version: 1.1.23-15
tags 340314 + fixed
tags 319602 + fixed
thanks

1.1.23-15 fixed the code around writing buggy Ports/Listen.
FYI, 1.2.1-3 and later have reverted to use single cupsd.conf file and
dropped debconf interface.

Thanks,
--
Kenshi Muto
<email address hidden>