On 03/05/2016 08:10 PM, 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.
From the systemd POV you should be able to get a specific drill down on postfix alone:
systemctl status postfix.service if that proves to be catastrophic then I'd take a close look at the unit file that manages postfix. See systemd.unit(5) As Per says, you can try starting postfix from the command line and see what is reporting. It may be that the upgrade has introduced new config files in /etc/postfix. Maybe/maybe-not there are rpmsave files there. Heck, I get then in normal 'zypper up' so if you got then in the 'upgrade' I wouldn't be surprised! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org