[heroes] anna rebooted last night?
When anna was rebooted last night, postfix failed to start - couldn't find an interface with the 192.168.47 address. Postfix did wait for network.target to complete (17:32:00) and started at 17:32:01, but still couldn't find an interface with the address ? I started up postfix this morning just before 8, the sudden flood of messages might have caused some receiving servers to start rate limiting. In the queue I see a few messages from icinga - recovery status or recovery notification - sent from "icinga@monitor.opensuse.org" to "icinga@localhost.opensuse.org". This can't be delivered, so an NDR is attempted sent back to "icinga@monitor.opensuse.org" which can't be delivered either. delivery temporarily suspended: connect to monitor.opensuse.org[2620:113:80c0:8::16]:25: Connection refused about 250 such mails right now :-) There were a few other issues - systemd-sysctl[397]: Couldn't write '655360' to 'net/nf_conntrack_max', ignoring: No such file or directory (long list of those). Some conntrack module not being loaded early enough? Keepalived - config problems Keepalived_vrrp - config problem I've captured all the output. Unless someone puts a hand up, I'll probably just open some issues for us to look at later. -- Per Jessen, Zürich (-0.4°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hi Per,
that was me... good findings and a nice test run how reboot-stable we are.
We need to look into this!
Thanks for the quickfix this morning. I wonder why the IP addr wasnt there. That shouldnt have happened.
Best regards,
Thorsten
Am 15. Februar 2019 08:50:49 MEZ schrieb Per Jessen
When anna was rebooted last night, postfix failed to start - couldn't find an interface with the 192.168.47 address. Postfix did wait for network.target to complete (17:32:00) and started at 17:32:01, but still couldn't find an interface with the address ?
I started up postfix this morning just before 8, the sudden flood of messages might have caused some receiving servers to start rate limiting.
In the queue I see a few messages from icinga - recovery status or recovery notification - sent from "icinga@monitor.opensuse.org" to "icinga@localhost.opensuse.org". This can't be delivered, so an NDR is attempted sent back to "icinga@monitor.opensuse.org" which can't be delivered either.
delivery temporarily suspended: connect to monitor.opensuse.org[2620:113:80c0:8::16]:25: Connection refused
about 250 such mails right now :-)
There were a few other issues -
systemd-sysctl[397]: Couldn't write '655360' to 'net/nf_conntrack_max', ignoring: No such file or directory (long list of those). Some conntrack module not being loaded early enough?
Keepalived - config problems Keepalived_vrrp - config problem
I've captured all the output. Unless someone puts a hand up, I'll probably just open some issues for us to look at later.
--
Thorsten Bro
Thorsten Bro | SUSE-IT wrote:
Hi Per,
that was me... good findings and a nice test run how reboot-stable we are.
We need to look into this!
Thanks for the quickfix this morning. I wonder why the IP addr wasnt there. That shouldnt have happened.
I can't figure it out. This is from the log: Feb 14 17:32:01 anna systemd[1]: Starting Postfix Mail Transport Agent... Feb 14 17:32:01 anna echo[1755]: Starting mail service (Postfix) Feb 14 17:32:01 anna postfix[1799]: fatal: parameter inet_interfaces: no local interface found for 192.168.47.4 Feb 14 17:32:02 anna systemd[1]: postfix.service: Control process exited, code=exited status=1 -- Per Jessen, Zürich (3.6°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
participants (2)
-
Per Jessen
-
Thorsten Bro | SUSE-IT