[DRBD-user] DRBD RA Error

Jake Smith jsmith at argotec.com
Thu Sep 22 15:05:58 CEST 2011


Forwarding messages that missed the list:

Hello Jake,

Thank you so much for your response. Yes, the "linbitt" is just a typo
in the email. I am using the deprecated Heartebeat drbd RA to fix
other issues... In terms of the DRBD status versus actual resource
name, the resource is actually:

resource r0.res {
device    /dev/drbd0;
disk      /dev/sda8;
meta-disk /dev/sda7 [0];
        on mydrbd1 {
                address   192.168.2.105:7789;
        }
        on mydrbd2 {
                address   192.168.2.106:7789;
        }
}

root at mydrbd1:/# /etc/init.d/drbd status
drbd driver loaded OK; device status:
version: 8.3.7 (api:88/proto:86-91)
srcversion: EE47D8BF18AC166BE219757
m:res     cs         ro                 ds                 p  mounted   fstype
0:r0_res  Connected  Primary/Secondary  UpToDate/UpToDate  C  /service  ext3

root at mydrbd1:/# drbdadm attach r0_res
'r0_res' not defined in your config.

And /dev/drbd/by-res/ contains r0.res, which is an empty when opening
it with nano?

Cheers,

Nick.



On Tue, Sep 20, 2011 at 2:53 PM, Jake Smith <jsmith at argotec.com> wrote:
> ----- Original Message -----
>> From: "Nick Khamis" <symack at gmail.com>
>> To: "drbd-user" <drbd-user at lists.linbit.com>
>> Sent: Tuesday, September 20, 2011 1:36:07 PM
>> Subject: [DRBD-user] DRBD RA Error
>>
>> Hello Everyone,
>>
>> I appologize if you are recieving this message again. I am recieving
>> an error when trying to load the DRBD RA within Pacemaker:
>>
>> primitive drbd_mysql ocf:linbitt:drbd \
>>                     params drbd_resource="r0.res" \
>>                     op monitor interval="15s"
>
> I assume the "linbitt" above is just a typo when you put it in the messages (should be "ocf:linbit:drbd")?
>
>>
>> lrmadmin[4153]: 2011/09/20_10:51:25 ERROR:
>> lrm_get_rsc_type_metadata(578): got a return code HA_FAIL from a
>> reply
>> message of rmetadata with function get_ret_from_msg.
>> ERROR: ocf:linbit:drbd: could not parse meta-data:
>> ERROR: ocf:linbit:drbd: no such resource agent
>>
>> Warnings in Log:
>>
>> Sep 20 10:51:25 mydrbd1 lrmd: [3560]: WARN: on_msg_get_metadata:
>> empty
>> metadata for ocf::linbit::drbd.
>>
>> /dev/drbd/by-res/r0.res
>> /usr/lib/ocf/resource.d/
>> /usr/lib/ocf/resource.d/linbit/drbd
>>
>> crm(live)ra# classes
>> heartbeat
>> lsb
>> ocf / heartbeat linbit pacemaker
>> stonith
>>
>> crm(live)ra# list ocf linbit
>> drbd
>>
>> DRBD is installed and working as expected manually.
>>
>> Only "drbd" is in /usr/lib/ocf/resource.d/linbit/. No other files
>>
>> /etc/init.d/drbd status
>> drbd driver loaded OK; device status:
>> version: 8.3.7 (api:88/proto:86-91)
>> srcversion: EE47D8BF18AC166BE219757
>> m:res     cs         ro                 ds                 p  mounted
>>   fstype
>> 0:r0_res  Connected  Primary/Secondary  UpToDate/UpToDate  C
>>  /service  ext3
>
> Is your resource named r0.res or r0_res?  Above the output of status looks like its "r0_res" but in the primitive above you have "r0.res"?  The pacemaker line "params drbd_resource="r0.res"" expects the name of the resource you used in the drbd resource definition - resource xxxx { } - not the name of the resource definition file in /etc/drbd.d/
>
>>
>>
>> Obeservations:
>> When running the drbd "/usr/lib/ocf/resource.d/linbit/drbd" sript
>> from
>> console, I get:
>> line 45:  /resource.d/heartbeat/.ocf-shellfuncs: No such file or
>> directory
>> line 801: usage: command not found
>>
>> When I use the deprecated ocf:heartbeat:drbd, I get no errors....
>>
>> DRBD: version: 8.3.7
>> Pacemaker: 1.1.6
>> RA: 1.0.4
>> Glue: 1.0.7
>>
>> Thanks in Advance,
>>
>> Nick
>> _______________________________________________
>> drbd-user mailing list
>> drbd-user at lists.linbit.com
>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>
>>
>




More information about the drbd-user mailing list