problem with cups

[Antoine Defontaine]

When I changed all 631 occurences to become 8631 in cupsd.conf, cupsd could 
start indeed. There is no log problem anymore. It seems to be the problem.

But, tell me if I am wrong, I will have the change them back to 631 (and 
consequently find out the conflicting one in NIS) to be able to print again. 
If so, I will see with the network administrator on Monday. If it should 
work with 8631 (but I don't thing so), I still have a problem since it is 
not working.

Just let me know.

Anyway, thanks very much for your help.
Antoine

>From: "Kurt Pfeifle" <kpfeifle at danka.de>
>Reply-To: "For users and developers of KDEPrint, the KDE 
>printingarchitecture" <kde-print at mail.kde.org>
>To: kde-print at mail.kde.org
>Subject: Re: problem with cups
>Date: Fri, 02 May 2003 14:51:00 +0200
>
>Antoine Defontaine wrote:
>>Hi,
>>
>>I am using a Linux machine with Suse 8.1 distribution and kde 3.0.
>>Up to few days ago, I had no problem for printing. I used to print on
>>network printers using kprinter.
>>I have made all the installations using yast2 and rpms.
>>
>>But cupsd does not start anymore now.
>>I have tried to launch it manually (as root) but I got the following error
>>message:
>>"cupsd: child exited with status 98!".
>>Using yast2, i can not access to the printer configuration panel. It tries
>>to call for lpq which crashes (i have to kill it manually) twice and
>>afterwards (after two successive kills of lpq) it says:
>>"the cups daemon has stopped during installation".
>>If I suppress cups programs (again with yast2), I can acces to the printer
>>configuration panel. It asks what I'd like to do and I can redo the
>>printer installation as I did at the beginning (it reinstalled cups) but
>>with no effect; it is still defective.
>>Another point that may be of interest (i don't know but it may have an
>>influence, I am far from being a expert), we have set up a small linux
>>network for 5/6 machines the NIS stuff and NFS stuff and some centralised
>>utilities. Can this be a cause (i have heard there may be something to
>>change in the cupsd.conf file but I don't knows what)?
>>Anyway, I may have done something wrong since it used to work but it
>>doesn't anymore.
>>
>>Can u help?
>>Cheers
>>Antoine
>>
>>I am using version 1.15-46 of cups.
>>Here is the /var/log/cups/error_log message i got:
>>
>>I [02/May/2003:11:15:35 +0200] Listening to 0:631
>>I [02/May/2003:11:15:35 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:15:48 +0200] LoadPPDs: Wrote "/etc/cups/ppds.dat", 1739
>>PPDs...
>>I [02/May/2003:11:15:53 +0200] Added remote printer "lw8"...
>>I [02/May/2003:11:15:54 +0200] Added remote printer "lw5recto"...
>>I [02/May/2003:11:16:00 +0200] Added remote printer "deskjet_6122"...
>>I [02/May/2003:11:16:07 +0200] Added remote printer "lw4"...
>>I [02/May/2003:11:16:16 +0200] Added remote printer "lw5"...
>>E [02/May/2003:11:16:16 +0200] Scheduler shutting down due to SIGTERM.
>>I [02/May/2003:11:16:16 +0200] Listening to 0:631
>>I [02/May/2003:11:16:16 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:16:16 +0200] LoadPPDs: Read "/etc/cups/ppds.dat", 1739
>>PPDs...
>>I [02/May/2003:11:16:16 +0200] LoadPPDs: No new or changed PPDs...
>>I [02/May/2003:11:16:17 +0200] Listening to 0:631
>>I [02/May/2003:11:16:17 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:16:17 +0200] LoadPPDs: Read "/etc/cups/ppds.dat", 1739
>>PPDs...
>>I [02/May/2003:11:16:17 +0200] LoadPPDs: No new or changed PPDs...
>>E [02/May/2003:11:16:17 +0200] Scheduler shutting down due to SIGTERM.
>>I [02/May/2003:11:17:04 +0200] Listening to 0:631
>>I [02/May/2003:11:17:04 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:17:04 +0200] LoadPPDs: Read "/etc/cups/ppds.dat", 1739
>>PPDs...
>>I [02/May/2003:11:17:04 +0200] LoadPPDs: No new or changed PPDs...
>>I [02/May/2003:11:17:09 +0200] Added remote printer "lw4"...
>>I [02/May/2003:11:17:18 +0200] Added remote printer "lw5"...
>>I [02/May/2003:11:17:26 +0200] Added remote printer "lw8"...
>>I [02/May/2003:11:17:27 +0200] Added remote printer "lw5recto"...
>>I [02/May/2003:11:17:33 +0200] Added remote printer "deskjet_6122"...
>>E [02/May/2003:11:18:19 +0200] Scheduler shutting down due to SIGTERM.
>>I [02/May/2003:11:18:19 +0200] Listening to 0:631
>>I [02/May/2003:11:18:19 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:18:19 +0200] LoadPPDs: Read "/etc/cups/ppds.dat", 1739
>>PPDs...
>>I [02/May/2003:11:18:19 +0200] LoadPPDs: No new or changed PPDs...
>>I [02/May/2003:11:18:20 +0200] Added remote printer "lw5"...
>>I [02/May/2003:11:18:20 +0200] Listening to 0:631
>>I [02/May/2003:11:18:20 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:18:20 +0200] LoadPPDs: Read "/etc/cups/ppds.dat", 1739
>>PPDs...
>>I [02/May/2003:11:18:20 +0200] LoadPPDs: No new or changed PPDs...
>>E [02/May/2003:11:18:22 +0200] Scheduler shutting down due to SIGTERM.
>>I [02/May/2003:11:18:22 +0200] Listening to 0:631
>>I [02/May/2003:11:18:22 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:18:22 +0200] LoadPPDs: Read "/etc/cups/ppds.dat", 1739 
>>PPDs...
>
>BTW -- this is all "LogLevel info". Change to "LogLevel debug" in 
>cupsd.conf
>if you want to track the problem down....
>
>>I [02/May/2003:11:18:22 +0200] LoadPPDs: No new or changed PPDs...
>>I [02/May/2003:11:18:28 +0200] Added remote printer "lw8"...
>>I [02/May/2003:11:18:29 +0200] Added remote printer "lw5recto"...
>>I [02/May/2003:11:18:35 +0200] Added remote printer "deskjet_6122"...
>>E [02/May/2003:11:18:38 +0200] Scheduler shutting down due to SIGTERM.
>>I [02/May/2003:11:20:02 +0200] Listening to 0:631
>>I [02/May/2003:11:20:02 +0200] Configured for up to 100 clients.
>>I [02/May/2003:11:20:03 +0200] LoadPPDs: Read "/etc/cups/ppds.dat", 1739
>>PPDs...
>>I [02/May/2003:11:20:05 +0200] LoadPPDs: No new or changed PPDs...
>>E [02/May/2003:11:20:06 +0200] StartListening: Unable to bind socket - 
>>Address already in use.
>
>Here is the problem. Another program seems to have stolen "well known
>port" 631 from underneath CUPS's a..
>
>To verify the problem and its cause, edit all occurences of "631" to
>become "8631" in cupsd.conf and try to restart it from the command line.
>
>Does cupsd start now?
>
>If yes try to hunt down the guilty one of your NIS programs...
>
>Cheers,
>Kurt
>
>_______________________________________________
>kde-print mailing list
>kde-print at mail.kde.org
>http://mail.kde.org/mailman/listinfo/kde-print


_________________________________________________________________
MSN Search, le moteur de recherche qui pense comme vous !  
http://search.msn.fr/worldwide.asp