Bug 106018

Summary:	cupsd won't start
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Glenn Holmer <gholmer>
Component:	Printing	Assignee:	Johannes Meixner <jsmeix>
Status:	RESOLVED INVALID	QA Contact:	Johannes Meixner <jsmeix>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 2
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Glenn Holmer 2005-08-20 16:48:06 UTC

YaST printer config hangs during "load current settings".
I still get this after re-installing the CUPS packages by updating from gwdg:

root@orac:~ # rccups start
Starting cupsd                                                       done
root@orac:~ # cupsd: Child exited with status 98!

root@orac:~ # rccups status
Checking for cupsd:                                                  unused
root@orac:~ # cupsd -f
unable to open /var/run/hpiod.port: No such file or directory:
prnt/hpijs/hplip_api.c 75
unable to connect hpiod socket 50000: Connection refused: prnt/hpijs/hplip_api.c 693
root@orac:~ #

Comment 1 Johannes Meixner 2005-08-22 07:32:09 UTC

The hplip message is normal when you doen't have the service "hplip"
up and running which is only needed for HP all-in-one devices, see
http://portal.suse.com/sdb/en/2005/02/jsmeix_print-einrichten-93.html
This doesn't cause cupsd to abort.

I need the complete cups error_log file to find out the real reason, see
http://portal.suse.com/sdb/en/2004/05/jsmeix_print-cups-in-a-nutshell.html
"If problems are encountered:"
how to provide relevant debugging information:
---------------------------------------------------------------------------
1. Set the "LogLevel debug" in /etc/cups/cupsd.conf.
2. Stop cupsd.
3. Move /var/log/cups/error_log* to another location (or delete it)
   in order to avoid having to search through gigantic log files.
4. Start cupsd.
5. Retry the action leading to the problem.
6. Now /var/log/cups/error_log* contains many messages
   that are useful for troubleshooting. 
---------------------------------------------------------------------------

Comment 2 Glenn Holmer 2005-08-22 13:49:09 UTC

cups came up normally this morning when the machine was started (unable to
reproduce).  I'll watch it closely in beta 3 and attach the above logs if it
happens again.

Comment 3 Johannes Meixner 2005-08-22 14:19:16 UTC

If it fails only sometimes, it is often this reason:
"Sometimes" another service which searches for an arbitrary
free port below 1024 grabs the IPP port 631 (and a bit later it may
have released it) and in CUPS's error_log you will find a message like
"Starting Listening : unable to bind socket, address already in use."

In this case the other service is the culprit and this other service
would have to be fixed.

Comment 4 Johannes Meixner 2005-08-25 14:31:42 UTC

I assume it was such another service.
Set it to INVALID regarding CUPS.
Please submit a new bug regarding the other service
if you found out which other service grabbed the IPP port.