Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind (Ken Gaillot)
On Wed, Mar 16, 2016 at 9:35 PM, Mike Bernhardt wrote: > I guess I have to say "never mind!" I don't know what the problem was > yesterday, but it loads just fine today, even when the named config and the > virtual ip don't match! But for your edamacation, ifconfig does NOT show the > address although ip addr does: > That's normal. ifconfig knows nothing about addresses added using "ip addr add". You can make it visible to ifconfig by adding label: ip addr add dev eth1 ... label eth1:my-label ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind (Ken Gaillot)
On 17.03.2016 08:45, Andrei Borzenkov wrote: > On Wed, Mar 16, 2016 at 9:35 PM, Mike Bernhardt wrote: >> I guess I have to say "never mind!" I don't know what the problem was >> yesterday, but it loads just fine today, even when the named config and the >> virtual ip don't match! But for your edamacation, ifconfig does NOT show the >> address although ip addr does: >> > > That's normal. ifconfig knows nothing about addresses added using "ip > addr add". You can make it visible to ifconfig by adding label: > > ip addr add dev eth1 ... label eth1:my-label Just stop using ifconfig/route and keep using the ip command. ifconfig/route have been deprecated for a decade now and I know old habits die hard but at some point you just have to move on otherwise you might end up like those admins who stopped learning in the 80s and now haunt discussion forums mostly contributing snark and negativity because they've come to hate their jobs. Regards, Dennis ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind
On 03/15/2016 06:47 PM, Mike Bernhardt wrote: > Not sure if this is a BIND question or a PCS/Corosync question, but > hopefully someone has done this before: > > > > I'm setting up a new CentOS 7 DNS server cluster to replace our very old > CentOS 4 cluster. The old one uses heartbeat which is no longer supported, > so I'm now using pcs, corosync, and pacemaker. The new one is running the > latest 9.10.x production release of BIND. I want BIND to listen on, query > from, etc on a particular IP address, which is virtualized with pacemaker. > > > > This worked fine on the old cluster. But whereas heartbeat would create a > virtual subinterface (i.e. eth0:0) to support the virtual IP, corosync does > not do that; at least it doesn't by default. So although the virtual IP > exists and is pingable, it is not tied to a "physical" interface- ifconfig > does not find it. And when BIND tries to start up, it fails because it can't > find the virtual IP it's configured to run on, even though it is reachable. > I only need IPv4, not IPv6. The old subinterfaces are no longer neded in linux-land for "virtual" IPs, which are now actually full-class citizens, just one of multiple IPs assigned to the interface. ifconfig (or its fashionably new alternative, "ip addr") should show both addresses on the same interface. BIND shouldn't have any problems finding the IP. Can you show the error messages that come up, and your pacemaker configuration? > > > So, I'm hoping that there is a way to tell corosync (hopefully using pcsd) > to create a virtual interface, not just a virtual address, so BIND can find > it. > > > > Thanks in advance! ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] PCS, Corosync, Pacemaker, and Bind (Ken Gaillot)
I guess I have to say "never mind!" I don't know what the problem was yesterday, but it loads just fine today, even when the named config and the virtual ip don't match! But for your edamacation, ifconfig does NOT show the address although ip addr does: ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:50:56:8b:d0:f7 brd ff:ff:ff:ff:ff:ff inet 192.168.30.36/26 brd 192.168.30.63 scope global eth0 valid_lft forever preferred_lft forever inet 192.168.30.38/26 brd 192.168.30.63 scope global secondary eth0 valid_lft forever preferred_lft forever ifconfig -a eth0 eth0: flags=4163 mtu 1500 inet 192.168.30.36 netmask 255.255.255.192 broadcast 192.168.30.63 ether 00:50:56:8b:d0:f7 txqueuelen 1000 (Ethernet) RX packets 1169357 bytes 163514247 (155.9 MiB) RX errors 0 dropped 4639 overruns 0 frame 0 TX packets 1351613 bytes 210957790 (201.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org