[olug] Jon Larsen, Thanks for the attempt (CUPS problems SuSE 9.1)
Terence Bradshaw
angrypuppy at tconl.com
Mon Aug 16 14:43:50 UTC 2004
On Monday 16 August 2004 09:09, Jon H. Larsen wrote:
> On Wed, 4 Aug 2004, Jon H. Larsen wrote:
<snip>
>
> Anyone have any suggestions as to why CUPS won't bind to 631 in SuSE 9.1?
>
> Jon L.
I found the following thread... worth checking.
I tried to include the URL, but it just wasn't working out...sorry for the
length of this reply, but I wanted to include the entire thread.
From: Tim Connors (tconnors+linuxdebianuser1090655061 at astro.swin.edu.au)
Subject: Cups can't start with error 98
View this article only
Newsgroups: linux.debian.user
Date: 2004-07-24 01:10:08 PST
I haven't used cups in a while, and tried to today. It fails at
startup, with error code 98:
E [24/Jul/2004:17:39:06 +1000] StartListening: Unable to bind socket for
address c0a80102:631 - Address already in use.
c0a80102==192.168.1.2==the box I am trying to start cups from
That was fair enough the first time, because somehow lpr was installed
at the same time, so I stop and removed it. The error stays, and I
have done a netstat -au, and found nothing is bound to port 631. lsof
agrees with me. There is no lp* or cups* processes running.
I googled, and found that someone found a problem with nfs taking the
port randomly, so I stopped the nfs processes.
I waited 5 minutes, because I rememeber something about the kernel
sometimes keeping ports open for a little while despite the exit of
the owner process.
I partially upgraded sid - so now cups* and libcupsys are up to date.
I really can't work out why I keep getting this message.
And ideas?
--
TimC -- http://astronomy.swin.edu.au/staff/tconnors/
My cats are forbidden from walking on my computer keyboard on the desk
when I'm asdfjjhhkl;ljfd.;oier' puyykmm4hbdm9lo9j USING IT.
--
To UNSUBSCRIBE, email to debian-user-REQUEST at lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
Post a follow-up to this message
Message 2 in thread
From: CW Harris (charris at rtcmarketing.com)
Subject: Re: Cups can't start with error 98
View this article only
Newsgroups: linux.debian.user
Date: 2004-07-26 16:00:14 PST
I don't see any answers so I'll try (not really good with CUPS though):
On Sat, Jul 24, 2004 at 05:52:29PM +1000, Tim Connors wrote:
> I haven't used cups in a while, and tried to today. It fails at
> startup, with error code 98:
> E [24/Jul/2004:17:39:06 +1000] StartListening: Unable to bind socket for
address c0a80102:631 - Address already in use.
>
> c0a80102==192.168.1.2==the box I am trying to start cups from
>
> That was fair enough the first time, because somehow lpr was installed
> at the same time, so I stop and removed it. The error stays, and I
> have done a netstat -au, and found nothing is bound to port 631. lsof
What about tcp (netstat -at)?
> agrees with me. There is no lp* or cups* processes running.
>
> I googled, and found that someone found a problem with nfs taking the
> port randomly, so I stopped the nfs processes.
A quick look and I don't see a similar bug (1 unreproducible from a year
ago is all). Any more info if you set LogLevel to "debug" in
/etc/cups/cupsd.conf?
>
> I waited 5 minutes, because I rememeber something about the kernel
> sometimes keeping ports open for a little while despite the exit of
> the owner process.
>
> I partially upgraded sid - so now cups* and libcupsys are up to date.
Sorry, I don't have any current experience with sid.
>
> I really can't work out why I keep getting this message.
>
> And ideas?
>
> --
> TimC -- http://astronomy.swin.edu.au/staff/tconnors/
> My cats are forbidden from walking on my computer keyboard on the desk
> when I'm asdfjjhhkl;ljfd.;oier' puyykmm4hbdm9lo9j USING IT.
^^^^^^^^^^^^^^^^^^^^^^^^
Just like a cat. :->
--
Chris Harris <charris at rtcmarketing.com>
-------------------------------------------
GNU/Linux --- The best things in life are free.
--
To UNSUBSCRIBE, email to debian-user-REQUEST at lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
Post a follow-up to this message
Message 3 in thread
From: Tim Connors (tconnors+linuxdebianuser1090894093 at astro.swin.edu.au)
Subject: Re: Cups can't start with error 98
View this article only
Newsgroups: linux.debian.user
Date: 2004-07-26 19:30:11 PST
CW Harris <charris at rtcmarketing.com> said on Mon, 26 Jul 2004 16:56:12 -0600:
> I don't see any answers so I'll try (not really good with CUPS though):
>
> On Sat, Jul 24, 2004 at 05:52:29PM +1000, Tim Connors wrote:
> > I haven't used cups in a while, and tried to today. It fails at
> > startup, with error code 98:
> > E [24/Jul/2004:17:39:06 +1000] StartListening: Unable to bind socket for
address c0a80102:631 - Address already in use.
> >
> > c0a80102==192.168.1.2==the box I am trying to start cups from
> >
> > That was fair enough the first time, because somehow lpr was installed
> > at the same time, so I stop and removed it. The error stays, and I
> > have done a netstat -au, and found nothing is bound to port 631. lsof
>
> What about tcp (netstat -at)?
Oops, I should have read the manpage rather than asking someone else.
But nothing there, either.
> > agrees with me. There is no lp* or cups* processes running.
> >
> > I googled, and found that someone found a problem with nfs taking the
> > port randomly, so I stopped the nfs processes.
>
> A quick look and I don't see a similar bug (1 unreproducible from a year
> ago is all). Any more info if you set LogLevel to "debug" in
> /etc/cups/cupsd.conf?
Nothing interesting, but I did notice one more line of output that I
didn't before:
I [27/Jul/2004:12:04:46 +1000] Listening to 0:631
I [27/Jul/2004:12:04:46 +1000] Listening to c0a80102:631
I [27/Jul/2004:12:04:46 +1000] Sending browsing info to c0a801ff:631
I [27/Jul/2004:12:04:46 +1000] Loaded configuration file
"/etc/cups/cupsd.conf"
I [27/Jul/2004:12:04:46 +1000] Configured for up to 100 clients.
I [27/Jul/2004:12:04:46 +1000] Allowing up to 100 client connections per host.
I [27/Jul/2004:12:04:46 +1000] Full reload is required.
I [27/Jul/2004:12:04:47 +1000] LoadPPDs: Read "/etc/cups/ppds.dat", 2402
PPDs...
I [27/Jul/2004:12:04:49 +1000] LoadPPDs: Wrote "/etc/cups/ppds.dat", 2402
PPDs...
I [27/Jul/2004:12:04:49 +1000] Full reload complete.
E [27/Jul/2004:12:04:49 +1000] StartListening: Unable to bind socket for
address c0a80102:631 - Addre
ss already in use.
The start line says listening. Has it opened the port for listen yet,
or does it defer the actual open until the E line, where it fails? Or
is it indeed trying to open the port twice?
--
TimC -- http://astronomy.swin.edu.au/staff/tconnors/
Weeks of coding can save you hours of planning.
--
To UNSUBSCRIBE, email to debian-user-REQUEST at lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
Post a follow-up to this message
Message 4 in thread
From: CW Harris (charris at rtcmarketing.com)
Subject: Re: Cups can't start with error 98
View this article only
Newsgroups: linux.debian.user
Date: 2004-07-27 10:30:09 PST
I believe I'm starting to know more about CUPS than I really want to.
If the following solves your problem, we both need to RTFM better ;-)
On Tue, Jul 27, 2004 at 12:09:56PM +1000, Tim Connors wrote:
[...]
> Nothing interesting, but I did notice one more line of output that I
> didn't before:
>
> I [27/Jul/2004:12:04:46 +1000] Listening to 0:631
> I [27/Jul/2004:12:04:46 +1000] Listening to c0a80102:631
I believe this is a configuration error in your cupsd.conf
I can replicate this error with the following:
Port 631
Listen 192.168.1.2:631
I think the Port directive binds to *any* address on 631. The second
directive tries to bind 192.168.1.2 on port 631, but that is already
taken with the *any* address on 631. So I *think* you can either let it
bind to *any* address and not have a listen directive. Or remove the
port directive and list the address/ports you want it to listen on (you
may need to allow it to listen on 127.0.0.1)
> I [27/Jul/2004:12:04:46 +1000] Sending browsing info to c0a801ff:631
> I [27/Jul/2004:12:04:46 +1000] Loaded configuration file
"/etc/cups/cupsd.conf"
> I [27/Jul/2004:12:04:46 +1000] Configured for up to 100 clients.
> I [27/Jul/2004:12:04:46 +1000] Allowing up to 100 client connections per
host.
> I [27/Jul/2004:12:04:46 +1000] Full reload is required.
> I [27/Jul/2004:12:04:47 +1000] LoadPPDs: Read "/etc/cups/ppds.dat", 2402
PPDs...
> I [27/Jul/2004:12:04:49 +1000] LoadPPDs: Wrote "/etc/cups/ppds.dat", 2402
PPDs...
> I [27/Jul/2004:12:04:49 +1000] Full reload complete.
> E [27/Jul/2004:12:04:49 +1000] StartListening: Unable to bind socket for
address c0a80102:631 - Addre
> ss already in use.
For what it's worth, a successful start in my logs looks the same up to
the "StartListening: Unable ..."
>
> The start line says listening. Has it opened the port for listen yet,
> or does it defer the actual open until the E line, where it fails? Or
> is it indeed trying to open the port twice?
The latter I believe.
HTH
--
Chris Harris <charris at rtcmarketing.com>
-------------------------------------------
GNU/Linux --- The best things in life are free.
--
To UNSUBSCRIBE, email to debian-user-REQUEST at lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
Post a follow-up to this message
Message 5 in thread
From: Tim Connors (tconnors+linuxdebianuser1090983735 at astro.swin.edu.au)
Subject: Re: Cups can't start with error 98
View this article only
Newsgroups: linux.debian.user
Date: 2004-07-27 20:30:07 PST
CW Harris <charris at rtcmarketing.com> said on Tue, 27 Jul 2004 10:56:44 -0600:
> I believe I'm starting to know more about CUPS than I really want to.
> If the following solves your problem, we both need to RTFM better ;-)
>
> On Tue, Jul 27, 2004 at 12:09:56PM +1000, Tim Connors wrote:
> [...]
> > Nothing interesting, but I did notice one more line of output that I
> > didn't before:
> >
> > I [27/Jul/2004:12:04:46 +1000] Listening to 0:631
> > I [27/Jul/2004:12:04:46 +1000] Listening to c0a80102:631
>
> I believe this is a configuration error in your cupsd.conf
> I can replicate this error with the following:
> Port 631
> Listen 192.168.1.2:631
>
> I think the Port directive binds to *any* address on 631. The second
> directive tries to bind 192.168.1.2 on port 631, but that is already
> taken with the *any* address on 631. So I *think* you can either let it
> bind to *any* address and not have a listen directive. Or remove the
> port directive and list the address/ports you want it to listen on (you
> may need to allow it to listen on 127.0.0.1)
Aha. I wonder when that LISTEN line crept in? Cups was working at some
point in time, then I went and screwed it. :)
Thanks.
--
TimC -- http://astronomy.swin.edu.au/staff/tconnors/
PUBLIC NOTICE AS REQUIRED BY LAW: Any Use of This Product, in Any Manner
Whatsoever, Will Increase the Amount of Disorder in the Universe. Although No
Liability Is Implied Herein, the Consumer Is Warned That This Process Will
Ultimately Lead to the Heat Death of the Universe.
--
To UNSUBSCRIBE, email to debian-user-REQUEST at lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
Post a follow-up to this message
More information about the OLUG
mailing list