I think that the delayed response from the dhcp server is causing my network related services to timeout/not find addresses (ie nfs mounts, nis, ntp, etc) When it boots up it complains that it cant find the servers .. but once the machine is up, if I start any of the services that failed during boot up, they all seem to work fine. Has anyone had something similar to this ? does anyone know if I can increase the timeout before it gives up on dhcp and continues to boot ? Btw this is sles9 and happens on every machine I have .. I would almost suggest looking at the dhcp server .. but since we are a large corp. this is not an option. Any help would be great.. Thanks, rod
On Tuesday 16 November 2004 01:04, Rod Rioux wrote:
I think that the delayed response from the dhcp server is causing my network related services to timeout/not find addresses (ie nfs mounts, nis, ntp, etc)
When it boots up it complains that it cant find the servers .. but once the machine is up, if I start any of the services that failed during boot up, they all seem to work fine.
They all seem to work fine? Does that mean you got an ip# from the dhcp server?
does anyone know if I can increase the timeout before it gives up on dhcp and continues to boot ?
File /etc/sysconfig/network/dhcp, variable DHCP_TIMEOUT.
Btw this is sles9 and happens on every machine I have .. I would almost suggest looking at the dhcp server .. but since we are a large corp. this is not an option.
Perhaps the dhcp-server is slow. Look in the lease to see what dhcp server handed out that lease. Cheers, Leen
On Mon, Nov 15, 2004 at 04:04:23PM -0800, Rod Rioux wrote:
I think that the delayed response from the dhcp server is causing my network related services to timeout/not find addresses (ie nfs mounts, nis, ntp, etc)
When it boots up it complains that it cant find the servers .. but once the machine is up, if I start any of the services that failed during boot up, they all seem to work fine.
Has anyone had something similar to this ? does anyone know if I can increase the timeout before it gives up on dhcp and continues to boot ?
I have seen it only with Firewalls falsly blocking regular traffic and DNS lookups, basically.
Btw this is sles9 and happens on every machine I have .. I would almost suggest looking at the dhcp server .. but since we are a large corp. this is not an option.
There is a number of possible reasons, and you would need to debug it to find out what's going on. strace would help. Close examination of the boot logs might give a hint. Luckily, because you have read the release notes, you are not using a local domain called .site. ;) Peter
On Monday 22 November 2004 13:48, poeml@cmdline.net wrote:
Luckily, because you have read the release notes, you are not using a local domain called .site. ;)
You mean .local don't you? Surely there's no problem with a domain called site is there?
On Mon, Nov 22, 2004 at 03:51:52PM +0100, Anders Johansson wrote:
On Monday 22 November 2004 13:48, poeml@cmdline.net wrote:
Luckily, because you have read the release notes, you are not using a local domain called .site. ;)
You mean .local don't you? Surely there's no problem with a domain called site is there?
Yes, that's what I meant, sorry. Peter
participants (4)
-
Anders Johansson
-
Leendert Meyer
-
poeml@cmdline.net
-
Rod Rioux