drbd : Refusing to be Primary while peer is not outdated (PACEMAKER)

This document (7018879) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11

Situation

In a working active/passive drbd setup during the graceful stop of the passive node. the active node shows in the cluster logs:

Apr 26 16:25:49 mars kernel: block drbd0: State change failed: Refusing to be Primary while peer is not outdated
Apr 26 16:25:49 mars kernel: block drbd0:   state = { cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate r----- }
Apr 26 16:25:49 mars kernel: block drbd0:  wanted = { cs:TearDown ro:Primary/Unknown ds:UpToDate/DUnknown s---F- }
Apr 26 16:25:49 mars kernel: drbd r0: State change failed: Refusing to be Primary while peer is not outdated

This is the normal Documentation of the Actions and Responses of the drbd to the Change. The Primary stops to work, ensures that it gets the Information that the Secondary is gone. Then continues working as soon as the "outdated" State is confirmed for the Secondary. Which, despite the number of lines in the logs, is nearly instantly.

Most importantly drbd did not restart or demote, so constraints to the Master State are not triggerd

Resolution

Entries are Information only, not an Error.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.