bitnode runs slack-invite.service so that the slack invite link on bitraf.no works. Today that service had stopped, but state was not 'failed' but 'exited'
tingo@bitnode:~$ systemctl status slack-invite.service
● slack-invite.service
Loaded: loaded (/etc/init.d/slack-invite; generated; vendor preset: enabled)
Active: active (exited) since Fri 2019-06-28 02:38:51 CEST; 3 months 18 days ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0
Memory: 0B
CPU: 0
CGroup: /system.slice/slack-invite.service
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
the reason might be because of a full disk (see #134), or something else.
A restart fixed the problem (after cleaning to get space on the disk)
tingo@bitnode:~$ sudo systemctl restart slack-invite.service
tingo@bitnode:~$ systemctl status slack-invite.service
● slack-invite.service
Loaded: loaded (/etc/init.d/slack-invite; generated; vendor preset: enabled)
Active: active (running) since Tue 2019-10-15 16:50:10 CEST; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 27095 ExecStop=/etc/init.d/slack-invite stop (code=exited, status=1/FAILURE)
Process: 27108 ExecStart=/etc/init.d/slack-invite start (code=exited, status=0/SUCCESS)
Tasks: 12
Memory: 50.9M
CPU: 1.244s
CGroup: /system.slice/slack-invite.service
├─27121 /usr/bin/nodejs /usr/local/lib/node_modules/forever/bin/monitor bin/www
└─27136 /usr/bin/nodejs /home/bitweb/slack-invite/bin/www
Oct 15 16:50:09 bitnode systemd[1]: Stopped slack-invite.service.
Oct 15 16:50:09 bitnode systemd[1]: slack-invite.service: Unit entered failed state.
Oct 15 16:50:09 bitnode systemd[1]: slack-invite.service: Failed with result 'exit-code'.
Oct 15 16:50:09 bitnode systemd[1]: Starting slack-invite.service...
Oct 15 16:50:09 bitnode runuser[27108]: pam_unix(runuser:session): session opened for user nodejs by (uid=0)
Oct 15 16:50:10 bitnode slack-invite[27108]: warn: --minUptime not set. Defaulting to: 1000ms
Oct 15 16:50:10 bitnode slack-invite[27108]: warn: --spinSleepTime not set. Your script will exit if it does no
Oct 15 16:50:10 bitnode slack-invite[27108]: info: Forever processing file: bin/www
Oct 15 16:50:10 bitnode runuser[27108]: pam_unix(runuser:session): session closed for user nodejs
Oct 15 16:50:10 bitnode systemd[1]: Started slack-invite.service.
Perhaps thsi service should be rewritten so it fails instead of exiting?
bitnode runs slack-invite.service so that the slack invite link on bitraf.no works. Today that service had stopped, but state was not 'failed' but 'exited'
the reason might be because of a full disk (see #134), or something else. A restart fixed the problem (after cleaning to get space on the disk)
Perhaps thsi service should be rewritten so it fails instead of exiting?