Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Thursday 06 March 2003 02:56 am, David Whiting wrote: On Wed, Mar 05, 2003 at 01:27:43PM +, Anne Wilson wrote: It looks okay to me (i.e. no garbage characters, but it could be misconfigured without me having a clue) NETWORKING=yes FORWARD_IPV4=false DHCP_HOSTNAME=ganymede HOSTNAME=ganymede DOMAINNAME=ammp.net GATEWAY=192.168.57.1 I'm pretty sure that this has not changed for a long time though so I do not think it should be related to my cups problem. Hmm - I don't have the dhcp line, so I can't comment on that, but I have the FQDN, so I would have expected HOSTNAME=ganymede.ammp.net? I tried this and it lead to a variety of problems with applications not being able to find ganymede.ammp.net. For a long time I have some 'little' networking problems (like not being able to ping ganymede from ganymede) but things seemed to work so I figured I needed to find time to understand more about netorking ... eventually ... but that it was not a critical issue for me. Thanks. Dave Dave: Check your mail settings -- you have two To entries: [EMAIL PROTECTED] and [EMAIL PROTECTED], hence the double postings. -- cmg Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Thu, Mar 06, 2003 at 08:51:52AM -0500, Pierre Fortin wrote: On Thu, 6 Mar 2003 07:35:19 + David Whiting [EMAIL PROTECTED] wrote: [06/Mar/2003:07:17:05 +] StartListening: Unable to bind socket - Cannot assign requested address. So, something is stopping it from getting the address it wants. I also noticed that named wasn't happy either: see if anything else has port 631 with: lsof -i :631 No, nothing on 631. This was a new one for me, so I tried it with port 80 to see what the output should look like and got what appears to be sensible so it was working okay, there's nothing to report for port 631. [EMAIL PROTECTED] cups]# service named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. Check that your /etc/named.conf and /etc/rndc.conf have the same secret (key). If that's ok, you'll need to dig into your network setup... Aha! They are very obviously very different. I'll try to RTFM about how to fix this... but might need some help. Watch this space. Thanks. Dave -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Thu, Mar 06, 2003 at 08:51:52AM -0500, Pierre Fortin wrote: [EMAIL PROTECTED] cups]# service named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. Check that your /etc/named.conf and /etc/rndc.conf have the same secret (key). If that's ok, you'll need to dig into your network setup... YES! I copied the key from rndc.conf to named.conf and now: [EMAIL PROTECTED] dave]# service named status number of zones: 3 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF server is up and running I still don't have cupsd running but it is nice to have this sorted. Thanks! Dave -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Thu, Mar 06, 2003 at 10:17:02AM -0500, Carroll Grigsby wrote: Dave: Check your mail settings -- you have two To entries: [EMAIL PROTECTED] and [EMAIL PROTECTED], hence the double postings. -- cmg Oh, sorry! I only see one so didn't know this was happening...still learning. I'll fix it now. Thanks. Dave -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Tue, Mar 04, 2003 at 11:30:40PM -0800, Alan wrote: On Wed, 2003-03-05 at 01:12, David Whiting wrote: Hi, I've just upgraded from 8.2 to 9.0 (just as everyone else is getting exited about 9.1 :-) and have a printing problem. msec_find ran this morning and now cups is unable to bind to socket 631. I am not sure if this is a coincidence but I remember seeing previous posts about woes with msec. I have tried to google the error message but have not found anything that worked. I have tried assigning a higher port in /etc/cups/cups.conf but that did not work. I tried: Port 1631 Listen localhost:1631 I am running at standard level security. As I said, I recall seeing similar posts in the past but can't quite find the solution. Any ideas? This may sound unrelated, but bear with me... Are there any kernel panic messages in /var/log/messages? None. And the only messages I see directly related to cups tell me child exited with status 99!. I have also looked at the various files in /var/log/security but can see nothing obvious and /var/log/secure is empty. Do you have an ide-zip drive? No, just a laptop, with a usb mouse. I have not made any changes to my hardware either. Strange, cups was working fine under 9.0 for a few days, this is not something that happened immediately after the upgrade. I have retried starting apache but that didn't help. I get this message in /var/log/messages though. Any chance it is related? [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName If not, I'll worry about this one another day. I am not so sure that msec is the culprit anymore. Does anyone have any other suggesetions about where to look to track this down? Thanks. Dave -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Wednesday 05 Mar 2003 1:48 pm, David Whiting wrote: I get this message in /var/log/messages though. Any chance it is related? [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName I don't know whether it's related or not, but have you checked that you haven't a corruption in /etc/sysconfig/network ? Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Wed, Mar 05, 2003 at 11:13:19AM +, Anne Wilson wrote: On Wednesday 05 Mar 2003 1:48 pm, David Whiting wrote: I get this message in /var/log/messages though. Any chance it is related? [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName I don't know whether it's related or not, but have you checked that you haven't a corruption in /etc/sysconfig/network ? It looks okay to me (i.e. no garbage characters, but it could be misconfigured without me having a clue) NETWORKING=yes FORWARD_IPV4=false DHCP_HOSTNAME=ganymede HOSTNAME=ganymede DOMAINNAME=ammp.net GATEWAY=192.168.57.1 I'm pretty sure that this has not changed for a long time though so I do not think it should be related to my cups problem. Dave Anne -- Registered Linux User No.293302 -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Wednesday 05 Mar 2003 3:08 pm, David Whiting wrote: On Wed, Mar 05, 2003 at 11:13:19AM +, Anne Wilson wrote: On Wednesday 05 Mar 2003 1:48 pm, David Whiting wrote: I get this message in /var/log/messages though. Any chance it is related? [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName I don't know whether it's related or not, but have you checked that you haven't a corruption in /etc/sysconfig/network ? It looks okay to me (i.e. no garbage characters, but it could be misconfigured without me having a clue) NETWORKING=yes FORWARD_IPV4=false DHCP_HOSTNAME=ganymede HOSTNAME=ganymede DOMAINNAME=ammp.net GATEWAY=192.168.57.1 I'm pretty sure that this has not changed for a long time though so I do not think it should be related to my cups problem. Hmm - I don't have the dhcp line, so I can't comment on that, but I have the FQDN, so I would have expected HOSTNAME=ganymede.ammp.net? It's worth a try, anyway. Anne -- Registered Linux User No.293302 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
Welcome to the hell of 9.0 on a laptop... just for starters, I've removed shorewall and msec from mine. Reliability is so bad (I don't have the HD space to install more than one distro, and won't install 9.0 on any other system I own or support) that I'm lucky to go a week without rebooting... see my weird time/mouse bug post last night for the latest (apmd changes the time the time change kills mouse's drag functions -- resetting the time fixes the mouse -- go figre!!) :^P I used to get that with 8.2, but don't get it now. Strange. That said, have you used suspend/resume? That's the worst offender for me... so bad that I just shutdown/reboot instead... with suspend/resume, I lose sound, printer, and looking at a hard lockup within an hour or so... hmm maybe due to the time change or anything UNrelated... I use it all the time and have no problems that I am aware of. I have been using apm - s with 8.2 (and got the can't drag problem) and have been using it for a week or so with 9.0 and not had a problem until this broken cups thing. Also, are you sure the printer is not working at all... I had one problem that cleared up as mysteriously as it appeared... printing would take several minutes to start -- cups was trying to access my LinkSys gateway, probably thinking it should act as a print server or somesuch... Then, there were the cases where the only way to get the printer working again was to remove and re-create it... if I do service cups status I am told that cups is stopped. I do service cups start and it tells me that it has started [ok] in the term but /var/log/cups tells otherwise. Hmm. -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Wed, Mar 05, 2003 at 10:13:50AM -0400, Adolfo Bello wrote: It shows a DNS problem that might be related to your printing problem. It is not resolving the server name and it defaulting it to IP 127.0.0.1. Is the printer a local or network printer? Is it attached to the server whose name can not be resolved? The printer is a network printer and on http://localhost:631 cups has always reported that it can't resolve the address but then happily printed to it anyway. I wanted to get fix it, but as it worked it went way down on my list of priorities. I think my problem is bigger/earlier than not finding the printer because cupsd bombs out. Dave -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Wed, Mar 05, 2003 at 08:51:57AM -0500, Pierre Fortin wrote: That said, have you used suspend/resume? That's the worst offender for me... so bad that I just shutdown/reboot instead... with suspend/resume, I lose sound, printer, and looking at a hard lockup within an hour or so... hmm maybe due to the time change or anything UNrelated... I have just rebooted instead of apm -s to suspend/resume and still cups bombs out. /var/log/cups/error_log says: [06/Mar/2003:07:17:04 +] Listening to 7f01:631 [06/Mar/2003:07:17:04 +] Listening to c0a8391d:631 [06/Mar/2003:07:17:04 +] Sending browsing info to c0a839ff:631 [06/Mar/2003:07:17:04 +] Configured for up to 100 clients. [06/Mar/2003:07:17:04 +] LoadPPDs: Read /etc/cups/ppds.dat, 645 PPDs... [06/Mar/2003:07:17:04 +] LoadPPDs: No new or changed PPDs... [06/Mar/2003:07:17:05 +] StartListening: Unable to bind socket - Cannot assign requested address. So, something is stopping it from getting the address it wants. I also noticed that named wasn't happy either: [EMAIL PROTECTED] cups]# service named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. but I am clutching at straws here. I wonder if the fact that cups cannot assign the requested address and service named status tells me that this host is not authorised to connect have the same root cause (no pun intended). -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Wed, Mar 05, 2003 at 01:27:43PM +, Anne Wilson wrote: It looks okay to me (i.e. no garbage characters, but it could be misconfigured without me having a clue) NETWORKING=yes FORWARD_IPV4=false DHCP_HOSTNAME=ganymede HOSTNAME=ganymede DOMAINNAME=ammp.net GATEWAY=192.168.57.1 I'm pretty sure that this has not changed for a long time though so I do not think it should be related to my cups problem. Hmm - I don't have the dhcp line, so I can't comment on that, but I have the FQDN, so I would have expected HOSTNAME=ganymede.ammp.net? I tried this and it lead to a variety of problems with applications not being able to find ganymede.ammp.net. For a long time I have some 'little' networking problems (like not being able to ping ganymede from ganymede) but things seemed to work so I figured I needed to find time to understand more about netorking ... eventually ... but that it was not a critical issue for me. Thanks. Dave -- Dave Whiting Dar es Salaam, Tanzania Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] 8.2 - 9.0, msec ran and now cups unable to bind socket
On Wed, 2003-03-05 at 01:12, David Whiting wrote: Hi, I've just upgraded from 8.2 to 9.0 (just as everyone else is getting exited about 9.1 :-) and have a printing problem. msec_find ran this morning and now cups is unable to bind to socket 631. I am not sure if this is a coincidence but I remember seeing previous posts about woes with msec. I have tried to google the error message but have not found anything that worked. I have tried assigning a higher port in /etc/cups/cups.conf but that did not work. I tried: Port 1631 Listen localhost:1631 I am running at standard level security. As I said, I recall seeing similar posts in the past but can't quite find the solution. Any ideas? This may sound unrelated, but bear with me... Are there any kernel panic messages in /var/log/messages? Do you have an ide-zip drive? Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
