Re: [expert] what to do when "Socket in use"?
On Tue, 2002-06-25 at 18:53, Jeremy Mereness wrote: > > Thenks for the reply. It only happens to me when I print over SAMBA. Printing > locally is fine. > > I will take a look thru the cupsd.conf file as suggested. Do you have any > advice how to investigate a "could not bind; socket in use" message? Such as > determine what other process is using it? > > -- j In my case, cups wouldn't start at all so I don't think we had the same situation. My guess it that it would be your smb.conf file. If you want to see what files are connecting to what networking ports use the following command: # lsof -i Actually, even better is Todd's suggestion in a different post: # netstat -ltunp -- /curtis ><> Mandrake Linux 8.3 (cooker) Kernel Version 2.4.18-20mdk Uptime 3 days 13 hours 2 minutes Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] what to do when "Socket in use"?
On Sun, 2002-06-23 at 16:54, Jeremy Mereness wrote: > I'm trying to print to a Windows printer over SAMBA on Mandrake 8.2. > > When I add the device, the first notable error in the CUPS error_log is > > LoadDevices: Added device "smb"... > StartListening: NumListeners=3 > StartListening: address=7f01 port=631 > Unable to bind to socket - Address already in use. > > Later on, while trying to print something, I get... > foomatic-gswrapper: gs '-dBATCH' -dSAFER' etc. etc. etc. > Unable to open initial device, quitting. > > Assuming these two events are related, what can I do about a socket > "already in use"? > > What do I do to diagnose which socket and what's locking it up? I just had this recently after an upgrade. It was due to an error in my cupsd.conf file that prevented cups from starting properly. Can you print locally? Or is it just printing over samba that doesn't work? -- /curtis ><> Mandrake Linux 8.3 (cooker) Kernel Version 2.4.18-20mdk Uptime 1 day 10 hours 32 minutes Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[expert] what to do when "Socket in use"?
I'm trying to print to a Windows printer over SAMBA on Mandrake 8.2. When I add the device, the first notable error in the CUPS error_log is LoadDevices: Added device "smb"... StartListening: NumListeners=3 StartListening: address=7f01 port=631 Unable to bind to socket - Address already in use. Later on, while trying to print something, I get... foomatic-gswrapper: gs '-dBATCH' -dSAFER' etc. etc. etc. Unable to open initial device, quitting. Assuming these two events are related, what can I do about a socket "already in use"? What do I do to diagnose which socket and what's locking it up? -- j Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com