resolved

  1. M

    <span>nodename</span> showing up in front of everything

    we ran into a weird issue. when we came in this morning and checked our main cluster node, we get <span> in front of everything in the GUI. reset browser cache and still there. tried apt reset via shell and still no go. anyone ever run into this before?
  2. M

    VE_9.0.1 Fiber Channel only 1 of 3 hosts see the storage as active. Status Unknown

    After following 10 different articles including 5 from this site I got 1 node to successfully accept the new FC storage. the other 2 show it there but with a status unknown. when checking the services it says the storage (5T size) is inactive. Strange thing is on the working node, we moved a...
  3. B

    PVE to PBS

    For some reason I can’t get my pve to authenticate my pbs. I have tried any and everything except the right thing I presume. Its on the same bare metal to test then I plan to move it to its on bare metal. Do I have to have PBS on separate bare metal for PBS to work properly? I’ve been trying to...
  4. K

    [SOLVED] [Solved]EDAC MCO: ### error on cpu 1

    Can someone help point me in the direction of what this error might be created by as I think this is what is causing my vm instability
  5. P

    [SOLVED] dont have access to gui and command line

    hi i have no access to gui and also command line but vm are working good this is my log what can cause this issue!? root@m3784:~# systemctl status pvestatd.service ● pvestatd.service - PVE Status Daemon Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled) Active: failed...
  6. L

    [SOLVED] proxmox failed to start after reboot

    my proxmox web interface failed to start after reboot. i ran a systemctl status pveproxy.service and here is the log. root@odc-host1:~# systemctl status pveproxy.service ● pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset...
  7. C

    [SOLVED] cfs lock 'domain-ha' timeout & master old timestamp

    Hey guys ! We're having 2 issues on our cluster, who are likely to be related. Since a few hours, most of our HA task fails, with the error 'update resource failed: error with cfs lock 'domain-ha': got lock request timeout', and our ha-manager reports that the master is old timestamp - dead...