[solved]network services not started when using DHCPD+OpenRC

xaviermiller · Last edited by xaviermiller on Wed Oct 24, 2018 7:01 pm; edited 1 time in total

Hi!

I use DHCPCD as main network manager with OpenRC, but I see some network service don't start automatically at boot : ntp-client (from net-misc/ntp) ("Temporary failure in name resolution") and samba ("start-stop-daemon: failed to start `/usr/sbin/smbd'", kinda a crash).

I use parallel startup (RC_PARALLEL=YES).

If I disable parallel startup (RC_PARALLEL=NO), samba starts, but still not ntp-client.

DHCPCD is started at boot runlevel, the other network services at default runlevel.

I have to start them manually.

What can I do to let them natively start?

EDIT: solution is : set dhcpcd at boot runlevel, and put "waitip" in /etc/dhcpcd.conf
_________________
Kind regards,
Xavier Miller

Suicidal · l33t Joined: 30 Jul 2003 Posts: 959 Location: /dev/null

You could try adding your network adapter to the boot runlevel to give it more time to initialize
before network dependent services start. I know my Wireless takes about 10 seconds after login
before I have a IP, so I just dont use ntp-client.

Once the time is set, ntpd should keep it within a few ms of the servers.

Anon-E-moose · Posted: Wed Oct 24, 2018 9:40 am Post subject:

Yeah, you need to leave some time between the network adapter being turned on/modules loaded/etc and the starting up of dhcpcd and then a little more time between that and something like ntp starting up. I know it kind of defeats the purpose of parallel, but ....
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

krinn · Watchman Joined: 02 May 2003 Posts: 7470

Same answer as Anon-E-moose: ntp-client is called after net, it doesn't garanty net has setup the network fine when ntp-client is called.

You may delegate the run of ntp-client and other to another initscript that do nothing except looping ping -c1 8.8.8.8 and once it have an answer trigger ntp-client and friends.

khayyam · Posted: Wed Oct 24, 2018 10:36 am Post subject:

Anon-E-moose · Posted: Wed Oct 24, 2018 10:56 am Post subject:

once "ip route show default" gives you a valid ip then you're good to go with net-client, samba, etc.

I would imagine a one second delay after dhcpd would be plenty of time or move their startup to /etc/local.d/baselayout1.start

I have a usb drive that (most of the time) was starting normally, but once in a while it would't start up, so I turned of auto mount for it and added the mount command to /etc/local.d
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

bunder · Bodhisattva Joined: 10 Apr 2004 Posts: 5934

are you using /etc/init.d/dhcpcd or /etc/init.d/net.* ? if you're using the dhcpcd init script, i'd try net.* instead with a /etc/conf.d/net containing

P.Kosunen · Guru Joined: 21 Nov 2005 Posts: 309 Location: Finland

Put "waitip" option to dhcpcd.conf and it waits until it gets ip before starting other services depending network.

Suicidal · l33t Joined: 30 Jul 2003 Posts: 959 Location: /dev/null

There’s also the timeout value in ntpdate, but if you’re willing to do that; there’s no sanity in setting RC_PARALLEL.

xaviermiller · Posted: Wed Oct 24, 2018 6:49 pm Post subject:

Hi,

Thank you all for your replies !