Release Asuswrt-Merlin 3004.388.6 is now available

[GLISIT]

I am going to do a router power cycle, try to flash immediately after, see if that helps. If not, I might have to wait to do a full reset and reconfig from scratch.

Things to try:
Try clearing Browser Cache.
Unplug any USB ad on devices.
Electrical Reset Router followed by immediate flashing.

Edit: you are on a new router, when you converted from stock to rmerlin you were supposed to do a factory reset with the box checked to clear the entire unit before setting it up.

If after the above, if it still does not successfully flash, then you need to "Restore" to get it going properly.

@John Fitzgerald The power cycle did the trick. Earlier, I did a power cycle when I tried the upgrade a second time but let it sit for several long minutes before having a chance to try the upgrade. This time, I grabbed my laptop, sat next to the router and did the upgrade as soon as the router came online after the power cycle. Worked like a charm.

Thanks!

 

[tarzan2000]

Friends!
Tell me, why in my WEB GUI the processor load is constantly up to 50%, while in top I see that it is no higher than 2%.
It seems to me that it started after the transition to 388.6.

Spoiler

 

[dave14305]

Tell me, why in my WEB GUI the processor load is constantly up to 50%, while in top I see that it is no higher than 2%.

The second line in the top output shows the system at 60% idle, so the GUI is accurate. There’s a high system utilization at 29%, which isn’t easy to explain. What happens if you kill the wan-failover script? Does it settle down at all?

 

[tarzan2000]

The second line in the top output shows the system at 60% idle, so the GUI is accurate. There’s a high system utilization at 29%, which isn’t easy to explain. What happens if you kill the wan-failover script? Does it settle down at all?

I disabled (uninstall) the script and it had no effect.
The CPU load was removed only after a complete restart of the router.

Spoiler

I have another 86Pro on 388.6 with almost similar functionality - and everything is ok in terms of the processor.

Spoiler

Some strange situation, almost mysterious

 

[jeepr]

@jeepr There's nothing particularly obvious in the logs. There may have been some VPN events around 08:10 and 08:58 in the morning. Overnight an Ethernet device connected to eth1 was flapping, but that might just be its normal standby behaviour. You'll probably need to change "Log only messages more urgent than" to "all" to get more useful information.

Is this something that's only started happening after installing this release? If not then it would be best to open a separate thread.

got sick and tired of the disconnects
reverted back to 388.5
no unscheduled disconnects

 

[Ripshod]

got sick and tired of the disconnects
reverted back to 388.5
no unscheduled disconnects

Did you even try a factory reset?

 

[Piotrek]

RT-AX86U - ~912 MB from 1024 MB
View attachment 56085

# grep "memory  :" /tmp/syslog.log*
/tmp/syslog.log-1:May  5 06:05:08 kernel:     memory  : 0xffffffc000000000 - 0xffffffc040000000   (  1024 MB)

Thanks! It seems that around 100MB of RAM is lost in some devices, but this has nothing to do with this release of Asuswrt-Merlin 3004.388.6. This issue may be discussed in a new topic.

 

[L&LD]

Nothing is lost.

Simply different methods to count.

And, different methods to count from.

 

[Piotrek]

Me too

Thanks! It turns out that this is the limitation of RT-AX56U as a node in AiMesh.

 

[Piotrek]

Nothing is lost.

Simply different methods to count.

And, different methods to count from.

I disagree, but as I mentioned, this is not the place for this discussion.

 

[glens]

Where do you suppose the running kernel / modules reside?

 

[L&LD]

Not a discussion. Fact.

 

[Piotrek]

Where do you suppose the running kernel / modules reside?

Not a discussion. Fact.

You know my opinion. If you want to discuss this further, please start a new topic - this one is about the Asuswrt-Merlin release.

 

[glens]

I don't guess I /do/ know your opinion, but I do guess that's okay, if you don't want to state it.

 

[swejuggalo]

My returning "drop" everything issue I have. Wired/WiFi, everything drops. Simply looks like everything reboots. Could be hours between, or days.
Diversion/Skynet. My syslog server don't show any critical error. From the normal block notice to sudden restart.

 

[ColinTaylor]

My returning "drop" everything issue I have. Wired/WiFi, everything drops. Simply looks like everything reboots. Could be hours between, or days.
Diversion/Skynet. My syslog server don't show any critical error. From the normal block notice to sudden restart.

That doesn't show us anything useful as it's from after the event happened. The entries leading up to the event would be more interesting, as would the subsequent bootup messages in the router's syslog (not from the remote log server).

 

[swejuggalo]

That doesn't show us anything useful as it's from after the event happened. The entries leading up to the event would be more interesting, as would the subsequent bootup messages in the router's syslog (not from the remote log server).

I try to grab it. But how long log can I grab directly from the router? If I'm "lucky" it happens with a few hours apart but most of times it would mean I'm logged out already from the router.

But anyways, via the remote server, nothing of value is shown before it happens.

And if my logged in desktop looses connection too, am I stilled logged in and can see the whole log from before the failure/disconnect?
If I log in and look at my logs now I literally just see logs 10 minutes back in time.
Or is would a temporary disconnect not matter and logout time is indefinite on that page?

 

[ColinTaylor]

If I log in and look at my logs now I literally just see logs 10 minutes back in time.

You should be seeing hundreds of lines of log entries stretching back beyond when the router rebooted. If you're not seeing that there's either something seriously wrong with your router or something (like the Scribe addon script) is interfering with your syslog.

Have you tried doing a hard reset since this problem started?

 

[swejuggalo]

You should be seeing hundreds of lines of log entries stretching back beyond when the router rebooted. If you're not seeing that there's either something seriously wrong with your router or something (like the Scribe addon script) is interfering with your syslog.

Have you tried doing a hard reset since this problem started?

The log spam is Skynet blocked inbound/outbound traffic.

Yes, wiped twice in multiple attempts to trial and error.

 

[ColinTaylor]

The log spam is Skynet blocked inbound/outbound traffic.

If you are saying that Skynet is producing so much spam that your log file only goes back 10 minutes then you need to disable Skynet so you can do some sensible diagnosis.