Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
Highlighted
New Member
Posts: 12
Registered: ‎01-22-2015
Kudos: 3
Accepted Solution

Unstable Security Gateway

First, a huge thanks to this community. You've helped me numerous times debug my devices, and for that I'm incredibly thankful. This particular problem has been incredibly painful. I've done a lot of combing through these forums, and following some general strategies, haven't been able to figure out the cause of the issue, or even to generate any kind of idea on how to fix it.

 

Problem: My USG (fw 4.2.6.4751786) restarts itself numerous times per day. Most days it resets once. Sometimes it can reset itself 3-4 times in a single 60 minute period. Sometimes (like this morning, although incredibly rare) the device will completely disconnect, and require plugging out/in the power cable to get it to reset.

 

I've been working with Unifi's Support people, sending them my console logs, and they say they're checking into the problem. Since many of you have expertise that far outranks my own, I figured publicly posting this issue, and hopefully its eventual solution may be of assistance to the general community.

 

Some current knowledge...

  • Controller is not restarting the USG. Controller logs simply indicate a "Heartbeat Missed" status, which is followed up by reconnect update. There's nothing previous in the controller logs. I can see it's past inform:8080 status update as connected, and then the next line, it's in Heartbeat Missed, with nothing suspicious around it.
  • Server room is maintained at 75 deg F. USG has great airflow and is not obstructed (nor on a metal surface).
  • Controller version is 4.6.3.
  • I've tinkered with the USG (custom VPN stuffs, squidguard), but have reset it back to factory default settings a number of times, without the ability to resolve it.

Speculation and questions...

  • This behavior seems to align with a past controller software update. I update to 4.6.3 a few months ago I believe. I don't think that the USG was doing this before.
  • I believe the device was restarting before I had done the CLI backend tinkering mentioned above. Is it possible that that tinkering somehow is causing the problems? Even though I've factory reset it numerous times? (Both set-default CLI command, and reset button?)
  • I've also (recently) "Forget this AP" from the controller, resetting it to factory and readopting it through those means.

In other USG debugging posts, there's a request for console output. I've attached two .txt logs that represent the output from a few crashes. It doesn't make any sense to me, other than the fact that something critical is occurring and causing the device to restart.

 

Thank you so much for the help, and please feel free to ask any questions.


Accepted Solutions
Ubiquiti Employee
Posts: 6,816
Registered: ‎01-28-2013
Kudos: 7327
Solutions: 569
Contributions: 20

Re: Unstable Security Gateway

[ Edited ]

For anyone that reads this, the firmware with the fix for this is included in controller version 4.6.6. It provides stable operation while leaving hardware offload enabled.

 

Cheers,

Mike

 

EDIT: currently the controller is in soaking status (near stable), so it's only avilable in the beta section. If you can't access the above post please see THIS KB article.

UBNT_Alternate_Logo.png

View solution in original post


All Replies
New Member
Posts: 12
Registered: ‎01-22-2015
Kudos: 3

Re: Unstable Security Gateway

Welcome to EdgeOS Gateway ttyS0

By logging in, accessing, or using the Ubiquiti product, you
acknowledge that you have read and understood the Ubiquiti
License Agreement (available in the Web UI at, by default,
http://192.168.1.1) and agree to be bound by its terms.

Gateway login: administrator
Password:
Linux Gateway 3.4.27-UBNT #1 SMP Tue Aug 12 17:54:01 PDT 2014 mips64
Welcome to EdgeOS
administrator@Gateway:~$ skb_under_panic: text:ffffffff8044d8bc len:60 put:-4 he
ad:800000041d01a000 data:800000031d01a146 tail:0x182 end:0xe80 dev:eth1
Kernel bug detected[#1]:
Cpu 0
$ 0   : 0000000000000000 0000000050108ce1 0000000000000085 0000000000000001
$ 4   : 0000000000000001 0000000000000000 0000000000000244 0000000000000000
$ 8   : 0000000000000004 000000000000000a 000000000000ffff 0000000000000003
$12   : 000000000000000f ffffffff802e969c ffffffffb8b0851d 0000000000000000
$16   : 800000041defb780 800000041d5c8800 800000041caca000 800000041d01a142
$20   : 0000000000000040 0000000000000040 ffffffff806000a0 ffffffff80621280
$24   : 0000000000000002 ffffffffc0090000
$28   : ffffffff805e4000 ffffffff805e79b0 0000000000000001 ffffffff803a9a30
Hi    : 0000000000000005
Lo    : 333333333333333b
epc   : ffffffff803a9a30 skb_push+0x70/0x80
    Tainted: P           O
ra    : ffffffff803a9a30 skb_push+0x70/0x80
Status: 50108ce3    KX SX UX KERNEL EXL IE
Cause : 00800024
PrId  : 000d0601 (Cavium Octeon+)
Modules linked in: xt_mac ipt_REDIRECT xt_mark xt_multiport cvm_ipsec_kame(O) 80
21q garp stp llc ipt_MASQUERADE xt_set xt_state xt_comment ip_set_bitmap_port xt
_TCPMSS xt_tcpudp ip6table_mangle ip6table_filter ip6table_raw ip6_tables iptabl
e_nat iptable_mangle xt_NOTRACK iptable_raw nf_nat_pptp nf_conntrack_pptp nf_con
ntrack_proto_gre nf_nat_h323 nf_conntrack_h323 nf_nat_sip nf_conntrack_sip nf_na
t_proto_gre nf_nat_tftp nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_co
nntrack_tftp nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables ip_
set_hash_net ip_set nfnetlink ipv6 jeetpktdo(PO) unifigpio(PO) unifihal(PO) cavi
um_ip_offload(PO) octeon_rng rng_core octeon_ethernet ethernet_mem mdio_octeon o
f_mdio ubnt_platform(PO) libphy
Process swapper/0 (pid: 0, threadinfo=ffffffff805e4000, task=ffffffff80602400, t
ls=0000000000000000)
Stack : 800000041caca000 8000000410235d80 8000000410235d80 ffffffff8044d8bc
        800000041caca000 800000041d01a146 800000041defb780 800000041d3d3c80
        ffffffff80600608 800000041caca000 ffffffff806672c8 ffffffff80600000
        ffffffff806000a0 ffffffff803b420c 800000041d3d3cc8 ffffffffc0090428
        800000041defb780 5000d056b8b0851d 800000041defb780 0000000000000001
        ffffffffc007e180 800000041cb56480 0000000000000000 0000000000000001
        0000000000000001 0000000080000000 800000041cac8680 ffffffff803b57a8
        0000000000000001 0000000080000000 800000041defb780 ffffffffc007533c
        0000000000000000 0000000000000000 0000000000000020 0000000000000001
        8001670000000000 ffffffffc007e400 000000000000ffff 0000000000000001
        ...
Call Trace:
[<ffffffff803a9a30>] skb_push+0x70/0x80


Code: 6484ec88  0c116e35  0040482d <0200000d> 3c038051  080ea686  6463e280  8c83
0174  dc870180
---[ end trace 81701f93780d905b ]---
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 60 seconds..
*** NMI Watchdog interrupt on Core 0x01 ***
        $0      0x0000000000000000      at      0x0000000010108ce0
        v0      0xffffffff80139d20      v1      0x0000000000000001
        a0      0xfffffffffffffffd      a1      0x0000000000000000
        a2      0x000000000000cecb      a3      0x0000000000000000
        a4      0x0000000000493a54      a5      0x0000000071f0daf8
        a6      0x0000000000a6ffac      a7      0x0000000000000000
        t0      0x0000000000000000      t1      0x000000001000001f
        t2      0x000000000000000c      t3      0x0000000000000000
        s0      0xffffffff80670000      s1      0x0000000000000001
        s2      0x0000000000200200      s3      0x0000000000100100
        s4      0x000000007726a2d4      s5      0x0000000000000069
        s6      0x0000000000000000      s7      0x0000000000a6fe1c
        t8      0x0000000000000001      t9      0x0000000000000000
        k0      0x0000000000000000      k1      0x0000000000000000
        gp      0x800000041cb6c000      sp      0x800000041cb6fd30
        s8      0xffffffff804ef490      ra      0xffffffff80141410
        err_epc 0xffffffff80139d40      epc     0x000000007726a2d4
        status  0x0000000010588ce4      cause   0x0000000040808800
        sum0    0x000400f000000000      en0     0x0000000000000000
*** Chip soft reset soon ***

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000


U-Boot 1.1.1 (UBNT Build ID: 4674499-gfa58f5d) (Build time: Jun  9 2014 - 14:38:
01)

BIST check passed.
UBNT_E120 r1:0, r2:16, f:8/135, serial #: 0418D6A129F3
MPR 13-02044-16
Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM:  512 MB
Clearing DRAM....... done
Flash:  8 MB
Net:   octeth0, octeth1, octeth2

USB:   (port 0) scanning bus for devices... 1 USB Devices found
       scanning bus for storage devices...
  Device 0: Vendor:          Prod.: USB DISK 2.0     Rev: PMAP
            Type: Removable Hard Disk
            Capacity: 3824.0 MB = 3.7 GB (7831552 x 512)
 0
reading vmlinux.64
............................

5683792 bytes read
argv[2]: coremask=0x3
argv[3]: root=/dev/sda2
argv[4]: rootdelay=15
argv[5]: rw
argv[6]: rootsqimg=squashfs.img
argv[7]: rootsqwdir=w
argv[8]: mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@1024k(eeprom)
ELF file is 64 bit
Allocating memory for ELF segment: addr: 0xffffffff80100000 (adjusted to: 0x1000
00), size 0x59c5f0
Allocated memory for ELF segment: addr: 0xffffffff80100000, size 0x59c5f0
Processing PHDR 0
  Loading 567400 bytes at ffffffff80100000
  Clearing 351f0 bytes at ffffffff80667400
## Loading Linux kernel with entry point: 0xffffffff804585b0 ...
Bootloader: Done loading app on coremask: 0x3
Linux version 3.4.27-UBNT (ancheng@ubnt-builder2) (gcc version 4.7.0 (Cavium Inc
. Version: SDK_3_0_0 build 16) ) #1 SMP Tue Aug 12 17:54:01 PDT 2014
CVMSEG size: 2 cache lines (256 bytes)
Cavium Inc. SDK-3.0
bootconsole [early0] enabled
CPU revision is: 000d0601 (Cavium Octeon+)
Checking for the multiply/shift bug... no.
Checking for the daddiu bug... no.
Determined physical RAM map:
 memory: 0000000007800000 @ 0000000000700000 (usable)
 memory: 0000000007c00000 @ 0000000008200000 (usable)
 memory: 000000000fc00000 @ 0000000410000000 (usable)
 memory: 0000000000047000 @ 0000000000629000 (usable after init)
Wasting 88312 bytes for tracking 1577 unused pages
Placing 0MB software IO TLB between 8000000001707000 - 8000000001747000
software IO TLB at phys 0x1707000 - 0x1747000
Zone PFN ranges:
  DMA32    0x00000629 -> 0x000f0000
  Normal   0x000f0000 -> 0x0041fc00
Movable zone start PFN for each node
Early memory PFN ranges
    0: 0x00000629 -> 0x00000670
    0: 0x00000700 -> 0x00007f00
    0: 0x00008200 -> 0x0000fe00
    0: 0x00410000 -> 0x0041fc00
Cavium Hotplug: Available coremask 0x0
Primary instruction cache 32kB, virtually tagged, 4 way, 64 sets, linesize 128 b
ytes.
Primary data cache 16kB, 64-way, 2 sets, linesize 128 bytes.
Secondary unified cache 128kB, 8-way, 128 sets, linesize 128 bytes.
PERCPU: Embedded 10 pages/cpu @8000000001784000 s9216 r8192 d23552 u40960
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 67946
Kernel command line:  bootoctlinux $loadaddr coremask=0x3 root=/dev/sda2 rootdel
ay=15 rw rootsqimg=squashfs.img rootsqwdir=w mtdparts=phys_mapped_flash:512k(boo
t0),512k(boot1),64k@1024k(eeprom) console=ttyS0,115200
PID hash table entries: 2048 (order: 2, 16384 bytes)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 499340k/508188k available (3469k kernel code, 8848k reserved, 1812k data
, 284k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:256
Calibrating delay loop (skipped) preset value.. 1000.00 BogoMIPS (lpj=5000000)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 256
Checking for the daddi bug... no.
SMP: Booting CPU01 (CoreId  1)...
CPU revision is: 000d0601 (Cavium Octeon+)
Brought up 2 CPUs
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource OCTEON_CVMCOUNT
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
ERROR: octeon_pci_console_setup0 failed.
/proc/octeon_perf: Octeon performance counter interface loaded
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering unionfs 2.5.11 (for 3.4)
msgmni has been set to 975
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
loop: module loaded
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
OcteonUSB 16f0010000000.usbc: Octeon Host Controller
OcteonUSB 16f0010000000.usbc: new USB bus registered, assigned bus number 1
OcteonUSB 16f0010000000.usbc: irq 56, io mem 0x00000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
OcteonUSB: Registered HCD for port 0 on irq 56
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
octeon_wdt: Initial granularity 5 Sec
TCP: cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
L2 lock: TLB refill 256 bytes
L2 lock: General exception 128 bytes
L2 lock: low-level interrupt 128 bytes
L2 lock: interrupt 640 bytes
L2 lock: memcpy 1152 bytes
1180000000800.serial: ttyS0 at MMIO 0x1180000000800 (irq = 34) is a OCTEON
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
1180000000c00.serial: ttyS1 at MMIO 0x1180000000c00 (irq = 35) is a OCTEON
Bootbus flash: Setting flash for 8MB flash at 0x1f400000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank. Manufacturer ID 0x0
000c2 Chip ID 0x0000c9
Amd/Fujitsu Extended Query Table at 0x0040
  Amd/Fujitsu Extended Query version 1.1.
phys_mapped_flash: Swapping erase regions for top-boot CFI table.
number of CFI chips: 1
3 cmdlinepart partitions found on MTD device phys_mapped_flash
Creating 3 MTD partitions on "phys_mapped_flash":
0x000000000000-0x000000080000 : "boot0"
0x000000080000-0x000000100000 : "boot1"
0x000000100000-0x000000110000 : "eeprom"
Waiting 15sec before mounting root device...
usb 1-1: new high-speed USB device number 2 using OcteonUSB
scsi0 : usb-storage 1-1:1.0
scsi 0:0:0:0: Direct-Access              USB DISK 2.0     PMAP PQ: 0 ANSI: 6
sd 0:0:0:0: [sda] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] No Caching mode page present
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk
kjournald starting.  Commit interval 3 seconds
EXT3-fs (sda2): using internal journal
EXT3-fs (sda2): recovery complete
EXT3-fs (sda2): mounted filesystem with journal data mode
VFS: Mounted root (unionfs filesystem) on device 0:11.
Freeing unused kernel memory: 284k freed
Algorithmics/MIPS FPU Emulator v1.5
INIT: version 2.88 booting
INIT: Entering runlevel: 2
Starting daemon monitor: monit.
Starting routing daemon: rib.
Starting EdgeOS router: migrate rl-system configure


 

New Member
Posts: 12
Registered: ‎01-22-2015
Kudos: 3

Re: Unstable Security Gateway

I apologize for the code spam, but the system is not letting me attach my .txt files. Below is another snippet, that's more relevant to the crash, without the restart spam.

 

skb_under_panic: text:ffffffff8044d8bc len:60 put:-4 head:8000000001ae1000 data&colon;7fffffff01ae1146 tail:0x182 end:0xe80 dev:eth1
Kernel bug detected[#1]:
Cpu 0
$ 0   : 0000000000000000 0000000050108ce1 0000000000000085 0000000000000001
$ 4   : 0000000000000001 0000000000000000 000000000000026f 0000000000000000
$ 8   : 0000000000000004 000000000000000a 000000000000ffff 0000000000000003
$12   : 000000000000000f ffffffff802e969c ffffffffb8b0851d 0000000000000000
$16   : 800000041ca2a180 800000041c135000 800000041cab5000 8000000001ae1142
$20   : 0000000000000040 0000000000000040 ffffffff806000a0 ffffffff80621280
$24   : 0000000000000002 ffffffffc0090000                                  
$28   : ffffffff805e4000 ffffffff805e79b0 0000000000000001 ffffffff803a9a30
Hi    : 0000000000000000
Lo    : 0000000000000000
epc   : ffffffff803a9a30 skb_push+0x70/0x80
    Tainted: P           O
ra    : ffffffff803a9a30 skb_push+0x70/0x80
Status: 50108ce3    KX SX UX KERNEL EXL IE 
Cause : 00800024
PrId  : 000d0601 (Cavium Octeon+)
Modules linked in: xt_mac ipt_REDIRECT xt_mark xt_multiport cvm_ipsec_kame(O) 8021q garp stp llc ipt_MASQUERADE xt_set xt_state xt_comment ip_set_bitmap_port xt_TCPMSS xt_tcpudp ip6table_mangle ip6table_filter ip6table_raw ip6_tables iptable_nat iptable_mangle xt_NOTRACK iptable_raw nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_h323 nf_conntrack_h323 nf_nat_sip nf_conntrack_sip nf_nat_proto_gre nf_nat_tftp nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables ip_set_hash_net ip_set nfnetlink ipv6 jeetpktdo(PO) unifigpio(PO) unifihal(PO) cavium_ip_offload(PO) octeon_rng rng_core octeon_ethernet ethernet_mem mdio_octeon of_mdio ubnt_platform(PO) libphy
Process swapper/0 (pid: 0, threadinfo=ffffffff805e4000, task=ffffffff80602400, tls=0000000000000000)
Stack : 800000041cab5000 8000000001b8eb80 8000000001b8eb80 ffffffff8044d8bc
        800000041cab5000 8000000001ae1146 800000041ca2a180 800000041d4f6c80
        ffffffff80600608 800000041cab5000 ffffffff806672c8 ffffffff80600000
        ffffffff806000a0 ffffffff803b420c 800000041d4f6cc8 ffffffffc0090428
        800000041ca2a180 5000d8c1b8b0851d 800000041ca2a180 0000000000000002
        ffffffffc007e180 800000041cb2c680 0000000000000000 0000000000000001
        0000000000000001 0000000080000000 800000041cab3680 ffffffff803b57a8
        0000000000000001 0000000080000000 800000041ca2a180 ffffffffc007533c
        800000041ce078b0 8000000001784b68 0000000000000020 0000000000000001
        8001670000000000 ffffffffc007e400 000000000000ffff 0000000000000001
        ...
Call Trace:
[<ffffffff803a9a30>] skb_push+0x70/0x80


Code: 6484ec88  0c116e35  0040482d <0200000d> 3c038051  080ea686  6463e280  8c830174  dc870180 
---[ end trace 3e062e2090e63eb9 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 60 seconds..
*** NMI Watchdog interrupt on Core 0x01 ***
	$0	0x0000000000000000	at	0x0000000010108ce0
	v0	0xffffffff80139d20	v1	0x0000000000000001
	a0	0xfffffffffffffffd	a1	0x0000000000000000
	a2	0x00000000000022d5	a3	0xffffffffffff00fe
	a4	0x0000000000000400	a5	0x0000000000000400
	a6	0x800000041ce07708	a7	0x800000041ce077c0
	t0	0x0000000000000000	t1	0x000000001000001f
	t2	0x800000041ce04000	t3	0x0000000000000000
	s0	0xffffffff80670000	s1	0x0000000000000001
	s2	0x0000000000200200	s3	0x0000000000100100
	s4	0xffffffff80139d40	s5	0x0000000000000069
	s6	0x0000000000000000	s7	0x800000041ff00000
	t8	0x0000000000000001	t9	0xffffffff80188e80
	k0	0x0000000000000000	k1	0x0000000000000000
	gp	0x800000041c0a4000	sp	0x800000041c0a7bb0
	s8	0xffffffff804ef490	ra	0xffffffff80141410
	err_epc	0xffffffff80139d40	epc	0xffffffff80139d40
	status	0x0000000010588ce4	cause	0x0000000040808800
	sum0	0x000000f000000000	en0	0x0000000000000000
*** Chip soft reset soon ***

Looking for valid bootloader image....
Jumping to start of image at address 0xbfc80000
Ubiquiti Employee
Posts: 6,816
Registered: ‎01-28-2013
Kudos: 7327
Solutions: 569
Contributions: 20

Re: Unstable Security Gateway

[ Edited ]

Thanks again for the report. I've sent you a PM about this.

 

Thanks,

Mike

 

EDIT: Nevermind about my PM, I see a .supp file in the support ticket. That should be sufficient. Will report back..

UBNT_Alternate_Logo.png
Ubiquiti Employee
Posts: 6,816
Registered: ‎01-28-2013
Kudos: 7327
Solutions: 569
Contributions: 20

Re: Unstable Security Gateway

So, going by THIS post, and the OP in this thread, I'm guessing you haven't noticed any particular activities that are triggering the restart? I know you tried the main known issue (at the present time). 

 

I don't see anything listed in the OP about a particular activity. Just wanted to confirm.

 

Cheers,

Mike

UBNT_Alternate_Logo.png
New Member
Posts: 12
Registered: ‎01-22-2015
Kudos: 3

Re: Unstable Security Gateway

I cannot really confirm a definite behavior.

 

Just yesterday I spent some time going through the last 10 or so restarts, checking syslog, and controller log, hoping to find a common cause. There didn't seem to be similar behavior from my clients (lots of AP switching, guest authentications) during the restarts.

 

I could never recreate it. My first hunches were that client load (10-15 active), throw in some Skype and an MMO might just be causing too much... but then the system will restart at a weird time when only a few clients are active, and the load isn't large.

 

Small update: System does seem more stable since yesterday. Haven't had a restart in about 20hrs. Might be the offload disables, but I also wonder if it had something to do with my "Forget this device" and complete factory reset.

 

 

 

 

New Member
Posts: 12
Registered: ‎01-22-2015
Kudos: 3

Re: Unstable Security Gateway

Two restarts today, about an hour apart, both happened to be around peak times of guest access.

 

I believe my support ticket ID is 175092.

 

I emailed two files, each representing a restart, and each file contains logs from server.log, syslog, and console, around the restart time.

 

 

 

 

 

Ubiquiti Employee
Posts: 6,816
Registered: ‎01-28-2013
Kudos: 7327
Solutions: 569
Contributions: 20

Re: Unstable Security Gateway

So it's been recreated in the lab. It's a little too early to comment on anything more than that, but we should see this resolved, possibly as early as the next release. 

 

Cheers,

Mike

UBNT_Alternate_Logo.png
Ubiquiti Employee
Posts: 6,816
Registered: ‎01-28-2013
Kudos: 7327
Solutions: 569
Contributions: 20

Re: Unstable Security Gateway

[ Edited ]

For anyone that reads this, the firmware with the fix for this is included in controller version 4.6.6. It provides stable operation while leaving hardware offload enabled.

 

Cheers,

Mike

 

EDIT: currently the controller is in soaking status (near stable), so it's only avilable in the beta section. If you can't access the above post please see THIS KB article.

UBNT_Alternate_Logo.png
New Member
Posts: 39
Registered: ‎02-06-2015
Kudos: 1
Solutions: 1

Re: Unstable Security Gateway

I get access denied why trying to go to the link to v4.6.6.  Should it be available to everyone?

Ubiquiti Employee
Posts: 6,816
Registered: ‎01-28-2013
Kudos: 7327
Solutions: 569
Contributions: 20

Re: Unstable Security Gateway


jbrockett wrote:

I get access denied why trying to go to the link to v4.6.6.  Should it be available to everyone?


Yes, although you have to sign up for beta access as right now it's in soaking status (that means near stable). I'm about to update my post to include the link. I've added access to your account.

 

Cheers,

Mike

UBNT_Alternate_Logo.png
New Member
Posts: 12
Registered: ‎11-30-2015

Re: Unstable Security Gateway

Hi,

i have also an USG with a CloudKey on the network. The USG is unstable and restarts at least twice a day. It's updated and the version i use is 4.8.10

 

Do you have any news when this bug will be fixed?

Thank you very much

Emerging Member
Posts: 52
Registered: ‎07-29-2014
Kudos: 9
Solutions: 4

Re: Unstable Security Gateway

I have a similar problem. My Security Gateway restarts spontaneously from time to time. I have the latest firmware (4.8.5) and also a Cloud Key. What causes this restarting, which of course blocks Internet access for users? Can it be fixed (please)?
New Member
Posts: 12
Registered: ‎11-30-2015

Re: Unstable Security Gateway

I partially solved the problem deactivating the "deep packets inspection" on the gateway. In any case this gateway needs as soon as possible a major fix by Ubiquiti developers as it's far to be a firewall...

Ubiquiti Employee
Posts: 6,816
Registered: ‎01-28-2013
Kudos: 7327
Solutions: 569
Contributions: 20

Re: Unstable Security Gateway

[ Edited ]

In case you missed it, this particular bug was fixed in 4.6.6. I mentioned that HERE. If you are experiencing random reboots on a later release then you either have found a different software bug or may have faulty hardware.

 

On the latest releases, please do not use DPI, unless you want to experience random reboots and possibly some packetloss. This statement is based on user feedback. 

 

I'm closing this thread. If you aren't using DPI and are experiencing random reboots, please start a new thread with details specific to the issue you're experiencing.

 

Thanks,

Mike

UBNT_Alternate_Logo.png
Reply