Search results

  1. A

    Proxmox VE40 incompatible with HP Proliant Servers...

    Hi Manu, Yes :( * HP Proliant DL320 G6 install and run fine. But strange and random hangs with this ILO LOG: * HP Proliant 320 G8 we had no hpwdt issues. Installation and runtime fine. * HP Proliant DL350 G7 no hpwdt issues and installation & runtime fine. * HP Proliant DL350 G8 we had...
  2. A

    Proxmox VE40 incompatible with HP Proliant Servers...

    Hi Manu! I'm very sorry, but we needed the cluster running and we have ended downgrading all the nodes to Proxmox 3.4 and recreating the cluster, where everything runs smoothly :(. So that machine is not available now :( If you want I can test with a Proliant 320 G6, which theoretically was...
  3. A

    [solved]HP proliant Randoms reboots

    Re: HP proliant Randoms reboots Hi, Maybe it is a DL385 G8? I've ended up coming back to 3.4... where all is working perfectly with all kind of HP Proliants (DL320 G6, G8 and DL385 G8) without hpwdt issues and without 420i controller issues too :(
  4. A

    Issues in cluster on Proxmox v4

    Hi again! An update... tailing the nodes log i've found this: Dec 1 11:41:42 eimtvm4 pveproxy[111354]: ipcc_send_rec failed: Transport endpoint is not connected Maybe the cause?
  5. A

    Issues in cluster on Proxmox v4

    Hi, Thanks dietmar. I discard switch issues (I've grouped proxmox nodes into a snopping group. But problem persists!! I've been debugging a bit more... * I connect to node 1 via UI * I browse node 3 via UI (*connected via node 1*) * Then it throws me out the UI... as usual...:( * In node 1...
  6. A

    Issues in cluster on Proxmox v4

    Hi, I have exactly the same issues that erk :( I checked Switch (Dlink 1510) and IGMP Snooping was disabled. I enabled it, and also enabled querier. But results are the same :( BTW, in Proxmox multicast documentation (http://pve.proxmox.com/wiki/Multicast_notes#Testing_multicast), It says...
  7. A

    Issues in cluster on Proxmox v4

    Hi erk! This is windows-style and prefer to avoid it :( (If it's not working and you don't know why: REINSTALL) I'll review multicast issues (maybe switch is blocking it?) but If final solution is to reinstall all nodes I think we will end up with a clean pure-KVM scheme... Thank you!
  8. A

    Issues in cluster on Proxmox v4

    Hi! I discard network problem, since cluster was running smoothly with 3.5 (and with 4.0 at the begining). The most weird is that via mobile UI the behavior is the same: it disconnects me and throw me back to login after few seconds after logging in. VMs are running without problem...
  9. A

    Issues in cluster on Proxmox v4

    Hi dietmar! Thanks. I made a little script to run a process in every node of the cluster. I ran a timedatctl and every node has the date/time correct and sincronized. BTW: Now I can't access one of the nodes via UI at all. The error that throws is: Secure Connection Failed The connection...
  10. A

    Issues in cluster on Proxmox v4

    I will add that I've had some issues related to the famous hpwdt watchdog module and HP Proliants... But I've blacklisted it on all the nodes. Thanks again,
  11. A

    Issues in cluster on Proxmox v4

    Hi! In our labs we had 5 Proxmox nodes since this summer. Version 3.5 was all gone right (without any kind of problem). This last month we are migrating the cluster to Proxmox v4 and issues have appeared :( Suddently "Permission denied - invalid ticket 401" appears while browsing the UI, and...
  12. A

    VE 4.0 Kernel Panic on HP Proliant servers

    Hi,Same issue here with a DL320 G6. Blacklisted module and (by the moment) all is working fine.I think that I will blacklist this module in all our Proliants...Thanks!
  13. A

    Proxmox VE40 incompatible with HP Proliant Servers...

    Hi! We are having the same issue in a DL385 G8 :( As says p1v12002, the Proxmox installation hangs with fans at 100%. Later I tried to boot with kernel args "iommu=soft nmi_watchdog=0" and it boots correctly, but it get stuck at 0% when partitioning. In a fresh Debian 8, everything is OK. If...