What's new
  • 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!

Problem when rebooting RT-AC56U in command line

kcobain1992

Occasional Visitor
Hello,

I wanted to report an issue: in SSH, after issuing the command reboot, the router hangs in an inconsistent state, rather than cleanly finishing the reboot cycle.
When trying to access any web page, it redirects to 192.168.1.1 and displays the message shown in the screenshot below.
After manually rebooting (from the switch at the back) everything comes back to normal.
I'd like to know if I'm the only one having this issue.
Firmware version is 376.49_2

Vladimir
 

Attachments

  • router.png
    router.png
    55.6 KB · Views: 237
Check your System Log during the reboot to see if there's any additional info as to where it gets stuck in the shutdown.
 
Hello,

I wanted to report an issue: in SSH, after issuing the command reboot, the router hangs in an inconsistent state, rather than cleanly finishing the reboot cycle.
When trying to access any web page, it redirects to 192.168.1.1 and displays the message shown in the screenshot below.
[...]
Vladimir
When you say "an inconsistent state", do you mean that the router is no longer working when the uploaded page is displayed ?

I'm asking because I did get this page and it had no effect on the router. When I got that page, I just remove the part of the URL other that http://192.168.1.1 and made "return".
 
I can't seem to pinpoint what causes it. Neither /jffs/syslog.log nor dmesg seem to show anything suspicious, but it's definitely happening each time I reboot the router from ssh. Now it seems to go away after logging in to its administration webpage.
 
I can't seem to pinpoint what causes it. Neither /jffs/syslog.log nor dmesg seem to show anything suspicious, but it's definitely happening each time I reboot the router from ssh. Now it seems to go away after logging in to its administration webpage.

My questions were:
1- when you see that page after the terminal reboot, is the router performing well at the same time?
2- when this situation happens, after correcting the url (by just keeping http://192.168.1.1 portion of the url), is the usual home page displayed ?
 
My questions were:
1- when you see that page after the terminal reboot, is the router performing well at the same time?
2- when this situation happens, after correcting the url (by just keeping http://192.168.1.1 portion of the url), is the usual home page displayed ?

The first time when it happened, it would even block ping requests to 8.8.8.8, wouldn't let me log in, etc. I had to restart it the hard way.
But now I can open the config page (the answer to the second question is yes), and after I do so, it seems to start working again normally. That's why I need to investigate a little more.
 
A couple of possibilities.....

How long are you waiting after the reboot command to access the router? The router is actually still processing the reboot after all the LEDs come active. Try waiting about 2min and see if it still fails.

Do you have USB drives attached? As a test, try disconnecting the USB drives before the reboot and see if still fails.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top