routerbattles
Occasional Visitor
Hi all,
I'm having more issues on Merlin firmware.
A bit of history, up to about version 13 everything was fine and I installed lots of standard scripts to try things out, and had no issues with the webui or putty login being slow.
Since updating to 384.17 I have had issues as follows:
1. SKynet was locking up and showing it permanantly had a file locked so I could neither unistall it or disable it. Managed to disable then install after a bit of messing around in scmerlin.
2. Webui is slow or sometimes doesn't work at all. Sometimes the status part with the cpu bars doesn't show.
3. Putty login is very slow and scripts interfaces load slowly.
This all points to something locking up the cores and the status page confirms this - sometimes it's only one core maxed sometimes both as per graph.
However when I look at the cpu monitor in SCmerlin there is no instance that is over about 10% at any one time. All looks okay generally.
I have recently updated to 384.18 and still have the issues - don't really want to go through a nuclear reset procedure but is this the only way forward?
I did a full reset to get me to 384.17 when that was released but something went wrong after a while after introducing some of the standard scripts - flexqos was the only new one different from last time.
Any thoughts?
Thanks
I'm having more issues on Merlin firmware.
A bit of history, up to about version 13 everything was fine and I installed lots of standard scripts to try things out, and had no issues with the webui or putty login being slow.
Since updating to 384.17 I have had issues as follows:
1. SKynet was locking up and showing it permanantly had a file locked so I could neither unistall it or disable it. Managed to disable then install after a bit of messing around in scmerlin.
2. Webui is slow or sometimes doesn't work at all. Sometimes the status part with the cpu bars doesn't show.
3. Putty login is very slow and scripts interfaces load slowly.
This all points to something locking up the cores and the status page confirms this - sometimes it's only one core maxed sometimes both as per graph.
However when I look at the cpu monitor in SCmerlin there is no instance that is over about 10% at any one time. All looks okay generally.
I have recently updated to 384.18 and still have the issues - don't really want to go through a nuclear reset procedure but is this the only way forward?
I did a full reset to get me to 384.17 when that was released but something went wrong after a while after introducing some of the standard scripts - flexqos was the only new one different from last time.
Any thoughts?
Thanks