From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
I have a network of 24 computers in a University Lab, which all print
through another instance of CUPS on a server. About one of these
computers a day will stop printing.
Restarting CUPS on the lab workstation does solve the problem, but
does not keep it from happening again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I have not figured out how to forcibly reproduce the error, but it
reoccurs every once in a while.
I [11/Feb/2004:11:00:14 -0500] Listening to 7f000001:631
I [11/Feb/2004:11:00:14 -0500] Loaded configuration file
I [11/Feb/2004:11:00:14 -0500] Configured for up to 100 clients.
I [11/Feb/2004:11:00:14 -0500] Allowing up to 100 client connections
I [11/Feb/2004:11:00:14 -0500] Full reload is required.
I [11/Feb/2004:11:00:15 -0500] LoadPPDs: Read "/etc/cups/ppds.dat", 13
I [11/Feb/2004:11:00:15 -0500] LoadPPDs: No new or changed PPDs...
I [11/Feb/2004:11:00:15 -0500] Full reload complete.
E [11/Feb/2004:11:00:15 -0500] StartListening: Unable to bind socket -
Address already in use.
Apply the test updates for redhat-config-printer:
Does the problem still occur after doing that?
Same problem for me - random crashes which leave nothing in the
logs. However this is with Red Hat 9. I'm compiling the Fedora RPM
(without DBUS) to see if the problem goes away with this.
David: if there is nothing in the logs, it is a *different* problem.
Or do you see the 'Unable to bind socket' message?
Sorry - you're right, different problem. It just dies, and logs
nothing in /var/log/cups/* or /var/log/messages. No pattern to it as
far as I can see. All clients are using CUPS or Adobe postscript
I won't bother to file a new bug if the Fedora RPM works.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to "CURRENTRELEASE", however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thanks in advance.