Reply
Ubiquiti Employee
Posts: 9,081
Registered: ‎01-28-2013
Kudos: 15486
Solutions: 600
Contributions: 20

Re: UniFi Network Controller 5.10.12 Stable has been released

[ Edited ]

@ncscomm wrote: I had the same thought, thinking that you needed to be at 5.9.33 before going up to 5.10, thats why I asked where I could dl 5.9.33, since I was at 5.9.29. Maybe that line in the upgrade notes should be changed to better illustrate that point.Maybe state what the minimum build required to upgrade to the next level. Also using ascii art to illustrate this in text isn't exactly clear as I am not the only one to not grasp this otherwise obvious information.

You did read the other bullet points immediately below that line, right? You reference "line" (singular) so I have to ask, as there are multiple lines to the `Possible Upgrade Paths` section  Also, the minimum build is 3.1.0. Will look at improving this..

 

Possible Upgrade Paths:

  • <=5.10.11 | <=5.9.33 | <=5.8.30 | <=5.7.28 | <=5.6.40 and most earlier releases (going back to 3.1.0). There may be some version specific exceptions to this list.
    • The above versions are to indicate which version is supported to upgrade from for recent release branches. As long as you are on that release, or an earlier release within that branch, then you can (directly) upgrade to this release.
    • If you're on a newer release than what is mentioned, then you'll have to wait until this release is updated so that it supports upgrading from the release you're running now.

Cheers,

Mike

 

EDIT: Added this point, to further help clarify. Will redo the section later.

 

The release branch is determined by the first 2 numbers (so 5.10, 5.9, 5.8, etc). Then the version within the branch is the last number. A newer release is indicated by a higher number, and an earlier release is indicated by a lower number. All release branches start at .0 (e.g. 5.10.0, 5.9.0, etc.). The earliest release you can directly upgrade from is 3.1.0. If your controller is version starts with 2.x or 1.x, then you will need to upgrade to 3.x before you can upgrade to this release.

Established Member
Posts: 1,251
Registered: ‎07-17-2013
Kudos: 833
Solutions: 84
Contributions: 1

Re: UniFi Network Controller 5.10.12 Stable has been released

[ Edited ]

@UBNT-MikeD  it is actually being hidden by the browser scroll indicator, as it's now on the very right corner of the screen ...

 


Captura de Tela 2019-02-07 às 16.42.42.png

 

Captura de Tela 2019-02-07 às 16.42.38.png

Solutti Tecnologia Ltda - Goiânia/Goiás/Brazil
www.solutti.com.br / www.wifiquefunciona.com.br
Ubiquiti Enterprise Wireless Admin (UEWA) certified
did my answer helped you ? if yes, i would love your kudos on it Man Happy
Ubiquiti Employee
Posts: 9,081
Registered: ‎01-28-2013
Kudos: 15486
Solutions: 600
Contributions: 20

Re: UniFi Network Controller 5.10.12 Stable has been released


@leonardogyn wrote:

@UBNT-MikeD  is was actually being hidden by the browser scroll indicator, as it's now on the very right corner of the screen ...


Ah, okay. Interesting. Will investigate. Thanks!

 

Cheers,

Mike

Established Member
Posts: 1,507
Registered: ‎08-20-2012
Kudos: 795
Solutions: 19

Re: UniFi Network Controller 5.10.12 Stable has been released


@rdahlin wrote:

@AmazedMender16 wrote:

Hello @rdahlin,

 

Shouldn't take that long, could you send me your controller logs?

 

 

Regards,

Glenn R.


It's not possible I'm afraid. I had to use the controller to adopt some devices so I simply restored the snapshot I made before I started the upgrade.

 

I'll give it another try soon and if it happens again you might get them.


@AmazedMender16 @UBNT-MikeD 

I tried to upgrade again and I think that I'll get the same result again..

 

This is what I got in the console when upgrading:

Previous setting (UniFi 5.9.32) is found.
Unpacking unifi (5.10.12-11629-1) over (5.9.32-11402-1) ...
Setting up unifi (5.10.12-11629-1) ...
Processing triggers for systemd (232-25+deb9u8) ...

But this is the later part that I got with "tail -f /var/log/unifi/*" (not everything from when I started the upgrade but I think that I've got the most important parts...)

 

==> /var/log/unifi/server.log <==
[22:09:51,458] <launcher> INFO  db     - waiting for db connection...
[22:09:53,113] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117

==> /var/log/unifi/mongod.log <==
2019-02-07T22:09:58.647+0100 I CONTROL  [main] ***** SERVER RESTARTED *****
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] MongoDB starting : pid=7612 port=27117 dbpath=/usr/lib/unifi/data/db 64-bit host=ubnt-1
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] db version v3.2.11
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] git version: 009580ad490190ba33d1c6253ebd8d91808923e4
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2q  20 Nov 2018
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] allocator: tcmalloc
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] modules: none
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] build environment:
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten]     distarch: x86_64
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten]     target_arch: x86_64
2019-02-07T22:09:58.952+0100 I CONTROL  [initandlisten] options: { net: { bindIp: "127.0.0.1", port: 27117, unixDomainSocket: { pathPrefix: "/usr/lib/unifi/run" } }, storage: { dbPath: "/usr/lib/unifi/data/db" }, systemLog: { destination: "file", logAppend: true, path: "/usr/lib/unifi/logs/mongod.log" } }
2019-02-07T22:09:59.100+0100 I -        [initandlisten] Detected data files in /usr/lib/unifi/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-02-07T22:09:59.100+0100 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=4G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2019-02-07T22:10:15.201+0100 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/usr/lib/unifi/data/db/diagnostic.data'
2019-02-07T22:10:15.201+0100 I NETWORK  [HostnameCanonicalizationWorker] Starting hostname canonicalization worker
2019-02-07T22:10:16.527+0100 I NETWORK  [initandlisten] waiting for connections on port 27117
2019-02-07T22:10:16.540+0100 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:53540 #1 (1 connection now open)
2019-02-07T22:10:16.691+0100 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:53542 #2 (2 connections now open)
2019-02-07T22:10:17.596+0100 I COMMAND  [conn2] command ace command: eval { $eval: "db.serverStatus()", args: [] } keyUpdates:0 writeConflicts:0 numYields:0 reslen:13915 locks:{ Global: { acquireCount: { r: 3, W: 1 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_query 838ms
2019-02-07T22:10:17.996+0100 I COMMAND  [conn2] command ace.$cmd command: listCollections { listCollections: 1, cursor: { batchSize: 0 } } keyUpdates:0 writeConflicts:0 numYields:0 reslen:112 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { R: 1 } } } protocol:op_query 102ms

==> /var/log/unifi/server.log <==
[22:10:18,159] <launcher> INFO  db     - DB version (5.9.32) different from Runtime Version(5.10.12), migrating...
[22:10:18,186] <launcher> INFO  system - [server backup] started
[22:10:18,188] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117

==> /var/log/unifi/mongod.log <==
2019-02-07T22:10:18.193+0100 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:53544 #3 (3 connections now open)
2019-02-07T22:10:18.306+0100 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:53546 #4 (4 connections now open)
2019-02-07T22:10:19.211+0100 I COMMAND  [conn4] command ace.setting command: getMore { getMore: 153800109752, collection: "setting" } planSummary: COLLSCAN cursorid:153800109752 keysExamined:0 docsExamined:1663 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:14 nreturned:1663 reslen:348682 locks:{ Global: { acquireCount: { r: 30 } }, Database: { acquireCount: { r: 15 } }, Collection: { acquireCount: { r: 15 } } } protocol:op_query 261ms
2019-02-07T22:10:19.490+0100 I COMMAND  [conn4] command ace.portconf command: getMore { getMore: 118598855361, collection: "portconf" } planSummary: COLLSCAN cursorid:118598855361 keysExamined:0 docsExamined:605 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:5 nreturned:605 reslen:114615 locks:{ Global: { acquireCount: { r: 12 } }, Database: { acquireCount: { r: 6 } }, Collection: { acquireCount: { r: 6 } } } protocol:op_query 122ms
2019-02-07T22:10:19.888+0100 I COMMAND  [conn4] command ace.wlanconf command: getMore { getMore: 200347960823, collection: "wlanconf" } planSummary: COLLSCAN cursorid:200347960823 keysExamined:0 docsExamined:263 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:4 nreturned:263 reslen:195243 locks:{ Global: { acquireCount: { r: 10 } }, Database: { acquireCount: { r: 5 } }, Collection: { acquireCount: { r: 5 } } } protocol:op_query 102ms
2019-02-07T22:10:20.195+0100 I COMMAND  [conn4] command ace.device command: find { find: "device", filter: {} } planSummary: COLLSCAN cursorid:34954009704 keysExamined:0 docsExamined:101 keyUpdates:0 writeConflicts:0 numYields:4 nreturned:101 reslen:264962 locks:{ Global: { acquireCount: { r: 10 } }, Database: { acquireCount: { r: 5 } }, Collection: { acquireCount: { r: 5 } } } protocol:op_query 160ms
2019-02-07T22:10:20.886+0100 I COMMAND  [conn4] command ace.device command: getMore { getMore: 34954009704, collection: "device" } planSummary: COLLSCAN cursorid:34954009704 keysExamined:0 docsExamined:493 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:13 nreturned:493 reslen:982883 locks:{ Global: { acquireCount: { r: 28 } }, Database: { acquireCount: { r: 14 } }, Collection: { acquireCount: { r: 14 } } } protocol:op_query 642ms
2019-02-07T22:10:24.672+0100 I COMMAND  [conn4] command ace.user command: find { find: "user", filter: { $or: [ { last_seen: { $gt: 1549573818 } }, { fixed_ip: { $exists: true } }, { is_blocked: { $exists: true } }, { name: { $exists: true } }, { network_id: { $exists: true } }, { note: { $exists: true } }, { use_fixedip: { $exists: true } }, { usergroup_id: { $exists: true } } ] } } planSummary: COLLSCAN cursorid:173283968452 keysExamined:0 docsExamined:17780 keyUpdates:0 writeConflicts:0 numYields:162 nreturned:101 reslen:24357 locks:{ Global: { acquireCount: { r: 326 } }, Database: { acquireCount: { r: 163 } }, Collection: { acquireCount: { r: 163 } } } protocol:op_query 3630ms
2019-02-07T22:10:28.349+0100 I COMMAND  [conn4] command ace.user command: getMore { getMore: 173283968452, collection: "user" } planSummary: COLLSCAN cursorid:173283968452 keysExamined:0 docsExamined:67998 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:559 nreturned:285 reslen:71314 locks:{ Global: { acquireCount: { r: 1120 } }, Database: { acquireCount: { r: 560 } }, Collection: { acquireCount: { r: 560 } } } protocol:op_query 3665ms
2019-02-07T22:12:26.673+0100 I COMMAND  [conn4] command ace.event command: find { find: "event", filter: { datetime: { $gt: new Date(1549573818188) } } } planSummary: COLLSCAN keysExamined:0 docsExamined:4455043 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:35799 nreturned:0 reslen:115 locks:{ Global: { acquireCount: { r: 71600 } }, Database: { acquireCount: { r: 35800 } }, Collection: { acquireCount: { r: 35800 } } } protocol:op_query 118200ms
2019-02-07T22:13:51.120+0100 I COMMAND  [conn4] command ace.rogue command: find { find: "rogue", filter: { last_seen: { $gt: 1549573818 } } } planSummary: COLLSCAN keysExamined:0 docsExamined:611202 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:5407 nreturned:0 reslen:115 locks:{ Global: { acquireCount: { r: 10816 } }, Database: { acquireCount: { r: 5408 } }, Collection: { acquireCount: { r: 5408 } } } protocol:op_query 84444ms
2019-02-07T22:13:51.123+0100 I NETWORK  [conn4] end connection 127.0.0.1:53546 (3 connections now open)
2019-02-07T22:13:51.126+0100 I NETWORK  [conn3] end connection 127.0.0.1:53544 (2 connections now open)

==> /var/log/unifi/server.log <==
[22:13:51,251] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117

==> /var/log/unifi/mongod.log <==
2019-02-07T22:13:51.255+0100 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:53990 #5 (3 connections now open)
2019-02-07T22:13:51.262+0100 I NETWORK  [conn5] end connection 127.0.0.1:53990 (2 connections now open)

==> /var/log/unifi/server.log <==
[22:14:08,487] <launcher> INFO  system - [server backup][BACKUP] end

==> /var/log/unifi/mongod.log <==
2019-02-07T22:14:09.392+0100 I WRITE    [conn2] update ace.device query: { _id: ObjectId('566fd541e4b042a702dd2b48') } update: { _id: ObjectId('566fd541e4b042a702dd2b48'), adopted: true, antenna_table: [ { default: true, id: 4, name: "Combined", wifi0_gain: 3 } ], board_rev: 18, cfgversion: "41398ad1c0a29a05", config_network: { type: "dhcp", ip: "192.168.0.199" }, countrycode_table: [], ethernet_table: [ { mac: "44:d9:e7:6c:a8:b4", num_port: 1, name: "eth0" } ], fw_caps: 194603, has_eth1: false, has_speaker: false, inform_ip: "62.101.37.242", inform_url: "http://unifi.amtech.se:8080/inform", ip: "192.168.0.199", mac: "44:d9:e7:6c:a8:b4", map_id: "566fd51ce4b042a702dd2b3e", model: "BZ2", name: "AP01 - Nedervåning", port_table: [], radio_table: [ { name: "wifi0", radio: "ng", wlangroup_id: "566fd51ce4b042a702dd2b3a", channel: "auto", ht: "20", tx_power_mode: "high", tx_power: "0", max_txpower: 23, min_txpower: 5, nss: 2, min_rssi_enabled: false, radio_caps: 16404, builtin_antenna: true, builtin_ant_gain: 3, antenna_gain: 6, current_antenna_gain: 0 } ], scan_radio_table: [], serial: "44D9E76CA8B4", site_id: "566fd51ce4b042a702dd2b35", type: "uap", version: "4.0.10.9653", vwire_table: [], wifi_caps: 15989, x: 60.96482, x_authkey: "f8048b707b3e9b09c341f82178afd3df", x_fingerprint: "14:5f:f9:af:78:4d:8c:7d:52:69:b3:fd:4b:5f:87:2d", x_vwirekey: "43e13345c14a061cab893844893b961f", y: 14.5448, wlangroup_id_ng: "566fd51ce4b042a702dd2b3a", wlan_overrides: [ { name: "SV11_N", radio: "ng", radio_name: "wifi0", wlan_id: "5b1f7c062fc92b9b2178f6f8" } ], hw_caps: 0, required_version: "2.4.4" } keysExamined:1 docsExamined:1 nMatched:1 nModified:0 keyUpdates:0 writeConflicts:0 numYields:1 locks:{ Global: { acquireCount: { r: 2, w: 2 } }, Database: { acquireCount: { w: 2 } }, Collection: { acquireCount: { w: 2 } } } 451ms
2019-02-07T22:14:09.393+0100 I COMMAND  [conn2] command ace.$cmd command: update { update: "device", ordered: true, updates: [ { q: { _id: ObjectId('566fd541e4b042a702dd2b48') }, u: { _id: ObjectId('566fd541e4b042a702dd2b48'), adopted: true, antenna_table: [ { default: true, id: 4, name: "Combined", wifi0_gain: 3 } ], board_rev: 18, cfgversion: "41398ad1c0a29a05", config_network: { type: "dhcp", ip: "192.168.0.199" }, countrycode_table: [], ethernet_table: [ { mac: "44:d9:e7:6c:a8:b4", num_port: 1, name: "eth0" } ], fw_caps: 194603, has_eth1: false, has_speaker: false, inform_ip: "62.101.37.242", inform_url: "http://unifi.amtech.se:8080/inform", ip: "192.168.0.199", mac: "44:d9:e7:6c:a8:b4", map_id: "566fd51ce4b042a702dd2b3e", model: "BZ2", name: "AP01 - Nedervåning", port_table: [], radio_table: [ { name: "wifi0", radio: "ng", wlangroup_id: "566fd51ce4b042a702dd2b3a", channel: "auto", ht: "20", tx_power_mode: "high", tx_power: "0", max_txpower: 23, min_txpower: 5, nss: 2, min_rssi_enabled: false, radio_caps: 16404, builtin_antenna: true, builtin_ant_gain: 3, antenna_gain: 6, current_antenna_gain: 0 } ], scan_radio_table: [], serial: "44D9E76CA8B4", site_id: "566fd51ce4b042a702dd2b35", type: "uap", version: "4.0.10.9653", vwire_table: [], wifi_caps: 15989, x: 60.96482, x_authkey: "f8048b707b3e9b09c341f82178afd3df", x_fingerprint: "14:5f:f9:af:78:4d:8c:7d:52:69:b3:fd:4b:5f:87:2d", x_vwirekey: "43e13345c14a061cab893844893b961f", y: 14.5448, wlangroup_id_ng: "566fd51ce4b042a702dd2b3a", wlan_overrides: [ { name: "SV11_N", radio: "ng", radio_name: "wifi0", wlan_id: "5b1f7c062fc92b9b2178f6f8" } ], hw_caps: 0, required_version: "2.4.4" } } ] } keyUpdates:0 writeConflicts:0 numYields:0 reslen:55 locks:{ Global: { acquireCount: { r: 2, w: 2 } }, Database: { acquireCount: { w: 2 } }, Collection: { acquireCount: { w: 2 } } } protocol:op_query 451ms
2019-02-07T22:14:10.482+0100 I COMMAND  [conn2] command ace.wlangroup command: find { find: "wlangroup", filter: { site_id: "5c360d330f20a115f95c84e2", attr_hidden_id: "Default" }, limit: 1, singleBatch: true } planSummary: IXSCAN { site_id: 1 } keysExamined:1 docsExamined:1 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:1 nreturned:1 reslen:245 locks:{ Global: { acquireCount: { r: 4 } }, Database: { acquireCount: { r: 2 } }, Collection: { acquireCount: { r: 2 } } } protocol:op_query 194ms
2019-02-07T22:14:10.785+0100 I COMMAND  [conn2] command ace.wlanconf command: find { find: "wlanconf", filter: { site_id: "52a04549e4b050c0ea182ccd" }, limit: 3000 } planSummary: IXSCAN { site_id: 1 } keysExamined:1 docsExamined:1 fromMultiPlanner:1 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:4 nreturned:1 reslen:1098 locks:{ Global: { acquireCount: { r: 10 } }, Database: { acquireCount: { r: 5 } }, Collection: { acquireCount: { r: 5 } } } protocol:op_query 219ms
2019-02-07T22:14:11.002+0100 I COMMAND  [conn2] command ace.setting command: find { find: "setting", filter: { key: "usg", site_id: "52a04549e4b050c0ea182ccd" }, limit: 1, singleBatch: true } planSummary: IXSCAN { site_id: 1, key: 1 } keysExamined:1 docsExamined:1 fromMultiPlanner:1 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:2 nreturned:1 reslen:491 locks:{ Global: { acquireCount: { r: 6 } }, Database: { acquireCount: { r: 3 } }, Collection: { acquireCount: { r: 3 } } } protocol:op_query 203ms

==> /var/log/unifi/server.log <==
[22:14:11,835] <launcher> WARN  AnnotationConfigApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'autoOptimizer' defined in com.ubnt.service.AppContext: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ubnt.service.int.OoOO]: Factory method 'autoOptimizer' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configService' defined in com.ubnt.service.AppContext: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.ubnt.service.voidsuper.OOOo]: Factory method 'configService' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dbService' defined in com.ubnt.service.AppContext: Invocation of init method failed; nested exception is java.lang.UnsupportedOperationException

==> /var/log/unifi/mongod.log <==
2019-02-07T22:14:12.682+0100 I NETWORK  [conn2] end connection 127.0.0.1:53542 (1 connection now open)
2019-02-07T22:14:12.682+0100 I NETWORK  [conn1] end connection 127.0.0.1:53540 (1 connection now open)

==> /var/log/unifi/server.log <==
[22:14:12,698] <UniFi> ERROR system - [exec] error, rc=1, cmdline=[/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java, -Dfile.encoding=UTF-8, -Djava.awt.headless=true, -Dapple.awt.UIElement=true, -Xmx2048M, -Xms2048M, -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, -XX:ErrorFile=/usr/lib/unifi/logs/hs_err_pid%p.log, -jar, /usr/lib/unifi/lib/ace.jar, start]
[22:14:20,564] <launcher> INFO  system - ======================================================================
[22:14:20,576] <launcher> INFO  system - UniFi 5.10.12 (build atag_5.10.12_11629 - release) is started
[22:14:20,576] <launcher> INFO  system - ======================================================================
[22:14:20,578] <launcher> INFO  system - BASE dir:/usr/lib/unifi
[22:14:20,667] <launcher> INFO  system - Current System IP: 172.21.0.1
[22:14:20,667] <launcher> INFO  system - Hostname: ubnt-1
[22:14:23,090] <launcher> INFO  db     - waiting for db connection...

==> /var/log/unifi/mongod.log <==
2019-02-07T22:14:23.323+0100 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:54094 #6 (1 connection now open)
2019-02-07T22:14:23.518+0100 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:54096 #7 (2 connections now open)
2019-02-07T22:14:23.555+0100 I COMMAND  [conn7] terminating, shutdown command received
2019-02-07T22:14:23.555+0100 I FTDC     [conn7] Shutting down full-time diagnostic data capture
2019-02-07T22:14:23.557+0100 I CONTROL  [conn7] now exiting
2019-02-07T22:14:23.557+0100 I NETWORK  [conn7] shutdown: going to close listening sockets...
2019-02-07T22:14:23.557+0100 I NETWORK  [conn7] closing listening socket: 6
2019-02-07T22:14:23.557+0100 I NETWORK  [conn7] closing listening socket: 7
2019-02-07T22:14:23.557+0100 I NETWORK  [conn7] removing socket file: /usr/lib/unifi/run/mongodb-27117.sock
2019-02-07T22:14:23.557+0100 I NETWORK  [conn7] shutdown: going to flush diaglog...
2019-02-07T22:14:23.557+0100 I NETWORK  [conn7] shutdown: going to close sockets...
2019-02-07T22:14:23.557+0100 I STORAGE  [conn7] WiredTigerKVEngine shutting down
2019-02-07T22:14:23.559+0100 I NETWORK  [conn6] end connection 127.0.0.1:54094 (1 connection now open)

==> /var/log/unifi/server.log <==
[22:14:23,594] <launcher> INFO  db     - Connecting to mongodb://127.0.0.1:27117

==> /var/log/unifi/mongod.log <==
2019-02-07T22:14:23.631+0100 I CONTROL  [main] ***** SERVER RESTARTED *****
2019-02-07T22:14:23.640+0100 I CONTROL  [initandlisten] MongoDB starting : pid=7960 port=27117 dbpath=/usr/lib/unifi/data/db 64-bit host=ubnt-1
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten] db version v3.2.11
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten] git version: 009580ad490190ba33d1c6253ebd8d91808923e4
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2q  20 Nov 2018
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten] allocator: tcmalloc
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten] modules: none
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten] build environment:
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten]     distarch: x86_64
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten]     target_arch: x86_64
2019-02-07T22:14:23.641+0100 I CONTROL  [initandlisten] options: { net: { bindIp: "127.0.0.1", port: 27117, unixDomainSocket: { pathPrefix: "/usr/lib/unifi/run" } }, storage: { dbPath: "/usr/lib/unifi/data/db" }, systemLog: { destination: "file", logAppend: true, path: "/usr/lib/unifi/logs/mongod.log" } }
2019-02-07T22:14:23.680+0100 I -        [initandlisten] Detected data files in /usr/lib/unifi/data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-02-07T22:14:23.691+0100 W -        [initandlisten] Detected unclean shutdown - /usr/lib/unifi/data/db/mongod.lock is not empty.
2019-02-07T22:14:23.708+0100 I STORAGE  [initandlisten] exception in initAndListen: 98 Unable to lock file: /usr/lib/unifi/data/db/mongod.lock errno:11 Resource temporarily unavailable. Is a mongod instance already running?, terminating
2019-02-07T22:14:23.708+0100 I CONTROL  [initandlisten] dbexit:  rc: 100

==> /var/log/unifi/server.log <==
[22:14:23,712] <db-server> INFO  db     - DbServer stopped
[22:14:23,713] <db-server> WARN  db     - DbServer not shutdown cleanly and need repairing on next startup

==> /var/log/unifi/mongod.log <==
2019-02-07T22:14:25.392+0100 I STORAGE  [conn7] shutdown: removing fs lock...
2019-02-07T22:14:25.392+0100 I CONTROL  [conn7] dbexit:  rc: 0
2019-02-07T22:14:27.785+0100 I CONTROL  [main] ***** SERVER RESTARTED *****
2019-02-07T22:14:27.795+0100 I CONTROL  [initandlisten] MongoDB starting : pid=7969 port=27117 dbpath=/usr/lib/unifi/data/db 64-bit host=ubnt-1
2019-02-07T22:14:27.795+0100 I CONTROL  [initandlisten] db version v3.2.11
2019-02-07T22:14:27.795+0100 I CONTROL  [initandlisten] git version: 009580ad490190ba33d1c6253ebd8d91808923e4
(Cut to save text lentgh).
Senior Member
Posts: 16,450
Registered: ‎08-04-2017
Kudos: 3006
Solutions: 810

Re: UniFi Network Controller 5.10.12 Stable has been released

Hello @rdahlin,

 

Looks like a common problem I have been helping ALOT of user with... could you send me the backup file on 5.9.32? ( will PM you a backup for 5.10.12 )

 

 

Regards,

Glenn R.

Cloud Hosted Controllers | Glenn R. | UniFi Installation/Easy Update Scripts | UniFi-VoIP Installation Scripts
USG-4-PRO • USG
USW-48-500W • USW-24-POE-250W 2x • USW-16-POE-150W 3x • USW-24 • USW-8-150W • USW-8
UAP XG • UAP-SHD • UAP-HD • UAP-NanoHD • UAP-AC-PRO 2x • UAP-AC-LITE • UAP-AC-IW • UAP-AC-M
UCK-G2-PLUS • UCK-G2 • UCK
Regular Member
Posts: 441
Registered: ‎09-28-2017
Kudos: 121
Solutions: 31

Re: UniFi Network Controller 5.10.12 Stable has been released

@UBNT-MikeD While you're investigating that...

Can the powers that be add the <-> icon at the top of all columns containing bar graphs so we can filter them out and just see the data.  Anything else to reduce column widths like shortening the column headers 2G EXP instead of 2G EXPERIENCE, so on and so forth.

 

While you're at it, have them invert the Dark theme backgroung and row highlight shades.  Make the background darker (black) and the highlight the washed out black the background currently is.

 

That's all for now.  Easy Peasy! Lol

 

Thanks for all the team's effort.

New Member
Posts: 2
Registered: ‎11-09-2016
Kudos: 3

Re: UniFi Network Controller 5.10.12 Stable has been released

Is there a post somewhere that documents what the network / wifi optimizer does?
I turned it on to give it a shot, saw it re-provision my access points but haven't seen much in the way of changes.

Really just curious.

Emerging Member
Posts: 50
Registered: ‎03-20-2017
Kudos: 2

Re: UniFi Network Controller 5.10.12 Stable has been released

Should that commands in Debian do the update??

 

apt update

apt upgrade

 

Cause I don't get the new version by doing this. Why? Is the new controller version not available in the repo?

New Member
Posts: 2
Registered: ‎11-09-2016
Kudos: 3

Re: UniFi Network Controller 5.10.12 Stable has been released


@jgreil wrote:

Should that commands in Debian do the update??

 

apt update

apt upgrade

 

Cause I don't get the new version by doing this. Why? Is the new controller version not available in the repo?


wget https://dl.ubnt.com/unifi/5.10.12-20644d4901/unifi_sysvinit_all.deb 
sudo dpkg -i unifi_sysvinit_all.deb
rm unifi_sysvinit_all.deb

 I couldn't find it in the repo either so I ran the above and it installed fine. 

Established Member
Posts: 969
Registered: ‎02-12-2013
Kudos: 248
Solutions: 89

Re: UniFi Network Controller 5.10.12 Stable has been released

Emerging Member
Posts: 50
Registered: ‎03-20-2017
Kudos: 2

Re: UniFi Network Controller 5.10.12 Stable has been released

Thanks for your quick help.

Why are the repos always so late updates?

Established Member
Posts: 969
Registered: ‎02-12-2013
Kudos: 248
Solutions: 89

Re: UniFi Network Controller 5.10.12 Stable has been released

@jgreil
That's known as a rolling release. It's a protective measure to try to catch grave errors that have slipped by alpha, beta, candidate and stable before hitting the repos and auto-updaters.
Member
Posts: 125
Registered: ‎03-15-2014
Kudos: 74
Solutions: 4

Re: UniFi Network Controller 5.10.12 Stable has been released

[ Edited ]
Member
Posts: 205
Registered: ‎01-20-2018
Kudos: 36
Solutions: 4

Re: UniFi Network Controller 5.10.12 Stable has been released

[ Edited ]

My controller upgrade on the CK (v0.12.4) went fine - upgrading from 5.9.32.
Was already at recommended fw for AP-Pros and USW's.

Love the "night" look on the new controller... Ubnt Banana

However,
I MISS being able to see stacked devices to the right. Being able to undock is awesome, but sizing and placing on the window was a bit of a challenge.
When docked, the windows stack, but not like they did in 5.9.32 - on top of each other - they now hide behind and one has to select which one if the foreground window.
I was unable to find a way to make then stack the old way...

Established Member
Posts: 1,251
Registered: ‎07-17-2013
Kudos: 833
Solutions: 84
Contributions: 1

Re: UniFi Network Controller 5.10.12 Stable has been released


@jgreil wrote:

Thanks for your quick help.

Why are the repos always so late updates?


5.10 was released as a stable release less than 48h ago ... at least for this 5.10 release, saying the repo is 'so late' doesn't seem right at all Man Happy

Solutti Tecnologia Ltda - Goiânia/Goiás/Brazil
www.solutti.com.br / www.wifiquefunciona.com.br
Ubiquiti Enterprise Wireless Admin (UEWA) certified
did my answer helped you ? if yes, i would love your kudos on it Man Happy
New Member
Posts: 6
Registered: ‎01-10-2019
Kudos: 3

Re: UniFi Network Controller 5.10.12 Stable has been released

Hi all. I upgraded our controller from 5.9.29 on Centos 7 VM.

I try to setup 2 AC-M. After adopting on device, they don't place on controller. I try to reset/hard reset devices, reset controller. Nothing help.

Restore snapshot before upgrade, devices stand in status adopted less than minute.

It's bug or new feature?

 

New Member
Posts: 5
Registered: ‎08-17-2015
Kudos: 1

Re: UniFi Network Controller 5.10.12 Stable has been released

Upgrading from 5.9.29 to this doesn't seem to work for me... the install completes successfully, but then the new controller just gets stuck:

 

[04:28:28,542] <launcher-ui> INFO  launcher - Initializing UniFi Controller ...
[04:28:37,074] <launcher-monitor> INFO  launcher - Starting UniFi Controller ...
[04:28:37,261] <UniFi> ERROR system - [exec] error, rc=1, cmdline=[C:\Program Files (x86)\Java\jre1.8.0_73\bin\java, -Dfile.encoding=UTF-8, -Djava.awt.headless=true, -Dapple.awt.UIElement=true, -Xmx1024M, -Xrs, -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, -XX:ErrorFile=C:\Users\root\Ubiquiti UniFi\logs\hs_err_pid%p.log, -jar, C:\Users\root\Ubiquiti UniFi\lib\ace.jar, start]
[04:28:47,136] <UniFi> ERROR system - [exec] error, rc=1, cmdline=[C:\Program Files (x86)\Java\jre1.8.0_73\bin\java, -Dfile.encoding=UTF-8, -Djava.awt.headless=true, -Dapple.awt.UIElement=true, -Xmx1024M, -Xrs, -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, -XX:ErrorFile=C:\Users\root\Ubiquiti UniFi\logs\hs_err_pid%p.log, -jar, C:\Users\root\Ubiquiti UniFi\lib\ace.jar, start]
[04:28:57,152] <UniFi> ERROR system - [exec] error, rc=1, cmdline=[C:\Program Files (x86)\Java\jre1.8.0_73\bin\java, -Dfile.encoding=UTF-8, -Djava.awt.headless=true, -Dapple.awt.UIElement=true, -Xmx1024M, -Xrs, -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, -XX:ErrorFile=C:\Users\root\Ubiquiti UniFi\logs\hs_err_pid%p.log, -jar, C:\Users\root\Ubiquiti UniFi\lib\ace.jar, start]

The last lines are repeated every 10 seconds until the controller is killed.

Had to uninstall then reinstall 5.9.29 - worked as if I hadn't upgraded!

 

This is on a Windows Server 2016 VM with Java V8 x86.

 

Any ideas?

Emerging Member
Posts: 88
Registered: ‎07-26-2018
Kudos: 6
Solutions: 1

Re: UniFi Network Controller 5.10.12 Stable has been released


@ThePhoton wrote:

Upgrading from 5.9.29 to this doesn't seem to work for me... the install completes successfully, but then the new controller just gets stuck:

 

[04:28:28,542] <launcher-ui> INFO  launcher - Initializing UniFi Controller ...
[04:28:37,074] <launcher-monitor> INFO  launcher - Starting UniFi Controller ...
[04:28:37,261] <UniFi> ERROR system - [exec] error, rc=1, cmdline=[C:\Program Files (x86)\Java\jre1.8.0_73\bin\java, -Dfile.encoding=UTF-8, -Djava.awt.headless=true, -Dapple.awt.UIElement=true, -Xmx1024M, -Xrs, -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, -XX:ErrorFile=C:\Users\root\Ubiquiti UniFi\logs\hs_err_pid%p.log, -jar, C:\Users\root\Ubiquiti UniFi\lib\ace.jar, start]
[04:28:47,136] <UniFi> ERROR system - [exec] error, rc=1, cmdline=[C:\Program Files (x86)\Java\jre1.8.0_73\bin\java, -Dfile.encoding=UTF-8, -Djava.awt.headless=true, -Dapple.awt.UIElement=true, -Xmx1024M, -Xrs, -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, -XX:ErrorFile=C:\Users\root\Ubiquiti UniFi\logs\hs_err_pid%p.log, -jar, C:\Users\root\Ubiquiti UniFi\lib\ace.jar, start]
[04:28:57,152] <UniFi> ERROR system - [exec] error, rc=1, cmdline=[C:\Program Files (x86)\Java\jre1.8.0_73\bin\java, -Dfile.encoding=UTF-8, -Djava.awt.headless=true, -Dapple.awt.UIElement=true, -Xmx1024M, -Xrs, -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, -XX:ErrorFile=C:\Users\root\Ubiquiti UniFi\logs\hs_err_pid%p.log, -jar, C:\Users\root\Ubiquiti UniFi\lib\ace.jar, start]

The last lines are repeated every 10 seconds until the controller is killed.

Had to uninstall then reinstall 5.9.29 - worked as if I hadn't upgraded!

 

This is on a Windows Server 2016 VM with Java V8 x86.

 

Any ideas?


Looks like you are using an old version of Java:

 

Java\jre1.8.0_73\bin\java

 

Install the latest version of Java 8 (think its update 201 at the moment...) and remove update 73 and it should work.

New Member
Posts: 5
Registered: ‎08-17-2015
Kudos: 1

Re: UniFi Network Controller 5.10.12 Stable has been released

Ah yes, good shout. That's done the trick thanks!
Emerging Member
Posts: 50
Registered: ‎09-07-2016
Kudos: 12

Re: UniFi Network Controller 5.10.12 Stable has been released


@jopierce wrote:

Is there a post somewhere that documents what the network / wifi optimizer does?
I turned it on to give it a shot, saw it re-provision my access points but haven't seen much in the way of changes.

Really just curious.


I agree, this would be nice information to have. It sounds like a significant feature I would have expected a little more detail around, so it was well understood before selecting the option.

Reply