View previous topic :: View next topic |
Author |
Message |
jyoung Guru
Joined: 20 Mar 2007 Posts: 443
|
Posted: Mon Jun 25, 2018 10:06 pm Post subject: |
|
|
This solution does feel like a bit of a hack. I'd be happy to continue investigating ... |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3186
|
Posted: Mon Jun 25, 2018 10:28 pm Post subject: |
|
|
Time to bring up the big guns then. And the bigger picture.
1)Go to /etc/rc.conf, and change rc_logger="NO" to "YES"
2) rc-update --update (just in case, shouldn't matter but it won't hurt)
3) reboot and post /var/log/rc.log and the output from rc-update (without any params). Actually, full /etc/conf.d/net in its current state could be useful too.
Let's see what's actually going on there. |
|
Back to top |
|
|
jyoung Guru
Joined: 20 Mar 2007 Posts: 443
|
Posted: Thu Jun 28, 2018 9:45 pm Post subject: |
|
|
Okay, here are the results:
When running rc --update, the following errors were generated:
Code: |
Error: modules-load is the name of a real and virtual service.
Error: tmpfiles.dev is the name of a real and virtual service.
Error: tmpfiles.setup is the name of a real and virtual service.
|
And here's /var/log/rc.log
www.pastebin.com/ucP6xvr4
The only thing in /etc/conf.d/net is
Code: |
dhcpcd_enp0s31f6="-t 60"
|
which is leftover from an earlier experiment to solve this problem. |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3186
|
Posted: Fri Jun 29, 2018 8:12 pm Post subject: |
|
|
rc-update --update and rc --update ain't the same thing. You're lucky you didn't fry your system.
I skimmed through your boot log and I noticed a few things:
1) You start dhcpcd in boot.
This is not necessarily bad, but certainly unusual. Net is much more common in "default", even though it doesn't make a big difference on a personal machine.
Interestingly enough, netmount service also starts there. This, wouldn't be too bad if not for 3.
2) You use both, dhcpcd AND netifrc to configure your network. This is bad. I don't suppose you explicitly disabled enp0s31f6 in dhcpcd's config, which means dhcpcd configures this interface in boot, and then netifrc calls dhcpcd again in default runlevel.
At least you can expect both of those services to produce the same result, which limits conflicts a bit, but it is a conflict nonetheless. Messy.
Chose one or the other. Either make sure dhcpcd does not provide net (and is not explicitly enabled), or remove netifrc symlink from /etc/init.d/
In either case you can completely clear /etc/conf.d/net. When empty, it defaults to dhcp, and dhcp tends to "just work", without any extra parameters.
3) What is eno1? Is this device supposed to exist?
If you replaced it with (or renamed to) enp0s31f6, remove the symlink too. This service will always fail and since it provides net, failure at this point should prevent ntp and nfs from starting. Oops.
4) Does your netmount service depend on net? Apparently it does not by default.
Go do /etc/conf.d/netmount and add the line:
rc_need="net !network"
(network is a deprecated service AND it is redundant - netmount's init script seems to be a bit outdated, but we can fix it with this config file)
With conflicts resolved and dependencies fixed you should be good to go. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|