- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- StoreEasy Storage
- >
- Failed task message stuck in checkhealth output - ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-10-2018 12:26 PM
ā08-10-2018 12:26 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-12-2018 09:27 PM - edited ā08-12-2018 09:28 PM
ā08-12-2018 09:27 PM - edited ā08-12-2018 09:28 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-13-2018 08:04 AM
ā08-13-2018 08:04 AM
SolutionHi 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-13-2018 11:06 AM
ā08-13-2018 11:06 AM
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.