What's new

Media server and Samba have to be reenabled after inactivity

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

vrapp

Senior Member
With AC-68R and firmware 378.56.2, it looks like some USB applications stop working after period of inactivity. I saw it yesterday with media server, when DLNA source was not visible in the LAN; today it was Samba, when the share was not visible in the LAN. In both cases I disabled /reenabled respective server, and they both instantly showed up for everybody. On the other hand, Transmission is working all the time. So I wonder if there's some "inactivity period".
 
With AC-68R and firmware 378.56.2, it looks like some USB applications stop working after period of inactivity. I saw it yesterday with media server, when DLNA source was not visible in the LAN; today it was Samba, when the share was not visible in the LAN. In both cases I disabled /reenabled respective server, and they both instantly showed up for everybody. On the other hand, Transmission is working all the time. So I wonder if there's some "inactivity period".
It's possibly your disk going into sleep mode, causing issues with services.

Sent from my Nexus 9 using Tapatalk
 
It's possibly your disk going into sleep mode, causing issues with services.

Sent from my Nexus 9 using Tapatalk

I am having the same problem after upgrading my AC68U to 378.56.2. For some reason the minidlna daemon is stopped.

I initially thought that was a bug with the included minidlna so I disabled it and installed the Entware version, which seems to be killed as well (log mentions having received signal 15), probably by rc (issuing "service stop_media" actually stops the entware version as well, I am guessing it matches the process name when killing it).

I now have a script running hourly to check the minidlna daemon status and saves a copy of minidlna.log and syslog.log in case it gets killed, will post them here when it does the next time (when I realized it was killed yesterday syslog.log didn't contain info for that timeframe anymore)
 
Make sure you did enable it on the Media Servers page.

If you want to run an external build (such as Entware), just rename the minidlna executable to a different name. That way it won't get touched by the firmware.
 
I am also having this issue, this wasn't the case in 50 I think it was? My Hd was always reachable even after going to sleep mode previously.
 
I don't think it's because of disk. There's Transmission running, and I see it's uploading a bunch of torrents all the time, from the same storage.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top