setup/start/systemd/box.service

[Unit]
Description=Box
After=mysql.service nginx.service
; As cloudron-resize-fs is a one-shot, the Wants= automatically ensures that the service *finishes*
Wants=cloudron-resize-fs.service

[Install]
WantedBy=multi-user.target

[Service]
Type=idle
WorkingDirectory=/home/yellowtent/box
User=yellowtent
Group=yellowtent
Restart=always
ExecStart=/home/yellowtent/box/box.js
ExecReload=/bin/kill -HUP $MAINPID
; we run commands like df which will parse properly only with correct locale
Environment="HOME=/home/yellowtent" "USER=yellowtent" "BOX_ENV=cloudron" "NODE_ENV=production" "LC_ALL=C"
; this sends the main process SIGTERM and then if anything lingers to the control-group . this is also the case if the main process crashes.
; the box code handles SIGTERM and cleanups the tasks
KillMode=mixed
KillSignal=SIGTERM
TimeoutStopSec=5s
SendSIGKILL=yes
; Do not kill this process on OOM. Children inherit this score. Do not set it to -1000 so that MemoryMax can keep working
OOMScoreAdjust=-999
MemoryMax=400M
StartLimitInterval=1
StartLimitBurst=60
Move from supervisor to systemd This removes logrotate as well since we use systemd logging 2015-09-07 11:18:44 -07:00			`[Unit]`
box.service: change description 2025-06-17 22:28:38 +02:00			`Description=Box`
box.service: start after nginx 2017-01-25 11:28:27 -08:00			`After=mysql.service nginx.service`
rename the service to cloudron-resize-fs 2016-12-30 11:27:00 -08:00			`; As cloudron-resize-fs is a one-shot, the Wants= automatically ensures that the service finishes`
			`Wants=cloudron-resize-fs.service`
Move from supervisor to systemd This removes logrotate as well since we use systemd logging 2015-09-07 11:18:44 -07:00
cloudron.target is not needed 2020-08-01 20:00:20 -07:00			`[Install]`
			`WantedBy=multi-user.target`

Move from supervisor to systemd This removes logrotate as well since we use systemd logging 2015-09-07 11:18:44 -07:00			`[Service]`
			`Type=idle`
			`WorkingDirectory=/home/yellowtent/box`
tasks: fix update failed notification https://forum.cloudron.io/topic/13408/update-to-cloudron-8.3-error We get a Task xx crashed with code null in the notification. The crux of the issue is that we use KillMode=control-group. This ends up sending SIGTERM signal to box code and all the sudo in parallel. The box code then sees the sudo die and records the task as failed. To fix, we switch to KillMode=mixed. This gives box code a chance to handle SIGTERM first. It cleans out its task list and kills all the sudo. 2025-06-17 22:30:34 +02:00			`User=yellowtent`
			`Group=yellowtent`
Move from supervisor to systemd This removes logrotate as well since we use systemd logging 2015-09-07 11:18:44 -07:00			`Restart=always`
hardcode logging of box code to box.log 2020-08-04 09:34:03 -07:00			`ExecStart=/home/yellowtent/box/box.js`
Revert "Only use "kill" as done in the upstream docs" This reverts commit 829d53915d656891bb9d10bab243f09d8008107a. This breaks on Ubuntu 18 systemd[1]: /etc/systemd/system/unbound.service:12: Executable path is not absolute: kill -HUP $MAINPID 2023-03-29 11:18:44 +02:00			`ExecReload=/bin/kill -HUP $MAINPID`
Fix issue where df output is not parsed correctly LANG is the default locale i.e when LC_* are not specificall LC_ALL will override them all https://forum.cloudron.io/topic/4681/going-to-system-info-triggers-assertion-error 2021-03-17 11:10:47 -07:00			`; we run commands like df which will parse properly only with correct locale`
replace debug() with our custom logger mostly we want trace() and log(). trace() can be enabled whenever we want by flipping a flag and restarting box 2026-03-12 22:55:28 +05:30			`Environment="HOME=/home/yellowtent" "USER=yellowtent" "BOX_ENV=cloudron" "NODE_ENV=production" "LC_ALL=C"`
tasks: fix update failed notification https://forum.cloudron.io/topic/13408/update-to-cloudron-8.3-error We get a Task xx crashed with code null in the notification. The crux of the issue is that we use KillMode=control-group. This ends up sending SIGTERM signal to box code and all the sudo in parallel. The box code then sees the sudo die and records the task as failed. To fix, we switch to KillMode=mixed. This gives box code a chance to handle SIGTERM first. It cleans out its task list and kills all the sudo. 2025-06-17 22:30:34 +02:00			`; this sends the main process SIGTERM and then if anything lingers to the control-group . this is also the case if the main process crashes.`
			`; the box code handles SIGTERM and cleanups the tasks`
			`KillMode=mixed`
			`KillSignal=SIGTERM`
			`TimeoutStopSec=5s`
			`SendSIGKILL=yes`
Set OOMScoreAdjust to stop box code from being killed OOMScoreAdjust can be set between -1000 and +1000. This value is inherited and systemd has no easy way to control this for children (box code also runs as non-root, so it cannot easily set it for the children using /proc/<pid>/oom_score_adj. When set to -1000 and the process reaches the MemoryMax, it seems the kernel does not kill any process in the cgroup and it spins up in high memory. In fact, 'systemctl status <service>' stops displaying child process (but ps does), not sure what is happenning. Keeping it -999 means that if a child process consumed a lot of memory, the kernel will kill something in the group. If the main box itself is killed, systemd will kill it at all because of KillMode=control-group. Keeping it -999 also saves box service group being killed relative to other docker processes (apps and addons). Fixes #605 2019-01-06 19:16:53 -08:00			`; Do not kill this process on OOM. Children inherit this score. Do not set it to -1000 so that MemoryMax can keep working`
			`OOMScoreAdjust=-999`
			`MemoryMax=400M`
Try alternative configuration for systemd restart rate limit 2015-12-12 13:14:50 -08:00			`StartLimitInterval=1`
			`StartLimitBurst=60`
Move from supervisor to systemd This removes logrotate as well since we use systemd logging 2015-09-07 11:18:44 -07:00