UniFi Controller News on Synology

27.01.2016 / Wakko / 67 Comments

Due to the changes in the latest beta versions of UniFi Controller and I want to give some guidance for customers:

  1. If you have updated the Synology DSM to version 6.0-nothing to worry about. And even good! You can install 64-bit Java, 7 or even 8-series. Let me remind you that the official JavaManager for DSM 5.0 only supports 32-bit Java.

    2.  

  2. If you are trying to run the UniFi Controller and you have a file /volume1/@appstore/UniFi Controller/logs/server.log the following errors occur: 
    [2016-01-22 00:14:28,273] <db-server> ERROR system - [exec] error, rc=141
[2016-01-22 00:14:28,273] <db-server> INFO  db     - DbServer stopped
[2016-01-22 00:14:33,280] <db-server> ERROR system - [exec] error, rc=141
[2016-01-22 00:14:33,281] <db-server> INFO  db     - DbServer stopped
[2016-01-22 00:14:38,291] <db-server> ERROR system - [exec] error, rc=141
[2016-01-22 00:14:38,292] <db-server> INFO  db     - DbServer stopped

    It’s not dead! Ubiquiti team aware of this problem and will fix it soon (at least so they wrote to me). For my part, I did everything I could – rewrite the startup script of UniFi Controller, increased the timeout to run. If this do not help, UniFi Controller does not start and logs only these errors, try to change the Java version, as practice shows some users – it helps.
    2016-07-04 Update: Please, read new information.

    3.  

  3. If you installed the 64-bit Java and at startup UniFi Controller and you see the following warning:
    Java HotSpot(™) 64-Bit Server VM warning: You have loaded library /volume1/@appstore/UniFi Controller/lib/native/Linux/amd64/libubnt_webrtc_jni.so which might have disabled stack guard. The VM will try to fix the stack guard now. It’s highly recommended that you fix the library with ‘execstack -c’, or link it with ‘-z noexecstack’.
    Nothing to worry about. As answered in the Ubiquiti – controller will work even if you Were at all will not be started.

    4.  

  4. Same girl from Ubiquiti said they plan to buy a test of Synology to test a UniFi Controller and the Synology. The good news. 🙂

    5.  

  5. If you are using ARM processor Synology is sad. Have to contend with a number of glitches. Will list several restrictions:
    • The MongoDB server to Synology with ARM processor is 32-bit, it imposes a number of restrictions;
    • The MongoDB server to Synology with ARM processor is enough of the old version, and the server periodically freeze that halts and the controller itself;
    • Java on Synology with ARM processor also works not always correctly.

    As soon as we have on sale in Russia appears UniFi Cloud Key – I’ll try to order it. This device is using ARM architecture too so that you can be any components for Synology to take with him. If you have the opportunity to provide this device for test – I would be happy to.

You could support our repository here.

Comments

  1. Rob
    27.01.2016 - 23:26

    I just want to generally thank you for your efforts. One of my Synology is Intel and works fine. The other one (216play) is ARM and doesn’t start. I still have about 6 weeks until my antennas arrive, so I will deal with it later. In the setup there a controller is not even Mandatory. Cheers, Rob.

  2. Jur.
    29.01.2016 - 20:44

    maybe you could also try to develop a version working with java from pcloadletter, the path of this version is not changing for what I know, and possibly the unifi controller will work?

    btw, have no problem on dsm 6.x, unifi controller with java on DS 712+ just working fine 🙂

  3. Jezyk
    10.02.2016 - 16:01

    Hi.
    I’ve the same problem with RPI 2 and 4.8.12 version.
    Exactly the same info in the log file.
    my post on ubnt community:
    https://community.ubnt.com/t5/UniFi-Wireless/Upgrade-Unififi-4-8-12-on-rasperry-pi/m-p/1478287#U1478287

  4. Rolando
    13.02.2016 - 11:57

    Hi. I own a synology 713+ with both mFi and UniFi controllers running (as a charm) on it. Now I’m trying to migrate to a 716+ (Intel Celeron N3150) but I’m unable to instally mFi and UniFi packages. Any suggestion?. Many thanks.

  5. Rolando
    16.02.2016 - 09:44

    Hi Wakko,

    out for work for 2 more days (and away from my 716+). I’ll try as soon as possible and I’ll let you know.
    many thanks for your fast answer!

  6. Rolando
    20.02.2016 - 12:11

    Hi Wakko,

    now it works! Thanks again!

  7. kuiperonline
    14.03.2016 - 12:01

    Dear Alexander, i installed http://pcloadletter.co.uk/2011/08/23/java-package-for-synology/ and then 4.9.1-1620210-beta on my synology DS412+ DSM 6.0 7274 but when i want to start the Unifiy it says: STARTING TO LOAD and then COULD NOT START PACKAGE SERVICE (translated from dutch) There is no log on the synology and not in the Unifiy package.
    The only log i see: Package [UniFi Controller] has been successfully installed.

  8. jurjen1971jurjen
    14.03.2016 - 20:26

    you should install the java version from synology package center, after that, java can be downloaded from http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
    You need an account to download!
    It won’t work with java from pcloadletter………
    For me on a DS712+ its working with java 8 and unifi controler 4.8.14-160223 (you have a similar kind cpu).

  9. daluaim
    24.03.2016 - 10:37

    Hi All,
    can i update my DS712+ to DSM 6.0 without any problems re UniFi Controller? Or is there still this Java issue?
    Thanks
    Daniel

  10. Mauro
    25.03.2016 - 03:57

    hey Alex, Mauro from italy here 🙂 any news for mfi controller on DSM6.0?

  11. Paul
    25.03.2016 - 16:19

    Hi Alex,

    It goes without saying that I love your work. ;-)) But, I have a DS414 based on the MARVELL Armada XP processor. That has been giving troubling me from the moment i wanted to run UniFi on my Syno, but up till now I was able to run it, configure my network and if I was finished, just stop it again. The database crashes every now and then, so I have no option (yet) of letting it run. I could live with that, since I don’t have the funds to buy me an intel based Syno (something with girlfriend and priorities…).
    Anyway, some time ago you released version 4.8.14-160223 which gave me the rc=141 error. Whatever I tried, nothing would work out to run UniFi. I ended up going back to version 4.7.5-151003 which worked fine for me after all, except the fact that I need to stop it once I finished my work.
    Today I upgraded my Syno to DSM6 and was trying again to run v160228. Too bad it gave me the same error. Switching between different java versions (both Java7 and Java8) gave the same results.
    Now actually the most strange thing is, once i upgraded from 151003 to 160228 UniFi started the first time! This was also the case with DSM5 before. I could login to the website and even manage my devices. Just when I tried to change a setting, it crashed and I have been not able to restart it anymore. Gives me the same error over and over again rc=141.
    My conclusion so far is that there is something changed after the first run, causing the package not able to start anymore afterwards. Do you have any clue what that could be?

  12. Jur.
    25.03.2016 - 20:06

    For me also 4.8.14 is working on DSM 6.0-7321.
    After first updating latest new apps, updating to the new DSM, updating than again the latest new apps and after that a restart even unifi controller started automatically (which it haven’t done for previous versions of DSM 6.x beta)

  13. zone11
    26.03.2016 - 11:26

    After upgrading my DS412+ to DSM 6.0-7321 (from latest DSM 5.x) the UniFi Controller died. I did a reinstall with lastest Java 7 and again with Java 8. Always stucket with database errors.
    Any idea how long an update for a working version takes?
    But hey, awesome work! Thank you for your efforts!!

    Here the output of a clean installation failing its startup.

    — cut —
    [2016-03-26 09:17:15,094] INFO system – *** Running for the first time, creating identity ***
    [2016-03-26 09:17:15,102] INFO system – UUID: 049f1e2d-a4d4-4bda-9939-f978fab0fbb0
    [2016-03-26 09:17:15,102] INFO system – ======================================================================
    [2016-03-26 09:17:15,103] INFO system – UniFi 4.9.2 (build atag_4.9.2_8140 – release) is started
    [2016-03-26 09:17:15,103] INFO system – ======================================================================
    [2016-03-26 09:17:15,118] INFO system – BASE dir:/volume1/@appstore/UniFi Controller
    [2016-03-26 09:17:15,137] INFO system – Current System IP: 192.168.253.10
    [2016-03-26 09:17:15,138] INFO system – Hostname: Datenbunker
    [2016-03-26 09:17:15,266] INFO system – Valid keystore is missing. Generating one …
    [2016-03-26 09:17:15,267] INFO system – Generating Certificate[UniFi]… please wait…
    [2016-03-26 09:17:24,158] INFO system – Certificate[UniFi] generated!
    [2016-03-26 09:17:27,067] ERROR system – [exec] error, rc=141
    [2016-03-26 09:17:27,068] INFO db – DbServer stopped
    [2016-03-26 09:17:32,114] ERROR system – [exec] error, rc=141
    [2016-03-26 09:17:32,115] INFO db – DbServer stopped
    [2016-03-26 09:17:37,126] ERROR system – [exec] error, rc=141
    [2016-03-26 09:17:37,126] INFO db – DbServer stopped
    [2016-03-26 09:17:42,138] ERROR system – [exec] error, rc=141
    [2016-03-26 09:17:42,139] INFO db – DbServer stopped
    [2016-03-26 09:17:47,150] ERROR system – [exec] error, rc=141
    [2016-03-26 09:17:47,151] INFO db – DbServer stopped
    [2016-03-26 09:17:52,163] ERROR system – [exec] error, rc=141
    [2016-03-26 09:17:52,163] INFO db – DbServer stopped
    [2016-03-26 09:17:57,175] ERROR system – [exec] error, rc=141
    [2016-03-26 09:17:57,176] INFO db – DbServer stopped
    [2016-03-26 09:18:02,186] ERROR system – [exec] error, rc=141
    [2016-03-26 09:18:02,187] INFO db – DbServer stopped
    [2016-03-26 09:18:07,240] ERROR system – [exec] error, rc=141
    [2016-03-26 09:18:07,241] INFO db – DbServer stopped
    [2016-03-26 09:18:12,275] ERROR system – [exec] error, rc=141
    [2016-03-26 09:18:12,305] INFO db – DbServer stopped
    [2016-03-26 09:18:14,177] ERROR system – [exec] error, rc=141
    [2016-03-26 09:18:14,177] INFO db – DbServer stopped
    — /cut —

  14. Rolando
    26.03.2016 - 13:39

    Hi Alex,

    I’ve a problem on re-installing mfi on a 713+ and I don’t know if I’m doing something wrong.

    Starting environment:
    – 713+ with last 5.x DSM version and both unfi and mfi package working
    – I don’t remember well which version of java and from where

    Steps done:
    – upgrade from 5.x to 6.x -> mfi don’t start anymore and unifi starts with a long error, so I decided to re-start from scratch
    – uninstall of mfi and unifi package and uninstall of java, reboot.
    – install of ‘Java8’ from Synology
    – install of unifi package -> the unifi package now starts without errors
    – during the install of mfi package an error ask for ‘JavaManager’ package (that I can’t find)
    – I tried, after an uninstall of both unifi and Java8, Java7 package from Synology, Java SE Embedded 7 and 8 package from Oracle, but the error message is still the same.

    where I’m doing something wrong?

    any help appreciated

    Rolando

  15. daluaim
    26.03.2016 - 15:22

    This worked on my DS712+:

    – update to DSM 6.0
    – update all packages installed
    – install Java 8
    – update Java 8 to Version 77 with jdk-8u77-linux-i586 from http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
    – restart Unifi Controller App

  16. Mauro
    26.03.2016 - 22:06

    any news on mfi for DSM6.0 con x86/x64 platform?

  17. Rafael
    27.03.2016 - 13:41

    Hellow daluaim,
    I have tried to update Java 8 to version 77 but when I download the file the synology doesn’t recognize the file. It appears file invalid. Which one have I to download: .rpm or .tar.gz?
    Thanks

  18. Rafael
    27.03.2016 - 23:04

    Hi Alex,

    I have this problem when I run the application after DSM 6.0 upgrade. I don’t know what to do.

    UniFi Controller: Exception in thread “launcher” org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘deviceManager’ defined in class com.ubnt.service.AppContext: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public com.ubnt.service.super.E com.ubnt.service.AppContext.deviceManager()] threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘dbService’ defined in class com.ubnt.service.AppContext: Invocation of init method failed; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:597) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1055) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:951) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:296) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:293) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at org.springframework.context.annotation.AnnotationConfigApplicationContext.(AnnotationConfigApplicationContext.java:73) at com.ubnt.service.B.?O0000(Unknown Source) at com.ubnt.ace.Launcher.main(Unknown Source) Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public com.ubnt.service.super.E com.ubnt.service.AppContext.deviceManager()] threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘dbService’ defined in class com.ubnt.service.AppContext: Invocation of init method failed; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:181) at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:586) … 14 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘dbService’ defined in class com.ubnt.service.AppContext: Invocation of init method failed; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1512) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:296) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:293) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:305) at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29.dbService() at com.ubnt.service.AppContext.deviceManager(Unknown Source) at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29.CGLIB$deviceManager$2() at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29$$FastClassBySpringCGLIB$$618e7384.invoke() at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:293) at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29.deviceManager() at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:160) … 15 more Caused by: java.lang.NullPointerException at com.ubnt.service.OoOO.J.interface(Unknown Source) at com.ubnt.service.OoOO.J.afterPropertiesSet(Unknown Source) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1571) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1509) … 34 more

  19. AJvK
    28.03.2016 - 02:20

    Was very happy with UniFi on my 412+ until I updated to DSM 6.0RC… Unify package wouldn’t start, and even messed up my beloved Plex. I was even busy preparing an old RaspberryPi to use that as the platform for the controller, but I found out that I would have had to reset all my AP’s… So I gave my NAS a final try – what solved it in the end was to install, and subsequently update Java 8, then delete Java 7 from the NAS. Now the UniFi package will start again… Phew…

  20. AJvK
    29.03.2016 - 23:34

    Well, I was too quick to celebrate… Had to restart the NAS due to slow performance. After the reboot, I couldn’t start the UniFi package anymore.
    Error message as follows:

    UniFi Controller: Exception in thread “launcher” org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘ubntDiscoveryServer’ defined in class com.ubnt.service.AppContext: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public com.ubnt.net.o0OO com.ubnt.service.AppContext.ubntDiscoveryServer()] threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘dbService’ defined in class com.ubnt.service.AppContext: Invocation of init method failed; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:597) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1055) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:951) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:296) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:293) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at org.springframework.context.annotation.AnnotationConfigApplicationContext.(AnnotationConfigApplicationContext.java:73) at com.ubnt.service.OoOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.?O0000(Unknown Source) at com.ubnt.ace.Launcher.main(Unknown Source) Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public com.ubnt.net.o0OO com.ubnt.service.AppContext.ubntDiscoveryServer()] threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘dbService’ defined in class com.ubnt.service.AppContext: Invocation of init method failed; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:181) at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:586) … 14 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘dbService’ defined in class com.ubnt.service.AppContext: Invocation of init method failed; nested exception is java.lang.NullPointerException at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1512) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:296) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:293) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:305) at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29.dbService() at com.ubnt.service.AppContext.ubntDiscoveryServer(Unknown Source) at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29.CGLIB$ubntDiscoveryServer$2() at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29$$FastClassBySpringCGLIB$$618e7384.invoke() at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:293) at com.ubnt.service.AppContext$$EnhancerBySpringCGLIB$$9b0adc29.ubntDiscoveryServer() at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:160) … 15 more Caused by: java.lang.NullPointerException at com.ubnt.service.new.if.super(Unknown Source) at com.ubnt.service.new.if.?00000(Unknown Source) at com.ubnt.service.new.if.?00000(Unknown Source) at com.ubnt.service.new.if.afterPropertiesSet(Unknown Source) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1571) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1509) … 34 more
    2016-03-29 22:28:32

    I see a lot of java mentions, but as I said I have the most recent version installed. Any suggestions to help me get UniFi running again (even if it was only to easily reset the APs so I can move the controller over to a RaspberryPi)?

  21. Jur.
    30.03.2016 - 06:35

    hapens for me too.. Refresh the dsm login page, and start the controller a second time, it will run..

  22. Dirk
    30.03.2016 - 08:30

    any updates on the mfi install. I accidentally uninstalled the mfi program. I hope that I dont have to reset all my settings to get things back up.

  23. IFN
    03.04.2016 - 13:09

    I have a similar error as AJvK (Error creating bean “housekeeping”) after a DSM upgrade on R812+. I have uninstalled Java7, reinstalled Java 8, updated the jdk to jdk-8u77-linux-i586.tar.gz

    I’m running controller 4.8.14-160223. Unlike Jur., a refresh of the login and restart does not work.

    Any suggestions?

  24. IFN
    03.04.2016 - 13:18

    Just tried beta 4.9.2 – same issue

  25. Dirk
    03.04.2016 - 17:20

    I cannot get mfi to load on DSM 6.0. Can anyone offer advice?

  26. Moucha
    12.04.2016 - 16:33

    I instaled today. MFI is 100% working and Unifi is running, but its not 100% stable..

    I have 713+, last version DSM 6.0

    but thanks and I look forward to new version 🙂

  27. Rolando
    14.04.2016 - 20:58

    Hi Moucha, I’ve the same 713+ and DSM 6.0. Since he upgrade to DSM 6 I’ve problem in installing mFI. Unifi is working well, but mFi seem to install and start (with some errors), but when I try to connect to the mFi GUI the browser remains in ‘trying to establish a secure connection’.
    Log reports many directory and java errors.
    I’ve Java 8 updated to 1.8.0_77 (from Oracle download site). Any suggestion?
    Many thanks

    Rolando

  28. Hamish
    05.05.2016 - 13:44

    Hi there! Any plans to update the packages for the newer Syno 216j which uses the Armada 385 CPU? Thanks 🙂

  30. Kenneth
    10.05.2016 - 11:05

    Same here.. Also getting the UniFi Controller: Exception in thread “launcher” org.springframework.beans.factory.BeanCreationException when trying to start the UniFi on my DS214se.. Tried installing like all possible java versions out there.. restarting the device several times etc.. no luck…

    Any idea what to do now?

  31. Rob R
    12.05.2016 - 02:54

    Ditto on the Armada 385 CPU (DS216j)! Thanks!

  32. namlaz
    19.05.2016 - 12:38

    Hello,

    All of you who have an error when starting Unifi Controller starting like the following

    > Exception in thread “launcher” org.springframework.beans.factory.BeanCreationException

    It may be because the controller didn’t start before the end of the timeout (default 60s).

    It is likely that it happens after an upgrade of the controller, because it needs to upgrade the database which can be very long (3 minutes for me on DS 416+) :
    > [2016-05-19 08:36:53,931] INFO db – DB version (4.8.15) different from Runtime Version(4.8.17), migrating…
    then many messages like this :
    > [2016-05-19 08:36:57,443] ERROR system – [exec] error, rc=141
    > [2016-05-19 08:36:57,444] INFO db – DbServer stopped
    until finally
    > [2016-05-19 08:39:37,931] INFO db – DB migration to version (4.8.17) is complete.

    The solution as said by Wakko is to extend the timeout in the startup script via SSH with your user that has to be an administrator :
    ~~~~
    ssh youruser@yourdiskstationIP
    sudo su
    cd /var/packages/UniFi\ Controller/scripts
    sed -i s/TIMEOUT=60/TIMEOUT=180 start-stop-status
    exit
    ~~~~
    Once this is done, start the Unifi Controller package and wait 🙂

    Cheers,

  33. jason
    22.05.2016 - 19:37

    i think there is a typo in your sed line:
    sed -i s/TIMEOUT=60/TIMEOUT=180 start-stop-status
    should be
    sed -i s/TIMEOUT=60/TIMEOUT=180/ start-stop-status

    I think ..

  34. jason
    22.05.2016 - 23:24

    On my 214play the timeout was already at 180. I used vi to change the timeout to 360, saved the start-stop-timeout file and the service would then start. Solution!

  35. turti
    23.05.2016 - 17:32

    @namlaz
    Great hint!
    which device do you have? I´ve got a DS215j, but your solution does unfortunateli not work on it…

  36. Paul
    26.05.2016 - 13:35

    Until a while ago I had issues running the Unifi Controller on my DS414 (ARM arch). However, i’ve managed to get a hold of an ARM package of MongoDB v2.6.3 which is running stable, instead of the original v2.1 delivered with the Unifi controller package which crashes all the time. This worked fine for 4.8.14 and 4.8.15 release and was running stable for months. Using the original MongoDB package, it usually crashed after a couple of hours (if not already during configuration). Yesterday I wanted to upgrade the software to 4.8.18, but got errors while starting. Checking the logfiles it showed that it was going to upgrade the database from 4.8.15 to 4.8.18, but then the mongod logfile showed segmentation faults. I’ve tried to extend the time-out (even to 1440s), without any success. Seems logic, since the mongod crashes with the segmentation fault and nothing happens anymore.
    Next I uninstalled the Unifi Controller and installed again (so clean install). Replaced the original MongoDB with my version and I was able to start and configure Unifi Controller. 🙂 So far so good, so I tried a restore of my backup I made before installing 4.8.18. Got the same error again (segmentation fault). Too bad.
    After hours of trying and checking logfiles, I ended up configuring the whole Unifi Controller from scratch (I did it lots of times since the MongoDB crashed all time on me before, so didn’t take me too long luckily). Now, it’s running stable again with 3 APs and couple of (wireless) clients. Running for 1 hour only, but usually if something is wrong with the MongoDB it would crash on me already while configuring so I have good hopes it remains stable.
    By the way, the time-out still is on 60s, without any problems.

  37. Martin
    06.06.2016 - 16:01

    @Paul where du you get the MongoDB v2.6.3 package? Is it possible to upload it? I think that is an important hint to go forward with Unifi Controller on ARM arch!

  38. Paul
    07.06.2016 - 11:37

    To be honest, I’ve no clue where I found the MongoDB version; Google and patience are your best friends with these things. 😉 I’ve put it on my Dropbox so you can download it from there: https://www.dropbox.com/s/nfyfh1voq29q14a/mongodb-2.6.4-arm.7z?dl=0
    Replace the current “bin” folder from the UniFi installation with the “bin” folder from the package (or even better, create a symbolic link 🙂 ). Hit run package in Syno and you’re good to go. Sometimes it needs a second ‘run’ (like today when I updated my Syno), but it runs stable after that.

    Success!

  39. kevk85
    07.06.2016 - 20:03

    Do we know if he will be updating to Ubnt Controller 5.0?

  40. turti
    07.06.2016 - 22:14

    @Paul this solution works with my DS215J and UniFi 4.8.18 (TIMEOUT=600). Thanks a lot!

  41. Martin
    08.06.2016 - 16:49

    @Paul thank you very much! Its running! (with Armada 385 CPU) on DS416slim
    (i was not able to find this Version by google, thats wy i was asking to you.)
    Using UniFi 4.9.4

    @Wakko
    I think its a good way to update the mongoDB in your Packages with this Version.

    • Wakko
      08.06.2016 - 16:56

      Hi!
      Could you try to update 4.8.19? I’ve replaced binaries for mongo with newer version.

  42. Martin
    09.06.2016 - 18:53

    Hi Wakko,

    thanks for the new building. (4.8.19)
    First i did an implied upgrade. (Backup of running Version first) But this did not work.

    After that i uninstalled the Unifi Controller and reinstalled the new one (with the option import DATA and LOG files.)
    Make sure that the button “automatic Start after installation” is not chose.
    After that i copied backuped DATA and LOG Files and changed timeout option and start the Controller.
    But this did not work.

    So i reinstalled the Backup (4.8.14), and this run.

    Additional there is one more thing:
    Please, add arch=”armada38x” in the info file of package to add support for the new Generation of ARM V71 Processor.
    In the moment I had to fix this by my own with 7zip and editing the info file.
    And perhaps change the timeout by default to 180, als discussed before

    cd /var/packages/UniFi\ Controller/scripts
    sed -i s/TIMEOUT=60/TIMEOUT=180 start-stop-status

    ——— finaly: Error Log of mongod.log

    2016-06-09T16:15:15.800+0200 ***** SERVER RESTARTED *****
    2016-06-09T16:15:15.817+0200 [initandlisten] MongoDB starting : pid=28880 port=27117 dbpath=/volume1/@appstore/UniFi Controller/data/db 32-bit host=xxxxx
    2016-06-09T16:15:15.818+0200 [initandlisten]
    2016-06-09T16:15:15.818+0200 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary.
    2016-06-09T16:15:15.818+0200 [initandlisten] ** 32 bit builds are limited to less than 2GB of data (or less with –journal).
    2016-06-09T16:15:15.818+0200 [initandlisten] ** Note that journaling defaults to off for 32 bit and is currently off.
    2016-06-09T16:15:15.818+0200 [initandlisten] ** See http://dochub.mongodb.org/core/32bit
    2016-06-09T16:15:15.818+0200 [initandlisten]
    2016-06-09T16:15:15.818+0200 [initandlisten] db version v2.6.3
    2016-06-09T16:15:15.818+0200 [initandlisten] git version: nogitversion
    2016-06-09T16:15:15.818+0200 [initandlisten] build info: Linux dmy-VirtualBox 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 BOOST_LIB_VERSION=1_49
    2016-06-09T16:15:15.818+0200 [initandlisten] allocator: system
    2016-06-09T16:15:15.818+0200 [initandlisten] options: { net: { bindIp: “127.0.0.1”, http: { enabled: false }, port: 27117 }, storage: { dbPath: “/volume1/@appstore/UniFi Controller/data/db” }, systemLog: { destination: “file”, logAppend: true, path: “logs/mongod.log” } }
    2016-06-09T16:15:15.819+0200 [initandlisten]
    2016-06-09T16:15:15.819+0200 [initandlisten] ** WARNING: Readahead for /volume1/@appstore/UniFi Controller/data/db is set to 2048KB
    2016-06-09T16:15:15.819+0200 [initandlisten] ** We suggest setting it to 256KB (512 sectors) or less
    2016-06-09T16:15:15.819+0200 [initandlisten] ** http://dochub.mongodb.org/core/readahead
    2016-06-09T16:15:15.896+0200 [initandlisten] waiting for connections on port 27117
    2016-06-09T16:15:15.991+0200 [initandlisten] connection accepted from 127.0.0.1:47625 #1 (1 connection now open)
    2016-06-09T16:15:15.994+0200 [conn1] SEVERE: Invalid access at address: 0x40d9c000
    2016-06-09T16:15:15.997+0200 [conn1] SEVERE: Got signal: 11 (Segmentation fault).
    Backtrace:0x6e4db4 0x6e477c 0x6e4802 0x76cd9e80
    bin/mongod(_ZN5mongo15printStackTraceERSo+0x17) [0x6e4db4]
    bin/mongod() [0x6e477c]
    bin/mongod() [0x6e4802]
    /lib/libc.so.6(__default_rt_sa_restorer+0) [0x76cd9e80]

  43. Martin
    10.06.2016 - 17:49

    @Paul
    i think my Post before shows the same Error you got, by upgrading Daterbase Unifi Controller 4.8.14/15 to 4.8.18. I got the same issue first with running 4.9.4 on synology. After plain installation thr 4.94 runs without issues, but after installing Backup form 4.8.14 (from my MAC) it crashes all time.

    So i startet over reintalling the 4.8.14 Version on my Synology NAS and copied the Backup from my MAC 4.8.14 to the NAS. That was a good idea and every thing was running very well without issues.

    So i think, there is a big problem by upgrading the Database. Perhaps Timeout, but i dont think so.

    Perhaps i will try this workarround:
    Copy back the running setup of synolgy to my mac. Do the Database and Unifi Update on my Mac to Version 4.9.4 or higher (Unifi 5.07 is running very well in my office) and Install fresh and same Version of Unifi Controller on Synology with Backup of upgraded Daterbase on Mac.
    I think this will work.

    @Wakko
    Is there a posibility to get new 5.0.7 Package for ARM? I think you did everything right, but there is only a fault by upgrading the Database.
    I would like to test this with my synology and pushig the database Upgrade with my MAC.
    Sorry i read the Post of Paul again an after that i know that i did a mistake by testing your new Build of 4.8.19. I think the package is ok for the moment! (without testing it)

  44. namlaz
    20.06.2016 - 19:38

    @jason You’re right, little typo there and I can’t edit my comment :/

    @turti As said, I’ve got a DS416+, you may have to increase the timeout is your Diskstation is less powerfull.

    @Paul Strange issue you have there, I’ve noticed no crashes at all of the MongoDB process with older or newer version of the binaries, running 24/7.

    I still had to use my timeout fix to the latest release in order to run the controller. migration from 4.8.17 to 4.8.19 took 2minutes !

    Looking forward to a 5.0 package of the controller 🙂

  45. namlaz
    27.06.2016 - 15:11

    Hello all,

    After upgrading my DSM from 6.0.0 to 6.0.1 the controller doesn’t want to start anymore.
    server.log keeps saying DB is dead whereas the mongodb.log is silent.

    After a little more digging, it looks like the Unifi Controller Java process (java ace.jar) is unable to start MongoDB for some reason.
    If I start the DB manually, the Unifi Controller can talk to the DB, does its routine and everything goes fine…
    Here is the command I used to start MongoDB :

    /var/packages/UniFi\ Controller/target/bin/mongod –dbpath “/volume1/@appstore/UniFi Controller/data/db” –logpath “/volume1/@appstore/UniFi Controller/logs/mongod.log” –logappend –nohttpinterface –bind_ip 127.0.0.1 –port 27117

    I don’t really understand what changed between 6.0.0 and 6.0.1 so that the Unifi controller Java process is unable to start the MongoDB process, maybe a security restriction ?

  46. Pavlek
    29.06.2016 - 20:58

    Hello,
    something about DS 416play? It has celeron N3060.

    Thanks

  47. Wally
    03.07.2016 - 12:49

    Hi, I (try to) run UniFi 4.8.19-1606-08 on my DS 214+ with MARVELL Armada XP MV78230, DSM 6.0.1-7393 Update 1 and Java 8.0.60 … once I did the setup for my UniFi AP the system was running but now it wont start at all … I tried to increase the timeout and also start mongo db manual .. but all I get is:

    2016-07-03T11:41:01.584+0200 [initandlisten] MongoDB starting : pid=32538 port=27117 dbpath=/volume1/@appstore/UniFi Controller/data/db 32-bit host=DiskStation
    2016-07-03T11:41:01.584+0200 [initandlisten]
    2016-07-03T11:41:01.584+0200 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary.
    2016-07-03T11:41:01.584+0200 [initandlisten] ** 32 bit builds are limited to less than 2GB of data (or less with –journal).
    2016-07-03T11:41:01.584+0200 [initandlisten] ** See http://dochub.mongodb.org/core/32bit
    2016-07-03T11:41:01.585+0200 [initandlisten]
    2016-07-03T11:41:01.585+0200 [initandlisten] db version v2.6.3
    2016-07-03T11:41:01.585+0200 [initandlisten] git version: nogitversion
    2016-07-03T11:41:01.585+0200 [initandlisten] build info: Linux dmy-VirtualBox 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 BOOST_LIB_VERSION=1_49
    2016-07-03T11:41:01.585+0200 [initandlisten] allocator: system
    2016-07-03T11:41:01.585+0200 [initandlisten] options: { net: { bindIp: “127.0.0.1”, http: { enabled: false }, port: 27117 }, storage: { dbPath: “/volume1/@appstore/UniFi Controller/data/db”, journal: { enabled: true } }, systemLog: { destination: “file”, logAppend: true, path: “/volume1/@appstore/UniFi Controller/logs/mongod.log” } }
    2016-07-03T11:41:01.585+0200 [initandlisten]
    2016-07-03T11:41:01.586+0200 [initandlisten] ** WARNING: Readahead for /volume1/@appstore/UniFi Controller/data/db is set to 2048KB
    2016-07-03T11:41:01.586+0200 [initandlisten] ** We suggest setting it to 256KB (512 sectors) or less
    2016-07-03T11:41:01.586+0200 [initandlisten] ** http://dochub.mongodb.org/core/readahead
    2016-07-03T11:41:01.676+0200 [initandlisten] journal dir=/volume1/@appstore/UniFi Controller/data/db/journal
    2016-07-03T11:41:01.677+0200 [initandlisten] recover : no journal files present, no recovery needed
    2016-07-03T11:41:01.812+0200 [initandlisten] info openExisting file size 16777216 but storageGlobalParams.smallfiles=false: /volume1/@appstore/UniFi Controller/data/db/local.0
    2016-07-03T11:41:01.820+0200 [IndexRebuilder] info openExisting file size 16777216 but storageGlobalParams.smallfiles=false: /volume1/@appstore/UniFi Controller/data/db/local.0
    2016-07-03T11:41:01.822+0200 [initandlisten] waiting for connections on port 27117
    2016-07-03T11:41:01.830+0200 [initandlisten] connection accepted from 127.0.0.1:34998 #1 (1 connection now open)
    2016-07-03T11:41:01.835+0200 [conn1] SEVERE: Invalid access at address: 0x404c0000
    2016-07-03T11:41:01.838+0200 [conn1] SEVERE: Got signal: 11 (Segmentation fault).
    Backtrace:0x6e4db4 0x6e477c 0x6e4802 0x2ad8fe80
    /var/packages/UniFi Controller/target/bin/mongod(_ZN5mongo15printStackTraceERSo+0x17) [0x6e4db4]
    /var/packages/UniFi Controller/target/bin/mongod() [0x6e477c]
    /var/packages/UniFi Controller/target/bin/mongod() [0x6e4802]
    /lib/libc.so.6(__default_rt_sa_restorer+0) [0x2ad8fe80]

    Can anyone help me to get this working again ???

  48. Eugenio Hombrado
    05.07.2016 - 09:49

    I upgraded my Synology DS1815+ to unifi controller to 5.1.1 and you can not run …
    The web gui does not work …

    ERR_CONNECTION_REFUSED

    What could be the problem?

    Before the 4.9 beta and had worked perfectly …

    Thank you

    • Wakko
      05.07.2016 - 11:22

      Without logs I can say only one: “You doing something wrong”.

  49. Eugenio Hombrado
    05.07.2016 - 12:42

    I Wakko

    I install first unifi controller 4.8.20 configure my network, I perform the backup and stop the unifi controller in the synology.
    After download & run the unifi controller 5.1.1 via web …and you can not run …

    web error : ERR_CONNECTION_REFUSED

    I urged java java 7 and 8 and Mongo …

    no longer where the problem …

    Thanks
    Sorry for my English

    Regards

  50. Eugenio Hombrado
    05.07.2016 - 21:14

    Adjunt picture…

    [img=http://s2.subirimagenes.com/imagen/previo/thump_9617525captura-de-pantalla.png]

    INFO db – DbServer stopped

    Thanks

    • Wakko
      06.07.2016 - 01:05

      As you can see on this picture – something is already use port #3478. You need to find this application an stop it.
      Or you can specify another port for stun in UniFi. You need to edit /volume1/\@appstore/UniFi\ Controller\ 5/data/system.properties file.

  51. Martin
    10.07.2016 - 17:15

    Hi Wakko, i installed the 5.1.1 on ARM with Armada38x. You did use the old MongoDB (Version 2.1.1) an this will Point Error RC=141 again.

    I changed the mongod file to the newer one, as writen before, after that RC=141, was gone, but new issue startet.

    So only copy new Firmware for Access Points and go back to 4.8.14

    2016-07-10T15:44:40.772+0200 ***** SERVER RESTARTED *****
    2016-07-10T15:44:40.789+0200 [initandlisten] MongoDB starting : pid=21715 port=27117 dbpath=/volume1/@appstore/UniFi Controller 5/data/db 32-bit host=NAS2
    2016-07-10T15:44:40.789+0200 [initandlisten]
    2016-07-10T15:44:40.789+0200 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary.
    2016-07-10T15:44:40.789+0200 [initandlisten] ** 32 bit builds are limited to less than 2GB of data (or less with –journal).
    2016-07-10T15:44:40.789+0200 [initandlisten] ** See http://dochub.mongodb.org/core/32bit
    2016-07-10T15:44:40.790+0200 [initandlisten]
    2016-07-10T15:44:40.790+0200 [initandlisten] db version v2.6.3
    2016-07-10T15:44:40.790+0200 [initandlisten] git version: nogitversion
    2016-07-10T15:44:40.790+0200 [initandlisten] build info: Linux dmy-VirtualBox 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 BOOST_LIB_VERSION=1_49
    2016-07-10T15:44:40.790+0200 [initandlisten] allocator: system
    2016-07-10T15:44:40.790+0200 [initandlisten] options: { net: { bindIp: “127.0.0.1”, http: { enabled: false }, port: 27117 }, storage: { dbPath: “/volume1/@appstore/UniFi Controller 5/data/db”, journal: { enabled: true }, smallFiles: true }, systemLog: { destination: “file”, logAppend: true, path: “logs/mongod.log” } }
    2016-07-10T15:44:40.791+0200 [initandlisten]
    2016-07-10T15:44:40.791+0200 [initandlisten] ** WARNING: Readahead for /volume1/@appstore/UniFi Controller 5/data/db is set to 2048KB
    2016-07-10T15:44:40.791+0200 [initandlisten] ** We suggest setting it to 256KB (512 sectors) or less
    2016-07-10T15:44:40.791+0200 [initandlisten] ** http://dochub.mongodb.org/core/readahead
    2016-07-10T15:44:40.837+0200 [initandlisten] journal dir=/volume1/@appstore/UniFi Controller 5/data/db/journal
    2016-07-10T15:44:40.838+0200 [initandlisten] recover begin
    2016-07-10T15:44:40.838+0200 [initandlisten] info no lsn file in journal/ directory
    2016-07-10T15:44:40.838+0200 [initandlisten] recover lsn: 0
    2016-07-10T15:44:40.838+0200 [initandlisten] recover /volume1/@appstore/UniFi Controller 5/data/db/journal/j._0
    2016-07-10T15:44:40.866+0200 [initandlisten] recover cleaning up
    2016-07-10T15:44:40.866+0200 [initandlisten] removeJournalFiles
    2016-07-10T15:44:40.874+0200 [initandlisten] recover done
    2016-07-10T15:44:41.146+0200 [initandlisten] preallocateIsFaster=true 3.38
    2016-07-10T15:44:41.296+0200 [initandlisten] waiting for connections on port 27117
    2016-07-10T15:44:41.717+0200 [initandlisten] connection accepted from 127.0.0.1:41121 #1 (1 connection now open)
    2016-07-10T15:44:41.719+0200 [conn1] SEVERE: Invalid access at address: 0x5d6c9000
    2016-07-10T15:44:41.721+0200 [conn1] SEVERE: Got signal: 11 (Segmentation fault).
    Backtrace:0x6e4db4 0x6e477c 0x6e4802 0x76cdee80
    bin/mongod(_ZN5mongo15printStackTraceERSo+0x17) [0x6e4db4]
    bin/mongod() [0x6e477c]
    bin/mongod() [0x6e4802]
    /lib/libc.so.6(__default_rt_sa_restorer+0) [0x76cdee80]

  52. Wally
    22.07.2016 - 08:38

    I have posted the same error trace before, but none seem to take notice (:-((

    2016-07-03T11:41:01.822+0200 [initandlisten] waiting for connections on port 27117
    2016-07-03T11:41:01.830+0200 [initandlisten] connection accepted from 127.0.0.1:34998 #1 (1 connection now open)
    2016-07-03T11:41:01.835+0200 [conn1] SEVERE: Invalid access at address: 0x404c0000
    2016-07-03T11:41:01.838+0200 [conn1] SEVERE: Got signal: 11 (Segmentation fault).
    Backtrace:0x6e4db4 0x6e477c 0x6e4802 0x2ad8fe80
    /var/packages/UniFi Controller/target/bin/mongod(_ZN5mongo15printStackTraceERSo+0x17) [0x6e4db4]
    /var/packages/UniFi Controller/target/bin/mongod() [0x6e477c]
    /var/packages/UniFi Controller/target/bin/mongod() [0x6e4802]
    /lib/libc.so.6(__default_rt_sa_restorer+0) [0x2ad8fe80]

    Which installed component could be responsible for this and how to fix this ?? Any ideas ??

  53. Wally
    27.07.2016 - 21:28

    @Wakko … could you as the expert please help to solve this mystery !! I don’t want to buy a new NAS with some Intel CPU, just because the bloody MongoDB this UniFi software is using … actually I would love to, but limited budget (;-)) I need to keep my DS-214+ for a while so please, please help !!

  54. Martin
    23.09.2016 - 22:11

    Hi folks,

    i would you like to know, i installed 5.2.4-160831-beta on armada38x (DS416slim)
    after plain install, i imported config of 4.8.14 an it works!!!
    So Unifi Controller 5 works on ARM, too. New Firmware for the AC was flashed an extended 5GHZ AC Support is available.
    Iphone App works, too.

    Everything is finde for the moment. Great thing! Thank you very much

  55. Mattias
    28.09.2016 - 20:07

    Hi Guys,
    I get a SSL issue when trying to access the https://xxx.xxx.xxx.xxx:8443 webpage? I get a SSL_ERROR_NO_CYPHER_OVERLAP error in both Firefox and Safari. Unfi controller 5.2.8-160926-beta is running and syno Java 7 is installed.

    I am running this on my DS214Play.

    I get some errors in the log for java which seems related…

    [2016-09-28 18:31:11,277] WARN system – cannot load native lib – ubnt_webrtc_jni
    [2016-09-28 18:31:13,540] WARN JSSESocketFactory – None of the ciphers specified are supported by the SSL engine : TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_EMPTY_RENEGOTIATION_INFO_SCSVF
    [2016-09-28 18:31:13,652] WARN JSSESocketFactory – None of the ciphers specified are supported by the SSL engine : TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_EMPTY_RENEGOTIATION_INFO_SCSVF

    Any idea how to fix this?

    Thanks

    /Mattias

  56. Erwan
    22.12.2016 - 00:44

    Hello Mathias

    Try to install java 8 and uninstall java 7 but i think java 8 is not available for dsm 5 just for dsm 6

  57. Michael
    06.05.2018 - 01:52

    Is this Project still active? Just bougt a brand new RS 2418+ and would love to get it installed, but it shows not comapatible 🙁

  58. Gustavo Maluk
    23.01.2019 - 22:17

    Hi, I migrated the hard drives from a ds415+ to a ds918+. Package Center suggested I should repair the MongoDB installation which I could do.
    Finally I uninstalled it and now I can’t install it again.
    Is there a solution for this.
    Kind regards.

  59. Stefan
    27.09.2019 - 14:14

    New Verision Update pls

Leave a Reply