Page 1 of 1

Device "Settings" hangs/freezes

Posted: Thu Oct 04, 2007 11:30 pm
by RouterPimp
I have been working with v3.0 beta 6, and have also noticed this in v2.2...

When I open the device "settings" for most nodes, everything open just fine, but sometimes, I will click on the settings for a node and the "settings" window will freeze or hang for about 3-4 minutes. The window will not display the pie chart for the services. After this time frame, the window will function as normal. If I make any changes, and apply it, the window will lock up again for about the same time period.

Any suggestions?

Re: Device "Settings" hangs/freezes

Posted: Wed Nov 14, 2007 8:10 am
by schorsch
The same thing sometimes happens here. I suggested it is the guest system of the virtual host which runs out of power (7 W2k3 Servers incl. Dude 2.2 on a proliant server @3GHz 4GB RAM).
Next week the dude runs on a dedicated server again, maybe the problem is gone away....

Re: Device "Settings" hangs/freezes

Posted: Wed Nov 14, 2007 10:19 pm
by VTWifiGuy
Can you check to see if it is the same glitch i described here http://forum.mikrotik.com/viewtopic.php?f=8&t=18698

try removing all services and seeing what it shows for in the pie chart area.
there has to be a glitch in the way this data is saved so the only thing you can really do is delete and recreate the device.

Re: Device "Settings" hangs/freezes

Posted: Wed Nov 14, 2007 11:31 pm
by RouterPimp
[quote="VTWifiGuy"]Can you check to see if it is the same glitch i described here http://forum.mikrotik.com/viewtopic.php?f=8&t=18698

try removing all services and seeing what it shows for in the pie chart area.
there has to be a glitch in the way this data is saved so the only thing you can really do is delete and recreate the device.[/quote]

Yes, this is the same thing I am experiencing. I could remove the device and allow the Dude to "discover" the device and services by IP. After that I haven't experienced the problem with the same node. Just wanted to see if there was something I was doing wrong, or if there are other users experiencing the same thing.

Thanks for the update.