Hi, I have some strange issue with containers.
systemd is not running on containers after proxmox reboots.
This is my setup:
I created all my containers with template debian 8.0 (version 8.4-1)
and then I replaced sysv with systemd (installed systemd and systemd-sysv packages)
Also I have all containers configured not to start on boot,
so If I reboot proxmox server containers will not start (I have to do it manually and this is what I want)
Issue:
For example, my 112 container has a tomcat8 and postgresql database.
after proxmox reboot I have to start manually with pct start 112.
Container is running (as I see it with pct list and can enter with pct enter 112)
but I can't ssh into it and any other services aren't running.
If I enter into container and run systemctl status tomcat8 is enabled but inactive, so running systemctl start tomcat8 it hangs forever and I can cancel with Control+C
If I reboot container all comes to normal.
That's very strange. Same happens with other containers: LAMP, OpenVPN, Munin, etc.
Seems that systemd can't start services (but rebooting containers from inside solves this issue)
I don't know where to start looking as journactl -b (on proxmox and containers) doesn't show relevant information.
My network is IPv4 and all containers have static IP, IPv6 is configured as dynamic and I do see errors on journal (dhclient fails). Should I disable IPv6??
Any hint/help will be appreciated. Thanks
systemd is not running on containers after proxmox reboots.
This is my setup:
Code:
# uname -a
Linux proxmox 4.4.13-2-pve #1 SMP Fri Jul 15 06:36:47 CEST 2016 x86_64 GNU/Linux
# pveversion --verbose
proxmox-ve: 4.2-58 (running kernel: 4.4.13-2-pve)
pve-manager: 4.2-17 (running version: 4.2-17/e1400248)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.4.13-2-pve: 4.4.13-58
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-43
qemu-server: 4.0-85
pve-firmware: 1.1-8
libpve-common-perl: 4.0-71
libpve-access-control: 4.0-18
libpve-storage-perl: 4.0-56
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6-1
pve-container: 1.0-71
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
fence-agents-pve: not correctly installedI created all my containers with template debian 8.0 (version 8.4-1)
and then I replaced sysv with systemd (installed systemd and systemd-sysv packages)
Also I have all containers configured not to start on boot,
so If I reboot proxmox server containers will not start (I have to do it manually and this is what I want)
Issue:
For example, my 112 container has a tomcat8 and postgresql database.
after proxmox reboot I have to start manually with pct start 112.
Container is running (as I see it with pct list and can enter with pct enter 112)
but I can't ssh into it and any other services aren't running.
If I enter into container and run systemctl status tomcat8 is enabled but inactive, so running systemctl start tomcat8 it hangs forever and I can cancel with Control+C
If I reboot container all comes to normal.
That's very strange. Same happens with other containers: LAMP, OpenVPN, Munin, etc.
Seems that systemd can't start services (but rebooting containers from inside solves this issue)
I don't know where to start looking as journactl -b (on proxmox and containers) doesn't show relevant information.
My network is IPv4 and all containers have static IP, IPv6 is configured as dynamic and I do see errors on journal (dhclient fails). Should I disable IPv6??
Any hint/help will be appreciated. Thanks
