Hi, I still have not been able to resolve the print problem I have been having. I believe it is probably a combination of the susepro 9.1 and samba 3.0.9-2.6-suse interactions as the two systems on the lan have had the same problem of losing their printer and then not being able to regenerate them. I tried to access cups via //localhost:631/ with no success. I have tried a number of approaches: upgraded kde to v3.4; taken the unit out of the lan but nothing works so I am hoping somebody out there will have suggestion[s] which will solve the problem. Following is a copy of the /var/log/cups/errorlog: Listening to 0:631 E [31/Jul/2005:18:40:00 -0400] Unknown Location directive # on line 811. I [31/Jul/2005:18:40:00 -0400] Loaded configuration file "/etc/cups/cupsd.conf" I [31/Jul/2005:18:40:00 -0400] Configured for up to 100 clients. I [31/Jul/2005:18:40:00 -0400] Allowing up to 100 client connections per host. I [31/Jul/2005:18:40:00 -0400] Full reload is required. I [31/Jul/2005:18:40:03 -0400] LoadPPDs: Read "/etc/cups/ppds.dat", 3592 PPDs... I [31/Jul/2005:18:40:04 -0400] LoadPPDs: No new or changed PPDs... I [31/Jul/2005:18:40:04 -0400] Full reload complete. E [31/Jul/2005:18:40:04 -0400] StartListening: Unable to bind socket - Address already in use. Can someone tell me what the last line means? It seems to me to have the key? Thanks for your input. -- Cheers, Serge [Naggar Consulting]
On Monday 01 August 2005 03:25, Serge Naggar wrote:
E [31/Jul/2005:18:40:04 -0400] StartListening: Unable to bind socket - Address already in use.
Can someone tell me what the last line means? It seems to me to have the key?
Maybe you have some other program configured to listen on one of the cups ports. netstat -anp (as root) (I have erased the irrelevant stuff.) Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 5722/cupsd udp 0 0 0.0.0.0:631 0.0.0.0:* 5722/cupsd
Hello, On Monday 01 August 2005 03:25, Serge Naggar wrote:
E [31/Jul/2005:18:40:04 -0400] StartListening: Unable to bind socket - Address already in use.
Some other program or service has posr 631 already in use. It may happen that the other program has finished so that cupsd would start fine later. It may happen that the other sevice still has the port 631 in use so that you must stop the other sevice, start cups and then start the other sevice. The reason is that the other program or service simply uses any free port and by accident it may use the IPP port. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
Hi Johannes and others, Your analysis made a lot of sense to me and I have been trying to see where port 631 has been used: I found that I had added port 631 to the firewall and the /etc/samba/smb.conf I eliminated both and tried to start cupsd ... the result is not clear: http://localhost:631/ goes howhere
west:/home/scn # cupsd cupsd: Child exited with status 98!
I am not sure what status 98 and child mean? I also tried to get the yast printer configuation tool to complete but it is still stalling in the `load current settings´ phase of the printer definition. Is there a command/function which will let me find out where/how port 631 is being used? I also feel, no proof, that the problem has to do with the interaction of samba3.0.9-2.6-suse and susepro9.1 because the printer-loss and yast-printer-definition stall occurred with both machines - each has a different printer. Both were in samba. Any thoughts? I look forward to resolving this problem. On Mon, 2005-08-01 at 08:22, Johannes Meixner wrote:
Hello,
On Monday 01 August 2005 03:25, Serge Naggar wrote:
E [31/Jul/2005:18:40:04 -0400] StartListening: Unable to bind socket - Address already in use.
Some other program or service has posr 631 already in use.
It may happen that the other program has finished so that cupsd would start fine later.
It may happen that the other sevice still has the port 631 in use so that you must stop the other sevice, start cups and then start the other sevice.
The reason is that the other program or service simply uses any free port and by accident it may use the IPP port.
Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/ -- Cheers, Serge [Naggar Consulting]
Hello How do install counter strike for suse 9.3? Can you help me? --------------------------------- Yahoo! kullaniyor musunuz? Istenmeyen postadan biktiniz mi? Istenmeyen postadan en iyi korunma Yahoo! Posta’da http://tr.mail.yahoo.com
On Thu, 2005-08-04 at 12:10 -0400, Serge Naggar wrote:
Hi Johannes and others, Your analysis made a lot of sense to me and I have been trying to see where port 631 has been used:
I found that I had added port 631 to the firewall and the /etc/samba/smb.conf
I eliminated both and tried to start cupsd ... the result is not clear:
http://localhost:631/ goes howhere
west:/home/scn # cupsd cupsd: Child exited with status 98!
I am not sure what status 98 and child mean?
I also tried to get the yast printer configuation tool to complete but it is still stalling in the `load current settings´ phase of the printer definition.
Is there a command/function which will let me find out where/how port 631 is being used?
I also feel, no proof, that the problem has to do with the interaction of samba3.0.9-2.6-suse and susepro9.1 because the printer-loss and yast-printer-definition stall occurred with both machines - each has a different printer. Both were in samba. Any thoughts? I look forward to resolving this problem. What does the command (as root) kcmshell printmgr show? Does it allow you to configure a printer? Also, remember that SuSE 9.1 required that you set a cups admin passwd with lppasswd -g sys root in order to modify settings.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Thursday 04 August 2005 19:10, Serge Naggar wrote:
Hi Johannes and others, Your analysis made a lot of sense to me and I have been trying to see where port 631 has been used:
I found that I had added port 631 to the firewall and the /etc/samba/smb.conf
How about you stop the firewall and samba and see if cups starts as it should?
On Sun, 2005-07-31 at 20:25 -0400, Serge Naggar wrote:
I tried to access cups via //localhost:631/ with no success.
Have you created a cups user/passwd? If not, then look at man lppasswd.
--
Arun Khan
participants (6)
-
Arun Khan -
Johannes Meixner -
Ken Schneider -
Serge Naggar -
Silviu Marin-Caea -
Tora TORAMAN