Home

ReadyNAS Sickrage App

There has been some questions on the ReadyNAS Sickrage App, so documenting some of the questions that have come up in the wiki.

Note: These notes are for users in cli or ssh that are having troubles in getting to the web interface.

Configuration

The configuration on the ReadyNAS App is running based on the default as the Sickrage's default.

ReadyNAS prefers things in the /apps/ directory:

Bin dir:      /apps/sickrage/
Config file:  /apps/sickrage/app-config/config.ini
Logs:         /apps/sickrage/app-config/Logs/
Address:      http://${nas_ip}:8081/
PID file:     /var/run/sickrage.pid

Troubleshooting

systemd status

ReadyNAS runs services via systemd and you can gather the app's current status with the systemctl status fvapp-sickrage command.

Example:

# systemctl status fvapp-sickrage
fvapp-sickrage.service - Service for sickrage app
          Loaded: loaded (/lib/systemd/system/fvapp-sickrage.service; enabled)
          Active: active (running) since Sun, 26 Jun 2016 21:21:40 -0700; 6 days ago
         Process: 32399 ExecStart=/usr/bin/python /apps/sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/apps/sickrage/app-config --config=/apps/sickrage/app-config/config.ini --pidfile=/var/run/sickrage.pid (code=exited, status=0/SUCCESS)
        Main PID: 32409 (python)
          CGroup: name=systemd:/system/fvapp-sickrage.service
                  └ 32409 /usr/bin/python /apps/sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/apps/sickrage/app-config --config=/apps/sickrage/app-config/config.ini --pidfile=/var/run/sickrage.pid

Loaded

Loaded: loaded (/lib/systemd/system/fvapp-${readynas_app}.service; enabled)

• enabled - Service will start on bootup
• disabled - Service will not start on bootup

(Note: The ReadyNAS may handle the status separately and may handle the status different than other systemd services.)

Active

Active: active (running) since *${start_timestamp}; ${uptime}

• active (running) - Currently running (and healthy)
  • Turned on and good to go!
• activating (start) - Starting the process
  • There is a timeout period for about 2 minutes. (Be patient.)
  • In extreme cases when the unit is under load to time out and not start the application.
  • Gathering the logs better helps determine the application's state.
• inactive (dead) - Stopped service
  • The application is turn off; please turn on the application.
• failed (broken) - Not successfully able to execute/run
  • This has been seen in early development and should be fix. Logs will be needed in these scenarios.

Process

Process: ${pid} ExecStart=${Executable} (code=exited, status=0/SUCCESS)

• status=0/SUCCESS - Program status successful
• status=1/FAILURE - Program status failed

(These normally should cordinate with the Loaded part. The status=1/FAILURE will require logs to better understand the issue.)

Example (starting process):

# systemctl status fvapp-sickrage
fvapp-sickrage.service - Service for sickrage app
Loaded: loaded (/lib/systemd/system/fvapp-sickrage.service; enabled)
 Active: activating (start) since Wed, 01 Jun 2016 18:23:38 +1000; 3s ago Main PID: 5199 (code=killed, signal=KILL);
 Control: 15992 (python)
 CGroup: name=systemd:/system/fvapp-sickrage.service
 └ 15992 /usr/bin/python /apps/sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/apps/sickrage/app-config --config=/apps/sickrage/app-config/config.ini --pidfile=/var/run/sickrage.pid

Logs

Sickrage log location:

cat /apps/sickrage/app-config/Logs/sickrage.log

Systemd logs:

The systemctl status normally provides some information from the systemd logs.

systemctl status fvapp-${readynas_app}.service

In the event you are not able to see the logs from the systemctl status, you will need to pull it from the journald. Getting the last 10 lines normally will be enough for what is needed:

journalctl -a --no-pager _SYSTEMD_UNIT=fvapp-sickrage.service | tail -n 10