v1.5.0 Bug reports and Comments

[sirhc]

Great news.

Well I think they still have to pass your approval mike?

Mike has been a BIG help.

[IntL-Daniel]

Hi Chris, on 13/07/2018 I have sent you crashlogs from my WS-12-250-AC on 1.5.0 via email. Did you received that and did you find the reason of that crash? We have regular crashes there since 1.4.8 firmware and I do not think it is a hw failure. Thanks for your interest.

[theteksolution]

Hi Chris, on 13/07/2018 I have sent you crashlogs from my WS-12-250-AC on 1.5.0 via email. Did you received that and did you find the reason of that crash? We have regular crashes there since 1.4.8 firmware and I do not think it is a hw failure. Thanks for your interest.

We just had one of our WS-12-250 DC crash and reboot today. I thought initially it was the backhaul rebooting, but after logging into the netonix its up time is only a couple hours. It actually shut down all of our radios on the tower during rebooting as well. How did u pull the crash logs? Any word on a fix for this sirhc? I have another netonix at the same location running 1.4.9, its uptime is 220 days.

[IntL-Daniel]

I got the standard syslog (included crash reasons) via external syslog server. Unfortunately no reply/interest from Netonix :-(.

[mike99]

Shouldn't a reboot from the UI only do a soft reboot and leave PoE on ?

I had to reboot a mini with 1.5.0 because I was not able to do any config change (disk full error while via CLI but fix after reboot) but didn't expect radios to also reboot.

I was not able to find why disk was full. df don't seem to be able to calculate the size of the tmpfs. Without specific the folder, it don't tmpfs drive and by specifing it like "df /var", it show 0 for every value (size 0, size left 0, available 0, use 0%, etc.). I could have look more with du but too late, it's rebooted.

I look at log change between 1.5.0 and 1.5.x, no fix seem related.

[sirhc]

Mike99

This happens on a rare events, we know it happens sometimes but have been unable to replicate it on demand to figure out why. We have discussed it on the forums before somewhere. It is on the LONG list to investigate but recently all resources have been on WS2 and WS3 development and only fixing critical bugs in WS line.

What we know:
Sometimes on a UI reboot it will cycle POE but this is not common and we do not know why.

Can you verify that this to be the case that you do not see it every time and in fact it is rare event?

There is a log entry on boot up that calls out if it is a COLD or WARM.

A COLD reboot will resets POE where as a WARM reboot leaves POE alone.

[Digitexwireless]

We are getting random reboots on a WS-12-250-DC. Logfile reports: Dec 31 18:00:26 switch[799]: Detected cold boot

Do we need to move some cables inside the switch like the 500's or is this a software fixable issue?

[sirhc]

We are getting random reboots on a WS-12-250-DC. Logfile reports: Dec 31 18:00:26 switch[799]: Detected cold boot

Do we need to move some cables inside the switch like the 500's or is this a software fixable issue?

This is not normal behavior. Either something is wrong with the unit or something is wrong with your power source.

I am assuming you are running at least v1.5.0 if not v1.5.1rc4.

If I was you I would swap unit with a spare and if problem persists you know it is not the switch and you can look elsewhere.

If the problem stops you can bench test as detailed here: viewtopic.php?f=6&t=2780#p19221

If need be RMA it.

How are you powering the unit (in detail please)?

[Digitexwireless]

We are runing v1.5.0. This is a 24 volt solar tower. I think i will swap out the solar controller tomorrow, that will rule out the power source. If it still reboots i will swap it for a spare.

[mblfone]

Hello,

I also just had a "Cold Reboot". No other indications of issues. This took everything down for about 3 minutes. No other indications of problems. I am running 1.5.0 on a WS-26-400-AC. This is the firs problem that we have had since installing it new this spring.

Scott