Hello,
I need some help to solve this issue...
I've a LXC container (PLEX) that fail to start,after a restore:
today I decided to restore a backup made the 1th of August (Mode = Stop)
immediately before the restore, just to be sure, also another backup was also made in order to have the possibility to come back to the current situation.
the 1th August backup restored, didn't start (errors above)
At this point I tried also to come back with the latest backup, made 15 minutes before doing anything..and also this backup fail with the same errors.
from the log file i get:
Some addittional information:
1) the Plex container is Debian, unprivileged, and was made with a script (https://tteck.github.io/Proxmox/#plex-media-server-lxc).
was running correctly, and in these days I rebooted the container many times without any issues.
there are two mount point (mp0,mp1), smb folder binded through the host to the container, that seems to work correctly as usual (still now are correctly mounted by the host).
2)proxmox was updated with the latest kernel the 1th of August. Not sure if the 1th August update was made before or after the Backup of the container, in any case the previous update dates back to a few days earlier.
3) there is one thing, that I din't say yet, that maybe is not important, but maybe it is...
the first backup was made with the container without VLAN, running on the main subnet 192.168.1.x
few days ago, i moved the container on another VLAN (113), on subnet 192.168.113.x....everything was working correctly.
So when today I made the restore (for PLEX database reason), before to start the container, in order to get things working (new firewall rules for VLAN 113, static IP from the router,etc) I had to change manually again the VLAN, DNS,etc moving to vlan/subnet 113. then I started the container but the container didn't start...
I tried to launch the container inside the previous VLAN/subnet but still errors...
so my fear was that due to the different vlan the restore can have some problems....so I loaded the last backup, that was made with the correct VLAN 113 with the hope that things come back to work....but same problem....
So or VLAN/Network subnet is not the problem, or something was broken and things didn't work also coming back with last working configuration...
--------------------------------------
I need some help to solve this, I'm learning to use proxmox and linux, so I'm not yet an expert.
thank you
I need some help to solve this issue...
I've a LXC container (PLEX) that fail to start,after a restore:
Code:
run_buffer: 571 Script exited with status 255
lxc_init: 845 Failed to run lxc.hook.pre-start for container "151"
__lxc_start: 2034 Failed to initialize container "151"
TASK ERROR: startup for container '151' failedtoday I decided to restore a backup made the 1th of August (Mode = Stop)
immediately before the restore, just to be sure, also another backup was also made in order to have the possibility to come back to the current situation.
the 1th August backup restored, didn't start (errors above)
At this point I tried also to come back with the latest backup, made 15 minutes before doing anything..and also this backup fail with the same errors.
from the log file i get:
Code:
lxc-start 151 20240812173921.748 INFO confile - ../src/lxc/confile.c:set_config_idmaps:2273 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 151 20240812173921.748 INFO confile - ../src/lxc/confile.c:set_config_idmaps:2273 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 151 20240812173921.751 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 151 20240812173921.752 INFO utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "1>
lxc-start 151 20240812174004.552 DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 151 lxc pre-start produced o>
dmesg(1) may have more information after failed mount system call.
lxc-start 151 20240812174004.565 DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 151 lxc pre-start produced o>
lxc-start 151 20240812174004.582 ERROR utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 255
lxc-start 151 20240812174004.582 ERROR start - ../src/lxc/start.c:lxc_init:845 - Failed to run lxc.hook.pre-start for container "151"
lxc-start 151 20240812174004.582 ERROR start - ../src/lxc/start.c:__lxc_start:2034 - Failed to initialize container "151"
lxc-start 151 20240812174004.582 INFO utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "151", confi>
lxc-start 151 20240812174005.842 INFO utils - ../src/lxc/utils.c:run_script_argv:587 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "1>
lxc-start 151 20240812174005.671 DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 151 lxc post-stop produced o>
lxc-start 151 20240812174005.671 DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 151 lxc post-stop produced o>
lxc-start 151 20240812174005.685 ERROR utils - ../src/lxc/utils.c:run_buffer:571 - Script exited with status 1
lxc-start 151 20240812174005.685 ERROR start - ../src/lxc/start.c:lxc_end:986 - Failed to run lxc.hook.post-stop for container "151"
lxc-start 151 20240812174005.685 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:lxc_start_main:307 - The container failed to start
lxc-start 151 20240812174005.685 ERROR lxc_start - ../src/lxc/tools/lxc_start.c:lxc_start_main:312 - Additional information can be obtained by setting the --logfile a>Some addittional information:
1) the Plex container is Debian, unprivileged, and was made with a script (https://tteck.github.io/Proxmox/#plex-media-server-lxc).
was running correctly, and in these days I rebooted the container many times without any issues.
there are two mount point (mp0,mp1), smb folder binded through the host to the container, that seems to work correctly as usual (still now are correctly mounted by the host).
2)proxmox was updated with the latest kernel the 1th of August. Not sure if the 1th August update was made before or after the Backup of the container, in any case the previous update dates back to a few days earlier.
3) there is one thing, that I din't say yet, that maybe is not important, but maybe it is...
the first backup was made with the container without VLAN, running on the main subnet 192.168.1.x
few days ago, i moved the container on another VLAN (113), on subnet 192.168.113.x....everything was working correctly.
So when today I made the restore (for PLEX database reason), before to start the container, in order to get things working (new firewall rules for VLAN 113, static IP from the router,etc) I had to change manually again the VLAN, DNS,etc moving to vlan/subnet 113. then I started the container but the container didn't start...
I tried to launch the container inside the previous VLAN/subnet but still errors...
so my fear was that due to the different vlan the restore can have some problems....so I loaded the last backup, that was made with the correct VLAN 113 with the hope that things come back to work....but same problem....
So or VLAN/Network subnet is not the problem, or something was broken and things didn't work also coming back with last working configuration...
--------------------------------------
I need some help to solve this, I'm learning to use proxmox and linux, so I'm not yet an expert.
thank you
Last edited: