plabberrunt
New Around Here
I have an annoying situation. I have a remote router that I cannot access to do a physical restart for a few more weeks.
What happened is a little confusing - but basically I have two "dnsmasq" processes running at the same time, and I do NOT have dropbear (ssh) running.
How did that happen?
The dropbear process was killed because I had idle copies running and couldn't figure out which one was the "host" process vs a stalled client.
The dnsmasq duplicate was a mistake during reconfiguration.
Usually when dropbear is killed I would go into the web interface and disable/enable it and it would restart the service.
This time, the router seems to get stuck and cannot apply settings changes. The changes "save" in the config, but the services don't restart.
So - reboot right?
Well, whatever is stopping the settings from applying is blocking the reboot command also.
Attempts to reboot the router fail, the syslog shows this:
Any solution ideas?
My next idea is to try to disable and re-enable dnsmasq entirely... but considering even reboot gets stuck, that might be a waste of time.
What happened is a little confusing - but basically I have two "dnsmasq" processes running at the same time, and I do NOT have dropbear (ssh) running.
How did that happen?
The dropbear process was killed because I had idle copies running and couldn't figure out which one was the "host" process vs a stalled client.
The dnsmasq duplicate was a mistake during reconfiguration.
Usually when dropbear is killed I would go into the web interface and disable/enable it and it would restart the service.
This time, the router seems to get stuck and cannot apply settings changes. The changes "save" in the config, but the services don't restart.
So - reboot right?
Well, whatever is stopping the settings from applying is blocking the reboot command also.
Attempts to reboot the router fail, the syslog shows this:
Code:
Jan 20 02:07:42 rc_service: httpd 231:notify_rc reboot
Jan 20 02:07:42 rc_service: waitting "restart_time;restart_upnp;restart_bhblock;" via httpds ...
Jan 20 02:07:57 rc_service: skip the event: reboot.
Jan 20 02:13:41 rc_service: httpd 231:notify_rc start_sig_check
Jan 20 02:13:41 rc_service: waitting "restart_time;restart_upnp;restart_bhblock;" via httpds ...
Jan 20 02:13:56 rc_service: skip the event: start_sig_check.
Jan 20 02:24:28 rc_service: httpds 230:notify_rc restart_time;restart_upnp;restart_bhblock;
Jan 20 02:24:28 rc_service: waitting "restart_time;restart_upnp;restart_bhblock;" via httpds ...
Jan 20 02:24:43 rc_service: skip the event: restart_time;restart_upnp;restart_bhblock;.
Jan 20 02:27:07 rc_service: httpd 231:notify_rc reboot
Jan 20 02:27:07 rc_service: waitting "restart_time;restart_upnp;restart_bhblock;" via httpds ...
Jan 20 02:27:22 rc_service: skip the event: reboot.
Any solution ideas?
My next idea is to try to disable and re-enable dnsmasq entirely... but considering even reboot gets stuck, that might be a waste of time.