StoreEasy Storage

Failed task message stuck in checkhealth output - 3PAR CLI

 
SOLVED
Go to solution
BORDELEAU
Occasional Visitor

Failed task message stuck in checkhealth output - 3PAR CLI

Hi,

One of our production 3PAR had an issue running its hourly task check_slow_disk and resulted in a failed state. After removing it with the removetask -d <task id> command, it stills appear under the output of the checkhealth command.

Do you have an idea how we can completely get rid of it ? Our monitoring system keeps on reporting that the 3PAR is in a critical state.


Thank you for your advice!
Regards,

Alexandre

3 REPLIES 3
Dennis Handly
Acclaimed Contributor

Re: Failed task message stuck in checkhealth output

removetask -d doesn't remove the task, just the details.

You should look at the details and fix THAT problem, not remove the task.  Can you please provide them?

There is likely a slow disk that may need replacing.

 

> Our monitoring system keeps on reporting that the 3PAR is in a critical state.

It might be, if you have too many slow disks.

BORDELEAU
Occasional Visitor
Solution

Re: Failed task message stuck in checkhealth output

Hi Dennis,

The error occured because an HP rep came to update one of our 3PAR cage and his manipulations caused the scan to fail. The failed task disappeared 24 hours after on Saturday from the checkhealth command.

Thank you for the specifications regarding the removetask command.
Have a great day!

Alexandre

Dennis Handly
Acclaimed Contributor

Re: Failed task message stuck in checkhealth output

> The failed task disappeared 24 hours

FYI: The task is still there but you must use showtask -t 9999 to see it.