Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • When you say "no error messages are report", are you looking in the serviio logs? Or the systemd logs? Commented Mar 18, 2016 at 5:47
  • @XiongChiamiov both. Serviio isn't being called by the init.d script for some reason, and when it runs it runs fine. The init.d script doesn't seem to be aware that the script it is calling is failing, so isn't generating any messages to systemd. Commented Mar 18, 2016 at 6:15
  • Try to add set -x somewhere to the top of the init script, and then try to start the service. This should give you some extended logging when you do; you can see the output with journalctl -u <init script name> -f. Commented Aug 20, 2018 at 9:44