systemd

  1. R

    Upgrade LXC 16.04 -> 18.04 probleme

    Hallo zusammen, ich habe meinen Ubuntu Container nun von 16.04 auf 18.04 upgedatet. Alles hat bisher geklappt nun erhalte ich jedoch Probleme: Failed to attach 321 to compat systemd cgroup /system.slice/nginx.service: No such file or directory Im Internet ist etwas zu Berechtigungen zu finden...
  2. A

    [SOLVED] LXC unprivileged Fedora 27 systemctl: Failed to connect to bus: No such file or directory

    Hello, recently, after upgrading both the container (unprivileged Fedora 27, although changing it to privileged doesn't change anything) and the host system, I can't get systemctl to work anymore in the container. Whenever I try to call it I get the error message:"Failed to connect to bus: No...
  3. P

    [SOLVED] Unit file order to mount from client container

    I'll start out acknowledging that some will think this is nuts and people will respond with "Why?". The answer, It's what I've got to work with; so given that... PVE 5.2-5 Node 100 is a virtual machine running FreeNAS with PCI passthrough (This part is working great BTW) Other nodes are...
  4. L

    Wiki improvement: Web Interface via Nginx Proxy

    Hi, I propose that these lines are added to the article here in order to fix the boot order of the services. Otherwise nginx won't come up correctly after reboot because the certificate files are not available before pve-cluster service was started. sed -i...
  5. L

    Reinstalled node doesn't start osd's after reboot

    After getting the node up and running again (https://forum.proxmox.com/threads/it-seemed-failed-disks-prevent-proxmox-from-booting-but-it-was-actually-noapic-that-was-needed.43720/) I now have a problem that has been reported a few time elsewhere, but not in the systemd based version of Proxmox...
  6. D

    Predictable network interface names broken in 4.13.13-6-pve (4.13.13-41)

    Hi guys ! I had a 2 node cluster with 4.13.13-6-pve (4.13.13-41) and 4.13.13-5-pve (4.13.13-36). Hardware is - HP DL360G7 with Broadcom NetXtreme II 4 ports integrated network card. After upgrade one node from 4.13.13-36 to 4.13.13-41 all ethernet interfaces names changed from enp3s0f0 to eth0...
  7. fireon

    [SOLVED] Linux VM's hangs on reboot - on different server and different Linux OS's in VM's

    Hello, pve-manager/5.1-36/131401db (running kernel: 4.13.4-1-pve) since 5.1 we have the problem that linuxvm's, we are useing Ubuntu 16.04 and CentOS7, hanging at some reboot. We noticed that at the automaticly reboots after the unattended upgrades. After that i've done manualy some reboots...
  8. A

    [SOLVED] LXC container with Centos 7 - systemd using 100% of CPU

    Hi, I've setup an LXC container (no protection, not unprivileged) with Centos 7 on proxmox 4.4-1/eb2d6f1e. Randonmly, from time to time, systemd is using 100% of the CPU. This creates major timeouts for all services running on this LXC container. The only way to get around this is to restart...
  9. R

    systemd Cannot add dependency job for unit cgmanager.service and display-manager.service

    systemd Cannot add dependency job for unit cgmanager.service and display-manager.service Hi, upgrade to the new Virtual Environment 4.4-12/e71b7a74 version and noticed those fail warnings in the system log, should I be worried of those? Not sure if those exists in the old version. [...
  10. K

    Upgrade issue

    I wanted to just run a simple upgrade via apt-get but I'm met with the following: root@srv88:/home/k0nsl# apt-get update && apt-get upgrade Ign http://ftp.debian.org jessie InRelease Ign http://download.proxmox.com jessie InRelease Get:1 http://ftp.debian.org jessie Release.gpg [2,373 B] Get:2...
  11. F

    ISCSI Multipath does not create mapper devices during boot

    i want to use my iscsi target as volumegroup using multipath i configured multipath and "systemctl status multipath-tools" says "active (running)" but will not create the /dev/mapper/ devices i "fixed" it by adding "systemctl restart open-iscsi.service" in the rc.local how can i be sure that...
  12. K

    Constant "Stop job running for LSB" on reboot

    I have some issues where I cannot perform a graceful reboot of my PVE4.3 node. Sometimes I get "Stop job running for PVE Manager" but that becuase of stuck VM's. What is more annoiying is the stop job running for LSB - with no limit. I need to hard reboot it via IPMI to get around. I get some...
  13. D

    systemd and debian jessie template

    So, realized after I had setup a new lxc container from template that the debian jessie template provided does not appear to support systemd. Is there any modification I can made to the LXC container to create systemd compatibility?
  14. CTCcloud

    No networking on Startup (Systemd)

    Just installed Proxmox VE 4.0 fresh on a Dell R720 dual Octo Core 192GB Memory server with 6 Network Interface cards 2 10Gb Intel, 2 1Gb Intel, and 2 10Gb Broadcom First thing I did was to re-order the NICs via the /etc/udev/rules.d/70-persistent-net.rules file. I then re-applied the Proxmox VE...
  15. D

    Storage Controller initialisation order

    We have a 3 x Intel S2600WTTR systems where the storage controllers are initialised out of order, resulting in the discs being associated out of order: /dev/sda - disk 5 /dev/sdb - disk 6 /dev/sdc - disk 1 /dev/sdd - disk 2 /dev/sde - disk 3 /dev/sdf - disk 4 We previously addressed...
  16. T

    mysql not starting in LXC container

    Hi, i've set up a LXC container running Debian 8 along with MySQL. Everything was fine until i did a restart. Now mysql is not started automatically during boot. A manual try "service mysql start" has the following result: Job for mysql.service failed. See 'systemctl status mysql.service' and...
  17. A

    Multiple SystemD errors during startup after upgrade from PVE 3.4

    Hello list, I've upgraded a standalone node from PVE 3.4 to 4.1 by following the guide in Wiki (https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0). Everything went smooth until the point that I restarted the node. During startup I'm getting the following message which is flooding the...
  18. L

    what would be preventing me from using systemd start/stop in my container?

    Hello, I recently configured a suse container using the "suse-13-.1-x86_64-minimal.tar.gz" template. I'm able to get the container itself running to the point where I can go in and use suse as I normally would, but I am not able to start/stop services using systemd. Whenever I attempt to do...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!