After performing a backup of Shares 1.9 or when upgrading to Shares 1.9 on Linux, you may encounter the issue where services like NginX are unable to start.
During a normal upgrade or backup, Shares changes its runlevel to setup, and once the procedure is finished changes the runlevel back to up. If there was an issue during the backup or upgrade, the Shares runlevel may have never been switched back to up, which prevents services like NginX from running.
In order to check if your Shares runlevels are stuck on setup, run the following command:
ls -l /opt/aspera/shares/etc/runit/runlevels
The current directory should be pointing to up. If current is pointing to setup, you will need to change the runlevel to up yourself. Do not change the symlinks manually. Instead, use the following command:
Your Shares services should now be able to start as normal.