On Jul 12 10:00, Sam Varshavchik wrote: > Now that I have your attention, the background is as follows. This is a > server with only statically configured network interfaces. NetworkManager is > not installed. All network interfaces are statically configured via > /etc/sysconfig/network-scripts. > > The server is regularly updated to current Fedora packages. For the last > month, or so, the server has failed to come up in a sane state, reliably. > After it responds to pings, after ssh-ing in, and examining the aftermath, > the logs of all network services are consistent, in that they claim that > each network service – which includes: named-chroot, httpd, dhcpd, and > privoxy – their boot logs claim that no network interfaces were up at the > time they're started.
This is probably not exactly what you're looking for, but I had the same or, at least, a similar problem. The network init script creates four interfaces. All network services which listen on 0.0.0.0 or :: start up fine, even if they start too early. Network services which are supposed to listen to explicit network addresses often fail to start, because the bind(2) calls fail. What I did was to screw a new target between network-online and the affected services, like this: $ cat /etc/systemd/system/multi-user.target.wants/network-waiter.target # Wait for Network being online. # Let all network services depend on this one. [Unit] Description=Fake target to make sure network is online before starting dependent services After=network-online.target Before=dovecot.service named.service postfix.service sshd.service This seems to help. It sure would be nice if these service files would be corrected instead. Corinna -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
