Unreliable systemd (shit software in the mist)

Is it up or down ? systemd has one job although the megalomaniacs at the systemd project really want to make it linux itself after all who needs dns servers and other stuff – i mean they can do that too, systemd one day might build cars for elon musk.

So after fixing opendkim with my original systemd config it i turned my attention to postfix which works but systemd has decided is not loaded or active despite being so.  Go figure.

Starting postfix (via systemctl): postfix.serviceJob for postfix.service failed because
the control process exited with error code.
See “systemctl status postfix.service” and “journalctl -xe” for details.
failed!

So i go exploring the joys of systemd once more after debian 9.2 is released (my blog)

systemctl status postfix.service
● postfix.service – Postfix Mail Transport Agent
Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since x; 11min ago
Docs: man:postfix(1)
Main PID: 10259 (code=exited, status=1/FAILURE)

Oct 10 14:50:22 * postfix/postfix-script[13821]: fatal: the Postfix mail system is already running
Oct 10 14:50:24 * postfix-*/postfix-script[13828]: fatal: the Postfix mail system is already running
Oct 10 14:50:25 * postfix-*/postfix-script[13835]: fatal: the Postfix mail system is already running
Oct 10 14:50:26 * postfix-*/postfix-script[13844]: fatal: the Postfix mail system is already running
Oct 10 14:50:27 * postfix-*/postfix-script[13851]: fatal: the Postfix mail system is already running
Oct 10 14:50:28* systemd[1]: postfix.service: Control process exited, code=exited status=1
Oct 10 14:50:28 * systemd[1]: Failed to start Postfix Mail Transport Agent.
Oct 10 14:50:28 * systemd[1]: postfix.service: Unit entered failed state.
Oct 10 14:50:28 * systemd[1]: postfix.service: Failed with result ‘exit-code’.
Oct 10 15:01:00 * systemd[1]: postfix.service: Dependency Before=postfix.service dropped

systemctl start postfix.service
Job for postfix.service failed because the control process exited with error code.
See “systemctl status postfix.service” and “journalctl -xe” for details.

postmulti -p status
postfix/postfix-script: the Postfix mail system is not running
postfix-*/postfix-script: the Postfix mail system is running: PID: 16077
postfix-*/postfix-script: the Postfix mail system is running: PID: 16075
postfix-*/postfix-script: the Postfix mail system is running: PID: 15993
postfix-*/postfix-script: the Postfix mail system is running: PID: 15642

for example

So regardless of whether /usr/sbin/postfix and postmutli starting in systemd  still cannot figure out whether its running or not  – well done you systemd project geniuses.

I can still run the software because i know systemd is shit at what it does but is this really the future of init systems ?   If systemd is unreliable and with distros ignoring custom systemd files then clearly systemd is not up to the job unless you think the systemd way*.

Why it starts twice now is a mystery to me and yet another systemd fuckup (my blog) to savour. although there be others well worth lol’ing over.

I do not change postfix configurations often and feel happy with postmulti so i know its not me making these changes.

Enough of that shit software i think for today

*George Orwell’s boot on face quote seems apt.

One response

  1. Pingback: bsd as a linux killer (no systemd) | Bananas in the Falklands

by golly but...

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s