Problem with Resizing the VM Disk Size

[Bone8Head]

Hello guys.

I already have a Thread, but I think that was better to create a new one for this new issue.
My Nagios XI is not working anymore, because the Root Partition is 100% FULL.
So I'm trying to let it work with this good Guide:

Code: Select all

https://assets.nagios.com/downloads/nagiosxi/docs/Resizing-The-XI-VM-Disk.pdf

So, that's what I did:

I resized the VM Disk on VMWare vSphere from 20GB to 40GB.

-REBOOT

Then I did these commands:

# fdisk /dev/sda

Command (m for help): d
Partition number (1-4): 2
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2

Command (m for help): t
Partition number (1-4): 2
Hex code (type L to list codes): 8e
Changed system type of partition 2 to 8e (Linux LVM)
Command (m for help): w
The partition table has been altered!

--REBOOT

But here when I try to pvresize /dev/sda2 for resize the Partition, my System gave me this:

Is like the System don't see that my Disk now is more huge.

Any advice?

[hsmith]

Delete a file, such as a rotated log. Usually stuff in /var/log is all right to delete unless you're archiving that information for some reason or another. I believe pvresize fails if the disk is 100% full, I have no idea why, but I've seen it before.

[Bone8Head]

Delete a file, such as a rotated log. Usually stuff in /var/log is all right to delete unless you're archiving that information for some reason or another. I believe pvresize fails if the disk is 100% full, I have no idea why, but I've seen it before.

That's work, thank you very much.
Can you tell me why Nagios XI was "eating" so much Disk Space? I don't think that the cause was only the logs in /var/log/.

[Bone8Head]

And also I have another question:

why sometimes when I install a new plugin, it give me this error:

Code: Select all

-bash: ./check_ocsing: /usr/bin/php5: bad interpreter: No such file or directory

I'm pretty sure that I have php...and if I try to yum install php or php5 the System told me that I have already it on the last version.

[hsmith]

Can you tell me why Nagios XI was "eating" so much Disk Space? I don't think that the cause was only the logs in /var/log/.

I can't, but maybe this command can:

Code: Select all

find / -type f -print0 | xargs -0 du | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {}

How long has the machine been running for it to accumulate that much data? 20GB isn't a ton of space, but it depends on how fast it filled up that 20.

I'm pretty sure that I have php...and if I try to yum install php or php5 the System told me that I have already it on the last version.

Perhaps it's just a wrong file path?

Code: Select all

[root@XI5 tmp]# find /usr/bin -name *php*
/usr/bin/php

[Bone8Head]

Can you tell me why Nagios XI was "eating" so much Disk Space? I don't think that the cause was only the logs in /var/log/.

I can't, but maybe this command can:

Code: Select all

find / -type f -print0 | xargs -0 du | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {}

How long has the machine been running for it to accumulate that much data? 20GB isn't a ton of space, but it depends on how fast it filled up that 20.

I'm pretty sure that I have php...and if I try to yum install php or php5 the System told me that I have already it on the last version.

Perhaps it's just a wrong file path?

Code: Select all

[root@XI5 tmp]# find /usr/bin -name *php*
/usr/bin/php

40 Days.
Yes, and I don't have a file named php5, but only php there

[hsmith]

Change the script to say php instead of php5 at the top.

[Bone8Head]

Change the script to say php instead of php5 at the top.

I got another problem now.
Nagios XI is not sending Alerts E-Mail anymore.
All notification rules are always the same (all enabled), and if I try to send a E-Mail Test from Nagios XI I receveid it.
Any advice?

[hsmith]

I'm going to have to ask that you open a separate thread for that issue. It becomes very messy for other techs to try to pick up questions if the subject changes completely over the course of a thread. We'll be happy to help you out, but we want to keep it easy to read.

Thanks!