Got to get syslog set up... Haven't had any more of these problems, still don't know what it was. On Jun 28, 2016 1:40 PM, "Chris Ruschmann" <[email protected]> wrote:
> I have almost the same setup as you in several locations. I'm gonna lean > on a bad ground somewhere. Check all your cables to your radios, solar and > everything. Maybe a squirrel thought one of them tasted nice. > > Also setup syslog to a remote server. > On May 30, 2016 1:32 PM, "James Wilson" <[email protected]> wrote: > >> I replaced the switch with a cold backup off the shelf with 1.4 firmware >> and the problems stopped. But it turned out to have a dead fan. >> >> So I put the original switch back in after loading 1.4 firmware and >> manually rebuilding the configuration. Seems to be all back to normal >> now... >> >> On Fri, May 20, 2016 at 11:54 PM, RickG <[email protected]> wrote: >> >>> I saw this a couple times: Once with a bad POE surge protector and >>> another time it had a bad cable. >>> BTW: Firmware v1.4.0 - FINAL is out!!! >>> >>> On Fri, May 20, 2016 at 8:37 PM, James Wilson <[email protected]> >>> wrote: >>> >>>> This is sort of UBNT related - all of the radios are UBNT with a >>>> Netonix switch. I posted this on the Netonix forums, but they aren't as >>>> widely traveled. >>>> >>>> So I'm kind of crossposting here to see if anyone has some ideas. >>>> Thanks! >>>> >>>> We're having a problem that we're having a lot of trouble >>>> troubleshooting. I brought this up with Chris today, but no answers yet. >>>> >>>> So we have a solar powered relay site that takes about an hour to get >>>> to. In the last few days the site has been going down intermittently. And >>>> it may have been longer than that, but maybe not long enough outages for >>>> AirControl 1 to send us an alarm. >>>> >>>> Yesterday afternoon the old switch (running 1.3.2) went down and didn't >>>> come back up until about 1:30 am this morning. We could log into the >>>> backhaul and the backhaul showed link at 100 Mbps Full duplex, but we >>>> couldn't log into the switch or anything past it. The backhaul is a >>>> NanoBridge and we have three Rockets hooked to it as APs. >>>> >>>> Some ants had gotten into the enclosure and we thought that was the >>>> problem with the switch. So we swapped in a new switch, (running 1.4.0rc25) >>>> stayed around about an hour to watch it and saw no problems. >>>> >>>> This afternoon the new switch started rebooting. And the backhaul radio >>>> would lose power when the switch rebooted. >>>> >>>> I updated the firmware on the old switch and let it run on the bench >>>> for several hours with no problem. >>>> >>>> There are no AirFibers connected to this switch, but we do have an AF >>>> connected to a different WS-8-250-DC at a different site. >>>> >>>> I copied the log from the new switch below and maybe I can figure out >>>> how to insert a screen shot if that will help. >>>> >>>> >>>> >>>> Help! :) >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Dec 31 19:00:04 sysinit: killall: udhcpc: no process killed >>>> Dec 31 19:00:05 netonix: 1.4.0rc25 on WS-8-250-DC >>>> Dec 31 19:00:07 kernel: vtss_core: module license '(c) Vitesse >>>> Semiconductor Inc.' taints kernel. >>>> Dec 31 19:00:07 kernel: switch: 'Luton26' board detected >>>> Dec 31 19:00:09 kernel: vtss_port: Loaded port module on board Luton26, >>>> type 5 >>>> Dec 31 19:00:09 kernel: nf_conntrack version 0.5.0 (2048 buckets, 8192 >>>> max) >>>> Dec 31 19:00:10 kernel: i2c /dev entries driver >>>> Dec 31 19:00:10 system: Setting MAC address from flash configuration: >>>> EC:13:B3:51:xx:xx >>>> Dec 31 19:00:10 kernel: i2c_vcoreiii i2c_vcoreiii: i2c bus driver on >>>> IRQ 19 >>>> Dec 31 19:00:11 sysinit: Loading defaults >>>> Dec 31 19:00:11 sysinit: Adding custom chains >>>> Dec 31 19:00:11 system: starting ntpclient >>>> Dec 31 19:00:12 sysinit: Loading zones >>>> Dec 31 19:00:12 sysinit: Loading forwarding >>>> Dec 31 19:00:12 sysinit: Loading redirects >>>> Dec 31 19:00:12 sysinit: Loading rules >>>> Dec 31 19:00:12 sysinit: Loading includes >>>> Dec 31 19:00:12 admin: adding lan (eth0) to firewall zone lan >>>> Dec 31 19:00:17 Port: link state changed to 'up' (100M-F) on port 3 >>>> Dec 31 19:00:17 Port: link state changed to 'up' (10M-F) on port 1 >>>> Dec 31 19:00:18 sysinit: killall: telnetd: no process killed >>>> Dec 31 19:00:18 Port: link state changed to 'up' (10M-F) on port 5 >>>> Dec 31 19:00:18 Port: link state changed to 'up' (10M-F) on port 7 >>>> Dec 31 19:00:19 sysinit: 1969-12-31 19:00:18: (log.c.97) server started >>>> Dec 31 19:00:20 dropbear[741]: Running in background >>>> Dec 31 19:00:21 kernel: eth0: no IPv6 routers present >>>> Dec 31 19:00:22 Port: link state changed to 'down' on port 5 >>>> Dec 31 19:00:22 Port: link state changed to 'down' on port 1 >>>> Dec 31 19:00:23 Port: link state changed to 'down' on port 7 >>>> Dec 31 19:00:23 switch[769]: Detected cold boot >>>> Dec 31 19:00:24 Port: link state changed to 'down' on port 3 >>>> Dec 31 19:00:25 switch[769]: PoE enabled on port 1, PoE Smart is >>>> starting cable check >>>> Dec 31 19:00:25 switch[769]: PoE enabled on port 3, PoE Smart is >>>> starting cable check >>>> Dec 31 19:00:25 switch[769]: PoE enabled on port 5, PoE Smart is >>>> starting cable check >>>> Dec 31 19:00:25 switch[769]: PoE enabled on port 7, PoE Smart is >>>> starting cable check >>>> Dec 31 19:00:25 system: starting ntpclient >>>> Dec 31 19:00:30 switch[769]: Port 1 cable check results: Ok, Ok, Short, >>>> Short >>>> Dec 31 19:00:30 switch[769]: Port 1 passed PoE Smart cable check, >>>> turning on power >>>> Dec 31 19:00:30 switch[769]: Port 3 cable check results: Open, Open, >>>> Short, Short >>>> Dec 31 19:00:30 switch[769]: Port 3 passed PoE Smart cable check, >>>> turning on power >>>> Dec 31 19:00:30 switch[769]: Port 5 cable check results: Ok, Ok, >>>> Abnormal termination, Abnormal termination >>>> Dec 31 19:00:30 switch[769]: Port 5 passed PoE Smart cable check, >>>> turning on power >>>> Dec 31 19:00:30 switch[769]: Port 7 cable check results: Ok, Ok, Short, >>>> Short >>>> Dec 31 19:00:30 switch[769]: Port 7 passed PoE Smart cable check, >>>> turning on power >>>> Dec 31 19:00:32 Port: link state changed to 'up' (10M-F) on port 1 >>>> Dec 31 19:00:32 Port: link state changed to 'up' (10M-F) on port 5 >>>> Dec 31 19:00:33 Port: link state changed to 'up' (10M-F) on port 7 >>>> Dec 31 19:00:36 system: starting ntpclient >>>> Dec 31 19:00:38 Port: link state changed to 'up' (100M-F) on port 3 >>>> Dec 31 19:00:47 system: starting ntpclient >>>> Dec 31 19:00:55 Port: link state changed to 'down' on port 3 >>>> Dec 31 19:00:55 Port: link state changed to 'down' on port 1 >>>> Dec 31 19:00:56 Port: link state changed to 'down' on port 5 >>>> Dec 31 19:00:56 Port: link state changed to 'down' on port 7 >>>> Dec 31 19:00:57 Port: link state changed to 'up' (100M-F) on port 3 >>>> Dec 31 19:00:57 Port: link state changed to 'up' (100M-F) on port 1 >>>> Dec 31 19:00:58 Port: link state changed to 'up' (100M-F) on port 5 >>>> Dec 31 19:00:58 Port: link state changed to 'up' (100M-F) on port 7 >>>> Dec 31 19:00:59 system: starting ntpclient >>>> Dec 31 19:01:10 system: starting ntpclient >>>> Dec 31 19:01:21 system: starting ntpclient >>>> >>>> _______________________________________________ >>>> Ubnt_users mailing list >>>> [email protected] >>>> http://lists.wispa.org/mailman/listinfo/ubnt_users >>>> >>>> >>> >>> >>> -- >>> -RickG KyWiFi >>> >>> _______________________________________________ >>> Ubnt_users mailing list >>> [email protected] >>> http://lists.wispa.org/mailman/listinfo/ubnt_users >>> >>> >> >> _______________________________________________ >> Ubnt_users mailing list >> [email protected] >> http://lists.wispa.org/mailman/listinfo/ubnt_users >> >> > _______________________________________________ > Ubnt_users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/ubnt_users > >
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
