Re: Cups can't start with error 98
CW Harris <charris@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.
Reply to: