On boot container don't start apache and mysql

[henri]

Hi all,

I just upgrade my container from debian 8 to debian 9 and now when I restart the container with the button "shutdown" and after "start" from the proxmox interface the container start but the apache and mysql service need to be start by command line.

root@host4-vm106:~# cat /etc/debian_version
9.5

proxmox-ve: 4.4-112 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-24 (running version: 4.4-24/08ba4d2d)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.4.134-1-pve: 4.4.134-112
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+2
libqb0: 1.0.1-1
pve-cluster: 4.0-55
qemu-server: 4.0-115
pve-firmware: 1.1-12
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.9.1-9~pve4
pve-container: 1.0-106
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u4
lxc-pve: 2.0.7-4
lxcfs: 2.0.8-2~pve4
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

Any help on this?
Thanks

 

[fireon]

Looks likes an old version. Have you read the wiki about? https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0

 

[henri]

Yes I know that I make some test before upgrading proxmox so I test the container update debian 8 to 9 just to see if everything is fine or not like this thing

 

[henri]

Strange thing I retry the upgrade from the backup container and this time it's working

 

[t.lamprecht]

Strange thing I retry the upgrade from the backup container and this time it's working

Good to hear that everything is working, now.

A, a bit long, FYI, for readers possibly seeing this below:
If the startup of services in the container is not scheduled - but a manual start works this seems like a CT internal problem, Proxmox VE does not interferes with the services managed by the CT init service (e.g., systemd, sysvinit, openRC, ...) directly. There's a chance that through indirect interaction a newer CT systemd version and an older host systemd may have some issues, though.
Next time it'd be great if you could include the service status report of the affected ones, e.,g.: systemctl status apache mariadb (adapt service names, auto-completion may help )

Yes I know that I make some test before upgrading Proxmox so I test the container update Debian 8 to 9 just to see if everything is fine or not like this thing

Should be a test if the upgrade to Proxmox VE 5.X is fine be done with a PVE 5.X (test) host? As, in theory, a working upgrade of a CT from Debian Jessie to Stretch on PVE 4.X does not (necessarily) means that the same upgrade, or the upgraded CT works on PVE 5.X - not that this should be the case. We try hard to stay compatible in this regard, and as workaround for issues with newer CT versions are more likely included in a newer PVE which is not EOL, it could make sense to first upgrade PVE and then CTs, IMO. Ideally, such a process is tested first before doing live in production clusters.