Reply
New Member
Posts: 5
Registered: ‎11-02-2018

Re: Having serious issues with UniFi Security Gateway 3P - Freezes everyday!

I dove in deeper this AM... I went thru 3MB worth of logs. Here is a pattern that repeats itself.

 

The key problem is this:

[2019-01-12 10:32:20,529] <inform-25> INFO dev - saveDeviceAttr(): device[fc:ec:da:d7:07:3c][ip]=0.0.0.0 (orig=24.16.30.7)
[2019-01-12 10:32:20,534] <inform-25> INFO dev - [state] dev[fc:ec:da:d7:07:3c] UNKNOWN->CONNECTED, state_expire=0

 

Anyone else have the few lines in their logs? (Search for "<inform-25> INFO dev - saveDeviceAttr(): device")

 

 

Added comments as >>> ALL CAPS COMMENTS

   

>>> PROPER WAN ADDRESS (I CHANGED IT)


[2019-01-12 10:29:26,039] <inform-35> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=UNKNOWN, last_inform=40, ext/stun_ip=10.70.1.1, dev_ip=24.16.30.7, up=3029

 

>> LOADS OF THESE

[2019-01-12 10:29:34,185] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried

[2019-01-12 10:29:34,201] <MQTT Con: b340d6e3-89ae-4658-92f8-b0143e12cbc1> WARN AwsIotMqttConnectionListener - Connect request failure
MqttException (0) - java.net.UnknownHostException: xxxxxxxxxxxxxxxxxx.iot.us-west-2.amazonaws.com
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.UnknownHostException: xxxxxxxxxxxxxxxxxx.iot.us-west-2.amazonaws.com
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more


[2019-01-12 10:29:34,205] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:30:04,206] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:30:04,234] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:30:34,237] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:30:34,273] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:31:04,275] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:31:15,324] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

[2019-01-12 10:31:45,325] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:31:56,377] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

 

>> AFTER MANY RETRIES, THE IP FROM USG INFORM COMES BACK AS 0.0.0.0

 

[2019-01-12 10:32:20,528] <inform-25> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=UNKNOWN, last_inform=174, ext_ip=10.70.1.1, dev_ip=0.0.0.0, up=155

 

>>> THE USG TAKES WHAT WAS THE VALID IP ADDRESS AND SAVES 0.0.0.0 AS VALID. CLEARLY NOT GOOD GIVEN THE NETWORK CONNECTION IS IN FACT UP.


[2019-01-12 10:32:20,529] <inform-25> INFO dev - saveDeviceAttr(): device[fc:ec:da:d7:07:3c][ip]=0.0.0.0 (orig=24.16.30.7)
[2019-01-12 10:32:20,534] <inform-25> INFO dev - [state] dev[fc:ec:da:d7:07:3c] UNKNOWN->CONNECTED, state_expire=0

 

>>> FOLLOWING THS PERSISTENCE OF 0.0.0.0, THE USG BELIEVES IT IS NOW CONNECTED AND ACTS THAT WAY FROM HERE ON OUT.


[2019-01-12 10:32:20,536] <inform-25> INFO event - [event] Gateway[fc:ec:da:d7:07:3c] was connected
[2019-01-12 10:32:21,106] <inform-27> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=CONNECTED, last_inform=1, ext_ip=10.70.1.1, dev_ip=0.0.0.0, up=160

 

>>> YET, IOT CONNECTIONS CONTINUE TO FAIL FOR OBVIOUS REASONS (0.0.0.0 IS BEING ATTEMPTED)

 

[2019-01-12 10:32:26,379] <pool-6-thread-1> INFO AwsIotConnection - Connection is being retried
[2019-01-12 10:32:37,419] <pool-6-thread-1> INFO AwsIotConnection - Connection temporarily lost

[2019-01-12 10:32:37,449] <inform-91> INFO inform - from [fc:ec:da:d7:07:3c](net-vsh-usg, UGW3, 4.4.36.5146617): state=CONNECTED, last_inform=6, ext/stun_ip=10.70.1.1, dev_ip=0.0.0.0, up=176

 

 

House: 1x USG4, 1x sw-48x500w, 1x sw-8x60w, 3x sw-8, 2x ap-NanoHD, 1x ap-LR, 1x Cloudkey2
Cabin:1x USG3, 1x sw-8x60w, 3x sw-8, 1x ap-NanoHD, 1x Win10-Cloudkey
New Member
Posts: 2
Registered: ‎05-30-2016
Kudos: 1

Re: Having serious issues with UniFi Security Gateway 3P - Freezes everyday!

[ Edited ]

I'm having this issue, too. Depressingly, it's with a USG Pro,, installed for a finance company that has a small cafe attached. I look like a right royal knob seeing as the piece of trash Huawei modem, worth about $4.27, is outperforming the thousands of dollars worth of Unify gear.

 

Worse still, I'm not there, and can't access remotely, and the network can't be turned reset. Very frustrating...

This is not giving me much confidence in continuing to use the USG's.

 

Z... 

New Member
Posts: 3
Registered: ‎12-16-2018

Re: Having serious issues with UniFi Security Gateway 3P - Freezes everyday!

[ Edited ]

I had serious problems with USG Unifi Router - Freezes, no boot after flash, 6 moth i got this problem until USG complety dead. BUT dead is ONLY usb pendrive inside! Please check Your USB Pendrive which is inside of USG Router inserted! Flash has complety broken. I downloaded img image of flash and burdned via DMDE on new USB STIKC and now my USG works great again!

 

https://dl.ubnt-ut.com/cmb/USG-4_2_0-shipped.img.bz2

Przechwytywanie.JPG
New Member
Posts: 15
Registered: ‎09-11-2018
Kudos: 2

Re: Having serious issues with UniFi Security Gateway 3P - Freezes everyday!

Figured I should chime in since I'm the one that started this thread months ago.

 

I had to switch to a 4P (Pro) Gateway, then all was right again. And to those who say my 3P was faulty, it wasn't. I've had it at my mom's for the last few months with no issue. It's being running off my UniFi controller too, so I would be able to see if locks up, but both have been pretty stable.

 

Bottom line, the 3P is not equiped to deal with networks that actually have a lot of stuff on them. Sad but true. And most of us don't have tiny networks. Mine isn't crazy, but surely isn't small either. I would say on average I have around 50 clients connected to my network at all times. Whereas at my mom's there's about 6-7 devices connected at all times. That's a huge difference for the 3P. It just couldn't handle it.

 

My latest problems have been with the 10gb switch I just got from Ubiquiti. Not as powerful as I hoped. I also have a QNAP 16 port 10gb switch, and to honest, it does circles around my US-16-XG. Maybe firmware will help with that one.

 

But overall everything is stable now, and has been for some time. So that's #1 for me right now.

 

Here's my current setup now.

(1) Ubiquiti Cloud Key (UC‑CK)

(1) Ubiquiti Security Gateway 4P (USG-4P-Pro)

(1) Ubiquiti 16 port Poe Switch (US‑16‑150W)

(1) Ubiquiti 16 port 10Gb Switch (US-16-XG)

(2) Ubiquiti AP-AC-HD Access Points (UAP‑AC‑HD)

Reply