NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Subsonic 4.5.04 --Crashing
For me, instability in the Subsonic plugin has been occurring since version 1.9. The current and previous plugins crash regularly over time or upon restarting my pioneer-pro. If, after the plugin has crashed, it is manually disabled and re-enabled, it will either crash again soon after or refuse to restart and require removal/reinstallation of the plugin..
When this stability issue first appeared in v1.9, it was addressed with a patch by forum member Thoto, found here.
In that thread, Super-poussin, the plugins developer, stated that he would incorporate the patch into the next release, which would have been v2.0.00, but upon updating to radiator 4.2.17 and all the way through 4.2.19, the plugin continues crashing in subsonic v2.0.00 and all subsequent versions, including the current v4.5.04.
Furthermore, Thoto's patch no longer appears to have an affect on the stability of subsonic in either v4.5.03 or 4.5.04 w/ ffmpeg v1.2 or 1.3.
@super-poussin, is there anything I/we can do to help get a stable build of this plugin?
Over the past six-months, I've been unable to make use of the plugin due to the lack of stability. I've already donated but I understand that your time/resources may still be limited. Please let me what it would take to get a stable version of this plugin; name your price and I will pay it!
When this stability issue first appeared in v1.9, it was addressed with a patch by forum member Thoto, found here.
In that thread, Super-poussin, the plugins developer, stated that he would incorporate the patch into the next release, which would have been v2.0.00, but upon updating to radiator 4.2.17 and all the way through 4.2.19, the plugin continues crashing in subsonic v2.0.00 and all subsequent versions, including the current v4.5.04.
Furthermore, Thoto's patch no longer appears to have an affect on the stability of subsonic in either v4.5.03 or 4.5.04 w/ ffmpeg v1.2 or 1.3.
@super-poussin, is there anything I/we can do to help get a stable build of this plugin?
Over the past six-months, I've been unable to make use of the plugin due to the lack of stability. I've already donated but I understand that your time/resources may still be limited. Please let me what it would take to get a stable version of this plugin; name your price and I will pay it!
21 Replies
Replies have been turned off for this discussion
TeknoJnky wrote: yes its megs, do you have search index auto scan on?
I'm not familiar with this setting. Please describe where and how it may be accessed.- from the subsonic web management, log in as an administrator, settings > search > automatically update search index
fwiw, im running 4.2.17 on pro, 4.2.20 beta t4 on u4 - Now that I've got a cron job checking if subsonic needs to be restarted every 15 minutes, I find that it needs restarting on the first try after the cron.daily job runs. Looking at the scripts in /etc/cron.daily/* I suspect it is logtruncate. It does a lot of kills and also restarts apache. Maybe one of those causes the restart. I ran logtruncate manually though and it didn't do it so I may be wrong about which script it is.
steve TeknoJnky wrote: I can confirm that 4.5.04 addon green light does not stay on, but the subsonic service itself has been running fine on my pro.
You can fix the status indicator by changing /etc/frontview/addons/bin/SUBSONIC/running.sh as follows:
Change from:if ! ps -ef | grep "/subsonic-booter-jar-with-dependencies.jar" | grep -v grep &> /dev/null; then
exit 1
fi
Change to:if ! ps -ef | grep "subsonic-booter-jar-with-dependencies.jar" | grep -v grep &> /dev/null; then
exit 1
fi
The only difference is removal of the "/" before the word subsonic. Hopefully this fix can be included in the next release, as it seems like a pretty easy (and compatible) change.dsm1212 wrote: Now that I've got a cron job checking if subsonic needs to be restarted every 15 minutes, I find that it needs restarting on the first try after the cron.daily job runs. Looking at the scripts in /etc/cron.daily/* I suspect it is logtruncate. It does a lot of kills and also restarts apache. Maybe one of those causes the restart. I ran logtruncate manually though and it didn't do it so I may be wrong about which script it is.
steve
Just following up. subsonic crashes every night after the cron.daily script runs ONLY if it was started from frontview. Once my cron job restarts it, then it doesn't crash again until the system reboots or I stop/start from frontview. There is something in cron.daily that signals or restarts a frontview process (apache?) in a way that causes subsonic to go down. Once it's a child of cron, it's not a problem anymore. Maybe this can help someone track down the cause and fix it.
steve- Any chance you can post your band-aid?
- Sure, I added this to /etc/crontab:
5,20,35,50 * * * * root /c/home/Steve/ReadyNAS/subcheck.sh
And this is the contents of subcheck.sh:
#!/bin/sh
if [ "$(ps -ef | grep subsonic | grep java | wc -l)" = "0" ]
then
date >> /var/log/subcheck.log 2>&1
/c/webroot/subsonic/subsonic.sh >> /var/log/subcheck.log 2>&1
fi
You can look at /var/log/subcheck.log to see if it ever got restarted and when. There is probably a simpler command to see if it is running. Apparently the frontview addon suite includes one, but this was before I ready about that and it works so...
steve - Thank you! The equivalent using the logic from the frontview addon would be
if ! ps -ef | grep "subsonic-booter-jar-with-dependencies.jar" | grep -v grep &> /dev/null; then
but I think yours works just as well. I'm adding the same... - I installed this script and it kinda sorta works.
If I run subcheck.sh manually as root it works fine. But if I run it from /etc/crontab, the process restarts but the web server doesn't come up. Instead, I get
"
HTTP ERROR: 503
SERVICE_UNAVAILABLE
RequestURI=/index.view
Powered by jetty://
"
So there's some difference between what happens when I run a script manually vs what happens when it's run from crontab. I want to guess it's some sort of missing environment variable, but that's just a guess.
How do I troubleshoot this? - OK, I seem to have fixed but I'm not sure how. I ended up with:
/etc/crontab:
5,20,35,50 * * * * root /c/webroot/subsonic/subcheck2.sh
and subcheck2.sh is:
#!/bin/sh
echo "Starting subchck" >> /var/log/subcheck.log 2>&1
if [ "$(ps -ef | grep subsonic | grep java | wc -l)" = "0" ]
then
echo "Inside ifloop, subchck" >> /var/log/subcheck.log 2>&1
date >> /var/log/subcheck.log 2>&1
/etc/frontview/addons/bin/SUBSONIC/start.sh
fi
They key is calling /etc/frontview/addons/bin/SUBSONIC/start.sh, which as far as I can figure out is the shell script that starts up subsonic when the box boots.
This seems to work (so far!) where the other script didn't. Not sure why, don't care much.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
