From: "Tonči Stipičević" <tonci@suma-informatika.hr>
To: j.raats@dhzm.nl, PVE User List <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] PVE 7.2.-14 LXC boot problem
Date: Sat, 19 Nov 2022 08:44:25 +0100 [thread overview]
Message-ID: <e3e5ec83-369c-8583-f463-3c5518b9138b@suma-informatika.hr> (raw)
In-Reply-To: <0faa5905-9eec-3ecd-4a66-a6fbeb089525@dhzm.nl>
That's it ! ... Thank you
srdačan pozdrav / best regards
Tonči Stipičević, dipl. ing. elektr.
direktor / manager
SUMA Informatika d.o.o., Badalićeva 27, OIB 93926415263
Podrška / Upravljanje IT sustavima za male i srednje tvrtke
Small & Medium Business IT Support / Management
mob: 091 1234003
www.suma-informatika.hr
On 18. 11. 2022. 22:42, Jack Raats wrote:
> Logon your proxmox server and install binutils using
>
> apt install binutils
>
> That solved the problem on my proxmox server
>
> Gr.,
> Jack Raats
>
>
>
> Op 18-11-2022 om 21:23 schreef Tonči Stipičević:
>> Hello to all,
>> after today's upgrade from 7.2-11 to 7.2.14 LXC's won't boot
>>
>> run_buffer: 321 Script exited with status 2
>> lxc_init: 847 Failed to run lxc.hook.pre-start for container "109"
>> __lxc_start: 2008 Failed to initialize container "109"
>> TASK ERROR: startup for container '109' failed
>>
>> lxc-start 109 20221118200745.382 INFO confile -
>> ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type u
>> nsid 0 hostid 100000 range 65536
>> lxc-start 109 20221118200745.382 INFO confile -
>> ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type g
>> nsid 0 hostid 100000 range 65536
>> lxc-start 109 20221118200745.383 INFO lsm -
>> ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security
>> driver AppArmor
>> lxc-start 109 20221118200745.383 INFO conf -
>> ../src/lxc/conf.c:run_script_argv:337 - Executing script
>> "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "109",
>> config section "lxc"
>> lxc-start 109 20221118200747.295 DEBUG conf -
>> ../src/lxc/conf.c:run_buffer:310 - Script exec
>> /usr/share/lxc/hooks/lxc-pve-prestart-hook 109 lxc pre-start produced
>> output: objdump on /lib/systemd/systemd failed: open3: exec of
>> objdump -p /var/lib/lxc/109/rootfs/lib/systemd/systemd failed: No
>> such file or directory at /usr/share/perl5/PVE/Tools.pm line 455.
>>
>> lxc-start 109 20221118200747.321 ERROR conf -
>> ../src/lxc/conf.c:run_buffer:321 - Script exited with status 2
>> lxc-start 109 20221118200747.321 ERROR start -
>> ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start
>> for container "109"
>> lxc-start 109 20221118200747.321 ERROR start -
>> ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container
>> "109"
>> lxc-start 109 20221118200747.321 INFO conf -
>> ../src/lxc/conf.c:run_script_argv:337 - Executing script
>> "/usr/share/lxcfs/lxc.reboot.hook" for container "109", config
>> section "lxc"
>> lxc-start 109 20221118200747.827 INFO conf -
>> ../src/lxc/conf.c:run_script_argv:337 - Executing script
>> "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "109",
>> config section "lxc"
>> lxc-start 109 20221118200749.635 DEBUG conf -
>> ../src/lxc/conf.c:run_buffer:310 - Script exec
>> /usr/share/lxc/hooks/lxc-pve-poststop-hook 109 lxc post-stop produced
>> output: umount: /var/lib/lxc/.pve-staged-mounts/mp0: not mounted.
>>
>> lxc-start 109 20221118200749.636 DEBUG conf -
>> ../src/lxc/conf.c:run_buffer:310 - Script exec
>> /usr/share/lxc/hooks/lxc-pve-poststop-hook 109 lxc post-stop produced
>> output: command 'umount -- /var/lib/lxc/.pve-staged-mounts/mp0'
>> failed: exit code 32
>>
>> lxc-start 109 20221118200749.737 ERROR lxc_start -
>> ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
>> lxc-start 109 20221118200749.738 ERROR lxc_start -
>> ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be
>> obtained by setting the --logfile and --logpriority options
>>
>>
>> Host restart, restore from bck , ... nothing helps
>>
>> so take caution ....
>>
>> srdačan pozdrav / best regards
>>
>> Tonči Stipičević, dipl. ing. elektr.
>> direktor / manager
>>
>> SUMA Informatika d.o.o., Badalićeva 27, OIB 93926415263
>>
>> Podrška / Upravljanje IT sustavima za male i srednje tvrtke
>> Small & Medium Business IT Support / Management
>>
>> mob: 091 1234003
>> www.suma-informatika.hr
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2022-11-19 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8678ddf7-98ef-f87b-bb16-09ad4953804e@suma-informatika.hr>
[not found] ` <20190708201918.00ca0f22@rosa.proxmox.com>
[not found] ` <649afeba-9626-6688-7967-3ee604eea2bb@suma-informatika.hr>
2022-08-17 5:39 ` [PVE-User] Shared SAN <> ZFS concept Tonči Stipičević
[not found] ` <mailman.66.1660809003.345.pve-user@lists.proxmox.com>
2022-08-23 14:30 ` Kyle Schmitt
[not found] ` <000c2ab6-ea94-1979-57af-c2f20ba47e2a@suma-informatika.hr>
[not found] ` <0faa5905-9eec-3ecd-4a66-a6fbeb089525@dhzm.nl>
2022-11-19 7:44 ` Tonči Stipičević [this message]
2022-11-20 9:36 ` [PVE-User] password failure CFS
2022-11-20 9:41 ` Bennet Gallein
[not found] ` <4854e27d-8820-46fb-bca7-8c10f3413969@suma-informatika.hr>
2024-05-01 20:54 ` [PVE-User] 8.2.2 - limited cluster functionality Mark Schouten via pve-user
2024-05-01 20:54 ` Mark Schouten via pve-user
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3e5ec83-369c-8583-f463-3c5518b9138b@suma-informatika.hr \
--to=tonci@suma-informatika.hr \
--cc=j.raats@dhzm.nl \
--cc=pve-user@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox