On Mon, Mar 7, 2016 at 6:13 AM, Per Jessen <per@computer.org> wrote:
Greg Freemyer wrote:
A server I admin has been nothing but trouble today.
It started having a problem, and being smarter than average bear I thought the best way out was to go ahead and upgrade from 13.1 to 13.2 and all would be good.
Not so much.
I'm now running 13.2. zypper dup says I'm done and so does zypper verify.
The current trouble is postfix isn't running.
And when I try "systemctl start postfix.service" it triggers a systemd meltdown and I get thrown into a systemd maintenance mode.
There is probably useful info in the systemd journal, but there is a lot of stuff in there and I don't know what I'm looking for.
Guidance appreciated.
First bit - don't write "systemd" in the subject line, using "sistemad" has proven to be a better alternative. :-)
That is important advice!
Second, have you tried starting postfix manually? Just from the console with "postfix start"? Just in case something in the postfix startup is causing the problem.
I have upgraded several boxes from 13.1 to 13.2, never had an issue.
I have my server running for the last 12 hours so the urgency of troubleshooting is gone, but still this was a major bug for me. I found that even if I did nothing after re-boot the server would enter "systemd maintenance mode" after 15 minutes. Trying to start postfix (systemctl start postfix.service) simply triggered the failure sooner. I got a journal dump before and after the failure (journalctl -xb > log). About 500 lines of logs added in the post failure log. I went through and fixed every minor complaint until my server would run smoothly. Commenting out this line from fstab was the "fix". === #/srv_new/portal_backup_container /home/portal_backup/portal_backup ext4 loop 0 0 === I don't now if that line was was working last week or not. When I applied the last 13.1 patches saturday it apparently started causing systemd to fail shortly after re-boot. Upgrading my box to 13.2 did not change that. I haven't done any troubleshooting of the above yet. It may have to wait a couple days before I can dedicate my brainpower to it, but I'm glad to run troubleshooting commands others propose. The big thing for me that makes this a pretty major bug is that the above line for some reason made my server unusable as a server. Something about it caused systemd to revert to maintenance mode 15 minutes after boot. If I had a ssh connection going, it simply halted at that time. My only access was via an interface my cloud provider provides that lets me function as if I'm typing on the console (VNC is used for the remote console). Further, postfix wasn't running and trying to start it would trigger the same systemd failure. I assume because postfix was somehow dependent on all filesystems in fstab being mounted. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org