Web GUI not opening since morning.

AmithKumar

Active Member
May 8, 2018
16
0
41
38
Hi,

I am facing issue since morning and not able to login with web GUI portal. The link is coming as request timed out. But able to login via SSH. All the VM's inside is working fine.

2 Months back when I was cleaning the unwanted VM's, unfortunately, I deleted one VM disk file directly which resulted in disk usage reduction and many of the features were not working from them. I was able to work in the GUI and manage the VM's at least.

Now GUI is not opening and when i enter in SSH for pve version and any other activity facing this error.

pveversion
Can't locate PVE/OTP.pm in @INC (you may need to install the PVE::OTP module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /usr/share/perl5/PVE/AccessControl.pm line 13.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/AccessControl.pm line 13.
Compilation failed in require at /usr/share/perl5/PVE/RPCEnvironment.pm line 14.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/RPCEnvironment.pm line 14.
Compilation failed in require at /usr/share/perl5/PVE/API2/APT.pm line 20.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/APT.pm line 20.
Compilation failed in require at /usr/bin/pveversion line 7.
BEGIN failed--compilation aborted at /usr/bin/pveversion line 7.


Please suggest as I need to move the VM's to another server, not able to add backup storage and not able to mount the remote storage which was working earlier.

Very much scared will this result in any VM data loss.
 
it seems some pve packages are missing, try
Code:
apt install proxmox-ve
 
Hi,

If I install proxmox-ve again will it destroy the VM's & do I need to reboot the server?

Below is the output of this command,

apt install proxmox-ve
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
pve-kernel-4.4.134-1-pve
The following NEW packages will be installed:
pve-kernel-4.4.134-1-pve
The following packages will be upgraded:
proxmox-ve
1 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
88 not fully installed or removed.
Need to get 44.8 MB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]


Kindly suggest.
 
no this will not destroy the vms and after a kernel upgrade you need to reboot

1 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
it seems there are also updates available, use 'apt dist-upgrade' to upgrade, this can also be the reason

pve-kernel-4.4.134-1-pve
pve 4.4 is out of support since july, i would recommend to upgrade to 5.x
 
Hi,

Below error is coming,

Do you want to continue? [Y/n] y
Setting up pve-manager (4.4-13) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)


What to do now?
 
Also

apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-image-3.16.0-7-amd64
The following packages will be upgraded:
corosync-pve libcorosync4-pve libpve-common-perl linux-image-amd64 pve-cluster pve-container pve-manager pve-qemu-kvm qemu-server
9 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 44.0 MB of archives.
After this operation, 172 MB of additional disk space will be used.
Do you want to continue? [Y/n] y

............ trimmed the output
trimmed the output ............

Setting up libcorosync4-pve (2.4.2-2~pve4+2) ...
Setting up corosync-pve (2.4.2-2~pve4+2) ...
Setting up pve-cluster (4.0-55) ...
Setting up qemu-server (4.0-115) ...
Setting up pve-container (1.0-106) ...
Setting up pve-manager (4.4-24) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Setting up linux-image-3.16.0-7-amd64 (3.16.59-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-7-amd64
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.134-1-pve
Found initrd image: /boot/initrd.img-4.4.134-1-pve
Found linux image: /boot/vmlinuz-4.4.67-1-pve
Found initrd image: /boot/initrd.img-4.4.67-1-pve
Found linux image: /boot/vmlinuz-3.16.0-7-amd64
Found initrd image: /boot/initrd.img-3.16.0-7-amd64
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
done
Setting up linux-image-amd64 (3.16+63+deb8u3) ...
Processing triggers for pve-ha-manager (2.0-5) ...
Processing triggers for libc-bin (2.19-18+deb8u10) ...
Processing triggers for systemd (215-17+deb8u7) ...
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have not luck in both the update and install proxmox-ve

Please help what to do now. As I need to move the VM's from this node to a new setup.
 

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!

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!