Illegal division by zero

cdsJerry

Renowned Member
Sep 12, 2011
222
9
83
Have had my system up and running for while now. Haven't made any changes in some time. Haven't even logged onto it in weeks.
Today I was thinking about creating a new VM so I logged on and I see there's an "Error: Illegal division by zero at /usr/share/perl5/PVE/HTMLServices.pm line 154" error.

There's only one VM on this machine and as I said, I've made no changes. Proxmox version 1.9 The following repeats in the log over and over but with new child #

**************
Dec 19 13:11:22 proxwww 232375 Illegal division by zero at /usr/share/perl5/PVE/HTMLServices.pm line 154.
Dec 19 13:11:23 proxwww 232421 Starting new child 232421
Dec 19 13:11:27 pvedaemon 231354 WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Dec 19 13:11:27 proxwww 232375 Illegal division by zero at /usr/share/perl5/PVE/HTMLServices.pm line 154.
Dec 19 13:11:32 pvedaemon 232201 WARNING: Cannot encode 'meminfo' element as 'hash'. Will be encoded as 'map' instead
Dec 19 13:11:32 proxwww 232421 Illegal division by zero at /usr/share/perl5/PVE/HTMLServices.pm line 154.
*************
 
Is there a command line in the GUI where I can run such commands? You have to admit, having a machine that understands virtual but requires a local keyboard is ironic.
kvm:~# df -P /
Filesystem 1024-blocks Used Available Capacity Mounted on
ev/pve/root 99083868 1199112 92851592 2% /
 
you mean instead of ssh? the upcoming 2.0 got a VNC shell access already.

pve2-shell.png
 
Ran the command again. Here you go.

kvm:~# df -P /
Filesystem 1024-blocks Used Available Capacity Mounted on
ev/pve/root 99083868 1200900 92849804 2% /
kvm:~#
 
Anything? Yes, the drive isn't used very much so the 2% is probably right, but why the error where there was no error before?
 
Anything? Yes, the drive isn't used very much so the 2% is probably right, but why the error where there was no error before?

The device name 'ev/pve/root' looks really strange - you should get '/dev/pve/root' instead - please verify.
 
What is it I'm supposed to be verifying. I've run the command and done a copy and paste with the results, did it again, and now I'm supposed to verify it. I'm not sure what I'm supposed to be verifying. This is a copy and paste directly from Putty. I affirm that I did this three times. If I'm supposed to be doing something differently then please tell me. My understanding of Linux is limited. If I'm supposed to be doing something else I don't know what it is and I'll need more detailed instructions.
kvm:~# df -P /
Filesystem 1024-blocks Used Available Capacity Mounted on
ev/pve/root 99083868 1203100 92847604 2% /
kvm:~#
 
What is it I'm supposed to be verifying. I've run the command and done a copy and paste with the results, did it again, ...

Ok, so I assume you really get such strange result (you checked twice).

I suggest that you dump that whole node and reinstall from scratch.
 
Oh geeze. Is this a common problem? This thing has only been up for about a month, if that, and there were no problems until this mystery thing showed up. I was expecting something stable.
 
Oh geeze. Is this a common problem?

No, that is not common. A normal system cannot generate the output you posted - that is impossible. My assumption is that either you hardware/disk is damaged or the system got compromised somehow.
 
It's a Raid 10 system.

You should get the following output instead:

Code:
# df -P /
Filesystem         1024-blocks      Used Available Capacity Mounted on
/dev/pve/root           99083868   1203100  92847604       2% /

Any experienced linux admin should be able to debug whats wrong using strace.
 
I had an experienced Proxmox person take a look at this. He thinks the path was named wrong by the installer ISO for some reason. He's not sure if he can just rename the path or not. He was going to look into this. In the meantime, I've come down sick so I'm going to have to leave this for a day or two as I'm working from home and not feeling well enough to handle this. I'll peek on Tuesday. If he can't rename it I'll need to build another machine and have it run the VM while this one rebuilds.
 
Well
That's great.
I had an experienced Proxmox person take a look at this.
Thanks.