Nano M5 slow web response.

[vincefer]

Hi,

I'm testing my first M5 units at the office/lab. I had a nanostation M5 connected to a Rocket M5 AP for a little more than one day. And the web interface is responding slow sometimes. The "main" tab is specially slow and many times unable to show the LAN/WAN graphs.

On the terminal I can see boa webserver consuming 100% CPU for some seconds when this happens. But this doesn't occur always and it makes me think if this hardware with its first software version is stable enough to run in an unattended place. Have anyone had this units running uninterrupted for some days or weeks?

I'm very sure that Ubiquity has run thorough tests on them. Don't take me wrong. But as they are so new, I'd like to read some impressions on stability from other people testing them.

Regards.

[UBNT-Mike.Ford]

Hi,

I'm testing my first M5 units at the office/lab. I had a nanostation M5 connected to a Rocket M5 AP for a little more than one day. And the web interface is responding slow sometimes. The "main" tab is specially slow and many times unable to show the LAN/WAN graphs.

On the terminal I can see boa webserver consuming 100% CPU for some seconds when this happens. But this doesn't occur always and it makes me think if this hardware with its first software version is stable enough to run in an unattended place. Have anyone had this units running uninterrupted for some days or weeks?

I'm very sure that Ubiquity has run thorough tests on them. Don't take me wrong. But as they are so new, I'd like to read some impressions on stability from other people testing them.

Regards.


Hello,

Are you using RC firmware from the top of the forum?

Thanks,

Mike

[vincefer]

No, it was the original firmware installed on the units. I'll upgrade now. Thanks.

[MBChris]

Hello, good Place to jump in.

Ive the same Problem with a B5MHP, slow response to WEB-Gui requests, sometimes only half page displayed (without images on the main tabs).

Also i could only connect with IE because FF and GC respons with "invalid authentication"

FW is 5.0 as original / should i upgrade to the RC also ?

Thanky in advance
MBChris

[7omek]

Here's an old, good rule:

Have some problems? Upgrade to latest available to see if it solves the problems.
Have no problems? Leave it as it is.

;)

[MBChris]

Ciao 7omek,

im wondering if i should flash an "RC" Version within my production environment, better not.

The Version 5.0 is the latest Version with is available from the Firmware Download page.

Anyway thanks for your reply
MBChris

[vincefer]

Well 7omek, I use to follow that rule. But when looking for stability Release Candidates aren't always the best way to go.

Anyway, I agree. It is a new product and the fastest way to make it more stable is using and testing those RC builds. But on a production environment... ummm. I'll wait for a while.

[7omek]

MBChris and vincefer, obviously that golden rule should be applied only when the problem FORCES you to apply it.
I mean, when there are no other choices available (already changed configuration, changed technology, changed prayers/curses) then it's time to risk a Release Candidate firmware usage also in production environment, just because in that particular situation that environment is no more... productive. ;)

If that "slowness" only slows your maintenance procedures, but the service given to the customer is OK, then it's not a big deal: leave it as it is.
Else, when the given service is compromised, well... it's time to try the RC.

IMHO.

[MBChris]

Thank you 7omek,
now i will change to the RC2 candidate which just come in, will report if its ok

MBChris

[UBNT-Mike.Ford]

Hello,

Yes if you guys experience slow Web UI then please update to RC2 at the top of the forum.

Thanks,

MIke

[MBChris]

DONE, and functional so far, also with GC IE and FF
Thanks Mike

greetings
MBChris

[UBNT-Mike.Ford]

DONE, and functional so far, also with GC IE and FF
Thanks Mike

greetings
MBChris


Thanks for the update.

Mike

[vincefer]

WebUI is more responsive with RC2. But some other issues commented on other posts appeared with this update.

Thanks for the fix.