[Pkg-cups-devel] Bug#343279: new cupsys fails to start,
claiming can't bind port 631
Steve Langasek
vorlon at debian.org
Wed Dec 14 06:42:22 UTC 2005
severity 343279 important
thanks
On Tue, Dec 13, 2005 at 11:19:48PM -0600, Rodney Gordon II wrote:
> Package: cupsys
> Version: 1.1.23-13
> Severity: grave
> Justification: renders package unusable
> The latest cupsys update broke the port binding for me:
> root at ghreen { ~ }$ /etc/init.d/cupsys start
> Starting Common Unix Printing System: cupsd
> cupsd: Child exited with status 98!
> /var/log/cups/error_log:
> E [13/Dec/2005:23:16:09 -0600] StartListening: Unable to bind socket for
> address 00000000:631 - Address already in use.
> "lsof | grep 631" shows nothing binded to 631. I have checked and tried
> to open the port myself, and I am sure it's open. I have also rebooted.
This probably means that the port is opened by an NFS-related kernel thread
because portmap (incorrectly) assigns the port there. You can confirm this
by stopping the NFS server (/etc/init.d/nfs-kernel-server and
/etc/init.d/nfs-common) and starting cupsys again.
This is not a bug in cupsys, but a systemic problem with portmap's random
port assignment process.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon at debian.org http://www.debian.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cups-devel/attachments/20051213/a346b24a/attachment.pgp
More information about the Pkg-cups-devel
mailing list