pve-bridge failed with status 256

Discussion in 'Proxmox VE (Deutsch)' started by Christian95, Sep 7, 2018.

  1. Christian95

    Christian95 New Member

    Joined:
    Sep 7, 2018
    Messages:
    4
    Likes Received:
    0
    Hallo,

    nach einem Dateisystem Fehler musste ich einen fsck durchführen, damit Proxmox wieder startete, seitdem ist es mir nicht mehr möglich die Proxmox KVM Server mit dem Netzwerk zu starten. Entferne ich das Netzwerk aus den VMs starten diese wieder.

    Es sieht nach einem Fehler mit der Bridge aus, jedoch brachte auch ein neu anlegen der Bridge keinen Erfolg.

    Der Fehler:
    Code:
    kvm: -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown: network script /var/lib/qemu-server/pve-bridge failed with status 256
    TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=f1ef1106-b7ac-4c18-8ea9-616896374130' -name vm100 -smp '5,sockets=1,cores=5,maxcpus=5' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/100.vnc,x509,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce' -m 16384 -k de -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:4831d23f3674' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/data2/vm-100-disk-1,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-drive,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'vmxnet3,mac=FE:88:1C:8A:43:76,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1
     
  2. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,792
    Likes Received:
    251
    you can check that the files of that package are OK with
    Code:
    debsums qemu-server
    
    if not you can reinstall it with:

    Code:
    apt install --reinstall qemu-server
    
    sry, nochmal auf deutsch:

    überprüfen ob die files vom qemu-server package OK sind
    Code:
    debsums qemu-serveer
    
    wenn nicht, kann man das paket nochmal installieren mit:
    Code:
    apt install --reinstall qemu-server
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Christian95

    Christian95 New Member

    Joined:
    Sep 7, 2018
    Messages:
    4
    Likes Received:
    0

    Da scheint wohl etwas gewaltig schief zu laufen:

    Code:
    root@***:~# debsums qemu-server
    Cannot find md5sums path for qemu-server
    
    
    Edit:

    Neuinstallation klappt hier auch nicht:

    Code:
    root@***:~# apt install --reinstall qemu-server
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Reinstallation of qemu-server is not possible, it cannot be downloaded.
     
  4. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,792
    Likes Received:
    251
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Christian95

    Christian95 New Member

    Joined:
    Sep 7, 2018
    Messages:
    4
    Likes Received:
    0
    Es gab einen Stromausfall im Rechenzentrum .. dann wollte Proxmox wegen einem defekten Dateisystem nicht mehr starten, also wurde ein fsck ausgeführt, danach kam dann das Problem, vor dem Stromausfall und plötzlichen Neustart starteten die Server ja ohne Problem.
     
  6. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    2,792
    Likes Received:
    251
    ich hab das eher wegen dem debsums und reinstall gemeint ..
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Christian95

    Christian95 New Member

    Joined:
    Sep 7, 2018
    Messages:
    4
    Likes Received:
    0
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice