Upcoming Maintenance Alert:

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

Learn more

×
Reply
Highlighted
New Member
Posts: 31
Registered: ‎08-07-2013
Kudos: 3
Accepted Solution

Unifi Controller on Debian 9

Hello, 

 

I'm having a really hard time getting the controller started on Debian 9. I followed the instructions here:

https://help.ubnt.com/hc/en-us/articles/220066768-UniFi-How-to-Install-Update-via-APT-on-Debian-or-U...

 

And it just fails to start. I'm not even seeing it create log entries in either syslog or the ubnt log folders.

 

I also found a post saying that you are supposed to use oracle java 8, so I installed that and still nothing.

 

 

1 S root     17247     1  0  80   0 -  2623 -      13:46 ?        00:00:00 unifi -home /usr/lib/jvm/oracle-java8-jdk-amd64 -cp /usr/share/java/commons-daemon.jar:/usr/lib/unifi/lib/ace.jar -pidfile /var/run/unifi/unifi.pid -procname unifi -outfile SYSLOG -errfile SYSLOG -Dunifi.datadir=/var/lib/unifi -Dunifi.logdir=/var/log/unifi -Dunifi.rundir=/var/run/unifi -Xmx1024M -Djava.awt.headless=true -Dfile.encoding=UTF-8 com.ubnt.ace.Launcher start
1 S root     17249 17247  0  80   0 -  2623 core_s 13:46 ?        00:00:00 unifi -home /usr/lib/jvm/oracle-java8-jdk-amd64 -cp /usr/share/java/commons-daemon.jar:/usr/lib/unifi/lib/ace.jar -pidfile /var/run/unifi/unifi.pid -procname unifi -outfile SYSLOG -errfile SYSLOG -Dunifi.datadir=/var/lib/unifi -Dunifi.logdir=/var/log/unifi -Dunifi.rundir=/var/run/unifi -Xmx1024M -Djava.awt.headless=true -Dfile.encoding=UTF-8 com.ubnt.ace.Launcher start

 

root@ubnt:/usr/lib/jvm# service unifi start
root@ubnt:/usr/lib/jvm# service unifi status
● unifi.service - unifi
   Loaded: loaded (/lib/systemd/system/unifi.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2017-06-19 13:50:43 PDT; 2s ago
  Process: 17309 ExecStop=/usr/lib/unifi/bin/unifi.init stop (code=exited, status=0/SUCCESS)
  Process: 17413 ExecStart=/usr/lib/unifi/bin/unifi.init start (code=exited, status=0/SUCCESS)
 Main PID: 17428 (jsvc)
    Tasks: 2 (limit: 9830)
   CGroup: /system.slice/unifi.service
           ├─17428 unifi -home /usr/lib/jvm/oracle-java8-jdk-amd64 -cp /usr/share/java/commons-daemon.jar:/usr/lib/unifi/lib/ace.jar -pidfile /var/run/unifi/unifi.pid -procname u
           └─17430 unifi -home /usr/lib/jvm/oracle-java8-jdk-amd64 -cp /usr/share/java/commons-daemon.jar:/usr/lib/unifi/lib/ace.jar -pidfile /var/run/unifi/unifi.pid -procname u

Jun 19 13:50:42 ubnt systemd[1]: Starting unifi...
Jun 19 13:50:42 ubnt unifi[17430]: 2017-06-19 13:50:42 17428 unifi error: Service killed by signal 11
Jun 19 13:50:43 ubnt unifi.init[17413]: Starting Ubiquiti UniFi Controller: unifi failed!
Jun 19 13:50:43 ubnt systemd[1]: Started unifi.

 

root@ubnt:/usr/lib/jvm# uname -a
Linux ubnt 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux

 

Any suggestions on what to do next? 


Accepted Solutions
Emerging Member
Posts: 59
Registered: ‎01-01-2016
Kudos: 34
Solutions: 3

Re: Unifi Controller on Debian 9

@poisonsnak  You're going to love this. It's JUST the kernel update. On top of that, I think it's being snippy with mongodb because the mongod process is just plain ornery when the updated kernel is in place. All the libc stuff, exim, etc. is fine. Tested it backwards and forwards on my Debian 9 UniFi VM. 

 

apt install linux-image-4.9.0-3-amd64:amd64=4.9.30-2 

 That one-liner fixes it after a reboot, but like you said you need to hold the old version to keep it in place after an apt upgrade. I wonder how much other stuff is broken right now as a result...

 

You may want to try just the kernel on your Debian 8 box to see if it has the same effect.

View solution in original post


All Replies
New Member
Posts: 14
Registered: ‎05-06-2014
Kudos: 2

Re: Unifi Controller on Debian 9

I have exactly the same problem.

I did the update from Debian 8.8 to 9 yesterday and I am pretty sure the controller was running fine. But after some additional updates today (the kernel deb was also updated), the controller doesn't start and also blocks system shutdown/reboot without any hints in the logs.

New Member
Posts: 1
Registered: ‎06-19-2017
Kudos: 2

Re: Unifi Controller on Debian 9

[ Edited ]

Hi!

 

The same problem heere. I'm sure Debian 8.8 is also affected because I had noted the problem just before I upgraded one of my controllers to Debian 9.

 

Currenty I have two broken controllers: Debian 4.9.0-3 (Debian 9) and Ubuntu 16.04.2. In each case the problem emerged just after upgrade and device restart:


2017-06-19 22:15:37,462 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates']
2017-06-19 22:15:48,907 INFO Packages that will be upgraded: grub-common grub-pc grub-pc-bin grub2-common libc-bin libc6 linux-generic linux-headers-generic linux-headers-virtual linux-image-generic linux-image-virtual linux-virtual loc$

 

New Member
Posts: 8
Registered: ‎11-06-2016
Kudos: 3

Re: Unifi Controller on Debian 9

Same on Ubuntu Server 16.04.2 LTS. 

Here's the list of pkgs that were upgraded prior:

 

2017-06-19 17:05:19 upgrade libc6:amd64 2.23-0ubuntu7 2.23-0ubuntu9
2017-06-19 17:05:29 upgrade locales:all 2.23-0ubuntu7 2.23-0ubuntu9
2017-06-19 17:05:33 upgrade libc-bin:amd64 2.23-0ubuntu7 2.23-0ubuntu9
2017-06-19 17:05:51 upgrade grub-pc:amd64 2.02~beta2-36ubuntu3.9 2.02~beta2-36ubuntu3.11
2017-06-19 17:05:56 upgrade grub-pc-bin:amd64 2.02~beta2-36ubuntu3.9 2.02~beta2-36ubuntu3.11
2017-06-19 17:06:00 upgrade grub2-common:amd64 2.02~beta2-36ubuntu3.9 2.02~beta2-36ubuntu3.11
2017-06-19 17:06:05 upgrade grub-common:amd64 2.02~beta2-36ubuntu3.9 2.02~beta2-36ubuntu3.11
2017-06-19 17:06:15 upgrade multiarch-support:amd64 2.23-0ubuntu7 2.23-0ubuntu9
2017-06-19 17:06:25 upgrade isc-dhcp-client:amd64 4.3.3-5ubuntu12.6 4.3.3-5ubuntu12.7
2017-06-19 17:06:27 upgrade isc-dhcp-common:amd64 4.3.3-5ubuntu12.6 4.3.3-5ubuntu12.7
2017-06-19 17:06:31 upgrade libtasn1-6:amd64 4.7-3ubuntu0.16.04.1 4.7-3ubuntu0.16.04.2
2017-06-19 17:06:35 upgrade libgnutls-openssl27:amd64 3.4.10-4ubuntu1.2 3.4.10-4ubuntu1.3
2017-06-19 17:06:37 upgrade libgnutls30:amd64 3.4.10-4ubuntu1.2 3.4.10-4ubuntu1.3
2017-06-19 17:06:41 upgrade libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 1.0.2g-1ubuntu4.8
2017-06-19 17:06:46 upgrade libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.1 2.4.42+dfsg-2ubuntu3.2
2017-06-19 17:06:50 upgrade openssl:amd64 1.0.2g-1ubuntu4.6 1.0.2g-1ubuntu4.8
2017-06-19 17:06:54 upgrade libnl-genl-3-200:amd64 3.2.27-1 3.2.27-1ubuntu0.16.04.1
2017-06-19 17:06:56 upgrade libnl-3-200:amd64 3.2.27-1 3.2.27-1ubuntu0.16.04.1
2017-06-19 17:07:01 upgrade linux-firmware:all 1.157.10 1.157.11
2017-06-19 17:08:40 upgrade linux-generic:amd64 4.4.0.78.84 4.4.0.81.87
2017-06-19 17:08:41 upgrade linux-image-generic:amd64 4.4.0.78.84 4.4.0.81.87
2017-06-19 17:09:59 upgrade linux-headers-generic:amd64 4.4.0.78.84 4.4.0.81.87
2017-06-19 17:10:16 upgrade lxcfs:amd64 2.0.6-0ubuntu1~16.04.1 2.0.7-0ubuntu1~16.04.1
2017-06-19 17:10:21 upgrade vlan:amd64 1.9-3.2ubuntu1.16.04.1 1.9-3.2ubuntu1.16.04.3

New Member
Posts: 5
Registered: ‎12-09-2016

Re: Unifi Controller on Debian 9

[ Edited ]

Same issue on Debian 9 and latest stable Unifi controller.

New Member
Posts: 31
Registered: ‎08-07-2013
Kudos: 3

Re: Unifi Controller on Debian 9

Wow... Glad I'm not the only one!

New Member
Posts: 1
Registered: ‎08-20-2016

Re: Unifi Controller on Debian 9

Same issue here, I even tried to create a new clean VM with Stretch (Debian 9) and install the last package from the testing repo, with no luck:

 

root@unifi-controller:/home/mattia# service unifi status
● unifi.service - unifi
   Loaded: loaded (/lib/systemd/system/unifi.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2017-06-19 22:15:56 UTC; 16min ago
  Process: 627 ExecStart=/usr/lib/unifi/bin/unifi.init start (code=exited, status=0/SUCCESS)
 Main PID: 679 (jsvc)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/unifi.service
           ├─679 unifi -home /usr/lib/jvm/java-8-openjdk-amd64 -cp /usr/share/java/commons-daemon.jar:/usr/lib/unifi/lib/ace.jar -pidfile /var/run/unifi/unifi.pid -pro
cname unifi -outfile SYSLOG -errfile SYSLOG -Dunifi.datadir=/var/lib/unifi -Dunifi.logdir=/var/log/unifi -Dunifi.rundir=/var/run/unifi -Xmx1024M -Djava.awt.headless=tr
ue -Dfile.encoding=UTF-8 com.ubnt.ace.Launcher start
           └─681 unifi -home /usr/lib/jvm/java-8-openjdk-amd64 -cp /usr/share/java/commons-daemon.jar:/usr/lib/unifi/lib/ace.jar -pidfile /var/run/unifi/unifi.pid -pro
cname unifi -outfile SYSLOG -errfile SYSLOG -Dunifi.datadir=/var/lib/unifi -Dunifi.logdir=/var/log/unifi -Dunifi.rundir=/var/run/unifi -Xmx1024M -Djava.awt.headless=tr
ue -Dfile.encoding=UTF-8 com.ubnt.ace.Launcher start
Jun 19 22:22:56 unifi-controller unifi[681]: 2017-06-19 22:22:56 679 unifi error: Service killed by signal 11
Jun 19 22:23:56 unifi-controller unifi[681]: 2017-06-19 22:23:56 679 unifi error: Service killed by signal 11
Jun 19 22:24:56 unifi-controller unifi[681]: 2017-06-19 22:24:56 679 unifi error: Service killed by signal 11
Jun 19 22:25:56 unifi-controller unifi[681]: 2017-06-19 22:25:56 679 unifi error: Service killed by signal 11
Jun 19 22:26:56 unifi-controller unifi[681]: 2017-06-19 22:26:56 679 unifi error: Service killed by signal 11
Jun 19 22:27:56 unifi-controller unifi[681]: 2017-06-19 22:27:56 679 unifi error: Service killed by signal 11
Jun 19 22:28:56 unifi-controller unifi[681]: 2017-06-19 22:28:56 679 unifi error: Service killed by signal 11
Jun 19 22:29:56 unifi-controller unifi[681]: 2017-06-19 22:29:56 679 unifi error: Service killed by signal 11
Jun 19 22:30:56 unifi-controller unifi[681]: 2017-06-19 22:30:56 679 unifi error: Service killed by signal 11
Jun 19 22:31:56 unifi-controller unifi[681]: 2017-06-19 22:31:56 679 unifi error: Service killed by signal 11
New Member
Posts: 2
Registered: ‎06-19-2017
Kudos: 1

Re: Unifi Controller on Debian 9

[ Edited ]

Signal 11 is SIGSEGFAULT.

 

confirmed on Ubuntu 16.04.2 LTS.

 

strace:

[pid 4173] open("/lib/x86_64-linux-gnu/libz.so.1", O_RDONLY|O_CLOEXEC) = 5
[pid 4173] read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\35\0\0\0\0\0\0"..., 832) = 832
[pid 4173] fstat(5, {st_mode=S_IFREG|0644, st_size=104864, ...}) = 0
[pid 4173] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7ffdedc70fd8} ---
[pid 4173] --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
[pid 4173] +++ killed by SIGSEGV (core dumped) +++
# dpkg -S /lib/x86_64-linux-gnu/libz.so.1
zlib1g:amd64: /lib/x86_64-linux-gnu/libz.so.1

seems unrelated, though.

 

Edit:

All affected hosts (including mine) did a recent libc6 update (Ubuntu: https://launchpad.net/ubuntu/+source/glibc/2.23-0ubuntu9). I'd guess that either the jvm or the unifi tool trigger an overflow that now gets caught and leads to segfault.

New Member
Posts: 17
Registered: ‎02-27-2016
Kudos: 2

Re: Unifi Controller on Debian 9

And did the upgrade too. Now unify is dead Man Sad Hope for fix soon Man Happy
Regular Member
Posts: 432
Registered: ‎02-04-2015
Kudos: 246
Solutions: 20

Re: Unifi Controller on Debian 9

Add me to the list, I know Stretch is not officially supported, but I am runnin Stretch at home and have been for over a year, with a Unifi and Unifi-Video controller both with no issues, so I figured upgrading this machine at work would be no big deal.

 

(unifi video is affected by this too by the way).

 

/var/log/unifi is completely empty so I am not even sure where to start

New Member
Posts: 22
Registered: ‎03-28-2015
Kudos: 2
Solutions: 2

Re: Unifi Controller on Debian 9

[ Edited ]

Definitely a Linux update that did it. I just did a clean install of Ubuntu 16.04 LTS if I take all the updates except "dist-update" UniFi controller works. If I do a "dist-update" those updates break the controller.

 

Don't have time to troubleshoot anymore tonight. 

Regular Member
Posts: 498
Registered: ‎02-13-2014
Kudos: 303
Solutions: 13

Re: Unifi Controller on Debian 9

Add me to the list...

signal11.png

 

 

 

 

Emerging Member
Posts: 59
Registered: ‎01-01-2016
Kudos: 34
Solutions: 3

Re: Unifi Controller on Debian 9

[ Edited ]

I'm having the same issue. I noticed that there is a library included in the controller package at /usr/lib/unifi/lib/native/Linux/amd64/libubnt_webrtc_ini.so. Given that the rest of this is packaged away in jars, I'm starting to wonder if some of the updates (libc6?) are causing hell with that library.

 

Edit: I don't think it's the culprit. Still, ERMAHGERD! Glad I backed up my VM before I picked on the upgrade.

New Member
Posts: 1
Registered: ‎05-25-2016

Re: Unifi Controller on Debian 9

Same problem here as well.

New Member
Posts: 17
Registered: ‎11-17-2015
Kudos: 5

Re: Unifi Controller on Debian 9

[ Edited ]

My controller (5.4.16) is currently working on Ubuntu 16.04, and I updated all of the packages late last week. If I were to dist-upgrade now this is the new list of what's waiting:

 

  • libc-bin
  • libc-dev-bin
  • libc6 (2.23-0ubuntu9, 2.23-0ubuntu7 installed)
  • libc6-dbg
  • libc6-dev
  • linux-generic (4.4.0-81, booted on 4.4.0-78)
  • linux-headers-generic
  • linux-image-generic
  • linux-libc-dev
  • locales
  • multiarch-support

 

Hopefully this helps, I'm going to hold off updating this box for now. It does appear that if a recent update is a problem it's either libc or something in the new kernel.

Regular Member
Posts: 432
Registered: ‎02-04-2015
Kudos: 246
Solutions: 20

Re: Unifi Controller on Debian 9

[ Edited ]

I just got home and ran

 

apt update && apt upgrade

on my Debian 9 machine that has been running unifi and unifi-video for a year with no real issues (some java problems but that has been it).  Now they no longer run.

 

Here is the list of upgrades.  In brackets it shows (oldversion, newversion):

 

exim4-base:amd64 (4.89-2, 4.89-2+deb9u1)
linux-libc-dev:amd64 (4.9.30-2, 4.9.30-2+deb9u1) * probably unneccessary
libc6-dev:amd64 (2.24-11, 2.24-11+deb9u1) * probably unneccessary
linux-image-4.9.0-3-amd64:amd64 (4.9.30-2, 4.9.30-2+deb9u1)
libc6:amd64 (2.24-11, 2.24-11+deb9u1)
libc6:i386 (2.24-11, 2.24-11+deb9u1) * probably unnecessary
exim4-daemon-light:amd64 (4.89-2, 4.89-2+deb9u1)
locales:amd64 (2.24-11, 2.24-11+deb9u1)
libc-l10n:amd64 (2.24-11, 2.24-11+deb9u1)
libc-bin:amd64 (2.24-11, 2.24-11+deb9u1)
exim4-config:amd64 (4.89-2, 4.89-2+deb9u1)
exim4:amd64 (4.89-2, 4.89-2+deb9u1)
libc-dev-bin:amd64 (2.24-11, 2.24-11+deb9u1) * probably unneccessary
multiarch-support:amd64 (2.24-11, 2.24-11+deb9u1)

So I ran the following command to revert

 

apt install libc-dev-bin=2.24-11 libc6-dev:amd64=2.24-11 libc6:amd64=2.24-11 libc6:i386=2.24-11 linux-libc-dev:amd64=4.9.30-2 libc-bin=2.24-11 multiarch-support=2.24-11 exim4-config=4.89-2 exim4-base=4.89-2 exim4-daemon-light=4.89-2 exim4=4.89-2 libc-l10n=2.24-11 locales=2.24-11 linux-image-4.9.0-3-amd64=4.9.30-2

and now after a reboot they are working again.  Unifi hung up trying to stop but once the system rebooted all was well.

 

If you are going to run with this "workaround" for a while you should use

 

apt-mark hold libc-dev-bin=2.24-11 libc6-dev:amd64=2.24-11 libc6:amd64=2.24-11 libc6:i386=2.24-11 linux-libc-dev:amd64=4.9.30-2 libc-bin=2.24-11 multiarch-support=2.24-11 exim4-config=4.89-2 exim4-base=4.89-2 exim4-daemon-light=4.89-2 exim4=4.89-2 libc-l10n=2.24-11 locales=2.24-11 linux-image-4.9.0-3-amd64=4.9.30-2

Otherwise the next time you use "apt upgrade" they are just going to get upgraded again.  I don't think the =version is necessary with apt-mark hold but I just copied my list from my apt install command.

 

So, I'm sure by trial and error you could figure out which package it was but I am not really brave enough to do that on the off chance one package depends on another (the kernel is in there...) and the system fails to boot.  At least there is a workaround and maybe this will help troubleshooting.

 

@Aggraxis  you may be right about libc after all

 

edit: on the apt install (downgrade) and apt-mark hold listed above, this is from my machine at home which has a bunch of junk on it.   I just ran these on my machine at work and it is saying it is installing extra packages which isn't needed.  So if apt tells you it's installing stuff (should just be downgrading, it may recommend and you can ignore that) then delete those packages from my command and try again.  This is what I used at work, I removed 4 of the packages as my work machine didn't have them in the first place.  My work machine is now fixed as well.

apt install libc6:amd64=2.24-11 libc-bin=2.24-11 multiarch-support=2.24-11 exim4-config=4.89-2 exim4-base=4.89-2 exim4-daemon-light=4.89-2 exim4=4.89-2 libc-l10n=2.24-11 locales=2.24-11 linux-image-4.9.0-3-amd64=4.9.30-2

apt-mark hold libc6:amd64=2.24-11 libc-bin=2.24-11 multiarch-support=2.24-11 exim4-config=4.89-2 exim4-base=4.89-2 exim4-daemon-light=4.89-2 exim4=4.89-2 libc-l10n=2.24-11 locales=2.24-11 linux-image-4.9.0-3-amd64=4.9.30-2

 

Emerging Member
Posts: 59
Registered: ‎01-01-2016
Kudos: 34
Solutions: 3

Re: Unifi Controller on Debian 9

Awesome. I'll dig. 

 

Also, on the list of failures, I took my unifi install from 'stable' to 'testing'. My version numbers changed as follows:

 

5.4.16-9234 to 5.5.11-9464

 

Still doesn't work, but I'll look into the package holding.

Regular Member
Posts: 432
Registered: ‎02-04-2015
Kudos: 246
Solutions: 20

Re: Unifi Controller on Debian 9

[ Edited ]

@berlooI think you are right about it affecting Debian 8 Jessie as well.  I have a machine at work running unifi-video and I did today's update and restarted, sure enough it is no longer working.  I am going to cross post this to the unifi-video forums.  I only have two machines running a unifi controller and they are both on Debian 9 right now though so I can't test unifi.

 

Similarly for Debian 8 Jessie, packages upgraded:

 

multiarch-support:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10)
linux-image-3.16.0-4-amd64:amd64 (3.16.43-2, 3.16.43-2+deb8u1)
exim4-base:amd64 (4.84.2-2+deb8u3, 4.84.2-2+deb8u4)
exim4:amd64 (4.84.2-2+deb8u3, 4.84.2-2+deb8u4)
libc-bin:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10)
libc6:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10)
exim4-daemon-light:amd64 (4.84.2-2+deb8u3, 4.84.2-2+deb8u4)
exim4-config:amd64 (4.84.2-2+deb8u3, 4.84.2-2+deb8u4)
locales:amd64 (2.19-18+deb8u9, 2.19-18+deb8u10)
libffi6:amd64 (3.1-2+b2, 3.1-2+deb8u1)

temp fix:

 

apt install libc-bin=2.19-18+deb8u9 libc6:amd64=2.19-18+deb8u9 libffi6:amd64=3.1-2+b2 linux-image-3.16.0-4-amd64=3.16.43-2 multiarch-support=2.19-18+deb8u9 exim4-config=4.84.2-2+deb8u3 exim4=4.84.2-2+deb8u3 exim4-base=4.84.2-2+deb8u3 exim4-daemon-light=4.84.2-2+deb8u3 locales=2.19-18+deb8u9
apt-mark hold libc-bin libc6:amd64 libffi6:amd64 linux-image-3.16.0-4-amd64 multiarch-support exim4-config exim4 exim4-base exim4-daemon-light locales

 

and restart

 

*disclaimer* I don't know what I am doing other than this works for me to get my controllers back up and running.  I hope it works for you too.  I also hope it doesn't break anything else on your system.

 

Also I am not 100% sure that the upgrades from today break Unifi on Debian 8.  I am sure

- they break Unifi on Debian 9

- they break Unifi Video on Debian 8

- they break Unifi Video on Debian 9

Emerging Member
Posts: 59
Registered: ‎01-01-2016
Kudos: 34
Solutions: 3

Re: Unifi Controller on Debian 9

@poisonsnak Thanks for nailing the updated package list. I'm still working through them one by one to see if I can find a culprit. Also, I linked the thread over in /r/homelab since I'm sure we're bound to see a lot of people run into this same issue. You're about to be infamous. Man Happy

Emerging Member
Posts: 59
Registered: ‎01-01-2016
Kudos: 34
Solutions: 3

Re: Unifi Controller on Debian 9

@poisonsnak  You're going to love this. It's JUST the kernel update. On top of that, I think it's being snippy with mongodb because the mongod process is just plain ornery when the updated kernel is in place. All the libc stuff, exim, etc. is fine. Tested it backwards and forwards on my Debian 9 UniFi VM. 

 

apt install linux-image-4.9.0-3-amd64:amd64=4.9.30-2 

 That one-liner fixes it after a reboot, but like you said you need to hold the old version to keep it in place after an apt upgrade. I wonder how much other stuff is broken right now as a result...

 

You may want to try just the kernel on your Debian 8 box to see if it has the same effect.

Reply