NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jarodsmith
Jun 25, 2012Aspirant
ReadyDLNA high CPU after renames/deletes
Hello all!
For the past year (give or take), I have been experiencing an issue with the minidlna process reaching 100% CPU use shortly after renaming media files (audio or video). This has been observed across several different firmware versions but I am currently running version 4.2.21 on a Pro Business model.
The high CPU can be replicated and once it begins, it lasts for approximately 15 to 20 minutes. After approximately 3 to 5 minutes, the fans in the unit spin up to compensate for the extra heat caused by the CPU and become very loud.
During this high CPU period, the NAS shares are accessible although the NAS is slow to respond.
Any suggestions will be welcomed.
Thank you,
Jarod
For the past year (give or take), I have been experiencing an issue with the minidlna process reaching 100% CPU use shortly after renaming media files (audio or video). This has been observed across several different firmware versions but I am currently running version 4.2.21 on a Pro Business model.
The high CPU can be replicated and once it begins, it lasts for approximately 15 to 20 minutes. After approximately 3 to 5 minutes, the fans in the unit spin up to compensate for the extra heat caused by the CPU and become very loud.
During this high CPU period, the NAS shares are accessible although the NAS is slow to respond.
Any suggestions will be welcomed.
Thank you,
Jarod
3 Replies
Replies have been turned off for this discussion
- de_niroGuideHow much size of your media files(Audio and video)?I suspect the cache file of DLNA is huge and you might need to force rescan media folder once again.
- jarodsmithAspirantI do occasionally re-scan (every other month of so). I have also disabled DLNA and enabled it again .. that causes a re-scan as well .. but that too does not correct this issue.
Total size of media files is 4 TB.
Is there a log file that may indicate errors with DLNA scanning that may point to a corrupt file causing this issue?
Anything else I can do to further troubleshoot this issue?
Thank you in advance,
Jarod - de_niroGuidePlease see this note,you need DLNA debug addon to export debug logs
viewtopic.php?f=76&t=53356&p=355009&hilit=dlna+debug#p355009
If you feel hard to read logs,please contact support center to create a case number to find further help
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!