NethServer 7 RC2 crashes when I install / uninstall module or update system

Even reboot it works.
Failed to start Activation of org.freedesktop.systemd1 time out
See system logs and ‘systemctl status’ for details.
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.

The system was low memory and some processes were killed randomly. Crtl Alt Canc? Power reset?

I will brutally off the machine from the power button.
Ctrl Alt Del did not work.

I think you’re experiencing hardware problem:

  • your machine doesn’t have enough RAM + swap
  • IMHO you should check your RAM status

@davidep how can I check if the update has been successful?

Versione sistema
NethServer release 7.3.1611 (rc3)
Versione kernel

Modello CPU
2 x Intel® Xeon® CPU W3503 @ 2.40GHz

1730 / 5960 MB
Memoria libera
4230 MB

0 / 6016 MB
Swap libero
6016 MB

@giacomo believe that these resources are not enough?

I don’t believe it’s a ram shortage. I think you hit the nethserver-directory bug or similar during uninstall.

Follow rc3 release notes to fix the DPI module without Lt kernel

Not at all! :open_mouth:
But you surely have memory problems.

As first step, reboot the system with the new kernel and remove the kernel-lt.
Then try to list all memory hungry process (I’d check clamd as first).

less /etc/sysconfig/kernel

# ================= DO NOT MODIFY THIS FILE =================
# Manual changes will be lost when this file is regenerated.
# Please read the developer's guide, which is available
# at
# original work from
# Copyright (C) 2013 Nethesis S.r.l.
# -
# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default

# DEFAULTKERNEL specifies the default kernel package type

I successfully changed the /etc/sysconfig/kernel?

if you give me an ok, I proceed with yum reinstall grubby -y

That line must be removed


I followed your directions, backed reinstall the grubby.

Now how can I check if the upgrade was successful, and the installed modules are working properly?

Although the process of installation is not completed in a linear way, I still have to perform signal-event nethserver-sssd-save?

Doing it one more time does not harm… Yes, do it.

Log in on server-manager: if dashboard, user and groups show correctly I’d say you’re ok.

Check the kernel version in dashboard is 3 (no more lt).

Test also login on roundcubemail.

I launched the command signal-event nethserver-sssd-save, but no signs of life.

Again finding of saturation problems of RAM and SWAP. In the dashboard screen is visible memory saturation and the kernel version

Open a shell and type

chmod -x /etc/e-smith/events/actions/nethserver-directory-sssd

Let’s see if it stabilizes before starting to kill processes…

BTW your kernel is still LT! You must boot with the upstream kernel.

1 Like

ok! RAM was almost completely free, idem for swap.

I also relaunched signal-event nethserver sssd-save and this time it was successful.

Now it’s hard for me to reboot remotely and select the right kernel.
I do not know ways to do it.

The grubby command you issued above should select it automatically but it seems it didn’t work!

which kernel is the right one?

   # grep '^menuentry' /boot/grub2/grub.cfg
    menuentry 'CentOS Linux (4.4.22-1.el7.elrepo.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.el7.x86_64-advanced-a260fbcd-cb7b-4a08-8c24-0c300d78e506' {
    menuentry 'CentOS Linux (3.10.0-514.2.2.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.el7.x86_64-advanced-a260fbcd-cb7b-4a08-8c24-0c300d78e506' {
    menuentry 'CentOS Linux (3.10.0-327.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.el7.x86_64-advanced-a260fbcd-cb7b-4a08-8c24-0c300d78e506' {
    menuentry 'CentOS Linux (0-rescue-87dba42dfea045a9a4bcda15160cfb11) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-87dba42dfea045a9a4bcda15160cfb11-advanced-a260fbcd-cb7b-4a08-8c24-0c300d78e506' {

Second one:

1 Like

Since you didn’t fix the grubby template before the update, you now need to set the default kernel by hand.


grubby --set-default /boot/vmlinuz-3.10.0-514.2.2.el7.x86_64

Then reboot the machine. After the reboot, remove the lt kernel:

yum remove kernel-lt

More info:


@giacomo thanks! I managed to remove the kernel-lt and set the right kernel


We are testing a package that seems to fix your high load problem: do you want to help us?

Please install it by typing at the command line

yum --enablerepo=nethserver-testing update nethserver-directory

… and let’s see if the issue comes back!