Posted: Mon Feb 13, 2023 15:17 Post subject: New Build - 02/13/2023 - r51679
Welcome to MediaTek r51679 beta release thread for reporting, feedback to developers & community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp). 'write {file} linux' then 'reboot'.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Misc: stracetcpdumpwireshark.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
Router Model / Version: Dlink DIR-882 A1
File: dlink-dir882-a1-webflash.bin
Firmware: DD-WRT v3.0-r51679 std (02/12/23)
Previous: DD-WRT v3.0-r51506 std (01/25/23)
Reset: Yes
Mode: AP
Uptime: few hours
Services: Openvpn client, DLNA, SAMBA, PPPOE
Status: working
MiniDLNA database won't build or rebuild completely (no audio or image files detected and only half of video files detected). SMB works well and all the files are present and working properly when exploring the hard drive via SMB on computer.
If this device is in wired AP mode (not a gateway to another subnet or the internet), turn off ttraff daemon on the services page. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
If this device is in wired AP mode (not a gateway to another subnet or the internet), turn off ttraff daemon on the services page.
Thanks for the answer. I disabled ttraff but it didn't solve the issue. Still a maximum of 346 video files detected (there's a bit more than 500 video file in the drive), zero audio and image files (among thousands). MiniDlna may be crashing before ending the process. With older builds, minidlna database could be built/rebuilt almost without issues.
Last edited by Milax on Fri Feb 17, 2023 16:58; edited 1 time in total
the log says something about oom killer, the router is running out of RAM
Thanks. I also suspected CPU or RAM usage issue, so i disabled syslogd, klogd, openvpn, smartdns and minidlna. Then i deleted minidlna database in command line and rebooted the router.
I waited until cpu usage was near zero, and started minidlna, triggering database building. Everything was ok until nearly 346 video file were detected (strange, always the same number ! no matter what services are active) and then, CPU went very fast to 100%+ usage and minidlna was restarted with 346 files detected as usual.
My thought is your are totally right, ram issue but to my understanding, that's the consequence not the cause. I feel that something's wrong, since i never had those issues with older builds (don't know when it started though, since i don't rebuild the database often).
I finally found what was causing the issue. When building MiniDlna database, one relatively large video file (16GB+) was causing ram usage to increase exponetially and minidlna service to stop responding. That's why database building process was always stopping at the same number of files (346) because it never could go beyond the large video file as described above.
In conclusion, the issue was not directly related to this build. However, since i never experienced the issue before with older builds, may be most recent minidlna versions have heavier memory usage.
