[Pacemaker] DRBD+OCFS2+Pacemaker on UBUNTU 12.04, DRBD via pacemaker doesn't start when corosync invoked

[emmanuel segura]

Are you sure that your drbd work by hand? this is from your log

May 15 12:26:04 server1 lrmd: [1211]: info: RA output:
(Cluster-FS-DRBD:0:start:stderr) Command 'drbdsetup new-resource r0'
terminated with exit code 20
May 15 12:26:04 server1 drbd[1808]: ERROR: r0: Called drbdadm -c
/etc/drbd.conf new-resource r0
May 15 12:26:04 server1 drbd[1808]: ERROR: r0: Exit code 20
May 15 12:26:04 server1 drbd[1808]: ERROR: r0: Command output:


2014-05-15 10:37 GMT+02:00 kamal kishi <kamal.kishi at gmail.com>:

> Hi emi,
>
> The document also says the following :
>
> "It is also possible to use drbd.conf as a flat configuration file
> without any include statements at all. Such a configuration, however,
> quickly becomes cluttered and hard to manage, which is why the
> multiple-file approach is the preferred one.
>
> Regardless of which approach you employ, you should always make sure that
> drbd.conf, and any other files it includes, are *exactly identical* on
> all participating cluster nodes."
>
> I've tried that way too, but of no use.
>
> Tried giving -
>
> params device="/dev/drbd0" directory="/cluster" fstype="ocfs2" \
>
> instead of
>
> params device="/dev/drbd/by-res/r0" directory="/cluster" fstype="ocfs2" \
>
> even that failed.
>
> But my doubt is that i'm able to manually work with DRBD without any issue
> but why can't via pacemaker.
>
> Any useful info in logs??
>
> I did not get any, so inquiring
>
>
>
> On Thu, May 15, 2014 at 1:51 PM, emmanuel segura <emi2fast at gmail.com>wrote:
>
>> You don't declared your drbd resource r0 in the configuration, read this
>> http://www.drbd.org/users-guide/s-configure-resource.html
>>
>>
>> 2014-05-15 9:33 GMT+02:00 kamal kishi <kamal.kishi at gmail.com>:
>>
>>>  Hi All,
>>>
>>> My configuration is simple and straight, UBUNTU 12.04 used to run
>>> pacemaker.
>>> Pacemaker runs DRBD and OCFS2.
>>>
>>> The DRBD can be started manually without any error or issues with
>>> primary/primary configuration.
>>>
>>> (NOTE : This configuration is being done as base to configure
>>> ACTIVE-ACTIVE XEN configuration, hence the "become-primary-on both;' is
>>> used in DRBD config)
>>>
>>> Configuration attached :
>>> 1. DRBD
>>> 2. Pacemaker
>>>
>>> Log attached :
>>> Syslog1 - Server 1
>>> Syslog2 - Server 2
>>>
>>> Hope and wish I get a solution.
>>>
>>> --
>>> Regards,
>>> Kamal Kishore B V
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>>
>>> Project Home: http://www.clusterlabs.org
>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
>>>
>>>
>>
>>
>> --
>> esta es mi vida e me la vivo hasta que dios quiera
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>
>>
>
>
> --
> Regards,
> Kamal Kishore B V
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>


-- 
esta es mi vida e me la vivo hasta que dios quiera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140515/3d0e2aa5/attachment-0003.html>