Misskey: systemd not working

Created on 23 Dec 2020 · 4Comments · Source: syuilo/misskey

💡 Summary

Misskey have been installed successfully but cannot be run with systemd.
It can be started normally with NODE_ENV=production npm start

🙂 Expected Behavior

● misskey.service - Misskey daemon
   Loaded: loaded (/etc/systemd/system/misskey.service; disabled; vendor preset: disabled)
   Active: active

☹️ Actual Behavior

● misskey.service - Misskey daemon
   Loaded: loaded (/etc/systemd/system/misskey.service; disabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Wed 2020-12-23 16:45:43 CST; 6s ago
  Process: 5473 ExecStart=/usr/bin/npm start (code=exited, status=203/EXEC)
 Main PID: 5473 (code=exited, status=203/EXEC)

Dec 23 16:45:43 host systemd[1]: misskey.service: main process exited, code=exited, status=203/EXEC
Dec 23 16:45:43 host systemd[1]: Unit misskey.service entered failed state.
Dec 23 16:45:43 host systemd[1]: misskey.service failed.
Dec 23 16:45:43 host systemd[1]: misskey.service holdoff time over, scheduling restart.
Dec 23 16:45:43 host systemd[1]: Stopped Misskey daemon.
Dec 23 16:45:43 host systemd[1]: start request repeated too quickly for misskey.service
Dec 23 16:45:43 host systemd[1]: Failed to start Misskey daemon.
Dec 23 16:45:43 host systemd[1]: Unit misskey.service entered failed state.
Dec 23 16:45:43 host systemd[1]: misskey.service failed.

📝 Steps to Reproduce

https://github.com/syuilo/misskey/blob/develop/docs/setup.en.md#launch-with-systemd

📌 Environment

↓misskey.service↓

[Unit]
Description=Misskey daemon

[Service]
Type=simple
User=misskey
ExecStart=/usr/bin/npm start
WorkingDirectory=/home/misskey/misskey
Environment="NODE_ENV=production"
TimeoutSec=60
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=misskey
Restart=always

[Install]
WantedBy=multi-user.target

The workingDirectory and ExecStart were correct

⚠️bug?

Source

LCinHK

All 4 comments

Try cd /home/misskey/misskey and npm start manually and give me the log, please?

Xeltica on 23 Dec 2020

Try cd /home/misskey/misskey and npm start manually and give me the log, please?

]$ npm start

> [email protected] start /home/misskey/misskey
> node ./index.js

  _____ _         _           
 |     |_|___ ___| |_ ___ _ _ 
 | | | | |_ -|_ -| '_| -_| | |
 |_|_|_|_|___|___|_,_|___|_  |
 v12.63.0                |___|

 Misskey is an open-source decentralized microblogging platform.
 If you like Misskey, please donate to support development. https://www.patreon.com/syuilo

--- oranme557.1024.721 (PID: 20244) ---
INFO *  [core boot]     Welcome to Misskey!
INFO *  [core boot]     Misskey v12.63.0
INFO *  [core boot env] NODE_ENV is not set
WARN *  [core boot env] The environment is not in production mode.
WARN *  [core boot env] DO NOT USE FOR PRODUCTION PURPOSE!
INFO *  [core boot env] You do not have root privileges
VERB *  [core boot machine]     Hostname: oranme557.1024.721
VERB *  [core boot machine]     Platform: linux Arch: x64
VERB *  [core boot machine]     CPU: 2 core MEM: 1.0GB (available: 0.6GB)
INFO *  [core boot nodejs]      Version 14.15.3
DONE *  [core boot config]      Loaded
INFO *  [core boot db]  Connecting...
DONE *  [core boot db]  Connected: v13.0
DONE *  [core boot]     Misskey initialized
INFO *  [core boot]     Starting 1 worker...
VERB *  [core cluster]  Process forked: [1]
VERB *  [core cluster]  Process is now online: [1]
DONE *  [core boot]     All workers started
DONE *  [core boot]     Now listening on port 12450 on https://domain

LCinHK on 23 Dec 2020

👀2

Make sure that /usr/bin/npm exists just in case.