Ich bin leider nicht gemerkt, dass in einem Container der Stable Eintrag in der source.list war.
Nun habe ich ein Upgrade auf Stretch gemacht, leider ohne vorher zu testen.
Mc Murphy hat natürlich zugeschlagen- sieh Protokoll
Wie kann ich den Container mounten, wenn er nicht läuft, bzw den Fehler der aufgetreten ist beheben?
Nun habe ich ein Upgrade auf Stretch gemacht, leider ohne vorher zu testen.
Mc Murphy hat natürlich zugeschlagen- sieh Protokoll
Wie kann ich den Container mounten, wenn er nicht läuft, bzw den Fehler der aufgetreten ist beheben?
Code:
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Apr 20 09:00:01 srv2.myrootserver.de CRON[4027]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 20 09:00:01 srv2.myrootserver.de CRON[4028]: (root) CMD (/root/adaptec/status.sh)
Apr 20 09:00:03 srv2.myrootserver.de CRON[4027]: pam_unix(cron:session): session closed for user root
Apr 20 09:00:35 srv2.myrootserver.de pct[13950]: <root@pam> starting task UPID:srv2:00003682:01BF0502:5AD99013:vzstart:501:root@pam:
Apr 20 09:00:35 srv2.myrootserver.de pct[13954]: starting CT 501: UPID:srv2:00003682:01BF0502:5AD99013:vzstart:501:root@pam:
Apr 20 09:00:35 srv2.myrootserver.de systemd[1]: Starting PVE LXC Container: 501...
-- Subject: Unit [EMAIL]pve-container@501.service[/EMAIL] has begun start-up
-- Defined-By: systemd
-- Support: [URL]https://www.debian.org/support[/URL]
--
-- Unit [EMAIL]pve-container@501.service[/EMAIL] has begun starting up.
Apr 20 09:00:36 srv2.myrootserver.de kernel: EXT4-fs (loop4): mounted filesystem with ordered data mode. Opts: (null)
[B]Apr 20 09:00:36 srv2.myrootserver.de kernel: IPv6: ADDRCONF(NETDEV_UP): veth501i0: link is not ready
Apr 20 09:00:36 srv2.myrootserver.de systemd-udevd[13981]: Could not generate persistent MAC address for vethD2VAAJ: No such file or directory
Apr 20 09:00:36 srv2.myrootserver.de kernel: vmbr111: port 1(veth501i0) entered blocking state
Apr 20 09:00:36 srv2.myrootserver.de kernel: vmbr111: port 1(veth501i0) entered disabled state[/B]
Apr 20 09:00:36 srv2.myrootserver.de kernel: device veth501i0 entered promiscuous mode
Apr 20 09:00:36 srv2.myrootserver.de kernel: eth0: renamed from vethD2VAAJ
Apr 20 09:00:36 srv2.myrootserver.de lxc-start[13956]: lxc-start: 501: lxccontainer.c: wait_on_daemonized_start: 760 Received container state "STOPPING" instead of "RUNNING
Apr 20 09:00:36 srv2.myrootserver.de lxc-start[13956]: lxc-start: 501: tools/lxc_start.c: main: 371 The container failed to start.
Apr 20 09:00:36 srv2.myrootserver.de lxc-start[13956]: lxc-start: 501: tools/lxc_start.c: main: 373 To get more details, run the container in foreground mode.
Apr 20 09:00:36 srv2.myrootserver.de lxc-start[13956]: lxc-start: 501: tools/lxc_start.c: main: 375 Additional information can be obtained by setting the --logfile and --lo
Apr 20 09:00:36 srv2.myrootserver.de systemd[1]: [EMAIL]pve-container@501.service[/EMAIL]: Control process exited, code=exited status=1
Apr 20 09:00:36 srv2.myrootserver.de systemd[1]: [EMAIL]pve-container@501.service[/EMAIL]: Killing process 13958 (lxc-start) with signal SIGKILL.
Apr 20 09:00:36 srv2.myrootserver.de systemd[1]: Failed to start PVE LXC Container: 501.
-
[\code]