subsonic stops

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.

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

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) ?

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:

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

Put the following lines BEFORE the above lines:

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:

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:

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

pkas wrote:

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. ... 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

Hi Phil - I would be interested to hear what he alternatives would be since unfortunately this didn't work for me on my Ultra 4 Plus :(

(In fact for me the light goes off not every night, but straight away / as soon as I refresh the browser)

Thanks

I have an ultra 4 plus also, so hopefully we can get this working for you.

By the way, I would not worry about the "light" ; it turns out that the light is not an accurate indication of whether the Subsonic server is running. The first thing we need to do is determine if Subsonic is running or not. To do this, you need to ssh into the ReadyNAS as root. Have you already installed the "Enable Root SSH Access" add-on? If not, then please do so.

For now, I will assume you are comfortable using Linux, ssh, bash, and etc. If you are not, let me know and I will provide more details.

We're going to see if the Subsonic server is running by looking for it in the running process list. So, do the following:
1) ssh into the ReadyNAS
2) type: ps aux | grep -i subsonic | grep java

Copy and paste what is returned and we'll take it from there.

pkas

pkas wrote:
I have an ultra 4 plus also, so hopefully we can get this working for you... Copy and paste what is returned and we'll take it from there. pkas

Thanks, I'll do this when I get back from travelling next week

for me, the workaround proposed by Phil / pkas works since some days
Thanks a lot !

pkas wrote:
We're going to see if the Subsonic server is running by looking for it in the running process list. So, do the following: 1) ssh into the ReadyNAS 2) type: ps aux | grep -i subsonic | grep java Copy and paste what is returned and we'll take it from there. pkas

OK, So when I left last week subsonic was running. When I got back apparently not.

Box2:~# ps aux | grep -i subsonic | grep java
Box2:~#

So I went back into frontview re-ticked the Subsonic add-on, clicked 'save', green light back on, and the pop-up 'Subsonic services started'. Clicked 'launch', but this time no subsonic (not found)

So back to ssh

Box2:~# ps aux | grep -i subsonic | grep java
root     24270 97.8 10.3 943356 104904 ?       Sl   17:26   1:22 /c/webroot/subsonic/jre1.6.0_20/bin/java -Xmx700m -Dsubsonic.home=/c/webroot/subsonic -Dsubsonic.host=0.0.0.0 -Dsubsonic.port=4040 -Dsubsonic.httpsPort=0 -Dsubsonic.contextPath=/ -Dsubsonic.defaultMusicFolder=/c/media/music -Dsubsonic.defaultPodcastFolder=/c/media/Podcast -Dsubsonic.defaultPlaylistFolder=/c/media/playlists -Djava.awt.headless=true -verbose:gc -jar subsonic-booter-jar-with-dependencies.jar
root     24408 12.8  4.5 878960 45948 ?        Sl   17:26   0:08 /c/webroot/subsonic/jre1.6.0_20/bin/java -Xmx700m -Dsubsonic.home=/c/webroot/subsonic -Dsubsonic.host=0.0.0.0 -Dsubsonic.port=4040 -Dsubsonic.httpsPort=0 -Dsubsonic.contextPath=/ -Dsubsonic.defaultMusicFolder=/c/media/music -Dsubsonic.defaultPodcastFolder=/c/media/Podcast -Dsubsonic.defaultPlaylistFolder=/c/media/playlists -Djava.awt.headless=true -verbose:gc -jar subsonic-booter-jar-with-dependencies.jar
Box2:~#

Tried launching again, and this time got:

HTTP ERROR: 503

SERVICE_UNAVAILABLE
RequestURI=/index.view

Powered by jetty://

Ok. well one thing that is wrong is that you have two instances running.

Via ssh, kill BOTH instances:

kill -9 24270
kill -9 24408

Then, copy and paste the following as a shell command (it is a SINGLE command)

/c/webroot/subsonic/jre1.6.0_20/bin/java -Xmx700m -Dsubsonic.home=/c/webroot/subsonic -Dsubsonic.host=0.0.0.0 -Dsubsonic.port=4040 -Dsubsonic.httpsPort=0 -Dsubsonic.contextPath=/ -Dsubsonic.defaultMusicFolder=/c/media/music -Dsubsonic.defaultPodcastFolder=/c/media/Podcast -Dsubsonic.defaultPlaylistFolder=/c/media/playlists -Djava.awt.headless=true -verbose:gc -jar subsonic-booter-jar-with-dependencies.jar

Do NOT use the launcher for now. Do NOT try to start or restart subsonic via FrontView. Just use the above command.

After executing the above command and before doing anything else, check to see if subsonic WORKS. Do NOT worry about FrontView. Instead, what you want to do is to use the ip address of your ReadyNAS and port 4040 as a URL. For example, if your ReadyNAS has an ip address of 192.168.1.101, then you would open a web browser and use the foilowing URL: 192.168.1.101:4040

So, go to that URL and let me know what you see.

Phil