Guest User

Hassbian

a guest
Sep 8th, 2018
74
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.24 KB | None | 0 0
  1. pi@hassbian:~ $ sudo systemctl status appdaemon@appdaemon.service
  2. ● appdaemon@appdaemon.service - AppDaemon
  3. Loaded: loaded (/etc/systemd/system/appdaemon@appdaemon.service; enabled; vendor preset: enabled)
  4. Active: failed (Result: exit-code) since Sat 2018-09-08 09:30:26 UTC; 10min ago
  5. Process: 2344 ExecStart=/usr/local/bin/appdaemon -c <full path to config directory> (code=exited, status=2)
  6. Main PID: 2344 (code=exited, status=2)
  7.  
  8. Sep 08 09:30:21 hassbian systemd[1]: Started AppDaemon.
  9. Sep 08 09:30:26 hassbian appdaemon[2344]: usage: appdaemon [-h] [-c CONFIG] [-p PIDFILE] [-t TICK] [-s STARTTIME]
  10. Sep 08 09:30:26 hassbian appdaemon[2344]: [-e ENDTIME] [-i INTERVAL]
  11. Sep 08 09:30:26 hassbian appdaemon[2344]: [-D {DEBUG,INFO,WARNING,ERROR,CRITICAL}] [-v] [-d]
  12. Sep 08 09:30:26 hassbian appdaemon[2344]: appdaemon: error: unrecognized arguments: path to config directory>
  13. Sep 08 09:30:26 hassbian systemd[1]: appdaemon@appdaemon.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  14. Sep 08 09:30:26 hassbian systemd[1]: appdaemon@appdaemon.service: Unit entered failed state.
  15. Sep 08 09:30:26 hassbian systemd[1]: appdaemon@appdaemon.service: Failed with result 'exit-code'.
  16. pi@hassbian:~ $
Add Comment
Please, Sign In to add comment