[SOLVED] Container Starten nicht mehr ?

[ralph hinrichs]

Hallo allerseits,

ich habe ein Problem eigentlich sogar 2.

1 Wenn ich Proxmox über das Webinterface Aktualisieren möchte bekomme ich immer diese Nachricht.

E: Some index files failed to download. They have been ignored, or old ones used instead.
TASK ERROR: command 'apt-get update' failed: exit code 100

Ich habe es dann immer per ssh mit

apt-get update && apt-get upgrade gemacht lief bisher auch ohne Probleme. Nun aber wollen nach dem letzten update die Container nicht mehr starten :-(

Folgene Fehler Meldungen habe ich

systemctl status lxc@100.service

● lxc@100.service - LXC Container: 100
   Loaded: loaded (/lib/systemd/system/lxc@.service; disabled; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/lxc@.service.d
           └─pve-reboot.conf
   Active: failed (Result: exit-code) since Thu 2018-04-05 00:15:43 CEST; 4min 19s ago
     Docs: man:lxc-start
           man:lxc
  Process: 3269 ExecStart=/usr/bin/lxc-start -n 100 (code=exited, status=1/FAILURE)

Apr 05 00:15:38 st systemd[1]: Starting LXC Container: 100...
Apr 05 00:15:43 st lxc-start[3269]: lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
Apr 05 00:15:43 st lxc-start[3269]: lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
Apr 05 00:15:43 st lxc-start[3269]: lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --lo
Apr 05 00:15:43 st systemd[1]: lxc@100.service: Control process exited, code=exited status=1
Apr 05 00:15:43 st systemd[1]: Failed to start LXC Container: 100.
Apr 05 00:15:43 st systemd[1]: lxc@100.service: Unit entered failed state.
Apr 05 00:15:43 st systemd[1]: lxc@100.service: Failed with result 'exit-code'.

journalctl -xe

Apr 05 00:19:01 st systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd

--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Apr 05 00:20:00 st systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd

--
-- Unit pvesr.service has begun starting up.
Apr 05 00:20:01 st systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd

--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Apr 05 00:20:22 st smartd[649]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 144 to 148

pveversion -v

proxmox-ve: 5.0-15 (running kernel: 4.10.15-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.15-1-pve: 4.10.15-15
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-10
qemu-server: 5.0-12
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-6
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-1
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

Vielleicht kann mir ja jemand Helfen würde mich sehr freuen.

LG

 

[ralph hinrichs]

Habe es selber hin bekommen es lag an fehlenden Repos. https://pve.proxmox.com/wiki/Package_Repositories

 

[TechLineX]

Welche Repos wurden eingespielt?

 

[ralph hinrichs]

Siehe Link im Beitrag Nummer 2.