Restarting Proxmox web Interface

K

Kaanha

New Member
Jan 4, 2013
20
0
1
I'm attempting to access the web interface of my ProxMox server via https://xxx.xxx.xxx.xxx:8006 and chrome just sits and spins not bringing anything up, I have verified I have proper network connection. I can access the server via SSH. I have run into this problem before, where the web interface simply fails to load and the way I've fixed it is by restarting the service(s) that the web interface uses, however I can not for the life of me remember what the service is.

Can someone tell me what service(s) needs to be restarted for the web interface? I have run an apt-get upgrade but other then that I've not done anything to the server and the web interface was functioning perfectly fine just a few days ago.

Here's my version information via pveversion -v

Code: 
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-95
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-7
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-6
libpve-access-control: 3.0-6
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1
 
I figured it'd be good to note, absolutely everything else is running fine on the server. All of my VM's are still running and accessible, etc.
 
Quick question: If i have running VMs that I do not want to go down, can I run # service pveproxy restart to restart the web gui without interference to the VMs?

EDIT: We are still running on proxmox version 3
 
Jtaylor said:
Quick question: If i have running VMs that I do not want to go down, can I run # service pveproxy restart to restart the web gui without interference to the VMs?
Click to expand...

Restarting pveproxy shouldn't effect the running guests.

Note:
Proxmox 3.x isn't being supported for a long time now, please upgrade your system to get the latest features and bugfixes.
Upgrade instructions:
https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0
https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0
 
Any suggestions if
systemctl restart pveproxy
doesn't help? (proxmox 8)

I am able to log into other nodes fine. The two functioning nodes show green, but the problem node and vms on the problem node are showing gray (and lacking details). The vm running on the problem node seems fine, but migrate option says it would be offline instead of online.

My guess is rebooting would clear it, but that would also reboot all vms that seem to be functioning on this degraded node....
 
  • Like
Reactions: andrew.dot
jlauro said:
Any suggestions if
systemctl restart pveproxy
doesn't help? (proxmox 8)

I am able to log into other nodes fine. The two functioning nodes show green, but the problem node and vms on the problem node are showing gray (and lacking details). The vm running on the problem node seems fine, but migrate option says it would be offline instead of online.

My guess is rebooting would clear it, but that would also reboot all vms that seem to be functioning on this degraded node....
Click to expand...

I was having an issue on a node that brought me here; turned out not to be proxy.
When I setup an LXC container, the auto set up the vm bridge killed the IP on my secondary interface.
Being a dev node, I forgot it had two connected interfaces :D
 
A bad fstab entry got me here so thanks for pointing me in the right direction.

I have a root partition on a non-PLP drive and I attempted to enable journaling in the latest proxmox but apparently I got it wrong. I did not reboot right away to test then it was like... what happened?

A botched fstab definitely gets you here.
 
You must log in or register to reply here.
Top Bottom