http://bugzilla.suse.com/show_bug.cgi?id=906900 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opensuse@schiller | |strasse42.de) --- Comment #34 from Thomas Blume <thomas.blume@suse.com> --- Ok, thanks for the feedback. Actually, the culprit was pam_unix. The init scripts switches to the postgres user via su. This creates a login session for user postgres. When such an login session finishes, some cleanup is done and all processes belonging to this session are deleted. The closing of login sessions is very early in the shutdown process and before the postgresql init script is called to stop the database. Therefore the processes were already dead when the stop command was run. Executing the postgres commands within a proper systemd services file, doesn't create a login session and hence the problem doesn't appear. Still, the init script contains some setup that is difficult to achieve within a service file. Therefore, I've created a combined setup that executes the init script to setup the environment and afterwards starts the database from within a service file. Please copy the attached file postgresql-init to /etc/init.d/ and postgresql.service to /etc/systemd/system/. Afterwards run: systemctl daemon-reload systemctl enable postgresql.service You might want to do a dry run then by executing: systemctl start postgresql.service and checking with: systemctl status postgresql.service If the database is correctly up, please reboot and check wheter the issue is fixed. -- You are receiving this mail because: You are on the CC list for the bug.