Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Yep,
To quote the drbd.conf manual :
http://www.drbd.org/users-guide-emb/re-drbdconf.html
[...]
address AF IP:port
A resource needs one IP address per device, which is used to wait
for incoming connections from the partner device respectively to reach
the partner device. AF must be one of ipv4, ipv6 or sci. It may be
ommited for IPv4 addresses. The actual IPv6 address that follows the
ipv6 keyword must be placed inside brackets.
Each DRBD resource needs a TCP port which is used to connect to
the node's partner device. Two different DRBD resources may not use
the same IP:port combination on the same node.
[...]
Not sure if it is present in any of the tutorial.
Pascal
--
Pascal Charest, Free software consultant {GNU/Linux}
http://blog.pacharest.com
On Fri, Sep 5, 2008 at 2:48 PM, Jeff Orr <jeff at attributor.com> wrote:
> Each resource needs its own port? o.0 In that case I will have to adjust
> the firewall settings on both machines. No matter, it works now. Is this
> mentioned in the DRBD docs, that each resource needs its own port?
>
> Regards,
> Jeff Orr
> Attributor Corporation
>
>
> Pascal Charest wrote:
>> Hi,
>>
>> First, your 2 resources should have different name.
>> Second, you should use a different port for your second resources the
>> first one already being binded by your first resources.
>>
>> That should take care of your problem.
>>
>> Pascal
>>
>> --
>> Pascal Charest, Free software consultant {GNU/Linux}
>> http://blog.pacharest.com
>>
>>
>>
>> On Fri, Sep 5, 2008 at 2:06 PM, Jeff Orr <jeff at attributor.com> wrote:
>>
>>> Hello!
>>>
>>> I have DRBD 8.2.6 up and working on my two CentOS 32-bit servers. Now I
>>> am trying to add a second resource on the machines, I am getting this error:
>>>
>>> /etc/drbd.conf:57: conflicting use of IP 'a.b.c.d:7789' ...
>>> /etc/drbd.conf:31: IP 'a.b.c.d:7789' first used here.
>>>
>>>
>>>
>>> Here is my (sanitized) config file:
>>>
>>> resource datavol {
>>> handlers {
>>> pri-on-incon-degr "echo 'DRBD: primary requested but inconsistent!' |
>>> wall; /etc/init.d/heartbeat stop";
>>> pri-lost-after-sb "echo 'DRBD: primary requested but lost!' | wall;
>>> /etc/init.d/heartbeat stop";
>>> }
>>>
>>> on host1 {
>>> device /dev/drbd1;
>>> disk /dev/sda5;
>>> address a.b.c.d:7789;
>>> meta-disk internal;
>>> }
>>> on host2 {
>>> device /dev/drbd1;
>>> disk /dev/sda5;
>>> address a.b.c.e:7789;
>>> }
>>>
>>> startup {
>>> degr-wfc-timeout 30; #2m timeout
>>> }
>>>
>>> disk {
>>> on-io-error detach;
>>> }
>>> }
>>>
>>> resource datavol {
>>> handlers {
>>> pri-on-incon-degr "echo 'DRBD: primary requested but inconsistent!' |
>>> wall; /etc/init.d/heartbeat stop";
>>> pri-lost-after-sb "echo 'DRBD: primary requested but lost!' | wall;
>>> /etc/init.d/heartbeat stop";
>>> }
>>>
>>> on host1 {
>>> device /dev/drbd5;
>>> disk /dev/loop1;
>>> address a.b.c.d:7789;
>>> meta-disk internal;
>>> }
>>> on host2 {
>>> device /dev/drbd5;
>>> disk /dev/loop1;
>>> address a.b.c.e:7789;
>>> meta-disk internal;
>>> }
>>> }
>>>
>>>
>>> If I leave the 'address' lines off the second resource, I get a 'missing
>>> address' error. Any thoughts?
>>>
>>> Regards,
>>> Jeff Orr
>>> Attributor Corporation
>>> _______________________________________________
>>> drbd-user mailing list
>>> drbd-user at lists.linbit.com
>>> http://lists.linbit.com/mailman/listinfo/drbd-user
>>>
>>>
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>