Web Console on 5.2-1 not responding anymore

Discussion in 'Proxmox VE: Installation and configuration' started by Bwalker, Sep 16, 2018.

  1. Bwalker

    Bwalker New Member

    Joined:
    Mar 22, 2017
    Messages:
    25
    Likes Received:
    0
    I have had a community version running for couple months now (may)

    pve-manager/5.2-1/0fcd7879 (running kernel: 4.15.17-1-pve)

    All of a sudden the Web Console just times out when it worked fine for months

    All the guest VMs are running and work,
    I can ssh into the server as root and run all commands
    Logs show nothing, no errors

    All services are ACTIVE RUNNING such as
    pveproxy.service - PVE API Proxy Server
    Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
    Active: active (running) since Sat 2018-09-15 22:09:02 PDT; 34min ago

    And I have restarted proxy,daemon and statd with no issues.

    The PVE manager I didn't restart it doesn't have a restart option

    root@delltower1:~# systemctl status pve-manager.service
    ? pve-guests.service - PVE guests
    Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
    Active: active (exited) since Thu 2018-05-17 22:28:24 PDT; 3 months 29 days ago
    Main PID: 3616 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 6144)
    Memory: 0B
    CPU: 0
    CGroup: /system.slice/pve-guests.service

    It appears too be up and listening

    pveproxy 26750 www-data 6u IPv4 151374159 0t0 TCP *:8006 (LISTEN)
    pveproxy 26753 www-data 6u IPv4 151374159 0t0 TCP *:8006 (LISTEN)
    pveproxy 26754 www-data 6u IPv4 151374159 0t0 TCP *:8006 (LISTEN)
    pveproxy 26755 www-data 6u IPv4 151374159 0t0 TCP *:8006 (LISTEN)

    I do not have a firewall or anything blocking it.

    What can possible be wrong? I don't really want to reboot the whole server and all the VMs if I don't have to.
     
  2. Bwalker

    Bwalker New Member

    Joined:
    Mar 22, 2017
    Messages:
    25
    Likes Received:
    0
    Solved it seems the second NIC in the server created a route to no where, used ip link down and its fixed. Seemed to happen after it did a

    update package database? not sure that's last thing in the logs
     
  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