Menu
What's new
By:
Filters Better Search

Recent content by Luky

  • 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!

  1. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    amas_lib process is respawning so i had to add line like this to cron: */15 * * * * killall amas_lib 15 mins is perhaps bit aggressive as an issue usually reappears after few hours since than my router don't get stuck, neither i got wifi reconnection problems
  2. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    Neither did I
  3. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    One more update Killing amas_lib process unblock other processes and everything starts to work as expected - nvram, webui etc. So the culprit is by my opinion amas_lib process - couldn't find anywhere what is it actually good for.
  4. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    Router was stable after manual workaround for few days. So I rebooted router and issue again reappear: here is a list of processes having nvram file open COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME wlc_nt 1157 admin 10w REG 0,13 0 1314 /var/nvram.lock...
  5. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    i will give it a try when it hangs. Just an idea - strace log shows /var/nvram.lock, but all other "lock" files are in /var/lock dir. Couldn't be there some raise condition when nvram ask for /var/nvram.lock but some other process asks for /var/lock/nvram.lock?
  6. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    hmm, given the orphan "locks" it seems some process died midway without properly cleaning after itself causing further issues down the road. I guess it would be hard to track down. I will see how long it will last after my manual recovery before it lock itself again. Yes I did
  7. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    For WebUI to start to work I had to remove /var/lock/allwevent.lock and than restart httpd
  8. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    Hmm, interesting. setting pid_max on already "locked" router doesn't help. I don't have anything running thousands of nvram commands in mine setup so it seems weird I would run out of pids. What's more it doesn't explain why "nvram get lan_ipaddr" works, and "nvram get asus_device_list" get...
  9. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    i have the router roughly for a year. I believe it's happening from the very beginning, just the gap between reboot and deadlock perhaps shortened. But i don't have any exact numbers. I saw other people reporting problems with login here on the forums - i guess it's related...
  10. L

    Asus AC86U - nvram show stops working after few hours causing router not accessible via WebUI

    Hi, I came across a strange problem with my AC86U running latest merlin firmware (but it was happening on older as well). Basically router becomes unaccessible via WebUI after few hours after reboot. Just login screen shows up and after putting in login details it doesn't continue any further...
See more
Top