Reply
New Member
Posts: 2
Registered: ‎03-15-2017

Re: Cloud Key - Unifi Stopped?

did an upgrade to 6.10,   now I get a login screen, but it hangs at login... ssh login works, but not sure what to look at...

 

 

help...

New Member
Posts: 7
Registered: ‎01-22-2014

Re: Cloud Key - Unifi Stopped?

We have approximately 20 Cloudkeys.  4 are stopped, including mine at home.  Shows Unifi stopped and cannot start it on the WebUI.  Unifi controller definitely not running, so not just a bug in the CK screen like stated previously.  What is the process for reviving?

New Member
Posts: 7
Registered: ‎01-22-2014

Re: Cloud Key - Unifi Stopped?

I just updated to 0.6.10 and stuck in an older backup and it seems to be back up again. Hopefully, it stays that way.
New Member
Posts: 1
Registered: ‎01-18-2017

Re: Cloud Key - Unifi Stopped?

I've got a cloudkey that seems pretty bricked as well. It stopped working a while ago after a switch reboot, and never came back online. I've upgraded the firmware to v0.6.10, the unfi software to 5.4.19-9258. I've tried moving the database out of the way, no luck there. I've tried restoring from backup, seems to hang.

 

This is what I see in the server.log:

root@UniFi-CloudKey:~/lib# tail /srv/unifi/logs/server.log
[2017-07-27 15:16:20,733] <db-server> ERROR system - [exec] error, rc=100
[2017-07-27 15:16:20,733] <db-server> INFO  db     - DbServer stopped
[2017-07-27 15:16:24,983] <db-server> ERROR system - [exec] error, rc=100
[2017-07-27 15:16:24,983] <db-server> INFO  db     - DbServer stopped
[2017-07-27 15:16:29,233] <db-server> ERROR system - [exec] error, rc=100
[2017-07-27 15:16:29,233] <db-server> INFO  db     - DbServer stopped
[2017-07-27 15:16:33,495] <db-server> ERROR system - [exec] error, rc=100
[2017-07-27 15:16:33,496] <db-server> INFO  db     - DbServer stopped
[2017-07-27 15:16:37,758] <db-server> ERROR system - [exec] error, rc=100
[2017-07-27 15:16:37,759] <db-server> INFO  db     - DbServer stopped

I looked into what the web interface tries to do when restoring from backup, and have tried to manually do that from the command line:

 

root@UniFi-CloudKey:/srv/unifi# /usr/bin/java -jar /usr/lib/unifi/lib/ace.jar restore /data/autobackup/autobackup_5.4.11_20170530_0700_1496127600192.unf

However, this seems to just hang. I tried letting the process run over night, and receive no output to stdio. I took a look into the java process, and it doesn't seem to be dead, just not doing anything:

 

root@UniFi-CloudKey:~/lib# ps auxwww | grep restore
root      3455  0.0  0.0   2072   544 pts/1    S+   15:21   0:00 grep restore
root      8393  1.2  2.1 345592 43868 pts/0    Sl+  Jul26  16:57 /usr/bin/java -jar /usr/lib/unifi/lib/ace.jar restore /data/autobackup/autobackup_5.4.11_20170530_0700_1496127600192.unf
root@UniFi-CloudKey:~/lib# jstack -l 8393
2017-07-27 15:21:11
Full thread dump Java HotSpot(TM) Client VM (25.131-b11 mixed mode):

"Attach Listener" #38861 daemon prio=9 os_prio=0 tid=0x6345dc00 nid=0x6ff8 waiting on condition [0x00000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
	- None

"MongoCleaner16542045" #14 daemon prio=5 os_prio=0 tid=0x6224a400 nid=0x213a waiting on condition [0x61f5e000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
	at java.lang.Thread.sleep(Native Method)
	at com.mongodb.Mongo$CursorCleanerThread.run(Mongo.java:796)

   Locked ownable synchronizers:
	- None

"cluster-2-127.0.0.1:27117" #12 daemon prio=5 os_prio=0 tid=0x6223fc00 nid=0x2138 waiting on condition [0x61ffe000]
   java.lang.Thread.State: TIMED_WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x69bc2240> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
	at com.mongodb.ServerMonitor$ServerMonitorRunnable.waitForSignalOrTimeout(ServerMonitor.java:178)
	at com.mongodb.ServerMonitor$ServerMonitorRunnable.waitForNext(ServerMonitor.java:159)
	at com.mongodb.ServerMonitor$ServerMonitorRunnable.run(ServerMonitor.java:125)
	at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:
	- None

"db-server" #10 daemon prio=5 os_prio=0 tid=0x62245000 nid=0x2124 waiting on condition [0x623ae000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
	at java.lang.Thread.sleep(Native Method)
	at com.ubnt.service.B.O$1.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:
	- None

"shutdown-listener" #9 daemon prio=5 os_prio=0 tid=0x627c7c00 nid=0x2123 waiting on condition [0x624fe000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
	at java.lang.Thread.sleep(Native Method)
	at com.ubnt.service.B.ooOo$1.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:
	- None

"process reaper" #8 daemon prio=10 os_prio=0 tid=0x62ba6400 nid=0x20fb waiting on condition [0x62d53000]
   java.lang.Thread.State: TIMED_WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x69887700> (a java.util.concurrent.SynchronousQueue$TransferStack)
	at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
	at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
	at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
	at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941)
	at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:
	- None

"Service Thread" #6 daemon prio=9 os_prio=0 tid=0x76183800 nid=0x20e2 runnable [0x00000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
	- None

"C1 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x76180400 nid=0x20e1 waiting on condition [0x00000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
	- None

"Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x7617ec00 nid=0x20e0 runnable [0x00000000]
   java.lang.Thread.State: RUNNABLE

   Locked ownable synchronizers:
	- None

"Finalizer" #3 daemon prio=8 os_prio=0 tid=0x76164c00 nid=0x20d9 in Object.wait() [0x636ae000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x696965f0> (a java.lang.ref.ReferenceQueue$Lock)
	at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
	- locked <0x696965f0> (a java.lang.ref.ReferenceQueue$Lock)
	at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
	at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

   Locked ownable synchronizers:
	- None

"Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x76162000 nid=0x20d8 in Object.wait() [0x636fe000]
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	- waiting on <0x69696790> (a java.lang.ref.Reference$Lock)
	at java.lang.Object.wait(Object.java:502)
	at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
	- locked <0x69696790> (a java.lang.ref.Reference$Lock)
	at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

   Locked ownable synchronizers:
	- None

"launcher" #1 prio=5 os_prio=0 tid=0x76107000 nid=0x20ca waiting on condition [0x7631d000]
   java.lang.Thread.State: TIMED_WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x69bae628> (a java.util.concurrent.CountDownLatch$Sync)
	at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
	at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
	at com.mongodb.BaseCluster.getDescription(BaseCluster.java:142)
	at com.mongodb.DBTCPConnector.getClusterDescription(DBTCPConnector.java:402)
	at com.mongodb.DBTCPConnector.getType(DBTCPConnector.java:584)
	- locked <0x69bae6b8> (a com.mongodb.DBTCPConnector)
	at com.mongodb.DBTCPConnector.getReplicaSetStatus(DBTCPConnector.java:370)
	at com.mongodb.Mongo.getReplicaSetStatus(Mongo.java:446)
	at com.mongodb.DB.getCommandReadPreference(DB.java:82)
	at com.mongodb.DB.command(DB.java:317)
	at com.mongodb.DB.command(DB.java:299)
	at com.mongodb.DB.command(DB.java:374)
	at com.mongodb.DB.command(DB.java:246)
	at com.mongodb.DB.command(DB.java:401)
	at com.ubnt.service.B.O.voidsuper(Unknown Source)
	at com.ubnt.service.B.O.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)
	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)
	- locked <0x6990b0e0> (a java.util.concurrent.ConcurrentHashMap)
	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.C$$EnhancerBySpringCGLIB$$229b78c3.o00000(<generated>)
	at com.ubnt.service.C.?00000(Unknown Source)
	at com.ubnt.service.C$$EnhancerBySpringCGLIB$$229b78c3.CGLIB$?00000$1(<generated>)
	at com.ubnt.service.C$$EnhancerBySpringCGLIB$$229b78c3$$FastClassBySpringCGLIB$$e7903b57.invoke(<generated>)
	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.C$$EnhancerBySpringCGLIB$$229b78c3.?00000(<generated>)
	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)
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:586)
	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)
	- locked <0x6990b0e0> (a java.util.concurrent.ConcurrentHashMap)
	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)
	- locked <0x698ec7d8> (a java.lang.Object)
	at org.springframework.context.annotation.AnnotationConfigApplicationContext.<init>(AnnotationConfigApplicationContext.java:73)
	at com.ubnt.service.new.?O0000(Unknown Source)
	- locked <0x698e4910> (a java.lang.Class for com.ubnt.service.new)
	at com.ubnt.ace.Launcher.main(Unknown Source)

   Locked ownable synchronizers:
	- None

"VM Thread" os_prio=0 tid=0x7615d800 nid=0x20d5 runnable 

"VM Periodic Task Thread" os_prio=0 tid=0x76185800 nid=0x20e3 waiting on condition 

JNI global references: 301

 

Any help here would be appreciated. Thanks

New Member
Posts: 2
Registered: ‎08-15-2017

Re: Cloud Key - Unifi Stopped?

Any update on a solution for this...

 

Just bought a complete solution (still waiting for a 48 ports switch) and having so much trouble keeping the cloud key alive - bordering on a joke.

 

Running latest firmware

New Member
Posts: 12
Registered: ‎04-05-2017
Kudos: 2

Re: Cloud Key - Unifi Stopped?

[ Edited ]

Yes ,

I have a loudkey, Ubiquiti switch , 10 Access points , and last time I used an upgrade on everything, the cloudkey no longer works. I thought that the cloudkey would be tested with any upgrades as normal testing procedures for software upgrades, prior to release.

At present, I have no time to stuff around with different softwares, rendering the paid for cloudkey as "Return to place of purchase, as it is currently "not fit for intended purpose"

Great idea, poor implementation.

Right now, it is sitting on a shelf, and I am 600 kms away from the actual switch and set Ubiquiti set up.

I am now very nervous to do any Ubiquiti software upgrades, if they are not adequately tested with Aps , switch , and cloudkey.  Happy with everything Ubiquiti as in AP's , but not the actual cloudkey.  If it is not resolved , I would say not to buy the cloudkey  for remote viewing of your Ubiquiti setup.

New Member
Posts: 8
Registered: ‎10-03-2016

Re: Cloud Key - Unifi Stopped?

@UBNT-KM

 

Hi, i have similiar issue with the cloudkey. The cloudkey is able to ping and SSH, but not able to load management and unifi controller web UI anymore.

My case number: 909255, more detail in case notes.

Can I know if UBNT support able to access the device remotely or user have to work with a remote session?

 

Appreciate your help.

Thanks

 

New Member
Posts: 1
Registered: ‎09-01-2017

Re: Cloud Key - Unifi Stopped?

I have been running into the same type of issue with one of our cloud keys. I can ping it and ssh into it, but not much else. I am unable to even login to the GUI, it doesn't show incorrect username or password, it just does nothing. It will show online but the launch option is greyed out. After SSH'ing in, I found I can essentially remotely reboot the key and this has re-established my ability to login to the GUI and manage it and allows me once again to launch it from the cloud. A few reboot commands failed at first, but this worked.

 

systemctl --force --force reboot

 

New Member
Posts: 15
Registered: ‎09-02-2017
Solutions: 1

Re: Cloud Key - Unifi Stopped?

[ Edited ]

I have the same problem. The cloud key seems to be offline in http://unifi.ubnt.com, but the wifi is running and guests can also still log in the guest wifi network, but I cannot open the cloudkey controller anymore. I updated or changed nothing before - the controller was just offline from one day to another after a power down period for 2 minutes.

 

But the power is back, of course, and the wifi works including the guest login again. The only issue is that I do not have access through http://unifi.ubnt.com anymore (he is still offline there).

 

The ports are forwarded, therefore I would be also able to access the cloudkey directly through the IP (or DynDNS) with the port 8443, which worked also fine before locally and through the internet. If I try now to open the cloudkey directly over DynDNS with port 8443, I get first the warn message, that the SSL certificate is not valid - so far so good (does this come from the security gateway or from the cloudkey by the way?). But after accepting the invalid SSL certificate nothing happens anymore and I get no further response of the cloudkey.

 

We also rebooted the Unifi switch again, we rebooted the Unifi security gateway again and of course we rebooted the cloud key. Everything is rebooting and working again, but not the access of the cloud key unfortunatly.

 

We also tried to add external power over USB to the cloudkey (he got power over PoE before), but this does also not help.

 

Does anyone have an idea what I could do to get access again - without resetting the cloud key?

New Member
Posts: 10
Registered: ‎09-20-2017

Re: Cloud Key - Unifi Stopped?

[ Edited ]

Add me to the list of dead cloud keys! Man Sad

 

I tested out the controller software on a raspberrypi 2 and was happy with it. Decided that it would be nice to use the pi for an OpenVPN server and use a cloud key instead. Purchased a refurb unit before I saw this thread. When I plugged it in and went through the setup it upgraded the firmware.

 

I thought my router was on the fritz (EdgeMaxPOE5) and power cycled it so that cauesd power loss to the key. Mine might be a total loss. About all I can do is get to the recovery mode. When I try to go to the 6.10 firmware it says that it is invalid. Actually, all the firmwares I've pushed to it are invalid. 

 

Of note, this thing gets hot! I understand it is passively cooled but I wouldn't be comfortable putting this thing in my home network gang box. 

 

Is SSH available in the recovery mode? I can't seem to get to it. Also, SSH is running on a standard port, right? I can't seem to get the key to run long enough for me to do anything.

 

EDIT:

I thought I read somewhere that the key uses the SD card for log and backup files. Is that true? In otherwords, a corrupt SD card wouldn't be causing this, correct?

 

EDIT:

Swapped out to another SD card. No difference. I cannot SSH into this thing at all. Ugh. Firing the pi back up in the meantime.

New Member
Posts: 7
Registered: ‎05-01-2017

Re: Cloud Key - Unifi Stopped?

Yeah there is definitely a flaw in the cloud key that is not being fixed (or even acknowledged really) by Unifi. All cloud keys / devices are updated to newest firmware.

 

I have two that slowly "degrade". At first they work normally (typically a few days to a week). Then you go to login and it just spins. Then the login page won't even work.

 

The first few times you can just cycle the power and it comes back. But after a few times that doesn't work so you need to do a factory reset. I then restore from a backup and I'm back at square one (i.e. after a few days it starts to degrade again). I tried new SD cards and just creating new settings thinking that either one may be the issue but that has done nothing.

 

Both cloud keys follow a similar degradation (not a precise timeline but definitely similar). Both live in well ventilated cabinets that are typically running around room temp (in air conditioned rooms).

 

The "live" support is just someone cutting / pasting scripts. Definitely no help there and definitely no acknowledgement that there is an issue of any sort.

 

I'm thinking of installing the controller on a Raspberry Pi on the assumption that it is a h/w issue and not an issue with the controller software. I've wasted way too much time on this already though.

 

Luckily I've had no issues with my other Unifi gear besides the blue light on the AP slowly fading away over time.

New Member
Posts: 10
Registered: ‎09-20-2017

Re: Cloud Key - Unifi Stopped?


@iano wrote:

 

I'm thinking of installing the controller on a Raspberry Pi on the assumption that it is a h/w issue and not an issue with the controller software. I've wasted way too much time on this already though.


I don't see why a Pi 3 wouldn't be able to handle the task of hosting the controller server. My only concern is RAM. The Pi 3 has 1Gb. I had installed it on my Pi 2 just as a way to play around with it. Not sure how much RAM it has, but haven't seen an issue so far. For my use case it actually works quite well.

 

If I don't see any resolution on this even show up on the horizon before my return window closes I'll just order a pi, a case, and a PoE splitter. I might even be able to find a white case and I can wire in a little blue LED!

Established Member
Posts: 1,613
Registered: ‎11-12-2015
Kudos: 445
Solutions: 46

Re: Cloud Key - Unifi Stopped?


@mikejr83 wrote:

@iano wrote:

 

I'm thinking of installing the controller on a Raspberry Pi on the assumption that it is a h/w issue and not an issue with the controller software. I've wasted way too much time on this already though.


I don't see why a Pi 3 wouldn't be able to handle the task of hosting the controller server. My only concern is RAM. The Pi 3 has 1Gb. I had installed it on my Pi 2 just as a way to play around with it. Not sure how much RAM it has, but haven't seen an issue so far. For my use case it actually works quite well.

 

If I don't see any resolution on this even show up on the horizon before my return window closes I'll just order a pi, a case, and a PoE splitter. I might even be able to find a white case and I can wire in a little blue LED!


Given the number of reports I guess that either we have a case of mass delusion or else there is a problem somewhere. But what? And is there any reason to believe it would be less of a problem on a Pi than on a cloud key?

 

The main problem I have seen reported appears to have to do with DB corruption provoked by an ungraceful shutdown. But I can see no reason why using a Pi rather than a cloud key would improve on that. It might just be that little appliances are treated differently than hosted servers.

 

But what @iano describes sounds like something different - accumulating rot over time. Again, without some hint as to what is causing that it is hard to see how running the controller on the Cloud Key would cause that.

 

I also wonder if there might be a difference between the newer (gen 2) cloud keys vs. the older ones. I have one of the old ones, and have experienced *none* of the problems that others are complaining about. AFAIK the main difference between the old ones and the new ones is that the old ones have less memory and flash. Again it is hard to see how that would prevent the problems.

 

New Member
Posts: 11
Registered: ‎10-17-2016

Re: Cloud Key - Unifi Stopped?

we were at version .7.3 (latest) yet all the reported problems here are 100% similar to what we experienced 

 

Key running fine for quite some time altough sometimes very slow, suddenly no more access

 

 

 

 

New Member
Posts: 5
Registered: ‎09-21-2017

Re: Cloud Key - Unifi Stopped?

No difference with a v2 key. I had these same problems. Do yourself a favor, backup, provision a small VM, install controller software, restore. My vendor is reporting 20 of the last 60 keys they sold are having this problem. My database was in good working condition and I tried every post, deleting local, deleting ace files. The real pain is when you plug a Unifi CloudKey into a Unifi switch. You reboot the switch, you nuke the key. It's fair to say you should run backups and keep these on a battery backup. But it is very easy to lose power to these. If any of us bought a CloudKey and it came with a sticker that said "Warning: Always provide power to this device or it will become unusable" we all would have thrown them out. I feel for the devs who were pressured to get this out the door, but we have customers of our own to protect.

Established Member
Posts: 1,613
Registered: ‎11-12-2015
Kudos: 445
Solutions: 46

Re: Cloud Key - Unifi Stopped?


@prasios wrote:

No difference with a v2 key. I had these same problems. Do yourself a favor, backup, provision a small VM, install controller software, restore. My vendor is reporting 20 of the last 60 keys they sold are having this problem. My database was in good working condition and I tried every post, deleting local, deleting ace files. The real pain is when you plug a Unifi CloudKey into a Unifi switch. You reboot the switch, you nuke the key. It's fair to say you should run backups and keep these on a battery backup. But it is very easy to lose power to these. If any of us bought a CloudKey and it came with a sticker that said "Warning: Always provide power to this device or it will become unusable" we all would have thrown them out. I feel for the devs who were pressured to get this out the door, but we have customers of our own to protect.


Do you have a v1 key? My suggestion was that this *might* be solely a v2 key problem, not v1.

 

I would think that if you run the controller locally on your network then the power problems would be much the same regardless of what you run it on. IIUC, rebooting a Unifi switch does not drop POE power. In any case, you can power the key with USB and plug the USB power source into a UPS, same as you can plug some other server into a UPS.

 

I do think there is some problem, but it hasn't been narrowed down to root cause.

New Member
Posts: 7
Registered: ‎05-01-2017

Re: Cloud Key - Unifi Stopped?

For me, it is definitely not a power issue. Everything is backed up via UPS and the switches uptime is several months (since I re-arranged a few things in the cabinet).
New Member
Posts: 5
Registered: ‎09-21-2017

Re: Cloud Key - Unifi Stopped?

I have not tried with a v1 key so I cannot comment on that. Regarding power, it is much less likely that my virtual hosts will go down abruptly due to power settings and graceful shutdown options I have in place. Additionally, I replicate VMs to secondary hosts so it is just more rubust for me. That on top of automatic backups means more confidence than a stick that may or may not corrupt its database if it loses power. I hope they do get this resolved, I like their software and hardware. But I can't install devices that can brick on power loss. Is that an acceptable norm?

Emerging Member
Posts: 44
Registered: ‎08-16-2016
Kudos: 17
Solutions: 2

Re: Cloud Key - Unifi Stopped?

Throughout this process thread I have lost 2, one recovered 1 time the other one 3 times. I have 4 deployed(on keys). Most recent was yesterday 0.7.3 Firmware 5.5.20-9565. Key went offline and I had to recover from backups. I have had auto backups running 1 time a week so I have always had a backup to restore from. (Also occasional manual backups.) Resources barely used. (I think there was a power event.)

 

Just wanted to post it for others to know it is still happening.

New Member
Posts: 10
Registered: ‎09-20-2017

Re: Cloud Key - Unifi Stopped?

How do you know if you have a v1 or v2 key?

Reply