LXC Container wird nicht mehr gestartet !!!!

[pitti71]

Hallo,

vorweg, bin ganz Neu was Proxmox angeht. ;-)

Habe folgendes Problem: Nach einbau einer weiteren HDD werden meine bereits erstellten LXC Container nicht meher automatisch gestartet:

Fehlermelddung:

Job for pve-container@100.service failed because the control process exited with error code.
See "systemctl status pve-container@100.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@100' failed: exit code 1

Führe ich den Befehel systemctl status pve-container@100 aus kommt folgendes:

● pve-container@100.service - PVE LXC Container: 100
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-12-01 10:50:41 CET; 21s ago
Docs: man:lxc-start
man:lxc
manct
Process: 2240 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)

Dec 01 10:50:39 homecloud systemd[1]: Starting PVE LXC Container: 100...
Dec 01 10:50:41 homecloud lxc-start[2240]: lxc-start: 100: lxccontainer.c: wait_on_daemonized_start: 856 No such file or directory - Failed to receive the container sta
Dec 01 10:50:41 homecloud lxc-start[2240]: lxc-start: 100: tools/lxc_start.c: main: 330 The container failed to start
Dec 01 10:50:41 homecloud lxc-start[2240]: lxc-start: 100: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Dec 01 10:50:41 homecloud lxc-start[2240]: lxc-start: 100: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriorit
Dec 01 10:50:41 homecloud systemd[1]: pve-container@100.service: Control process exited, code=exited, status=1/FAILURE
Dec 01 10:50:41 homecloud systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Dec 01 10:50:41 homecloud systemd[1]: Failed to start PVE LXC Container: 100.

ein journalctl -xe bringt folgendes ans Licht:
An ExecStart= process belonging to unit pve-container@100.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Dec 01 10:50:41 homecloud systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pve-container@100.service has entered the 'failed' state with result 'exit-code'.
Dec 01 10:50:41 homecloud systemd[1]: Failed to start PVE LXC Container: 100.
-- Subject: A start job for unit pve-container@100.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-container@100.service has finished with a failure.
--
-- The job identifier is 482 and the job result is failed.
Dec 01 10:50:43 homecloud pvestatd[1150]: storage 'Proxmox_Backup' is not online
Dec 01 10:50:54 homecloud pvestatd[1150]: storage 'Proxmox_Backup' is not online
Dec 01 10:51:00 homecloud systemd[1]: Starting Proxmox VE replication runner...
-- Subject: A start job for unit pvesr.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has begun execution.
--
-- The job identifier is 486.
Dec 01 10:51:02 homecloud systemd[1]: pvesr.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvesr.service has successfully entered the 'dead' state.
Dec 01 10:51:02 homecloud systemd[1]: Started Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvesr.service has finished successfully.
--
-- The job identifier is 486.
Dec 01 10:51:03 homecloud pvestatd[1150]: storage 'Proxmox_Backup' is not online
Dec 01 10:51:13 homecloud pvestatd[1150]: storage 'Proxmox_Backup' is not online

was kann ich tun um dies wieder zum laufen zu bringen ? Für Hilfe wäre ich sehr dankbar !


Grüsse Torsten

 

[blubber]

Hi,

eine manuelles Starten funktioniert?

Was wurde am Storage verändert?

Dec 01 10:51:03 homecloud pvestatd[1150]: storage 'Proxmox_Backup' is not online
Dec 01 10:51:13 homecloud pvestatd[1150]: storage 'Proxmox_Backup' is not online

 

[pitti71]

Hi, nein ein manuelles starten funktioniert nicht. Ich habe nur eine Neue HD eingebaut und danach Neugestartet. Und dann kam die o. g. Meldung.

 

[blubber]

gib mal bitte mehr infos zu:

- Wie sieht das Storage "Proxmox_Backup" aus bzw. welche Konfiguration ist dort vorhanden.
- Was wurde mit der einzelnen HDD gemacht. Wie ist diese eingebunden, oder einfach nur eingesteckt, mehr nicht?

Was passiert, wenn die Platte wieder draußen ist, kommt das Storage wieder hoch?

Was sagt "zpool list"

 

[pitti71]

also, ich habe die HDD nur in PC eingebaut und den Server Neugestartet.
wenn die HDD wieder aus den PC entfernt ist, bleibt das selbe Problem.

Jetzt ist die HDD über ZFS eingerichtet worden.

zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
Segate 928G 1.43M 928G - - 0% 0% 1.00x ONLINE -
WDHD 2.72T 55.0G 2.67T - - 0% 1% 1.00x ONLINE -
root@homecloud:~#

"Wie sieht das Storage "Proxmox_Backup" aus bzw. welche Konfiguration ist dort vorhanden. "
Wo kann ich das finden ?

 

[pitti71]

so jetzt habe ich mal auf der Hilfe Seite von Proxmox, folgenden Befehl aus geführt:

lxc-start -n 100 -F -l DEBUG -o /tmp/100.log

und das steht dann im log:

root@homecloud:/tmp# cat 100.log
lxc-start ID 20191201133455.304 ERROR lxc_start - tools/lxc_start.c:main:290 - No container config specified
lxc-start ID 20191201133518.902 ERROR lxc_start - tools/lxc_start.c:main:290 - No container config specified
lxc-start ID 20191201133600.400 ERROR lxc_start - tools/lxc_start.c:main:290 - No container config specified
lxc-start 100 20191201133614.612 INFO confile - confile.c:set_config_idmaps:1673 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 100 20191201133614.612 INFO confile - confile.c:set_config_idmaps:1673 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 100 20191201133614.613 INFO lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:759 - Processing "reject_force_umount # comment this to allow umount -f; not recommended"
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:759 - Processing "[all]"
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:759 - Processing "kexec_load errno 1"
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:759 - Processing "open_by_handle_at errno 1"
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:937 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:946 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:956 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:966 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:759 - Processing "init_module errno 1"
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:759 - Processing "finit_module errno 1"
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:759 - Processing "delete_module errno 1"
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 100 20191201133614.613 INFO seccomp - seccomp.carse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 100 20191201133614.614 INFO seccomp - seccomp.carse_config_v2:970 - Merging compat seccomp contexts into main context
lxc-start 100 20191201133614.614 INFO conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "100", config section "lxc"
lxc-start 100 20191201133616.322 DEBUG conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 100 lxc pre-start with output: cannot open directory //WDHD/subvol-100-disk-0: No such file or directory

lxc-start 100 20191201133616.341 ERROR conf - conf.c:run_buffer:335 - Script exited with status 2
lxc-start 100 20191201133616.341 ERROR start - start.c:lxc_init:861 - Failed to run lxc.hook.pre-start for container "100"
lxc-start 100 20191201133616.342 ERROR start - start.c:__lxc_start:1944 - Failed to initialize container "100"
lxc-start 100 20191201133616.342 ERROR lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 100 20191201133616.342 ERROR lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options

 

[CoolTux]

Naja Eindeutiger geht es ja nicht. Schau mal ob Du /WDHD/ hast und ob da subvol-100-disk-0 gibt. Wobei ich das schon sehr seltsam finde. Und wenn das da ist musst Du mal schauen wieso da zwei / stehen.

 

[fiona]

also, ich habe die HDD nur in PC eingebaut und den Server Neugestartet.
wenn die HDD wieder aus den PC entfernt ist, bleibt das selbe Problem.

Jetzt ist die HDD über ZFS eingerichtet worden.

zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
Segate 928G 1.43M 928G - - 0% 0% 1.00x ONLINE -
WDHD 2.72T 55.0G 2.67T - - 0% 1% 1.00x ONLINE -
root@homecloud:~#

"Wie sieht das Storage "Proxmox_Backup" aus bzw. welche Konfiguration ist dort vorhanden. "
Wo kann ich das finden ?

Hallo,
die Konfiguration befindet sich in '/etc/pve/storage.cfg'. Könntest du diese Datei und auch die Konfiguration deines Containers hier posten (unter '/etc/pve/lxc/100.conf') und bitte auch die Ausgabe von 'pveversion -v'?