subsonic stops

[ludwich]

My subsonic stops working every morning now after the new update =( I had the same problem before but there was a patch that made it work but now it stops every morning even when i dont restart the nas =( ... Anyone else who have the same issue ? And if i have it running and restart the nas it stops aswell =( this sucks

Well solved it by downgrading it back to 2.0

[acweb]

I am also seeing this issue...

[super-poussin]

did you try the last beta ?

[gibxxi]

Your probably already aware of this Super, but the add-on active light in Frontview doesn't stay lit when Subsonic is running (Latest Beta). Exactly the Opposite of transmission (Where the checkbox doesn't stay selected).

[acweb]

Yes I am using the latest beta v4.7.02

Thanks for your reply.

[super-poussin]

Your probably already aware of this Super, but the add-on active light in Frontview doesn't stay lit when Subsonic is running (Latest Beta). Exactly the Opposite of transmission (Where the checkbox doesn't stay selected).

let me check why

[ludwich]

Also using the latest beta but it stops at the same time every morning 7.15. Thats when i used to have it to power up but nowadays its up all the time so i removed thoose settings but it still keeps stoping =(

[gibxxi]

No issues with the latest version for me. My library is only 10,000 tracks large though. A medium sized library compared to some others on here. You may want to edit the config files for Subsonic and increase it's memory allocation, that has been proven to increase stability for some. Or see if the scan is interfering with another operation that's occuring at the same time. Try scheduling the daily update to a different time of day and see if that causes it to not stop.

[greee]

I have the same issue since I apply the last update (4.7 beta 2) on my readynas NVX
Please Super Poussin, can you do an update or patch ?

[Ping]

I have encountered the same problem after some adding and deleting files in my NAS two weeks ago. I have done many things trying to make it work again, turning it on and off for many times, reinstall it using either the 2.0 or 4.7 versions. They all did not work and it still crashed. Finally, I re-installed the subsonic 2.0, then updated it to 4.7 beta version. I could launch the page even the green light is not on. I disabled the automatic media re-scanning and I disabled the Podcast re-scanning button. I re-installed the ReadyNAS firmware by pressing the reset button with a clip and power on button for 5 seconds. The problem solved and subsonic won't crash anymore for the past 2 days. I hope that can solve the problem.

[greee]

hello ping.
WAOU, it is quite a violent respond to a software bug.
I hope and wait for Super Poussin (please!!!) to find a softer way (patch or new release) ; even if it's a really annoying bug during holidays (when you especially want to listen to your music from a far distance from home). But maybe Super Poussin is also under the sun somewhere far away from his computer

[Ping]

Hi greee,

I use my subsonic app in my android phone all the time, I have to get it fix as soon as possible. It's already 3 days since I re-install the Netgear NAS firmware, apparently it won't crash anymore. Hope that Super Possin will solve this problem soon as this may recur later if I do the updating.

[greee]

I was happy to see some days ago that a new version of subsonic is out (v4.7.03)
Unfortunatly, this does NOT correct this bug, subsonic service seems to stop everynight
In readynas web interface, the pluggin is noted activated but doesn(t work in reality
The only way i find is to stop/start it
note : when I try to stop it, an error apperars (erreur stopping service subsonic), strat is OK
Can someone look about it and tell what kind of correction we can have please !!
Thanks in addvabce

[greee]

is it possible to run a little script that will start subsonic at a precise time everyday.
Does someone know how to write this on readynas (with ssh I guess) ?

[pkas]

I have a ReadyNAS Ultra 4+, and I have the subsonic server running on it. Everything worked great until a few days ago -- I can't be sure, though, if what I am about to describe only started after I upgraded the subsonic server from 4.7.02 to 4.7.03.

Every morning the subsonic service is no longer running. It turns out, that the readyNAS has a daily cron job -- and the service stops as a result of the cron job. I walked though the daily cron, and found that this one command causes the subsonic service to stop:

start-stop-daemon -K -n apache-ssl -R 5; /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf

The above line has two commands; the first command (start-stop-daemon -K -n apache-ssl -R 5) is what causes the subsonic service to stop.

Here's how I am working around the problem. You need to be able to ssh into the ReadyNAS, as root, so that you can modify /etc/cron.daily/logtruncate. Find the following lines in /etc/cron.daily/logtruncate:

Code: Select all

foreach my $cmd (keys %restart) {
  system("$cmd");
}


Put the following lines BEFORE the above lines:

Code: Select all

my $subsonic = `ps aux | grep onic | grep jar | grep -v grep | sed -r -e 's/ +/ /g' | cut -f 11- -d ' '`; # PKAS
chomp($subsonic); # PKAS


And put the following lines after the original lines:

Code: Select all

my $isSubsonicStillThere =  `ps aux | grep onic | grep jar | grep -v grep`; # PKAS
if ($subsonic && $isSubsonicStillThere !~ /jar/) { # PKAS
  print "Restarting subsonic\n"; # PKAS
  system("cd /c/webroot/subsonic \&\& rm -f nohup.out \&\& nohup $subsonic 2>\&1 >/dev/null \&"); # PKAS
} # PKAS


In the end, this is what the section of code should look like:

Code: Select all

my $subsonic = `ps aux | grep onic | grep jar | grep -v grep | sed -r -e 's/ +/ /g' | cut -f 11- -d ' '`; # PKAS
chomp($subsonic); # PKAS

foreach my $cmd (keys %restart) {
  system("$cmd");
}
my $isSubsonicStillThere =  `ps aux | grep onic | grep jar | grep -v grep`; # PKAS
if ($subsonic && $isSubsonicStillThere !~ /jar/) { # PKAS
  print "Restarting subsonic\n"; # PKAS
  system("cd /c/webroot/subsonic \&\& rm -f nohup.out \&\& nohup $subsonic 2>\&1 >/dev/null \&"); # PKAS
} # PKAS


I considered alternative approaches - such as just adding a cron job to see if subsonic is still running, regardless of why it stops. I might switch to that approach, because it would decouple the logtruncate script from subsonic, but for now I am using the approach shown above.

Phil