Traste
Occasional Visitor
Hi,
I am running Firmware:380.60_beta2 on an Asus RT-AC68U and from a machine, i am running a monitoring script over SSH every few minutes, this is working great, however after a day or two, the router started acting up, disconnected from the internet, stopped responding to SSH connections, but the http/https was working so i restarted the router.
After manually monitoring the router for a while i noticed that the number of dropbear processes started to build up over time so I figured that my script didn't close the SSH session properly when closing the , so i changed the script to run "exit" at the end, but that doesnt seem to help, they are still building up.
Is this expected behaviour when running exit?
I tried to kill the processes from the script using "killall dropbear" , but that stops SSH from working all together.
I was also considering doing a "/etc/init.d/ssh stop ; /etc/init.d/dropbear start" at the end of the script, but both and killing the processes feels a little heavyhanded and would stop other sessions as well.
Am I doing something wrong, does anyone have any suggestions on how to get around this issue?
Much appreciated,
Traste
I am running Firmware:380.60_beta2 on an Asus RT-AC68U and from a machine, i am running a monitoring script over SSH every few minutes, this is working great, however after a day or two, the router started acting up, disconnected from the internet, stopped responding to SSH connections, but the http/https was working so i restarted the router.
After manually monitoring the router for a while i noticed that the number of dropbear processes started to build up over time so I figured that my script didn't close the SSH session properly when closing the , so i changed the script to run "exit" at the end, but that doesnt seem to help, they are still building up.
Is this expected behaviour when running exit?
I tried to kill the processes from the script using "killall dropbear" , but that stops SSH from working all together.
I was also considering doing a "/etc/init.d/ssh stop ; /etc/init.d/dropbear start" at the end of the script, but both and killing the processes feels a little heavyhanded and would stop other sessions as well.
Am I doing something wrong, does anyone have any suggestions on how to get around this issue?
Much appreciated,
Traste