CT Klon, Start: No container config specified

D

digidax

Renowned Member
Mar 23, 2009
99
1
73
Hallo zusammen,
ich habe mir eine Testumgebung aus zwei Hardwareknoten mit Proxmox 5.4-4 aufgesetzt.
Auf Knoten 1 eine CT erstellt. Mit dieser etwas herumgespielt, dann gestoppt. Im GUI nun mit der rechten Maustatste auf die CT und auf Klon gegangen. Als Ziel den anderen Konoten angeben und eine andere ID angeben. Der Task wurde ausgeführt und die CT erscheint im Knoten 2. Wenn ich diese nun starten will, bekomme ich den Fehler:

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

Code: 
systemctl status pve-container@1920.service
● pve-container@1920.service - PVE LXC Container: 1920
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-04-29 13:57:25 CEST; 1min 13s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 15987 ExecStart=/usr/bin/lxc-start -n 1920 (code=exited, status=1/FAILURE)

Apr 29 13:57:25 pve1 systemd[1]: Starting PVE LXC Container: 1920...
Apr 29 13:57:25 pve1 lxc-start[15987]: lxc-start: 1920: tools/lxc_start.c: main: 290 No container config specified
Apr 29 13:57:25 pve1 systemd[1]: pve-container@1920.service: Control process exited, code=exited status=1
Apr 29 13:57:25 pve1 systemd[1]: Failed to start PVE LXC Container: 1920.
Apr 29 13:57:25 pve1 systemd[1]: pve-container@1920.service: Unit entered failed state.
Apr 29 13:57:25 pve1 systemd[1]: pve-container@1920.service: Failed with result 'exit-code'.

wie kann ich den Fehler lxc-start: 1920: tools/lxc_start.c: main: 290 No container config specified weiter eingrenzen? Im GUI sind aber alle Konfigurationen vorhanden also vom Klongeber übernommen wurden. Die PVE config ist auch vorhanden:
Code: 
ls -l /etc/pve/lxc/
total 1
-rw-r--r-- 1 root www-data 374 Apr 29 14:03 1920.conf

Was mache ich falsch?
Viele Grüße, Frank
 
hmm - Wie wird versucht den Container zu starten? (über GUI?, über `systemctl`)

Funktioniert es, wenn du zuerst auf der commandline ein `pct start 1920` ausführst?

Hoffe das hilft mal weiter!
 
hab nochmal geclont und dann vom CLI des Kontens 2 `pct start 1920` ausgeführt.
Code: 
~# pct start 1920
Job for pve-container@1920.service failed because the control process exited with error code.
See "systemctl status pve-container@1920.service" and "journalctl -xe" for details.
command 'systemctl start pve-container@1920' failed: exit code 1

Code: 
~# systemctl status pve-container@1920.service
● pve-container@1920.service - PVE LXC Container: 1920
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-04-29 15:46:49 CEST; 1min 39s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 14907 ExecStart=/usr/bin/lxc-start -n 1920 (code=exited, status=1/FAILURE)

Apr 29 15:46:49 pve2 lxc-start[14907]: lxc-start: 1920: lxccontainer.c: wait_on_daemonized_start: 865 Received container state "ABORTING" instead of "RUNNING"
Apr 29 15:46:49 pve2 lxc-start[14907]: lxc-start: 1920: tools/lxc_start.c: main: 330 The container failed to start
Apr 29 15:46:49 pve2 lxc-start[14907]: lxc-start: 1920: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
Apr 29 15:46:49 pve2 lxc-start[14907]: lxc-start: 1920: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options
Apr 29 15:46:49 pve2 systemd[1]: pve-container@1920.service: Control process exited, code=exited status=1
Apr 29 15:46:49 pve2 systemd[1]: pve-container@1920.service: Killing process 14913 (3) with signal SIGKILL.
Apr 29 15:46:49 pve2 systemd[1]: pve-container@1920.service: Killing process 15048 (apparmor_parser) with signal SIGKILL.
Apr 29 15:46:49 pve2 systemd[1]: Failed to start PVE LXC Container: 1920.
Apr 29 15:46:49 pve2 systemd[1]: pve-container@1920.service: Unit entered failed state.
Apr 29 15:46:49 pve2 systemd[1]: pve-container@1920.service: Failed with result 'exit-code'.

die Fehler, dass die Konfig feht ist nun verschwunden, startet aber trotzdem nicht.
Kann ch mehr Informationen liefern?
 
here it comes:
Code: 
~# cat /tmp/lxc-1920.log
lxc-start 1920 20190429164742.600 INFO     lsm - lsm/lsm.c:lsm_init:50 - LSM security driver AppArmor
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "reject_force_umount  # comment this to allow umount -f;  not recommended"
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for reject_force_umount action 0(kill)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for reject_force_umount action 0(kill)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for reject_force_umount action 0(kill)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:do_resolve_add_rule:505 - Set seccomp rule to reject force umounts
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for reject_force_umount action 0(kill)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "[all]"
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "kexec_load errno 1"
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for kexec_load action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for kexec_load action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for kexec_load action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for kexec_load action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "open_by_handle_at errno 1"
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for open_by_handle_at action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for open_by_handle_at action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for open_by_handle_at action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for open_by_handle_at action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "init_module errno 1"
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for init_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for init_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for init_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for init_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "finit_module errno 1"
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for finit_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for finit_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for finit_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for finit_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:759 - Processing "delete_module errno 1"
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:937 - Added native rule for arch 0 for delete_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:946 - Added compat rule for arch 1073741827 for delete_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:956 - Added compat rule for arch 1073741886 for delete_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:966 - Added native rule for arch -1073741762 for delete_module action 327681(errno)
lxc-start 1920 20190429164742.600 INFO     seccomp - seccomp.c:parse_config_v2:970 - Merging compat seccomp contexts into main context
lxc-start 1920 20190429164742.600 INFO     conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "1920", config section "lxc"
lxc-start 1920 20190429164743.230 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 1920 lxc pre-start with output: storage does not support content type 'none'

lxc-start 1920 20190429164743.487 DEBUG    terminal - terminal.c:lxc_terminal_peer_default:714 - Using terminal "/dev/tty" as proxy
lxc-start 1920 20190429164743.487 DEBUG    terminal - terminal.c:lxc_terminal_signal_init:192 - Created signal fd 9
lxc-start 1920 20190429164743.487 DEBUG    terminal - terminal.c:lxc_terminal_winsz:90 - Set window size to 80 columns and 24 rows
lxc-start 1920 20190429164743.491 INFO     start - start.c:lxc_init:906 - Container "1920" is initialized
lxc-start 1920 20190429164743.492 INFO     conf - conf.c:run_script:495 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "1920", config section "net"
lxc-start 1920 20190429164744.993 DEBUG    network - network.c:instantiate_veth:206 - Instantiated veth "veth1920i0/vethX5ONP6", index is "37"
lxc-start 1920 20190429164744.100 INFO     conf - conf.c:run_script:495 - Executing script "/usr/share/lxc/lxcnetaddbr" for container "1920", config section "net"
lxc-start 1920 20190429164744.664 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/lxcnetaddbr 1920 net up veth veth1920i1 with output: bridge 'vmbr1' does not exist

lxc-start 1920 20190429164744.671 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 2
lxc-start 1920 20190429164744.706 ERROR    network - network.c:lxc_create_network_priv:2462 - Failed to create network device
lxc-start 1920 20190429164744.706 ERROR    start - start.c:lxc_spawn:1646 - Failed to create the network
lxc-start 1920 20190429164744.770 INFO     network - network.c:lxc_delete_network_priv:2599 - Removed interface "eth0" with index 37
lxc-start 1920 20190429164744.772 WARN     network - network.c:lxc_delete_network_priv:2618 - Invalid argument - Failed to remove interface "veth1920i0" from ""
lxc-start 1920 20190429164744.772 WARN     network - network.c:lxc_delete_network_priv:2594 - Operation not permitted - Failed to remove interface "eth1" with index 39
lxc-start 1920 20190429164744.773 DEBUG    network - network.c:lxc_delete_network:3185 - Deleted network devices
lxc-start 1920 20190429164744.773 ERROR    start - start.c:__lxc_start:1989 - Failed to spawn container "1920"
lxc-start 1920 20190429164744.893 INFO     conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "1920", config section "lxc"
lxc-start 1920 20190429164745.410 INFO     conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "1920", config section "lxc"
lxc-start 1920 20190429164746.342 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 1920 lxc post-stop with output: storage does not support content type 'none'

lxc-start 1920 20190429164747.369 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
lxc-start 1920 20190429164747.369 ERROR    lxc_start - tools/lxc_start.c:main:336 - Additional information can be obtained by setting the --logfile and --logpriority options

kann es sein, dass es daran liegt, dass im Container NFS genutzt wird?
eatures: mount=nfs4;nfs3;nfsd;nfs;rpc_pipefs

config des Contaners:
Code: 
arch: amd64
cores: 8
features: mount=nfs4;nfs3;nfsd;nfs;rpc_pipefs
hostname: farm11.cbr1.de
memory: 2048
net0: name=eth0,bridge=vmbr0,gw=192.168.130.254,hwaddr=56:12:08:B1:A5:7E,ip=192.168.130.192/24,type=veth
net1: name=eth1,bridge=vmbr1,hwaddr=8E:F1:EE:51:56:0C,ip=192.168.110.192/24,type=veth
ostype: centos
rootfs: pve_VMroot:1920/vm-1920-disk-1.raw,size=50G
swap: 2048
 
Ahhhh, ich Horn. Ich glaube auf der 2. Node fehlt das SAN Network und damit die 2. Bridge für den Container. Danke, ich sehe morgen gleich nach und melde mich.
 
  • Like
Reactions: CoolTux
Guten Morgen,
das Subnetz für das SAN war da, aber die 2. Bridge existierte (noch) nicht. Angelegt und der geklonte CT wurde problemlos gestartet.
@Leon Gaultier , welche Stelle gab im Debug Log des startenden CT Dir den Hinweis, dass es ein Netzwerkproblem sein könnte?

danke für Eure Hilfe.
 
Gleich der zweite Logauszug mit ERROR

lxc-start 1920 20190429164744.671 ERROR conf - conf.c:run_buffer:335 - Script exited with status 2
lxc-start 1920 20190429164744.706 ERROR network - network.c:lxc_create_network_priv:2462 - Failed to create network device
lxc-start 1920 20190429164744.706

Sorry muss mich erst in die Forumsoftware einarbeiten. Daher ohne Code oder quote tags
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back