[ClusterLabs] About DRBD9 managed by pacemaker

刘丹 mzlld1988 at 163.com
Sat Sep 24 10:52:42 UTC 2016


Hi everyone,


I have a question about DRBD9 managed by pacemaker.
When I used DRBD9 with pacemaker,  but the DRBD9 can't be started by pacemaker,the following error message is recorded in /var/log/messages.
The methods to use DRBD9 with pacemaker is the same with DRBD8.4 with pacemaker. Does pacemaker can't support DRBD9 now?



















Sep 23 04:00:16 drbd lrmd[6057]:  notice: WebData_start_0:6093:stderr [ 'r0' is a normal resource, and not available in stacked mode. ]
Sep 23 04:00:16 drbd lrmd[6057]:  notice: WebData_start_0:6093:stderr [ 'r0' is a normal resource, and not available in stacked mode. ]
Sep 23 04:00:16 drbd crmd[6060]:   error: Result of start operation for WebData on drbd.node102: Timed Out | call=7 key=WebData_start_0 timeout=240000ms
Sep 23 04:00:16 drbd crmd[6060]:  notice: drbd.node102-WebData_start_0:7 [ 'r0' is a normal resource, and not available in stacked mode.\n'r0' is a normal resource, and not available in stacked mode.\n'r0' is a normal resource, and not available in stacked mode.\n'r0' is a normal resource, and not available in stacked mode.\n'r0' is a normal resource, and not available in stacked mode.\n'r0' is a normal resource, and not available in stacked mode.\n'r0' is a normal resource, and not available in stacked mode.\n'r0' is a normal resource,
Sep 23 04:00:16 drbd lrmd[6057]:  notice: WebData_notify_0:7894:stderr [ 'r0' is a normal resource, and not available in stacked mode. ]

The following is the resource file content:

resource r0 {
          device minor 1;
          meta-disk internal;
          on drbd.node102 {
            disk /dev/ram0;
            address 192.168.56.102:7789;
            node-id 2;
          }
          on drbd.node101{
             disk /dev/ram0;
             address 192.168.56.101:7789;
             node-id 1;
          }
          on drbd.node103{
             disk /dev/ram0;
             address 192.168.56.103:7789;
             node-id 3;
          }
          connection{
             host  drbd.node102 port 7789;
             host  drbd.node101 port 7789;
          }
          connection{
             host drbd.node102 port 7789;
             host drbd.node103 port 7789;
          }
          connection{
             host drbd.node101 port 7789;
             host drbd.node103 port 7789;
          }

 }

I'm looking forward to your answers. thanks.

Best Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160924/159964c8/attachment-0003.html>


More information about the Users mailing list