![]() One could probably resolve it by downgrading all the way down to 162 but I didn't want to, since 275 should work I wanted that. Running java -version worked and when I put unifi-video openjdk 282 in google brought me here :-) # sudo /usr/sbin/unifi-video -vĮrror: A JNI error has occurred, please check your installation and try againĮxception in thread "main" : Illegal method name "new.super" in class com/ubnt/airvision/Main Looked in the service script and followed to unifi-video script. Though my NUC for some reason had full fan running (hot) and couldn't connect to ssh so I wasn't sure were to start. Between this and them killing support for all our old APs and the unstable Cloud Key G1 and its self-corrupting DB, I'm not happy with UniFi.Įxperienced the same. ![]() Looks like I gotta buy their shitty DVR (no RAID 10?) or Cloud Key G2 to keep getting updates. Then the unifi-video service started right up. I then froze the package to prevent upgrades: echo "openjdk-8-jre-headless:amd64" hold | dpkg -set-selections I then installed the old version (8u275) over the new one (8u282): dpkg -i openjdk-8-jre-headless_8u275-b01-0ubuntu1~18.04_b Running Ubuntu 18.04, I located the previous package and downloaded it to the server: wget Of course, that wouldn't work either, because even a fresh install would fail because of OpenJDK 8u282. I was ready to wipe the install and restore from backup. With other UniFi stuff, it was usually database corruption (mongod). I don't even know how I would have tried troubleshooting this. Sure enough, APT logs shows OpenJDK was recently updated from 8u275 to 8u282. And just the "failed!" message in the service status. ![]() I got an email from someone saying that they couldn't get to her videos. Well, this is how I found out that UniFi Video is dead. I'd love to hear if this happened to anyone else (on 1.8.0_282) - if so, then we're probably stuck on 275, if not, maybe I've done something weird that could be fixed. I only have the one version installed I tried this anyway and it did not help). I searched the UI community and only found one post and it seemed like the wrong java version was being used (the solution was update-alternatives -auto java. Nothing else comes up in journalctl and it doesn't write anything to the logs in /var/log/unifi-video/. Jan 21 21:08:33 systemd: Started LSB: Ubiquiti unifi-video. Jan 21 21:08:32 unifi-video: (unifi-video) checking for system.properties and truststore files. Jan 21 21:08:32 unifi-video: Starting Ubiquiti UniFi Video: unifi-video(unifi-video) Hardware type:Unknown Jan 21 21:08:32 systemd: Starting LSB: Ubiquiti unifi-video. Jan 21 21:08:32 systemd: Stopped LSB: Ubiquiti unifi-video. Jan 21 21:08:32 systemd: rvice: Succeeded. Process: 1494 ExecStart=/etc/init.d/unifi-video start (code=exited, status=0/SUCCESS) ![]() Loaded: loaded (/etc/init.d/unifi-video generated)Īctive: active (exited) since Thu 21:08:33 CST 14s ago This is what I get when it won't start: # java -version My server is running Debian 10 and I am on the last version of UniFi Video, 3.10.13. I upgraded again and the problem returned, rolling back again fixed it again. Rolling OpenJDK back to 1.8.0_275 fixed the problem. Just wondering if anyone else has seen this, and/or wanting to let people know it's easy to fix. Last night when I updated Java, my other services (UniFi and OpenHAB) restarted normally but UniFi Video failed to start. (I know UniFi Video is no longer officially supported by Ubiquiti) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |