pico locking up

[along5664]

I have about 10 pico installed and 6 out of 10 were locked up today, they showed power light but no other lights. They had been up approx 10 days or so. I had to reboot several of them a couple of times to get them going again. I will post config when I get back to office. I think most are running the new firmware, but some may still be at 3.3.1 version.Anyone seen this or know of any issues? They are just setup as ap in bridge mode with no encryption. Simple plain setup on each. Thanks for any help.

[skyhook]

I have about 10 pico installed and 6 out of 10 were locked up today, they showed power light but no other lights. They had been up approx 10 days or so. I had to reboot several of them a couple of times to get them going again. I will post config when I get back to office. I think most are running the new firmware, but some may still be at 3.3.1 version.Anyone seen this or know of any issues? They are just setup as ap in bridge mode with no encryption. Simple plain setup on each. Thanks for any help.

Connect Pico to a PC; run UBNT Discovery Tool anc chech if it show the devices.

[along5664]

I have no ethernet when I plugged in, nor a ssid being broadcast. Here is the config off a unit. Note this one is running 3.2.3 software.

aaa.1.status=disabled
aaa.status=disabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.1.status=enabled
bridge.1.port.2.devname=ath0
bridge.1.port.2.status=enabled
bridge.1.stp.status=enabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
dnsmasq.1.devname=eth0
dnsmasq.1.status=enabled
dnsmasq.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=disabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=disabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
ebtables.3.status=disabled
ebtables.50.status=disabled
ebtables.51.status=disabled
ebtables.52.status=disabled
ebtables.status=enabled
httpd.port=80
httpd.status=enabled
igmpproxy.status=disabled
iptables.3.status=disabled
iptables.status=disabled
netconf.1.alias.1.status=disabled
netconf.1.alias.2.status=disabled
netconf.1.alias.3.status=disabled
netconf.1.alias.4.status=disabled
netconf.1.alias.5.status=disabled
netconf.1.alias.6.status=disabled
netconf.1.alias.7.status=disabled
netconf.1.alias.8.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.alias.1.status=disabled
netconf.2.alias.2.status=disabled
netconf.2.alias.3.status=disabled
netconf.2.alias.4.status=disabled
netconf.2.alias.5.status=disabled
netconf.2.alias.6.status=disabled
netconf.2.alias.7.status=disabled
netconf.2.alias.8.status=disabled
netconf.2.allmulti=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=10.61.35.203
netconf.3.netmask=255.255.254.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
radio.1.ack.auto=enabled
radio.1.acktimeout=23
radio.1.channel=1
radio.1.chanshift=0
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.frag=off
radio.1.ieee_mode=g
radio.1.mcastrate=1M
radio.1.mode=master
radio.1.rate.auto=disabled
radio.1.rate.max=24M
radio.1.rts=off
radio.1.rx_antenna=1
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.thresh62a=28
radio.1.thresh62b=28
radio.1.thresh62g=28
radio.1.tx_antenna=1
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=16
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.nameserver.1.ip=0.0.0.0
resolv.nameserver.1.status=enabled
resolv.nameserver.2.status=disabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=10.61.34.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
tshaper.status=disabled
users.1.name=admin
users.1.password=HhQGqeWB.5f8o
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=disabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.compression=0
wireless.1.devname=ath0
wireless.1.fastframes=0
wireless.1.frameburst=0
wireless.1.hide_ssid=disabled
wireless.1.l2_isolation=enabled
wireless.1.mac_acl.1.mac=
wireless.1.mac_acl.1.status=disabled
wireless.1.mac_acl.10.mac=
wireless.1.mac_acl.10.status=disabled
wireless.1.mac_acl.11.mac=
wireless.1.mac_acl.11.status=disabled
wireless.1.mac_acl.12.mac=
wireless.1.mac_acl.12.status=disabled
wireless.1.mac_acl.13.mac=
wireless.1.mac_acl.13.status=disabled
wireless.1.mac_acl.14.mac=
wireless.1.mac_acl.14.status=disabled
wireless.1.mac_acl.15.mac=
wireless.1.mac_acl.15.status=disabled
wireless.1.mac_acl.16.mac=
wireless.1.mac_acl.16.status=disabled
wireless.1.mac_acl.2.mac=
wireless.1.mac_acl.2.status=disabled
wireless.1.mac_acl.3.mac=
wireless.1.mac_acl.3.status=disabled
wireless.1.mac_acl.4.mac=
wireless.1.mac_acl.4.status=disabled
wireless.1.mac_acl.5.mac=
wireless.1.mac_acl.5.status=disabled
wireless.1.mac_acl.6.mac=
wireless.1.mac_acl.6.status=disabled
wireless.1.mac_acl.7.mac=
wireless.1.mac_acl.7.status=disabled
wireless.1.mac_acl.8.mac=
wireless.1.mac_acl.8.status=disabled
wireless.1.mac_acl.9.mac=
wireless.1.mac_acl.9.status=disabled
wireless.1.mac_acl.policy=allow
wireless.1.mac_acl.status=disabled
wireless.1.macclone=disabled
wireless.1.security=none
wireless.1.signal_led1=94
wireless.1.signal_led2=80
wireless.1.signal_led3=73
wireless.1.signal_led4=65
wireless.1.sper=disabled
wireless.1.ssid=Aerowire_GD1604
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.1.wmm=disabled
wireless.1.wmmlevel=-1
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled

[skyhook]

I have no ethernet when I plugged in, nor a ssid being broadcast. Here is the config off a unit. Note this one is running 3.2.3 software.

No ethernet link?
Try to change cabel and PC.
Try to reset to default factory pressing reset button (about 10 seconds).

[along5664]

Cable is fine as I plugged in another ap and it came up fine. As soon as I reboot these, they work fine again. I have pulled all these from the field and have them at the office. I will upgrade to the new software and see how that goes.

[along5664]

Any help here. I think I have another one locked up and it has the latest firmware load on it.

[UBNT-Mike.Ford]

Hello,

I have my software team looking into this. One things. Can you update to v3.4. Next run the unis for a few hours. After tha go to the system tab and download the .sup file and email it to mike@ubnt.com

That will greatly help us.

Thanks,

Mike

[along5664]

Just sent the email....so far after upgrading, 3 days and no drop...but before it was about 10 days before a drop/lockup..

[pshakanet]

I am currently experiencing and can confirm this same issue on a brand new PS2 running 3.2.3 firmware.

We got one to test it out, and with the thing sitting here on my desk, I've had to reboot it multiple times to even get it to come up after a configuration change. It's not stable at all.

I've tried leaving it unplugged for at least 2 minutes between power-up attempts, and the same behavior occurs.

This is new-from-box, not otherwise used.

[pshakanet]

Managed to get the PicoStation up, and updated to 3.4-rc. Same lockup issue occurred after starting to change configuration settings. Only power light, no ethernet, no wi-fi lights.

[WHT]

Try defaulting the unit.

[pshakanet]

I have done so, and it continues to exhibit the same behavior.

[along5664]

Ok went on site to a unit that had been up about 2 weeks and it had no ethernet, nor broadcasting ssid....Had to reboot in order to get into it. It is running the 3.4rc software. Let me know what else I can try, to find a solution for this problem.

[along5664]

Found another oen this afternoon with same issue. Same setup as the rest of these that keep locking up and quit broadcasting.....Only light is power, no ethernet no ssid broadcast, a reboot gets it going again. I have setup ping watchdog, to see if it happens again can it recover on its own...

[UBNT-Mike.Ford]

Hello,

Please get me the .sup file.

Thanks,

Mike

[along5664]

I have emailed you the file.

[pshakanet]

Will be updating to the full 3.4 release this afternoon, and will see how that goes.

Would you like me to post config also, or start up a separate thread?

[pshakanet]

After updating my PicoStation to the 3.4 full release, it has become a lot more stable. I'm currently testing without WEP enabled; will be switching over to it in a few to test with it enabled.

All devices have been able to connect to it so far without issue.

[along5664]

I upgraded a few of mine also to the new version posted. It normally took a few days or more before I was seeing the lockup issues. I will upgrade the units I installed the other day at the hotel with the new version. Hopefully this will take care of the issues.

[along5664]

Just checked and one of the units I did yesterday is hung already. I am heading onsite to see what is going on...very frustrating......

[belyache]

I installed a new PICO that I flashed with the latest "stable" firmware. After 1 day in service, the unit has decided that it no longer wants to work. I have a power light and no ethernet or wireless.

I have finally been able to get the unit to respond to ethernet. I am currently upgrading the firmware from 3.3.2.4257.090214-8m to 3.4.4390.090521.1757-8m. I will let you know how it goes after a few days, or earlier if necessary.

Any help would be appreciated.

Glenn

[belyache]

After upgrading and then reconfiguring the AP. I have found the upgrade is working. However, and oddity. If I unplug the ethernet cable to the unit (for a power cycle) when I plug it back in, I do not get ethernet activity... on the other hand, if I pull the power supply cable to power cycle, the ethernet comes back up???? Very strange behavior.

glenn

I installed a new PICO that I flashed with the latest "stable" firmware. After 1 day in service, the unit has decided that it no longer wants to work. I have a power light and no ethernet or wireless.

I have finally been able to get the unit to respond to ethernet. I am currently upgrading the firmware from 3.3.2.4257.090214-8m to 3.4.4390.090521.1757-8m. I will let you know how it goes after a few days, or earlier if necessary.

Any help would be appreciated.

Glenn

[belyache]

It seems I was wrong... I cannot give an accurate way to reboot the system via power cycle. It seems that the system doesn't like to be power cycled, but in the real world power cycles happen.

From what I have seen, if the unit is power cycled once, the unit will not power up properly. But if you pull the power a second time, it will fire up properly... at least that is what is working for me.

Glenn

After upgrading and then reconfiguring the AP. I have found the upgrade is working. However, and oddity. If I unplug the ethernet cable to the unit (for a power cycle) when I plug it back in, I do not get ethernet activity... on the other hand, if I pull the power supply cable to power cycle, the ethernet comes back up???? Very strange behavior.

glenn

I installed a new PICO that I flashed with the latest "stable" firmware. After 1 day in service, the unit has decided that it no longer wants to work. I have a power light and no ethernet or wireless.

I have finally been able to get the unit to respond to ethernet. I am currently upgrading the firmware from 3.3.2.4257.090214-8m to 3.4.4390.090521.1757-8m. I will let you know how it goes after a few days, or earlier if necessary.

Any help would be appreciated.

Glenn

[along5664]

I have seen the same thing. Had the power flick at a site and a unit did not come back up until I powered it the second time.

[MCunha]

I'm having a very similar problem with my brand new, related in the following post:

http://forum.ubnt.com/forum/viewtopic.php?t=11722

But I'm sure this is a hardware issue, having nothing to do with the firmware. To test, I've installed DD-WRT firmware, and the same behavior has happened. So, i don't think this is related to AirOS version.

Regards.

[Shockware1]

I suspect if the power was left unplugged for a longer amount of time you would get better results. Try 60 seconds, then 30, then 20 till you figure out how long it takes. Might take more or less time on different units too

[teté]

I have done so, and it continues to exhibit the same behavior....

[along5664]

Had another power outage at site, that was just a blip of the power and my pico did not come back up. Had to get someone on site to power cycle it again.

[along5664]

Any update on this? I had 2 more this weekend that locked up on a power outage. One was plugged into a ups, and the other 3 on that ups were fine. Seems if the power goes out for a fews seconds they hang on reboot.

[MCunha]

Hi along5664,

I think this is hardware related. You will need a RMA if the reboot is a problem.

Regards.

[along5664]

I have had about 10 of these randomly do this. If it were the same unit every time, yea hardware. But I think there is another issue here.

[WISPNZ]

Any resolution on this UBNT?

[UBNT-Mike.Ford]

Hello,

I am askingmy software tema for an update.

Thanks,

Mike

[WISPNZ]

Hello,

I am askingmy software tema for an update.

Thanks,

Mike

Any update yet :) ?

[UBNT-Mike.Ford]

Any update yet :) ?


Hello,

No not yet. I do apologize as they have been crazy busy, and I have been in Europe. I will follow up with them tommorow when I get back into the office.

Thanks,

Mike