monit alert -- Resource limit matched localhost

Seen992 · 3. August 2013

Hi
I need help!

Zitat

Resource limit matched Service localhost

Date: Fri, 02 Aug 2013 05:43:58 +0600
Action: alert
Host: openmediavault
Description: cpu wait usage of 98.3% matches resource limit [cpu wait usage>95.0%]

Your faithful employee,
monit

Alles anzeigen

Zitat

Resource limit succeeded Service localhost

Date: Fri, 02 Aug 2013 05:44:33 +0600
Action: alert
Host: openmediavault
Description: 'localhost' cpu wait usage check succeeded [current cpu wait usage=18.3%]

Your faithful employee,
monit

Alles anzeigen

Zitat

Resource limit matched Service localhost

Date: Fri, 02 Aug 2013 13:45:05 +0600
Action: alert
Host: openmediavault
Description: cpu wait usage of 97.9% matches resource limit [cpu wait usage>95.0%]

Your faithful employee,
monit

Alles anzeigen

Zitat

Resource limit succeeded Service localhost

Date: Fri, 02 Aug 2013 13:45:43 +0600
Action: alert
Host: openmediavault
Description: 'localhost' cpu wait usage check succeeded [current cpu wait usage=33.2%]

Your faithful employee,
monit

Alles anzeigen

Zitat

Resource limit matched Service localhost

Date: Fri, 02 Aug 2013 13:45:05 +0600
Action: alert
Host: openmediavault
Description: cpu wait usage of 97.9% matches resource limit [cpu wait usage>95.0%]

Your faithful employee,
monit

Alles anzeigen

But I know that no one with him not working at the moment ...

hardware:
gigabyte g61
intel g620
DDR III 4gb
WD re4 1tb

Help solve the problem

ryecoaaron · 3. August 2013

Look at the processes tab to see which process is using the most cpu resources.

Seen992 · 3. August 2013

Looked through the top
but it did not help ...
There are more ideas?

tekkb · 3. August 2013

Download an ISO of Memtest. Burn it to a disk and boot to it. Run it for 2 passes and see if you get any errors. We have seen problems like this when there is an issue with ram.

http://www.memtest.org/#downiso

Seen992 · 3. August 2013

Hardware is ok .... I checked it memtest, goldmemory The results are normal. Check the cpu, hdd, power supply. Everything is in good standing. I think the problem is omv.

Seen992 · 3. August 2013

But what exactly is the problem .... the question is open.

ryecoaaron · 3. August 2013

What plugins are you using?

tekkb · 3. August 2013

give results of:

dpkg -l | grep openmediavault

Seen992 · 6. August 2013

Zitat

Post by ryecoaaron » Sun 4. Aug 2013, 01:54
What plugins are you using?

clamav
nothing more

Zitat

Post by tekkbebe » Sun 4. Aug 2013, 03:05
give results of:

dpkg -l | grep openmediavault

OK tomorrow I will try and write

PAPPL · 9. August 2013

I get the same CPU resource errors since last update.

Microserver N40L.

ryecoaaron · 9. August 2013

It isn't an error. Your cpu is bottlenecked by something. Not sure what it is though. I have three systems running the latest update without this issue. Maybe iotop would show more.

Seen992 · 12. August 2013

dpkg -l | grep openmediavault

Zitat

He recently became a hang. In the console, he writes.
This portion of the log, which I photographed on my phone.

Zitat

1141691 offset o 1194476.097562 EXT4-fs error (device sdb1): ext4-find entry: reading directory 0141691 offset 0 (198069 3537041
EXT4-fs error (device sdb1): ext4-find-entry: reading directory 1141691 offset 0 (201662.609849
EXT4-fs error (device sdb1): ext4-find entry: reading directory 1141691 offset 0 [205255 865993]
EXT4-fs error (device sdb1): ext4-find-entry: reading directory 0141691 offset 0 (208849 122138
EXT4-fs error (device sdb1): ext4-find-entry: reading directory 0141691 offset 0 [212442,378281]
EXT4-fs error (device sdb1): ext4-find-entry: reading directory 1141691 offset 0 216035 634427
EXT4-fs error (device sdb1) ext4-find-entry: reading director/ 0141691 offset 0 [219628.090573
EXTA-fs error (device sdb1): ext4-find-entry: reading directory 1141691 offset 0 (221281291644
EXT4-fs error (device sdb1): ext4-find-entry: reading directory offset 0 (221287, 291711 ExT4-fs error (device sdbi): ext4-find entry: reading director 1130049 offset 0 146120 ExT-fs error (device sdbi): ext4-find-entry: reading direct 1141691 offset 0 (226162 306567]
Kernel panic not syncing: Attempted to kill init

Alles anzeigen

Checked "sudo badblocks -v /dev/sdb1". No bad blocks.

Zitat

Maybe it disables the operating system partition?

ryecoaaron · 12. August 2013

It may not have any bad blocks but that doesn't mean the hard drive isn't failing. When a drive has problems, omv didn't have the nofail option in fstab until recently and you had to create that filesystem in the recent version. So, it stops to fix. You could add it to the fstab but I would remove the drive.

Seen992 · 12. August 2013

Zitat

It may not have any bad blocks but that doesn't mean the hard drive isn't failing. When a drive has problems, omv didn't have the nofail option in fstab until recently and you had to create that filesystem in the recent version. So, it stops to fix. You could add it to the fstab but I would remove the drive.

I do not understand you.

ryecoaaron · 12. August 2013

I was trying to tell you that I think the hard drive is failing and I wouldn't trust it. It will cause problems including making OMV halt in the boot process. I would reinstall OMV and update it to the most recent version before creating new filesystems.

Seen992 · 13. August 2013

I understood you. But are you sure that the problem with the disk? I checked it not only standart tools linux.
Just check out Victoria under DOS. In general, the problem appeared to 0.3.H when I installed antivirus.
Maybe the problem in it? The problem is that he does not write the log, not about the load on the CPU, not about the error in failovoy system. I can not watch those logs?

ryecoaaron · 13. August 2013

I suppose the problem might be with antivirus but it still worries me about the filesystem errors. Uninstall the antivirus and see if that fixes the problem.

Jetzt mitmachen!