Proxmox VE 4.3 Suddenly Not Working

A

Ahmad Anggra

New Member
Jan 23, 2017
4
0
1
35
Hi All,

Today after installing & configuring ocs inventory ng agent on my Proxmox VE 4.3 machine. The Proxmox suddenly not working.

I can not access from web manager nor I can using it related command. From netstat status, it is look like the Proxmox not running.

Please help me to trouble shot this problem since I do not want lose my container and VM setting that just done configure properly.


The /etc/pve directory is empty.
root@pve:~# ls -l /etc/pve/
total 0​

Nestat result & dpkg:
root@pve:~# netstat -an | grep 8006
root@pve:~# dpkg -l | grep proxmox
rc proxmox-ve 4.3-66 all The Proxmox Virtual Environment
​
Some log snapshot from daemon:
Jan 23 13:38:36 pve pve-ha-crm[5932]: Can't locate PVE/LXC.pm in @INC (you may need to install the PVE::LXC 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/HA/Resources/PVECT.pm line 8.
Jan 23 13:58:05 pve pveproxy[8062]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/HTTPServer.pm line 1626.
Jan 23 13:58:05 pve pveproxy[4221]: ipcc_send_rec failed: Connection refused​

Some log from syslog:
Jan 24 08:23:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:24:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:25:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:26:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:27:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:28:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:29:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:30:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 24 08:31:01 pve cron[1075]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)

​
 
Last edited:
Hi,
Ahmad Anggra said:
The /etc/pve directory is empty.
root@pve:~# ls -l /etc/pve/
Click to expand...
This indicated the pmxcfs is not running, so nothing can work

ocs inventory ng agent is writen in perl I think this packet install a package what conflicts with PVE packages.
What I can say you miss imported PVE files.

Try to
Code: 
apt-get install --reinstall proxmox-ve

I think it will fail but you get a clue where the problem is.
 
wolfgang said:
Hi,

This indicated the pmxcfs is not running, so nothing can work

ocs inventory ng agent is writen in perl I think this packet install a package what conflicts with PVE packages.
What I can say you miss imported PVE files.

Try to
Code: 
apt-get install --reinstall proxmox-ve

I think it will fail but you get a clue where the problem is.
Click to expand...

Yes it fail, I had tried to reinstall using command you mentioned (even before got reply from you).
And I had receive following messages:
root@pve:~# apt-get install --reinstall proxmox-ve
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package proxmox-ve is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'proxmox-ve' has no installation candidate
​
Does proxmox need special repository configuration? Oh yeah I have concern, does it means the container & vm that been created get destroyed... if so I will not meddle some any perl software on ocs machine.

Thank you very much for the reply.
 
I had reinstall it and get so many error. Look like it better for me to reinstall the machine from CD.

Failed to reload-or-restart pve-firewall.service: Unit pve-firewall.service is masked.
dpkg: error processing package pve-firewall (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
pve-ha-manager depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
pve-container depends on pve-ha-manager; however:
Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-firewall
qemu-server
pve-manager
proxmox-ve
pve-ha-manager
pve-container
E: Sub-process /usr/bin/dpkg returned an error code (1)
​
 
You must log in or register to reply here.
Top Bottom
Back