Minor issues with ntp and net

apberzerk · Posted: Fri Jul 08, 2005 7:17 am Post subject: Minor issues with ntp and net

Can anyone explain the following behavior?

Short story: init.d scripts in the default runlevel that require net (such as ntp-client and nfsmount) fail to start while booting, but I can start them manually just fine. If I put net.eth0 in the boot runlevel, there's a warning that it must wait until default runlevel, but then ntp-client and nfsmount start just fine!

Long Story: I looked around on the forums and could not find this anywhere, so I apologize if this is a duplicate thread.

Ever since my last round of updates, the network has been behaving rather strangely.

First of all, is net.eth0 supposed to come on by itself now? Even when I remove it with rc-update, it still seems to come up (I suppose this is convenient).

Also, I am having a problem with ntp-client when it starts. It is part of the default runlevel, and when it starts it says "temporary failure in name resolution" and fails. However, if I start it manually after the boot process, it works fine. The same thing happens sometimes for nfs mounts. They fail to mount while booting, but I can manually mount them myself after booting is complete.

It seems almost as if ntp-client and nfsmount are starting too early, before net.eth0. However, I checked the init.d scripts and they "need", "use", and "provide" all make sense, plus I have no modified them.

Now here's the interesting part. If I had net.eth0 to the boot runlevel, it gives me an error while it is booting, saying that it has to wait until after the boot runlevel to start it, but then it starts it during the default runlevel and ntp-client and nfsmount actually start correctly!

- Phil

Adrien · Posted: Fri Jul 08, 2005 8:31 am Post subject:

And, what if you put net.eth0 to the default runlevel? 'cause, that's where it has to be.... :roll:

EDIT: sorry I didn't understand you simply wanted an explaination...but anyway net.eth0 as to be into the default runlevel for things to work properly..

apberzerk · Posted: Fri Jul 08, 2005 6:00 pm Post subject:

Sorry, I guess I didn't explain it well enough. When net.eth0 is in the default runlevel, ntp-client and netmount fail to start. They act like the network isn't up yet, as if they are starting too soon, but they have "need net" in their init.d scripts.

But, after the computer boots, I can always start them manually....

apberzerk · Posted: Fri Jul 08, 2005 6:01 pm Post subject:

Oh yeah, and many init.d scripts that require net (like sshd) work fine.

ulysses_cruz · n00b Joined: 08 Apr 2004 Posts: 66 Location: Chicago, IL

I have the same problem. Some network services (like ntp-client) are starting before eth0 starts, and those that try to connect to an outside server (as opposed to waiting for connections from outside) fail because there is no working network connection.

The odd thing is that ntp-client tries to start before eth0 and dies, while ntpd (with the same need and use settings) starts after eth0 and has no problem.

Fortunately for me there are no critical services on my server with this problem.
_________________
If it were'nt for the voices in my head, I'd go insane from loneliness.
-Me, Myself and I

Iwill DK8X, 2x Opteron 244, 8x 512Mb PC2700, Geforce FX5600, Audigy 2 ZS Plat., MegaRAID SATA150-6

Mben · Posted: Fri Aug 05, 2005 11:41 pm Post subject:

i had this problem (with ntp-client) and was just about to ask also when i found the setting.
in /etc/conf.d/rc adjust this:

UberLord · Posted: Sat Aug 06, 2005 12:05 am Post subject:

Unfortunately, init ordering is badly foobared in baselayout.1.11.x

It's fixed in baselayout-1.12.0_pre4

Mben · Posted: Sat Aug 06, 2005 12:07 am Post subject:

the above fixed it for me using baselayout 1.11.13 on a ~x86 system

apberzerk · Posted: Sun Aug 07, 2005 2:11 am Post subject:

I still have the same problem with ntp-client. It fails at startup, saying no servers could be found, but if I start it manually, it works.

- Phil

UberLord · Posted: Mon Aug 08, 2005 6:00 am Post subject:

What version of baselayout do you have?

apberzerk · Posted: Mon Aug 08, 2005 6:39 pm Post subject:

baselayout: 1.11.13
ntp: 4.2.0.20040617-r2

- Phil

UberLord · Posted: Tue Aug 09, 2005 9:02 am Post subject:

Chances are that ntp-client is starting before net.xxx scripts. This is a baselayout bug and has been fixed in 1.12.0_pre4 but I'd wait for 1.12.0_pre5 if you're running vmware, samba and cups.