OpenRC shutdown sequence

willem-jan · n00b Joined: 12 Sep 2021 Posts: 7

Hi All,

I really love OpenRC, especially it's simplicity over systemd. There is however one annoyance that I cannot seem to fix. During each shutdown/restart I get this error (often 2 times):

cboldt · Veteran Joined: 24 Aug 2005 Posts: 1046

There is a good bit of information in /usr/share/doc/openrc-0.43.5/service-script-guide.md.bz2

Your openrc version and compression for docs may vary, but generally check /usr/share/doc/openrc-*/service-script-guide.*

The stop sequence parameters are covered by start parameter "depends" vs. "uses" sort of thing.

willem-jan · n00b Joined: 12 Sep 2021 Posts: 7

Thank you.

I have also found this on the OpenRC Github page. As far as I understood everything seems configured ok. Syncthing is using 'depend need net'. And while this also works correctly when I, for example, stop NetworkManager manually: syncthing is automatically stopped before NetworkManager is stopped. But it does not work when shutting down the system.

I am also not using 'rc_parallel="YES"'. So everything should be stopped sequentially. From the log this indeed seems the case.

The only problem is that is seems that NetworkManager is stopped before syncthing, which it obviously shouldn't. But maybe something else is causing this 'order change'? Or maybe it is even something completely else causing this problem?

Anyone a clue?

cboldt · Veteran Joined: 24 Aug 2005 Posts: 1046

My guess is the issue is that more than one service in /etc/init.d provides "net."

Is openrc setup to start any /etc/init.d/net.eth0 or other network, in addition to NetworkManager?

I don't run network manager or syncthing, so just stabbing inthe dark here. I did do some "grep need /etc/init.d" and "grep provide /etc/init.d" to get a sense of absolute dependencies.

I see openrc provides a service called "net-online" too. Never played with that one, but maybe just adding that will resolve the issue.

AJM · Posted: Mon Sep 13, 2021 8:20 pm Post subject:

Maybe this is a cheat kind of answer, but could you not just do away with NM? Unless your machine is a laptop which is used in many locations there's very little reason to use NM at all IMO.

Goverp · Veteran Joined: 07 Mar 2007 Posts: 1995

cboldt · Veteran Joined: 24 Aug 2005 Posts: 1046

Heh ... I've been doing wpa_supplicant the hard way for years. Didn't even know there was a wpa_gui

willem-jan · n00b Joined: 12 Sep 2021 Posts: 7

Thanks again for all your replies!

That actually sounded like a possible problem. But I don't use net.eth0 and alike. I also looked through every service including all the other runlevels, but none of them provide 'net' or 'net-online'. Also adding 'net-online' to did change anything help.

It almost feels like a bug in OpenRC since manually stopping NetworkManager works as expected (other services, like syncthing, that have 'depend net' stop first), but during shutdown OpenRC seems not to adhere to the order somehow. Also the error messages do give much of a clue...

I'm running out of options for this seemingly simple issue... I would indeed be willing to ditch NetworkManager but I remember I had issues during system installation with Netifrc and KDE.

Yes it is indeed laptop, hence have different WLAN, OpenVPN and ethernet configs that are 'dynamic'.

What would you recommend to use/do in this case?

dmpogo · Advocate Joined: 02 Sep 2004 Posts: 3267 Location: Canada