Discussion:
systemd kills user process (apache) when logout by sftp is initiated
Add Reply
Simon Becks
2018-02-01 11:32:32 UTC
Reply
Permalink
Raw Message
Is this an expected behavior?

Debian 9 with systemd 232-25+deb9u1

Apache is running as user wp_user.

After logging in and logging out via sftp as user wp_user - systemd
kills apache process.

Feb 1 10:58:25 shop systemd: pam_unix(systemd-user:session): session
opened for user wp_user by (uid=0)
Feb 1 11:01:58 shop sshd[23747]: Connection closed by client-ip port
38409 [preauth]
Feb 1 11:07:36 shop sshd[23673]: Received disconnect from client-ip2
port 53274:11:
Feb 1 11:07:36 shop sshd[23673]: Disconnected from client-ip2 port 53274
Feb 1 11:07:36 shop sshd[23664]: pam_unix(sshd:session): session
closed for user wp_user
Feb 1 11:07:36 shop systemd-logind[480]: Removed session 3177.
Feb 1 11:07:36 shop systemd: pam_unix(systemd-user:session): session
closed for user wp_user

[Thu Feb 01 11:07:36.170606 2018] [mpm_prefork:emerg] [pid 20396]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170606 2018] [mpm_prefork:emerg] [pid 20910]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170624 2018] [mpm_prefork:emerg] [pid 20394]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170625 2018] [mpm_prefork:emerg] [pid 20393]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170625 2018] [mpm_prefork:emerg] [pid 20408]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.175260 2018] [mpm_prefork:emerg] [pid 20407]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.218866 2018] [core:alert] [pid 20375] AH00050:
Child 20393 returned a Fatal error... Apache is exiting!
[Thu Feb 01 11:07:36.218914 2018] [:emerg] [pid 20375] AH02818: MPM
run failed, exiting

Feb 1 11:07:36 shop systemd[1]: Stopping User Manager for UID 1001...
Feb 1 11:07:36 shop systemd[23666]: Stopped target Default.
Feb 1 11:07:36 shop systemd[23666]: Stopped target Basic System.
Feb 1 11:07:36 shop systemd[23666]: Stopped target Sockets.
Feb 1 11:07:36 shop systemd[23666]: Closed GnuPG cryptographic agent
and passphrase cache (restricted).
Feb 1 11:07:36 shop systemd[23666]: Closed GnuPG cryptographic agent
and passphrase cache.
Feb 1 11:07:36 shop systemd[23666]: Stopped target Paths.
Feb 1 11:07:36 shop systemd[23666]: Closed GnuPG cryptographic agent
(access for web browsers).
Feb 1 11:07:36 shop systemd[23666]: Stopped target Timers.
Feb 1 11:07:36 shop systemd[23666]: Closed GnuPG cryptographic agent
(ssh-agent emulation).
Feb 1 11:07:36 shop systemd[23666]: Reached target Shutdown.
Feb 1 11:07:36 shop systemd[23666]: Starting Exit the Session...
Feb 1 11:07:36 shop systemd[23666]: Received SIGRTMIN+24 from PID 23832 (kill).
Feb 1 11:07:36 shop systemd[1]: Stopped User Manager for UID 1001.
Feb 1 11:07:36 shop systemd[1]: Removed slice User Slice of wp_user.
Feb 1 11:07:36 shop systemd[1]: apache2.service: Main process exited,
code=exited, status=1/FAILURE
Feb 1 11:07:36 shop apachectl[23842]: httpd (pid 20375?) not running
Feb 1 11:07:36 shop systemd[1]: apache2.service: Unit entered failed state.
Feb 1 11:07:36 shop systemd[1]: apache2.service: Failed with result
'exit-code'.
Feb 1 11:09:01 shop CRON[23872]: (root) CMD ( [ -x
/usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then
/usr/lib/php/sessionclean; fi)
Feb 1 11:09:01 shop systemd[1]: Starting Clean php session files...
Feb 1 11:09:01 shop systemd[1]: Started Clean php session files.
Feb 1 11:09:05 shop systemd[1]: Created slice User Slice of wp_user.
Feb 1 11:09:05 shop systemd[1]: Starting User Manager for UID 1001...
Feb 1 11:09:05 shop systemd[1]: Started Session 3180 of user wp_user.
Mantas Mikulėnas
2018-02-01 12:08:02 UTC
Reply
Permalink
Raw Message
Post by Simon Becks
Is this an expected behavior?
Debian 9 with systemd 232-25+deb9u1
Apache is running as user wp_user.
After logging in and logging out via sftp as user wp_user - systemd
kills apache process.
Feb 1 10:58:25 shop systemd: pam_unix(systemd-user:session): session
opened for user wp_user by (uid=0)
Feb 1 11:01:58 shop sshd[23747]: Connection closed by client-ip port
38409 [preauth]
Feb 1 11:07:36 shop sshd[23673]: Received disconnect from client-ip2
Feb 1 11:07:36 shop sshd[23673]: Disconnected from client-ip2 port 53274
Feb 1 11:07:36 shop sshd[23664]: pam_unix(sshd:session): session
closed for user wp_user
Feb 1 11:07:36 shop systemd-logind[480]: Removed session 3177.
Feb 1 11:07:36 shop systemd: pam_unix(systemd-user:session): session
closed for user wp_user
[Thu Feb 01 11:07:36.170606 2018] [mpm_prefork:emerg] [pid 20396]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170606 2018] [mpm_prefork:emerg] [pid 20910]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170624 2018] [mpm_prefork:emerg] [pid 20394]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170625 2018] [mpm_prefork:emerg] [pid 20393]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.170625 2018] [mpm_prefork:emerg] [pid 20408]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
[Thu Feb 01 11:07:36.175260 2018] [mpm_prefork:emerg] [pid 20407]
(43)Identifier removed: AH00144: couldn't grab the accept mutex
Child 20393 returned a Fatal error... Apache is exiting!
[Thu Feb 01 11:07:36.218914 2018] [:emerg] [pid 20375] AH02818: MPM
run failed, exiting
For users outside the "system account" UID range (usually 1–999), a logout
will cause systemd to clean up remaining "junk" such as SysV IPC resources.
(Those are unusual in that the OS doesn't automatically remove them after
the last process exits, unlike e.g. regular sockets...)

If you must give high UIDs to service accounts, set RemoveIPC=no in your
logind.conf.
--
Mantas Mikulėnas
Andrei Borzenkov
2018-02-01 18:42:58 UTC
Reply
Permalink
Raw Message
For users outside the "system account" UID range (usually 1–999), a logout
will cause systemd to clean up remaining "junk" such as SysV IPC resources.
Where is it documented?
Mike Gilbert
2018-02-01 19:00:30 UTC
Reply
Permalink
Raw Message
Post by Andrei Borzenkov
For users outside the "system account" UID range (usually 1–999), a logout
will cause systemd to clean up remaining "junk" such as SysV IPC resources.
Where is it documented?
In logind.conf(5).
Andrei Borzenkov
2018-02-01 19:02:03 UTC
Reply
Permalink
Raw Message
Post by Mike Gilbert
Post by Andrei Borzenkov
For users outside the "system account" UID range (usually 1–999), a logout
will cause systemd to clean up remaining "junk" such as SysV IPC resources.
Where is it documented?
In logind.conf(5).
Ah, thanks.

Loading...