File is not a perl storable error

[airaid]

My VM was taken offline yesterday due to an issue at my provider. My understanding is the VM was manually moved to a different storage layer because of an underlying fault.

Since it came back online the following error is being repeatedly logged here /usr/local/cpanel/3rdparty/perl/522/bin/munin-cron

File is not a perl storable at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/5.22.1/x86_64-linux-64int/Storable.pm line 410, at /usr/local/cpanel/3rdparty/perl/522/lib64/perl5/cpanel_lib/Munin/Master/Utils.pm line 279.

I don't understand the implications of this and I can't find any info related to it on Google. Do you have any idea how I can approach fixing this or what the impact might be?

 

[airaid]

As an update, when I click on 'Munin Service Monitor' in WHM I see a screen of garbage text. Is there an up-to-date procedure for re-installing munin and/or just stopping it for the time being?

Thanks

 

[Infopro]

Is the checkbox selected for Munin here?
WebHost Manager »cPanel »Manage Plugins

 

[airaid]

It is and apologies for not being aware of that page. What does the checkbox do exactly? I don't want to risk uninstalling munin for now, I'd rather just disable it. I found some instructions at the site below but maybe the checkbox does the same thing?

markus.revti.com/2014/05/disable-munin-without-uninstalling-it-on-cpanel-server/

Thanks for the reply.

 

[Infopro]

If you uncheck it and save, it will/should uninstall munin. Ticking it again and save, will/should install it properly.

 

[airaid]

That's great to know, thank you and I'll schedule this for later. For now, do you know if the advice in the post I linked (copied below) is correct/safe to disable rather than uninstall?

Stop and disable from startup:

service munin-node stop
chkconfig munin-node off

And then comment (#) the munin cron job in /var/spool/cron/munin

Thanks again, much appreciated.

 

[Infopro]

Seems reasonable to me, yes.

 

[airaid]

That's great, thanks very much. I followed the instructions and I'm no longer seeing the errors being logged. Really appreciate your help.

 

[Infopro]

Well, I'm happy to help of course, but you didn't fix the problem by simply disabling munin, did you? Or is that what you wanted?

 

[airaid]

No, I didn't fix the problem, you're correct. To be honest, I'm really nervous about doing anything more than the absolute minimum to this server. Since opening this thread I also discovered lots of these being logged in var/log/messages:

Dec 1 20:08:21 kernel: [78182.855608] EXT3-fs error (device loop0): ext3_lookup: deleted inode referenced: 128

These are still being logged so it would appear the problem is deeper than the munin cron job. This server is due to be decommissioned in the next couple of months so I'm hoping (possibly naively) that by making a minimal amount of changes I can ignore these until then. Unfortunately, I don't have the experience or knowledge to do otherwise.

 

[Infopro]

You should make sure your backups are up to date. I'm not sure I'd wait a couple of months if there are issues on the server when you could be moved to a new server by tomorrow morning.

Anyway, good luck with this.

 

[airaid]

Yes, backups are most definitely up to date. Thanks, and again, appreciate your help.