[SOLVED] Web UI Not loading (Ext is not defined)

Discussion in 'Proxmox VE: Installation and configuration' started by The Chill Pilgrim, May 20, 2019.

  1. The Chill Pilgrim

    The Chill Pilgrim New Member

    Joined:
    May 20, 2019
    Messages:
    2
    Likes Received:
    0
    Recently I've updated Proxmox (apt update && apt upgrade && apt dist-upgrade) across a three node cluster (with ceph for storage), I went to access the Web UI, and received a blank page.

    Dev tools indicate an issue with loading some of the JS
    Loading failed for the <script> with source pve2/ext6/ext-all.js”.
    Ext is not defined charts.js:1:1
    /pve2/ext6/charts.js:1

    It's really strange, the same issue occurs on all three hosts, and there are no events to indicate hardware or network issues (nothing has changed)

    I've rebooted one of the hosts - no change after reboot on web ui issue

    symptoms are as follows (really strange)

    1. downloading the ext-all.js with curl results in the following error
    A TLS packet with unexpected length was received.
    2. dmesg & journalctl pauses on the output (no disk errors or rpool raid events exist) - occurs on all hosts
    2a. curl request for ext-all.js also hangs
    3. pror to updating these issues were not presenting
    4. no visible ceph events to indicate there is a storage issue.

    pveversion -v
    proxmox-ve: 5.4-1 (running kernel: 4.15.18-13-pve)
    pve-manager: 5.4-5 (running version: 5.4-5/c6fdb264)
    pve-kernel-4.15: 5.4-2
    pve-kernel-4.15.18-14-pve: 4.15.18-39
    pve-kernel-4.15.18-13-pve: 4.15.18-37
    pve-kernel-4.15.18-12-pve: 4.15.18-36
    pve-kernel-4.15.18-11-pve: 4.15.18-34
    pve-kernel-4.15.18-10-pve: 4.15.18-32
    pve-kernel-4.15.18-9-pve: 4.15.18-30
    pve-kernel-4.10.17-3-pve: 4.10.17-23
    pve-kernel-4.10.17-2-pve: 4.10.17-20
    ceph: 12.2.12-pve1
    corosync: 2.4.4-pve1
    criu: 2.11.1-1~bpo90
    glusterfs-client: 3.8.8-1
    ksm-control-daemon: 1.2-2
    libjs-extjs: 6.0.1-2
    libpve-access-control: 5.1-9
    libpve-apiclient-perl: 2.0-5
    libpve-common-perl: 5.0-51
    libpve-guest-common-perl: 2.0-20
    libpve-http-server-perl: 2.0-13
    libpve-storage-perl: 5.0-42
    libqb0: 1.0.3-1~bpo9
    lvm2: 2.02.168-pve6
    lxc-pve: 3.1.0-3
    lxcfs: 3.0.3-pve1
    novnc-pve: 1.0.0-3
    proxmox-widget-toolkit: 1.0-26
    pve-cluster: 5.0-37
    pve-container: 2.0-37
    pve-docs: 5.4-2
    pve-edk2-firmware: 1.20190312-1
    pve-firewall: 3.0-20
    pve-firmware: 2.0-6
    pve-ha-manager: 2.0-9
    pve-i18n: 1.1-4
    pve-libspice-server1: 0.14.1-2
    pve-qemu-kvm: 3.0.1-2
    pve-xtermjs: 3.12.0-1
    qemu-server: 5.0-51
    smartmontools: 6.5+svn4324-1
    spiceterm: 3.0-5
    vncterm: 1.5-3
    zfsutils-linux: 0.7.13-pve1~bpo2
     
  2. dcsapak

    dcsapak Proxmox Staff Member
    Staff Member

    Joined:
    Feb 1, 2016
    Messages:
    3,519
    Likes Received:
    318
    you could try to reinstall the package with
    Code:
    apt install --reinstall libjs-extjs
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. The Chill Pilgrim

    The Chill Pilgrim New Member

    Joined:
    May 20, 2019
    Messages:
    2
    Likes Received:
    0
    Hey guys - i got up this morning, and realised my issue

    asymmetric routing... long story short, proxmox is straddling new and old management networks, for some reason I was trying the new network, and not the old.

    as soon as I hit the servers on the old IP's I was up and running

    Apologies, and thanks to those who offered advice.
     
  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