Skip to content

mxstartupctl stop X did not stop X (systemd service unit) #9

Closed
pmenzel opened this issue Jan 5, 2022 · 2 comments
Closed

mxstartupctl stop X did not stop X (systemd service unit) #9

pmenzel opened this issue Jan 5, 2022 · 2 comments

Comments

@pmenzel
Copy link
Contributor

pmenzel commented Jan 5, 2022

$ grep eturnal /etc/mxstartups
eturnal		pitti	eturnprj	eturnal.service {net02}eturnal[80:11080][443:11443][3478:3478]

Despite running mxstartupctl stop eturnal the service wasn’t stopped.

@pitti:~$ sudo mxstartupctl stop eturnal
stopping /run/mariux/mxservice.eturnal.cfg.r ..
stopping /run/mariux/mxvip.eturnal.cfg.r ..
removing forward 141.14.19.6:3478 <-> 141.14.19.6:3478
removing forward 141.14.19.6:80 <-> 141.14.19.6:11080
removing forward 141.14.19.6:443 <-> 141.14.19.6:11443
removing ip 141.14.19.6/20 broadcast 141.14.31.255 to net02
@pitti:~$ sudo mxstartupctl start eturnal
starting /run/mariux/mxvip.eturnal.cfg ..
adding ip 141.14.19.6/20 broadcast 141.14.31.255 to net02
adding forward 141.14.19.6:3478 <-> 141.14.19.6:3478
adding forward 141.14.19.6:80 <-> 141.14.19.6:11080
adding forward 141.14.19.6:443 <-> 141.14.19.6:11443
starting /run/mariux/mxservice.eturnal.cfg ..
@pitti:~$ logout
Connection to pitti closed.
@geniux:~$ ssh eturnprj@pitti
[…]
eturnprj@pitti:~> systemctl status eturnal
● eturnal.service - eturnal STUN/TURN server
   Loaded: loaded (/etc/systemd/system/eturnal.service; static; vendor preset: enabled)
   Active: active (running) since Tue 2021-05-18 22:58:19 CEST; 7 months 17 days ago
     Docs: https://eturnal.net/documentation/
           https://github.com/processone/eturnal/blob/1.4.1/README.md
           https://github.com/processone/eturnal/blob/1.4.1/CHANGELOG.md
 Main PID: 62523 (beam.smp)
    Tasks: 84 (limit: 19660)
   Memory: 50.8M
   CGroup: /system.slice/eturnal.service
           ├─62523 /project/eturnal/eturnal-20210323/bin/eturnal -Bd -- -root /project/eturnal/eturnal-20210323 -progname project/eturnal/eturnal-2021
           ├─62561 /project/eturnal/eturnal-20210323/erts-11.1.8/bin/epmd -daemon
           ├─62565 erl_child_setup 50000
           ├─62643 inet_gethost 4
           └─62644 inet_gethost 4

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

The second attempt worked.

@pitti:~$ sudo strace -o /dev/shm/xxx.log mxstartupctl stop eturnal
stopping /run/mariux/mxservice.eturnal.cfg.r ..
stopping /run/mariux/mxvip.eturnal.cfg.r ..
removing forward 141.14.19.6:3478 <-> 141.14.19.6:3478
removing forward 141.14.19.6:80 <-> 141.14.19.6:11080
removing forward 141.14.19.6:443 <-> 141.14.19.6:11443
removing ip 141.14.19.6/20 broadcast 141.14.31.255 to net02
@pitti:~$ systemctl status eturnal
● eturnal.service - eturnal STUN/TURN server
   Loaded: loaded (/etc/systemd/system/eturnal.service; static; vendor preset: enabled)
   Active: inactive (dead)
     Docs: https://eturnal.net/documentation/
           https://github.com/processone/eturnal/blob/1.4.1/README.md
           https://github.com/processone/eturnal/blob/1.4.1/CHANGELOG.md
@donald
Copy link
Contributor

donald commented Jan 5, 2022

Maybe: If you didn't restart the service after you made it into a systemd service, /bin/true was used to stop it because mxstartup remembered the script that was used to start it in /run/mariux/mxservice.eturnal.cfg.

commit 0c03ecdc9d6b52a4b5cf3b9e56281509e36e1903
Author: Paul Menzel <pmenzel@molgen.mpg.de>
Date:   Sat May 22 17:13:34 2021 +0200

    mxstartups: Start eturnal via systemd service unit

diff --git a/src/mxstartups b/src/mxstartups
index 579bf0057..f7f984f83 100644
--- a/src/mxstartups
+++ b/src/mxstartups
@@ -567,7 +567,7 @@ crm  pitti  civicprj  /project/civicrm/startstop.sh {net02}crm[80:9010][443:9235
 
 converse       pitti   conveprj        /project/converse/startstop.sh {net02}converse[80:10080][443:10443]
 
-eturnal                pitti   eturnprj        /bin/true {net02}eturnal[80:11080][443:11443][3478:3478]
+eturnal                pitti   eturnprj        eturnal.service {net02}eturnal[80:11080][443:11443][3478:3478]
 

@pmenzel
Copy link
Contributor Author

pmenzel commented Jan 5, 2022

mxstartup/mxservicectl

Lines 44 to 51 in 608babf

case "${MX_SRV_SCRIPT}" in
*.service)
systemctl stop "${MX_SRV_SCRIPT}" || true
;;
*)
su - ${MX_SRV_USER} -c "${MX_SRV_SCRIPT} stop" &
;;
esac

Indeed, that would explain it, as the service was running since Tue 2021-05-18 22:58:19 CEST.

2022-01-04T17:50:09+01:00 pitti sudo:  pmenzel : TTY=pts/17 ; PWD=/home/X ; USER=root ; COMMAND=/usr/sbin/mxstartupctl stop eturnal
2022-01-04T17:50:09+01:00 pitti sudo: pam_unix(sudo:session): session opened for user root by X(uid=0)
2022-01-04T17:50:09+01:00 pitti su[13436]: Successful su for eturnprj by root
2022-01-04T17:50:09+01:00 pitti su[13436]: + ??? root:eturnprj
2022-01-04T17:50:09+01:00 pitti su[13436]: pam_unix(su:session): session opened for user eturnprj by (uid=0)
2022-01-04T17:50:09+01:00 pitti sudo: pam_unix(sudo:session): session closed for user root
2022-01-04T17:50:09+01:00 pitti su[13436]: pam_unix(su:session): session closed for user eturnprj

@pmenzel pmenzel closed this as completed Jan 5, 2022
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants