[SOLVED] Lost webGUI on update to PVE 8.2

A

arcaeus

Member
Apr 20, 2022
12
2
8
Hi all, I just installed Proxmox 7.1 on an old HP Z800 workstation. I know the current version is 8.2, but during install it kept hanging on the "intel-powerclamp" stage. Thus, I installed 7.1 with the hopes of updating to current afterwords.

I got it up and running, logged into the wedGUI, updated the repos to use the non-subscription ones, and ran an apt-get update. I then ran an 'apt full-upgrade' to go to 8.2 which looked like it completed successfully.

Now for some reason, when I go to 'https://192.168.2.101:8006/', I get an "ERR_CONNECTION_REFUSED" message in chrome. I can ping local and WAN IPs from the directly connected screen & keyboard, and can SSH in from my desktop.

Code: 
ip addr
seems to show that the interfaces are up:
Image


and /etc/network/interfaces seems ok:
Image


My client is on the same subnet as the server (client IP is 192.168.2.86)


any idea why I can't access the webGUI anymore?
 
  • Like
Reactions: memeske
Well, as usual, after obligatory (did you also try to reboot, did you also clear browser cache), can you perhaps post:

journalctl -u pveproxy
 
esi_y said:
Well, as usual, after obligatory (did you also try to reboot, did you also clear browser cache), can you perhaps post:

journalctl -u pveproxy
Click to expand...

Yep, did a few reboots and cleared the browser cache, no change.

That command returns:
Code: 
root@proxmox:~# journalctl -u pveproxy
Aug 20 17:49:37 proxmox systemd[1]: Starting PVE API Proxy Server...
Aug 20 17:49:38 proxmox pvecm[1169]: Generating public/private rsa key pair.
Aug 20 17:49:38 proxmox pvecm[1169]: Your identification has been saved in /root/.ssh/id_rsa
Aug 20 17:49:38 proxmox pvecm[1169]: Your public key has been saved in /root/.ssh/id_rsa.pub
Aug 20 17:49:38 proxmox pvecm[1169]: The key fingerprint is:
Aug 20 17:49:38 proxmox pvecm[1169]: SHA256:yqIDL1Qu+S2oowGiBgFZuRUfw8f5s4Razedqnz/5qKE root@proxmox
Aug 20 17:49:38 proxmox pvecm[1169]: The key's randomart image is:
Aug 20 17:49:38 proxmox pvecm[1169]: +---[RSA 2048]----+
Aug 20 17:49:38 proxmox pvecm[1169]: |.o...oo. .       |
Aug 20 17:49:38 proxmox pvecm[1169]: |o . ...o+        |
Aug 20 17:49:38 proxmox pvecm[1169]: |.  o  .. =       |
Aug 20 17:49:38 proxmox pvecm[1169]: | ...    o * .    |
Aug 20 17:49:38 proxmox pvecm[1169]: |+ +    oS. =     |
Aug 20 17:49:38 proxmox pvecm[1169]: |*+ . ...  . .    |
Aug 20 17:49:38 proxmox pvecm[1169]: |+++ o o    ..  . |
Aug 20 17:49:38 proxmox pvecm[1169]: |+oo+ o    o. oo. |
Aug 20 17:49:38 proxmox pvecm[1169]: |=o...    .E.+ooo.|
Aug 20 17:49:38 proxmox pvecm[1169]: +----[SHA256]-----+
Aug 20 17:49:39 proxmox pvecm[1166]: got inotify poll request in wrong process - disabling inotify
Aug 20 17:49:41 proxmox pveproxy[1184]: starting server
Aug 20 17:49:41 proxmox pveproxy[1184]: starting 3 worker(s)
Aug 20 17:49:41 proxmox pveproxy[1184]: worker 1185 started
Aug 20 17:49:41 proxmox pveproxy[1184]: worker 1186 started
Aug 20 17:49:41 proxmox pveproxy[1184]: worker 1187 started
Aug 20 17:49:41 proxmox systemd[1]: Started PVE API Proxy Server.
Aug 20 17:56:59 proxmox pveproxy[1185]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:56:59 proxmox pveproxy[1185]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:56:59 proxmox pveproxy[1185]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:56:59 proxmox pveproxy[1186]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:56:59 proxmox pveproxy[1186]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:56:59 proxmox pveproxy[1186]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:57:02 proxmox pveproxy[1187]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:57:02 proxmox pveproxy[1187]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:57:02 proxmox pveproxy[1187]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:57:22 proxmox pveproxy[1185]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:57:22 proxmox pveproxy[1185]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:57:22 proxmox pveproxy[1185]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:57:22 proxmox pveproxy[1185]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:57:22 proxmox pveproxy[1185]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:57:22 proxmox pveproxy[1185]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:57:27 proxmox pveproxy[1185]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:57:27 proxmox pveproxy[1185]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:57:27 proxmox pveproxy[1185]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:57:34 proxmox pveproxy[1185]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:57:34 proxmox pveproxy[1185]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:57:34 proxmox pveproxy[1185]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:57:34 proxmox pveproxy[1185]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:57:34 proxmox pveproxy[1185]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:57:34 proxmox pveproxy[1185]: ipcc_send_rec[3] failed: Connection refused
Aug 20 17:57:41 proxmox pveproxy[1185]: ipcc_send_rec[1] failed: Connection refused
Aug 20 17:57:41 proxmox pveproxy[1185]: ipcc_send_rec[2] failed: Connection refused
Aug 20 17:57:41 proxmox pveproxy[1185]: ipcc_send_rec[3] failed: Connection refused

and repeats on a bunch more lines.
 
I wonder if this will be one of those "upgrades" where journalctl -xeu pve-cluster will show you fuse_mount errors ...
 
cheiss said:
Hi,

can you provide the output of systemctl status pve-cluster and pveversion -v?
Click to expand...
Sure!

Code: 
root@proxmox:~# systemctl status pve-cluster
○ pve-cluster.service
     Loaded: masked (Reason: Unit pve-cluster.service is masked.)
     Active: inactive (dead)

Code: 
root@proxmox:~# pveversion -v
-bash: pveversion: command not found
 
esi_y said:
Oh my, what happened during the upgrade? Like literally if you could reproduce this, I would like to know how you can end up with non-existent services.

I am not sure if this is some common upgrade pain (7 to 8), but if this is fresh install, I would probably prefer to install Debian first and then PVE 8 on top:

https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm
Click to expand...
haha that's my question. This was a fresh install so I'm surprised it got borked so bad. But good news is there's nothing on there as this is my test env so I can wipe it and start over pretty easily.

I was debating on doing PVE on top of Debian so that may be a better option. I'll keep that in my back pocket if a bare metal install doesn't work. I'm planning to spin up some VMs for a k3s cluster, so I'm trying to minimize my overhead if possible. Neither debian or PVE seem like they take that much tho so it may be a non issue.

Thanks for sending over the wiki page; that's super helpful. I'll poke through that and see if that fixes it.
 
arcaeus said:
I'll keep that in my back pocket if a bare metal install doesn't work.
Click to expand...

This might not be appreciated opinion here, but the ISO installer failed me so many times and others on different hardware (even just minor to minor version one works, another does not) ... that I do not use it. The only thing I can think of that you will not get with Debian is ZFS on root out of the box. Note you can still have pool for VMs, etc. Just not the host OS on the ZFS, which I wonder, how many really need. Also Debian uses GRUB as bootloader no matter what. I will not be pitching my opinion here, but for some reason, PVE installler gives you systemd-boot, but only if it's EFI and only if not in SecureBoot. Debian installer gives you quite decent partitioning options as opposed to ISO one.

arcaeus said:
I'm planning to spin up some VMs for a k3s cluster, so I'm trying to minimize my overhead if possible. Neither debian or PVE seem like they take that much tho so it may be a non issue.
Click to expand...

Why not run it directly on the hardware then? ;)

arcaeus said:
Thanks for sending over the wiki page; that's super helpful. I'll poke through that and see if that fixes it.
Click to expand...

Jokes and snide remarks aside, the install on top of Debian never failed me, it's perfectly normal way to do it, after all PVE is just additional repo and you exchange kernels (the custom one is basically Ubuntu-ish one).
 
esi_y said:
This might not be appreciated opinion here, but the ISO installer failed me so many times and others on different hardware (even just minor to minor version one works, another does not) ... that I do not use it. The only thing I can think of that you will not get with Debian is ZFS on root out of the box. Note you can still have pool for VMs, etc. Just not the host OS on the ZFS, which I wonder, how many really need. Also Debian uses GRUB as bootloader no matter what. I will not be pitching my opinion here, but for some reason, PVE installler gives you systemd-boot, but only if it's EFI and only if not in SecureBoot. Debian installer gives you quite decent partitioning options as opposed to ISO one.
Click to expand...
Hmm interesting. Maybe that's what was hanging me up when trying to install 8.2 through the ISO loader. I think the Z800 is from like 2009 so I'm sure there are things not terribly compatible between software and hardware.

esi_y said:
Why not run it directly on the hardware then? ;)
Click to expand...
So this is actually how I have my "prod" 4-node k3s cluster, debian on bare metal . I have this Z800 workstation laying around doing nothing which has 2x Zeon X5650s in it totaling 24 threads. I wanted to have a "dev" env to play around with things, but seeing as I only have 1 physical computer figured the next best option was Proxmox with 4x vms to resemble my "prod" cluster.


esi_y said:
Jokes and snide remarks aside, the install on top of Debian never failed me, it's perfectly normal way to do it, after all PVE is just additional repo and you exchange kernels (the custom one is basically Ubuntu-ish one).
Click to expand...
That's really good to know. Debian has worked well for my existing cluster, so hopefully it works well here too.
 
Ok, I finally figured it out.

It wasn't working because I didn't follow the 7 to 8 guide linked above. Certain steps needed to be completed for everything to update properly. Once I followed that, we were good to go.
 
arcaeus said:
Ok, I finally figured it out.

It wasn't working because I didn't follow the 7 to 8 guide linked above. Certain steps needed to be completed for everything to update properly. Once I followed that, we were good to go.
Click to expand...

FWIW I would prefer to install things fresh, in a cluster the whole point is one should be able to completely tear down a node and add new. In a standalone case, I understand that, in yours, it's really your call.

But good you got that working!
 
Oh My!! I had a Web GUI console issue and it was right after i moved upgraded to 8.2.4. Disclaimer, I am so new and I probably did something. I finally just got my 3rd machine to have a "proper cluster" and congressional quorum. My primary node just would not get the webGUI console working. for a few days, I just ssh'ed a lot, till I got mad and re-installed proxmox from scratch (talk about escalation a small thing) reading this post humbles me and inspires me to "check forums and other places". This community is great. Thank you all.
Another lesson, I should have captured the error on the web console GUI. I just let my emotions get the best of me. Rest assured this community forum will be top of list resources and "as a newbie", I will come armed with logs or screenshots...anything other than this blah blah I felt it necessary to say this really adjusted my mindset as I begin and move through this wonderful Proxmox journey.
 
memeske said:
Oh My!! I had a Web GUI console issue and it was right after i moved upgraded to 8.2.4.
Click to expand...

From v7?

memeske said:
I finally just got my 3rd machine to have a "proper cluster" and congressional quorum.
Click to expand...

The nodes are phenry, gwashington and jjay? :)

memeske said:
I will come armed with logs or screenshots...
Click to expand...

Please do, it helps a lot with the initial answer always, or even deciding to answer ...
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom