Re: fedora27: ypbind intermittent startup
On 02/02/18 15:51, Terry Barnaby wrote: > On 02/02/18 07:42, Terry Barnaby wrote: >> On 02/02/18 00:41, Ed Greshko wrote: >>> >>> I've not tried this since I don't have a need for ypbind. >>> >>> One may also consider copying /lib/systemd/system/ypbind.service to >>> /etc/systemd/system and then inserting the line, >>> >>> ExecStartPre=/usr/bin/sleep 5 >>> >>> From the systemd documentation >>> >>> ExecStart= commands are only run after all ExecStartPre= commands that were >>> not >>> prefixed with a "-" exit successfully. >>> >> Thanks I will try this out, but it would be nice to get it fixed properly in >> Fedora27. >> So, did you try it out? FWIW, since this appears to be mostly a "timing" issue I modified the name service in this way. Before the the modification [egreshko@f27k ~]$ systemd-analyze blame | grep named 904ms named-chroot.service 682ms named-chroot-setup.service 322ms named-setup-rndc.service after adding ExecStartPre=/usr/bin/sleep 30 (I wanted to see if any other processes would be affected) [egreshko@f27k ~]$ systemd-analyze blame | grep nam 30.377s named-chroot.service 613ms named-chroot-setup.service 189ms named-setup-rndc.service Other than the delay in starting named, the system booted in its usual 12 seconds. So, the workaround should be successful. And, I would also suggest you write a bugzilla and *maybe* things surrounding "wait-online" will improve. -- A motto of mine is: When in doubt, try it out signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedora27: ypbind intermittent startup
On 02/02/18 16:49, Ed Greshko wrote: > But, another thing you can try is to modify the > NetworkManager-wait-online.service by > making a copy of it in /etc/systemd/system and changing the line, Oh, just in case you're not familiar, when you make your own copy of the service you would have to do systemctl -f enable NetworkManager-wait-online to rewrite the symbolic link to point to the "custom" configuration. -- A motto of mine is: When in doubt, try it out signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedora27: ypbind intermittent startup
On 02/02/18 15:42, Terry Barnaby wrote: > On 02/02/18 00:41, Ed Greshko wrote: >> >> I've not tried this since I don't have a need for ypbind. >> >> One may also consider copying /lib/systemd/system/ypbind.service to >> /etc/systemd/system and then inserting the line, >> >> ExecStartPre=/usr/bin/sleep 5 >> >> From the systemd documentation >> >> ExecStart= commands are only run after all ExecStartPre= commands that were >> not >> prefixed with a "-" exit successfully. >> > Thanks I will try this out, but it would be nice to get it fixed properly in > Fedora27. > > Could it be due to "target Network is Online" being triggered by IPv6 being > configured first ? I don't use IPv6, but I guess the system could be setting > this > up somehow by default. > I will admit to having stayed away from the "Network-Online" discussions as they often devolve into rants against systemd. But, another thing you can try is to modify the NetworkManager-wait-online.service by making a copy of it in /etc/systemd/system and changing the line, ExecStart=/usr/bin/nm-online -s -q --timeout=30 to ExecStart=/usr/bin/nm-online q --timeout=30 Check out the man page for nm-online to see how it operates with and without -s. I'm speculating that with the -s the dhcp processes may not be fully completed when the ypbind process is started. You many want to check out the archives of this list for past "discussions" along similar lines. -- A motto of mine is: When in doubt, try it out signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedora27: ypbind intermittent startup
On 02/02/18 07:42, Terry Barnaby wrote: On 02/02/18 00:41, Ed Greshko wrote: I've not tried this since I don't have a need for ypbind. One may also consider copying /lib/systemd/system/ypbind.service to /etc/systemd/system and then inserting the line, ExecStartPre=/usr/bin/sleep 5 From the systemd documentation ExecStart= commands are only run after all ExecStartPre= commands that were not prefixed with a "-" exit successfully. Thanks I will try this out, but it would be nice to get it fixed properly in Fedora27. Could it be due to "target Network is Online" being triggered by IPv6 being configured first ? I don't use IPv6, but I guess the system could be setting this up somehow by default. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Actually I just noticed in the KDE/Plasma network manager settings there is now a "IPv4 is required for this connection" setting. From the tooltip which states "Allows the connection to complete if IPv4 configuration fails but IPv6 configuration succeeds". This tooltip appears to be written in the negative, but assuming that actual buttons text is correct then this may do what I need. I will try that. The Ethernet interface appears to have an IPv6 config, not sure where that is coming from. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedora27: ypbind intermittent startup
On 02/02/18 00:41, Ed Greshko wrote: I've not tried this since I don't have a need for ypbind. One may also consider copying /lib/systemd/system/ypbind.service to /etc/systemd/system and then inserting the line, ExecStartPre=/usr/bin/sleep 5 From the systemd documentation ExecStart= commands are only run after all ExecStartPre= commands that were not prefixed with a "-" exit successfully. Thanks I will try this out, but it would be nice to get it fixed properly in Fedora27. Could it be due to "target Network is Online" being triggered by IPv6 being configured first ? I don't use IPv6, but I guess the system could be setting this up somehow by default. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedora27: ypbind intermittent startup
On 02/01/18 21:41, Tom Horsley wrote: > On Thu, 1 Feb 2018 11:32:44 + > Terry Barnaby wrote: > >> Does the system " target Network is Online" get reached after DHCP >> configuration ? > Probably doesn't matter because systemd has no idea what "up" > means when it comes to networks :-(. > > ypbind is one of the services I always just start in rc.local > with a delay: > > /bin/bash -c 'sleep 5 ; systemctl restart ypbind' > /dev/null 2>&1 < > /dev/null & > > The only way I could get it to reliably start on every boot. > > Of course, you can't just put that in rc.local any longer because > something changed recently that makes systemd go funny in the head > with stuff started in rc.local, so this is really in the-real-rc.local > and rc.local looks like: > > /usr/bin/at -M now <<'HERE' > /dev/null 2>&1 > /etc/rc.d/the-real-rc.local > HERE > I've not tried this since I don't have a need for ypbind. One may also consider copying /lib/systemd/system/ypbind.service to /etc/systemd/system and then inserting the line, ExecStartPre=/usr/bin/sleep 5 From the systemd documentation ExecStart= commands are only run after all ExecStartPre= commands that were not prefixed with a "-" exit successfully. -- A motto of mine is: When in doubt, try it out signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: fedora27: ypbind intermittent startup
On Thu, 1 Feb 2018 11:32:44 + Terry Barnaby wrote: > Does the system " target Network is Online" get reached after DHCP > configuration ? Probably doesn't matter because systemd has no idea what "up" means when it comes to networks :-(. ypbind is one of the services I always just start in rc.local with a delay: /bin/bash -c 'sleep 5 ; systemctl restart ypbind' > /dev/null 2>&1 < /dev/null & The only way I could get it to reliably start on every boot. Of course, you can't just put that in rc.local any longer because something changed recently that makes systemd go funny in the head with stuff started in rc.local, so this is really in the-real-rc.local and rc.local looks like: /usr/bin/at -M now <<'HERE' > /dev/null 2>&1 /etc/rc.d/the-real-rc.local HERE If systemd gets much more helpful, no one will ever be able to use a computer again (which would at least make the security geeks happy). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
fedora27: ypbind intermittent startup
I am finding on my systems that ypbind is failing occasionally at boot (about 30% of the time). [ OK ] Started Network Manager Wait Online. [ OK ] Reached target Network is Online. Mounting /src... Mounting /scratch... Starting NIS/YP (Network Information Service) Clients to NIS Domain Binder... Mounting /home... Mounting /opt... Mounting /dist... Starting Notify NFS peers of a restart... Starting Beam BOAP Name Server... Mounting /usr/beam... Mounting /var/cache/dnf... [ OK ] Started Notify NFS peers of a restart. [ OK ] Started Beam BOAP Name Server. [FAILED] Failed to start NIS/YP (Network Information Service) Clients to NIS Domain Binder. See 'systemctl status ypbind.service' for details. [ OK ] Reached target User and Group Name Lookups. The error is: Feb 1 10:34:36 beam1 ypbind[788]: No NIS server and no -broadcast option specified. Feb 1 10:34:36 beam1 ypbind[788]: Add a NIS server to the /etc/yp.conf configuration file, Feb 1 10:34:36 beam1 ypbind[788]: or start ypbind with the -broadcast option. But /etc/yp.conf has: # generated by /sbin/dhclient-script domain beamnet server 192.168.201.1 ypbind starts fine after the system has booted. I assume that ypbind is being started by systemd before the dhcp client has actually written into /etc/yp.conf. Does the system " target Network is Online" get reached after DHCP configuration ? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org