NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
minidlna doesn't start automatically
Hy guys,
I've a Readynas NVX+ (x86) with RAIDiator 4.2.21.
Since several times I see when I start my NAS, the ReadyDLNA server doesn't start automatically. I tried to upgrade the module with the last one found on this forum but the problem still !
When I'm connecting to the frontview on the appropriate webpage, I see that the service has to be launch, when I uncheck and click on apply, the server return an error "there is a problem when stopping the service", which (on my point of view) is normal because the minidlna server is not started...
After if I recheck the service and click on apply, the service start.
Now when I check my NAS just after the power on directly on the ssh shell, I see that the minidlna server didn't start, all the trouble seems to be here ! I would check the initscript, but I don't find the one that should be use to start the server ...
Any help ?
(temporary fixed, I push in /etc/rc.local the server) but it's not the right way to solve the problem ...
Thks
Renaud
I've a Readynas NVX+ (x86) with RAIDiator 4.2.21.
Since several times I see when I start my NAS, the ReadyDLNA server doesn't start automatically. I tried to upgrade the module with the last one found on this forum but the problem still !
When I'm connecting to the frontview on the appropriate webpage, I see that the service has to be launch, when I uncheck and click on apply, the server return an error "there is a problem when stopping the service", which (on my point of view) is normal because the minidlna server is not started...
After if I recheck the service and click on apply, the service start.
Now when I check my NAS just after the power on directly on the ssh shell, I see that the minidlna server didn't start, all the trouble seems to be here ! I would check the initscript, but I don't find the one that should be use to start the server ...
Any help ?
(temporary fixed, I push in /etc/rc.local the server) but it's not the right way to solve the problem ...
Thks
Renaud
10 Replies
Replies have been turned off for this discussion
- Hi
For those in that case I fixed it creating the initscript from http://zeldor.biz/2012/01/dlna-minidlna-on-debian/
And using the first command to add the iniscript at the right runlevel. manda wrote: Hi
For those in that case I fixed it creating the initscript from http://zeldor.biz/2012/01/dlna-minidlna-on-debian/
And using the first command to add the iniscript at the right runlevel.
Can you tell me the exact command to put the script in the RIGHT runlevel? i've tried without luck.
Thanks,
Alessio- Hi Agessio,
Well netgear has completely override all startup routine.
on my NAS the current runlevel is:
readynasnvx:~# who -r
run-level 2 2012-07-25 09:57 last=S
So in fact after creating the initscript from the previous website, I added into /etc/rc2.d/S01readynas_startup :
echo -n "Starting DLNA server" >$OUT
/usr/sbin/minidlna -f /etc/minidlna.conf
echo "." >$OUT
However this modification will probably not survive to an firmware upgrade :(
Regards,
Renaud - Hi Renaud,
I've already tried that, i've added the command in that script but, still, after reboot, no minidlna process active
nas:~# ps -ef | grep minidlna | grep -v grep
nas:~#
I've even created a script called minidlna in /etc/init.d as the post you suggested and added it to rcupdate-rc.d minidlna defaults
but nothing, at reboot doesn't start.
If I launch it manually obviously it starts.
Any idea?
Thank you very much,
Alessio
P.S.
Same runlevel than yourswho -r
run-level 2 Jul 26 07:30 last=S - When enabled in Frontview ReadyDLNA should start automatically. Rather than trying to setup some 3rd party workaround I would think it would be best to contact support and seek their assistance. You could open a case at my.netgear.com and post the case number.
mdgm wrote: When enabled in Frontview ReadyDLNA should start automatically. Rather than trying to setup some 3rd party workaround I would think it would be best to contact support and seek their assistance. You could open a case at my.netgear.com and post the case number.
You're right, that should work, but it's not .... I would prefer to have a fix and it's why I initially posted here ...Hi Renaud,
I've already tried that, i've added the command in that script but, still, after reboot, no minidlna process active
nas:~# ps -ef | grep minidlna | grep -v grep
nas:~#
You can check the logfile /var/log/upnp-av.log to see if something is wrong. (Sometimes minidlna doesn't start simply because it tried to bind an IP address which is not yet setup)I've even created a script called minidlna in /etc/init.d as the post you suggested and added it to rc update-rc.d minidlna defaults
but nothing, at reboot doesn't start.
If I launch it manually obviously it starts.
Any idea?
Thank you very much,
Alessio
it's due to heavily customisation of netgear
As mdgm said, you could also contact the support, in my case there were unsuccessful to fix my trouble ;)manda wrote:
You can check the logfile /var/log/upnp-av.log to see if something is wrong. (Sometimes minidlna doesn't start simply because it tried to bind an IP address which is not yet setup)
In this log file I've foiund this:[2012/07/26 19:02:37] minidlna.c:153: warn: received signal 15, good-bye
Anybody knows what this means?
Anyway, opend a case online n# 19067253
Thank you,
Alessioalessio.71 wrote:
Anyway, opend a case online n# 19067253
Thank you,
Alessio
They've escalated to engineers...- Problem solved! :D
I'm afraid I don't know what they did but they stated thatThe fix was done by a senior engineer based in the US. I am afraid I do not have exact details of the fix applied but I have been informed that this fix will be rolled into the next firmware release 4.2.22.
Mr. Brendan stated also that he willsee if I can get a Jedi on the forum to update the forum thread.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
