Bug #2007

App Server Feature

Added by bigfoot65 over 6 years ago. Updated over 6 years ago.

Target version:
Start date:
Due date:
% Done:



Is there a way to use the App Server Feature when a service is called something different when grepped?

For example, qbittorrent-nox is the name of the service, there is no PID file, but when grepping qbittorrent, it comes back as qbittorrent-nox-bin.

Was wondering if there is a way to catch this so watchdog would know the app is running and if a start, stop, or restart is needed from the Servers tab it could be done. Since the service is called qbittorrent-nox, that would be the monit piece. However when checking whether it's running, it would look for qbittorrent-nox/bin.

Related issues

Related to apps - Bug #2006: qBittorrent: Watchdog logs error and info to monit.log. Closed 03/15/2016


#1 Updated by bigfoot65 over 6 years ago

cpg response:

There are ways to go about this, however, without a PID file, monit cannot really do much about it.

as things move to systemd, we need to get away from monit. then build an interface from the servers page to the status in systemd. i am not sure what is the right api, but monit is just bursting at the seams.

does qbittorrent have a systemd service file?

#2 Updated by bigfoot65 over 6 years ago

There is a systemd service file. It uses the command-line qbittorrent-nox -d which executes a binary file called qbittorrent-nox-bin. When doing a grp on qbittorrent, that's what shows up and not qbittorrent-nox.

It would be nice if we could get away from monit. I think a custom interface specific to Amahi would be wonderful and easier to work with.

Also available in: Atom