SOLVED: Apss not opening from Amahi Dashboard

[wyldeone]

Well back home from camping.

Had a look through a few log files, seems there's an issue with missing .pid files for couch potato and SABnzbd, i've attached a copy of monit & message log files from a reboot, not sure what im looking at so i thought it would be easier than cutting and pasting. I did fix a error with DLNA from the log file lol.

Cheers for the assistance

[bigfoot65]

When did you install these apps, recently? There were some minor changes made last week that you may have missed. Might consider uninstall and reinstalling SABnzbd Plus and CouchPotato.

If there are still issues, then we need to look at the app to see what might be going on.

[wyldeone]

I only install CP & SAB last week, but i have done the following.

1. Un-installed CP & SAB from Amahi Dashboard
2. Reset HDA
3. Installed CP & SAB from Amahi Dashboard.

at this point the CP & SAB servers were running under Settings/Servers.

here are logs
CP install log & Message Log

Code: Select all

======= app install begin @ 2013-12-23 08:54:19 +1100 ========== Installing app id r70fzy414f under /var/hda/platform/html ENV=production file /var/hda/tmp/amahi-download-cache/f0b53952130858a0cdab8b3a52f41320b6d11b2e picked up from cache. Your HDA services have been restarted. Your HDA services have been restarted. NOTE: file /tmp/amahi-download-cache/23682f9ec8dc3587c6c41d0882d4e6a9447337ba written in cache Installing couchpotato.service Reloading systemctl daemon Enabling couchpotato.service ln -s '/usr/lib/systemd/system/couchpotato.service' '/etc/systemd/system/multi-user.target.wants/couchpotato.service' Starting couchpotato.service App: CouchPotato installed ======= app install end @ 2013-12-23 08:54:55 +1100 ==========

Code: Select all

Dec 23 08:54:47 192-168-1-10 systemd[1]: Starting CouchPotato server... Dec 23 08:54:52 192-168-1-10 systemd[1]: couchpotato.service: Supervising process 27099 which is not our child. We'll most likely not notice when it exits. Dec 23 08:54:52 192-168-1-10 systemd[1]: Started CouchPotato server. Dec 23 08:54:55 192-168-1-10 systemd[1]: Reloading. Dec 23 08:54:55 192-168-1-10 systemd[1]: Started CouchPotato server. Dec 23 08:54:55 192-168-1-10 systemd[1]: Stopping Pro-active monitoring utility for unix systems... Dec 23 08:54:56 192-168-1-10 monit[27343]: monit daemon with pid [1115] killed Dec 23 08:54:56 192-168-1-10 systemd[1]: Starting Pro-active monitoring utility for unix systems... Dec 23 08:54:56 192-168-1-10 systemd[1]: Started Pro-active monitoring utility for unix systems. Dec 23 08:54:56 192-168-1-10 monit[27392]: Starting monit daemon with http interface at [localhost:2812]

SAB install log & Message Log

Code: Select all

======= app install begin @ 2013-12-23 09:01:19 +1100 ========== Installing app id l87u14kg9n under /var/hda/platform/html ENV=production file /var/hda/tmp/amahi-download-cache/6b15e7b86e6d1e9aa910b2af9d7a00f08749cb96 picked up from cache. Your HDA services have been restarted. Your HDA services have been restarted. Configuring Amahi settings Installing sabnzbd.service Reloading systemctl daemon Enabling sabnzbd.service ln -s '/usr/lib/systemd/system/sabnzbd.service' '/etc/systemd/system/multi-user.target.wants/sabnzbd.service' Starting sabnzbd.service App: SABnzbd Plus installed ======= app install end @ 2013-12-23 09:02:09 +1100 ==========

Code: Select all

Dec 23 09:01:58 192-168-1-10 systemd[1]: Reloading The Apache HTTP Server. Dec 23 09:01:59 192-168-1-10 systemd[1]: Reloaded The Apache HTTP Server. Dec 23 09:02:03 192-168-1-10 systemd[1]: PID file /var/run/sabnzbd/sabnzbd-25915.pid not readable (yet?) after start. Dec 23 09:02:05 192-168-1-10 systemd[1]: Started SABnzbd Plus server. Dec 23 09:02:08 192-168-1-10 systemd[1]: Reloading. Dec 23 09:02:09 192-168-1-10 systemd[1]: Started SABnzbd Plus server. Dec 23 09:02:09 192-168-1-10 systemd[1]: Stopping Pro-active monitoring utility for unix systems... Dec 23 09:02:09 192-168-1-10 monit[10799]: monit daemon with pid [27392] killed Dec 23 09:02:10 192-168-1-10 systemd[1]: Starting Pro-active monitoring utility for unix systems... Dec 23 09:02:10 192-168-1-10 systemd[1]: Started Pro-active monitoring utility for unix systems. Dec 23 09:02:10 192-168-1-10 monit[10875]: Starting monit daemon with http interface at [localhost:2812]

I then proceeded to reboot the HDA, now CP & SAB are now not running and get the following from the monit log

Code: Select all

[LHST Dec 23 11:52:47] error : 'sabnzbd' process is not running [LHST Dec 23 11:52:47] info : 'sabnzbd' trying to restart [LHST Dec 23 11:52:47] info : 'sabnzbd' start: /usr/bin/systemctl [LHST Dec 23 11:53:17] error : 'sabnzbd' failed to start [LHST Dec 23 11:53:17] error : 'couchpotato' process is not running [LHST Dec 23 11:53:17] info : 'couchpotato' trying to restart [LHST Dec 23 11:53:17] info : 'couchpotato' start: /usr/bin/systemctl

and from message log

Code: Select all

Dec 23 11:42:47 localhost systemd[1]: Failed to start CouchPotato server. Dec 23 11:42:47 localhost systemd[1]: Unit couchpotato.service entered failed state. Dec 23 11:42:50 localhost systemd[1]: PID file /var/run/sabnzbd/sabnzbd-25915.pid not readable (yet?) after start. Dec 23 11:43:17 localhost systemd[1]: Starting CouchPotato server... Dec 23 11:43:19 localhost systemd[1]: PID file /var/run/couchpotato/couchpotato.pid not readable (yet?) after start. Dec 23 11:44:17 localhost systemd[1]: sabnzbd.service operation timed out. Terminating. Dec 23 11:44:17 localhost systemd[1]: Failed to start SABnzbd Plus server. Dec 23 11:44:17 localhost systemd[1]: Unit sabnzbd.service entered failed state. Dec 23 11:44:47 localhost systemd[1]: couchpotato.service operation timed out. Terminating. Dec 23 11:44:47 localhost systemd[1]: Starting SABnzbd Plus server... Dec 23 11:44:47 localhost systemd[1]: Failed to start CouchPotato server. De11:42:17 localhost systemd[1]: Unit sabnzbd.service entered failed state. Dec 23 11:42:47 localhost systemd[1]: couchpotato.service operation timed out. Terminating. c 23 11:44:47 localhost systemd[1]: Unit couchpotato.service entered failed state.

Hope this is enough info.

[bigfoot65]

Yes, please check the ownership of the /var/run/sabnzbd and /var/run/couchpotato directories and display them here.

It could be a permissions issue causing them not to start on reboot. I will try to do some testing here too.

[bigfoot65]

Think I am on to something, just trying to figure it out. Appears when you reboot, the /var/run/sabnzbd and /var/run/couchpotato directories disappear. That is preventing the pid file from being written and thus causing the issues I believe.

I am working on a solution now to see if it will correct this problem.

[wyldeone]

With the above info i have done the following.

Created folders /var/run/sabnzbd and /var/run/couchpotato, from there i have set owner to Apache, PID files were then automatically created and dashboard reports both servers running.

Rebooting HDA the folder have now disappeared and dashboard reports servers are stopped.

[bigfoot65]

Yes that is the behavior I am trying to change. It should not be removing the folders, but does for some reason. Hope to have a solution soon.

[wyldeone]

No Rush Bigfoot its christmas

Just glad we found the cause.

Merry Xmas

[bigfoot65]

Thanks and same to you. I won't have a chance to do much until after the holidays.

[wyldeone]

Bigfoot

All the best for 2014.

Have you managed to have a look at this little problem yet?

Cheers