Couchpotato Errors on systemd-journal.log

I am not seeing a very good anwer to this issue as of yet. There are two things that could "work".

1) The current method where you get the errors from systemd.

The errors occur from system when there has been a fork in the process and the service attempts to start. Each attempt to start the service will try 5 times. You could work around it by "Shutdown" from the CouchPotato UI. This would end the process completely preventing the conflicts from systemd. The errors would not comback till there is another "Restart" from CouchPotato UI. The restart could be triggered from the UI or an (auto)update.

I will reach out to the CouchPotato dev to see if he has looked into the restart signalling to help prevent this issue.

2) systemd's and CouchPotato's recommends an alternative configuration

The configuration is very clean and I would like to use it, but once you run the "Restart" from CouchPotato UI or run the update from CouchPotato; it would be in the shut off state. You would then just go into the ReadyNAS Admin page to turn the CouchPotato app back on.

Here is what the configuration would look like with the 2nd option:

[Unit]
Description=CouchPotato application instance
After=network.target

[Service]
ExecStart=/usr/bin/python /apps/couchpotato/CouchPotato.py --data_dir=/apps/couchpotato/app-config
Type=simple
Nice=18
User=admin
Group=admin

[Install]
WantedBy=multi-user.target

The auto updates are nice, but since the development on that project is slower than some others.... the option two might be a good option to look at.

bedlam1 did you want to try that systemd config out?

Did you need instructions or a quick test build using that config?