systemd

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...

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...

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...

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...

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...

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...

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. [...

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...

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...

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...

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?

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...

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...

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...

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...

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...