Posted: Fri Feb 23, 2018 13:29 Post subject: Kong 3.0-r33675 Build - OOM Lock Ups
Hi All,
I've installed Kong's 3.0-r33675 build on my Netgear R6400 and it worked brilliantly for about 12 hours, but then got slower and slower until eventually it locked up until I could reboot it.
I had syslog enabled and so managed to spot that OOM had been invoked and was killing processes one after the other. I've attached the syslog records to the post. Can anyone advise what might have caused this?
Joined: 18 Mar 2014 Posts: 1885 Location: Netherlands
Posted: Fri Feb 23, 2018 17:52 Post subject:
I have not looked to your log, but why not get a more recent build, I am using kong's latest test build (35030) and it appears to be good.
Further builds with good mileage (all kong's builds): 30465M, 30700M, 30840M, 30910M (openVPN 2.3), 31160M (openVPN 2.4), 31525M, 31870M, 32170M, 33435M, 33525M, 33770M (KRACK patch), 34320 (reset to default).
Be sure to erase nvram from CLI and put settings in manually. _________________ Router Netgear R6400v1, Netgear R6400v2 (waiting for DDWRT build), Linksys EA6900 (XvortexCFE), Linksys E2000 (converted WRT320N), WRT54GS v1.
Install guide see Linksys EA6900: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=291230
Posted: Fri Feb 23, 2018 19:10 Post subject: Re: Kong 3.0-r33675 Build - OOM Lock Ups
bjones371 wrote:
Hi All,
I've installed Kong's 3.0-r33675 build on my Netgear R6400 and it worked brilliantly for about 12 hours, but then got slower and slower until eventually it locked up until I could reboot it.
I had syslog enabled and so managed to spot that OOM had been invoked and was killing processes one after the other. I've attached the syslog records to the post. Can anyone advise what might have caused this?
Cheers.
Unfortunately the oom dump usually doesn't show you which process/kernel module ate up ram.
Did you erase nvram after flashing dd-wrt?
Did you configure any services that use usb features, e.g. minidlna samba, they can be misconfigured where data is then stored in ram. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Posted: Fri Feb 23, 2018 19:47 Post subject: Re: Kong 3.0-r33675 Build - OOM Lock Ups
<Kong> wrote:
bjones371 wrote:
Hi All,
I've installed Kong's 3.0-r33675 build on my Netgear R6400 and it worked brilliantly for about 12 hours, but then got slower and slower until eventually it locked up until I could reboot it.
I had syslog enabled and so managed to spot that OOM had been invoked and was killing processes one after the other. I've attached the syslog records to the post. Can anyone advise what might have caused this?
Cheers.
Unfortunately the oom dump usually doesn't show you which process/kernel module ate up ram.
Did you erase nvram after flashing dd-wrt?
Did you configure any services that use usb features, e.g. minidlna samba, they can be misconfigured where data is then stored in ram.
Yeah I didn't spot anything that appeared to give away the cause of the problem. Is there anything I can schedule to run regularly with Cron to monitor it? It happened in the middle of the night when nobody was using the connection.
Yes nvram was erased by 30/30/30, and I did the same again this morning just to be sure. I've enabled core USB support just to supply power to the USB ports for an internet enabled thermostat, but none of the USB services are enabled.
Fairly certain the 6400 wont be effected by the 30/30/30 similar to the 7000.
The newer Broadcom chipsets you have to reset to factory via gui or command line commands. _________________ Router currently owned:
Netgear R7000 - AP mode
1st gen i7 pc running pfSense as WAN firewall/IPS.
Posted: Sat Feb 24, 2018 8:31 Post subject: Re: Kong 3.0-r33675 Build - OOM Lock Ups
bjones371 wrote:
<Kong> wrote:
bjones371 wrote:
Hi All,
I've installed Kong's 3.0-r33675 build on my Netgear R6400 and it worked brilliantly for about 12 hours, but then got slower and slower until eventually it locked up until I could reboot it.
I had syslog enabled and so managed to spot that OOM had been invoked and was killing processes one after the other. I've attached the syslog records to the post. Can anyone advise what might have caused this?
Cheers.
Unfortunately the oom dump usually doesn't show you which process/kernel module ate up ram.
Did you erase nvram after flashing dd-wrt?
Did you configure any services that use usb features, e.g. minidlna samba, they can be misconfigured where data is then stored in ram.
Yeah I didn't spot anything that appeared to give away the cause of the problem. Is there anything I can schedule to run regularly with Cron to monitor it? It happened in the middle of the night when nobody was using the connection.
Yes nvram was erased by 30/30/30, and I did the same again this morning just to be sure. I've enabled core USB support just to supply power to the USB ports for an internet enabled thermostat, but none of the USB services are enabled.
Erase nvram may not be enough, I had an issue before, where my newly flashed R7000 would reboot every 1-2h although I had cleared nvram through webif, but the normal method does not delete all vars, as on some routers certain vars must be protected. For netgear routers I restore all vars, thus it safe to use:
erase nvram
when logged in to the router via telnet/ssh.
This fully clears nvram, after that you can reboot and configure it.
Such a problem can happen if oem wireless vars are not usable anymore with our wireless driver, as we usually have much never drivers compared to oem. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Posted: Sat Feb 24, 2018 8:32 Post subject: Re: Kong 3.0-r33675 Build - OOM Lock Ups
bjones371 wrote:
<Kong> wrote:
bjones371 wrote:
Hi All,
I've installed Kong's 3.0-r33675 build on my Netgear R6400 and it worked brilliantly for about 12 hours, but then got slower and slower until eventually it locked up until I could reboot it.
I had syslog enabled and so managed to spot that OOM had been invoked and was killing processes one after the other. I've attached the syslog records to the post. Can anyone advise what might have caused this?
Cheers.
Unfortunately the oom dump usually doesn't show you which process/kernel module ate up ram.
Did you erase nvram after flashing dd-wrt?
Did you configure any services that use usb features, e.g. minidlna samba, they can be misconfigured where data is then stored in ram.
Yeah I didn't spot anything that appeared to give away the cause of the problem. Is there anything I can schedule to run regularly with Cron to monitor it? It happened in the middle of the night when nobody was using the connection.
Yes nvram was erased by 30/30/30, and I did the same again this morning just to be sure. I've enabled core USB support just to supply power to the USB ports for an internet enabled thermostat, but none of the USB services are enabled.
Erase nvram may not be enough, I had an issue before, where my newly flashed R7000 would reboot every 1-2h although I had cleared nvram through webif, but the normal method does not delete all vars, as on some routers certain vars must be protected. For netgear routers I restore all vars, thus it safe to use:
erase nvram
when logged in to the router via telnet/ssh.
This fully clears nvram, after that you can reboot and configure it.
Such a problem can happen if oem wireless vars are not usable anymore with our wireless driver, as we usually have much never drivers compared to oem. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Ah - thanks for the information! It hasn't occurred again since that first time so I'll stick with it for now, and if it happens again I'll run erase nvram.
