Actions
Bug #6445
closedCannot contact LDAP server due to mutex resource busy error
Status:
Rejected
Priority:
4
Assignee:
-
Category:
Server components
Target version:
-
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
This night, I got this on a newly migrated Rudder server (2.10.12 -> 2.11.9):
Mar 27 00:11:16 kingshead rudder-slapd[2678]: bdb(cn=rudder-configuration): unable to destroy mutex: Device or resource busy Mar 27 00:11:16 kingshead rudder-slapd[2678]: bdb(cn=rudder-configuration): Log sequence error: page LSN 1 8706217; previous LSN 1 8905065 Mar 27 00:11:16 kingshead rudder-slapd[2678]: bdb(cn=rudder-configuration): DB_TXN->abort: log undo failed for LSN: 1 8905065: Invalid argument Mar 27 00:11:16 kingshead rudder-slapd[2678]: bdb(cn=rudder-configuration): PANIC: Invalid argument Mar 27 00:11:17 kingshead rudder-slapd[2678]: bdb(cn=rudder-configuration): PANIC: fatal region error detected; run recovery
Not sure if it is due to a machine glitch or OpenLDAP/BDB one, so opening a ticket just in case.
Updated by Jonathan CLARKE almost 7 years ago
- Status changed from New to Rejected
- Priority set to 0
This hasn't ever surfaced again during our many tests. Closing - please reopen if this ever occurs again.
Actions