Actions
Bug #48230
closednautilus: cluster [ERR] mgr modules have failed (MGR_MODULE_ERROR)
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2020-11-12T22:33:15.916 INFO:tasks.ceph.mon.a.smithi038.stderr:2020-11-12 22:33:15.917 7fc763b5c700 -1 log_channel(cluster) log [ERR] : Health check failed: 3 mgr modules have failed (MGR_MODULE_ERROR)
Looking at the mon log:
2020-11-12 22:33:15.917 7fc763b5c700 20 mon.a@0(leader).mgrstat health checks:
{
"MGR_MODULE_ERROR": {
"severity": "HEALTH_ERR",
"summary": {
"message": "3 mgr modules have failed"
},
"detail": [
{
"message": "Module 'rbd_support' has failed: Not found or unloadable"
},
{
"message": "Module 'status' has failed: Not found or unloadable"
},
{
"message": "Module 'volumes' has failed: Not found or unloadable"
}
]
},
"PG_AVAILABILITY": {
"severity": "HEALTH_WARN",
"summary": {
"message": "Reduced data availability: 6 pgs peering"
},
"detail": [
{
"message": "pg 1.0 is stuck peering for 123.626751, current state peering, last acting [1,0]"
},
{
"message": "pg 1.2 is stuck peering for 123.624747, current state peering, last acting [0]"
},
{
"message": "pg 1.3 is stuck peering for 123.626252, current state peering, last acting [1]"
},
{
"message": "pg 1.4 is stuck peering for 123.627984, current state peering, last acting [1,0]"
},
{
"message": "pg 1.6 is stuck peering for 123.627208, current state peering, last acting [1,0]"
},
{
"message": "pg 1.7 is stuck peering for 123.625035, current state peering, last acting [1]"
}
]
}
}
.
.
.
2020-11-12 22:33:24.591 7fc766361700 0 log_channel(cluster) log [INF] : Health check cleared: MGR_MODULE_ERROR (was: 3 mgr modules have failed)
I think this can be ignored.
/a/yuriw-2020-11-12_20:34:09-rados-nautilus-distro-basic-smithi/5617251
Actions