Re: [Pacemaker] IPaddr2 started but "not working"
Am Montag, 28. Oktober 2013, 11:15:07 schrieb Francesco Namuri: > Il 28/10/2013 10.38, Michael Schwartzkopff ha scritto: > > Am Montag, 28. Oktober 2013, 10:25:47 schrieb Francesco Namuri: > >> Hi Lars, > >> > >> Il 28/10/2013 09.56, Lars Marowsky-Bree ha scritto: > >>> On 2013-10-28T09:38:34, Francesco Namuri wrote: > Hi, > I've a problem with a IPaddr2 resource, it appears to be started > correctly and it works for a while, but after it appears "to be > hanged", > it doesn't work until I send it a restart. > Does anyone has experienced similar issue? > >>> > >>> You're running it in cluster-ip mode; why? > >> > >> Is that question related to the cluster-ip parameter? > >> I removed it from the cluster ip of the WLAN... > >> > --code-- > primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ > > params ip="172.16.15.254" cidr_netmask="32" > > clusterip_hash="sourceip-sourceport" \ > > op monitor interval="10s" \ > meta target-role="Started" > > > >>> > >>> I'd suggest to drop the "clusterip_hash" parameter, unless you're also > >>> running it as a clone. (In which case seeing your full configuration > >>> would be needed.) > >> > >> I put the "clusterip_hash" option, thinking that it could help to avoid > >> dropping established connections when I switch from one node to the > >> other. > >> I followed a howto, but I'm really not sure about that. > > > > No. I will not preserve connections from one node to the other. > > If you are not sure, do not configure it. > > If you don't know what it does, do not configure it. > > It's always a good advice :) > I remove it from all the configuration. > Is there a method to avoid dropping connection when I switched from a > node to another? Generally: No. Only in very limited cases, when the applications provides a state table sync. This is the case i.e. for iptables firewalls and ipvs load balancers. In some cases the tcp stack can recover the connection and some times the applications can recover (FTP, downloads in HTTP, ...) or just retry. But in most cases the users will have to press "reload" or something comparable. -- Mit freundlichen Grüßen, Michael Schwartzkopff -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein signature.asc Description: This is a digitally signed message part. ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] IPaddr2 started but "not working"
Il 28/10/2013 10.38, Michael Schwartzkopff ha scritto: > Am Montag, 28. Oktober 2013, 10:25:47 schrieb Francesco Namuri: >> Hi Lars, >> >> Il 28/10/2013 09.56, Lars Marowsky-Bree ha scritto: >>> On 2013-10-28T09:38:34, Francesco Namuri wrote: Hi, I've a problem with a IPaddr2 resource, it appears to be started correctly and it works for a while, but after it appears "to be hanged", it doesn't work until I send it a restart. Does anyone has experienced similar issue? >>> You're running it in cluster-ip mode; why? >> Is that question related to the cluster-ip parameter? >> I removed it from the cluster ip of the WLAN... >> --code-- primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ params ip="172.16.15.254" cidr_netmask="32" clusterip_hash="sourceip-sourceport" \ op monitor interval="10s" \ meta target-role="Started" >>> I'd suggest to drop the "clusterip_hash" parameter, unless you're also >>> running it as a clone. (In which case seeing your full configuration >>> would be needed.) >> I put the "clusterip_hash" option, thinking that it could help to avoid >> dropping established connections when I switch from one node to the other. >> I followed a howto, but I'm really not sure about that. > No. I will not preserve connections from one node to the other. > If you are not sure, do not configure it. > If you don't know what it does, do not configure it. It's always a good advice :) I remove it from all the configuration. Is there a method to avoid dropping connection when I switched from a node to another? Thanks for all you answers, and sorry for my dumb question, I'm really a newbie with clusters... :) Best regards, Francesco ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] IPaddr2 started but "not working"
Am Montag, 28. Oktober 2013, 10:25:47 schrieb Francesco Namuri: > Hi Lars, > > Il 28/10/2013 09.56, Lars Marowsky-Bree ha scritto: > > On 2013-10-28T09:38:34, Francesco Namuri wrote: > >> Hi, > >> I've a problem with a IPaddr2 resource, it appears to be started > >> correctly and it works for a while, but after it appears "to be hanged", > >> it doesn't work until I send it a restart. > >> Does anyone has experienced similar issue? > > > > You're running it in cluster-ip mode; why? > > Is that question related to the cluster-ip parameter? > I removed it from the cluster ip of the WLAN... > > >> --code-- > >> primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ > >> > >> params ip="172.16.15.254" cidr_netmask="32" > >> > >> clusterip_hash="sourceip-sourceport" \ > >> > >> op monitor interval="10s" \ > >> meta target-role="Started" > >> > >> > > > > I'd suggest to drop the "clusterip_hash" parameter, unless you're also > > running it as a clone. (In which case seeing your full configuration > > would be needed.) > > I put the "clusterip_hash" option, thinking that it could help to avoid > dropping established connections when I switch from one node to the other. > I followed a howto, but I'm really not sure about that. No. I will not preserve connections from one node to the other. If you are not sure, do not configure it. If you don't know what it does, do not configure it. -- Mit freundlichen Grüßen, Michael Schwartzkopff -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein signature.asc Description: This is a digitally signed message part. ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] IPaddr2 started but "not working"
Hi Lars, Il 28/10/2013 09.56, Lars Marowsky-Bree ha scritto: > On 2013-10-28T09:38:34, Francesco Namuri wrote: > >> Hi, >> I've a problem with a IPaddr2 resource, it appears to be started >> correctly and it works for a while, but after it appears "to be hanged", >> it doesn't work until I send it a restart. >> Does anyone has experienced similar issue? > You're running it in cluster-ip mode; why? Is that question related to the cluster-ip parameter? I removed it from the cluster ip of the WLAN... >> --code-- >> primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ >> params ip="172.16.15.254" cidr_netmask="32" >> clusterip_hash="sourceip-sourceport" \ >> op monitor interval="10s" \ >> meta target-role="Started" >> > I'd suggest to drop the "clusterip_hash" parameter, unless you're also > running it as a clone. (In which case seeing your full configuration > would be needed.) I put the "clusterip_hash" option, thinking that it could help to avoid dropping established connections when I switch from one node to the other. I followed a howto, but I'm really not sure about that. This is my full config: node apollo node daphne primitive bind9 lsb:bind9 \ op monitor interval="30s" timeout="15s" primitive cluster_ip_dmz ocf:heartbeat:IPaddr2 \ params ip="192.168.253.254" cidr_netmask="32" clusterip_hash="sourceip-sourceport" \ op monitor interval="30s" \ meta target-role="Started" primitive cluster_ip_patton ocf:heartbeat:IPaddr2 \ params ip="172.16.17.254" cidr_netmask="32" clusterip_hash="sourceip-sourceport" \ op monitor interval="30s" \ meta target-role="Started" primitive cluster_ip_snoop ocf:heartbeat:IPaddr2 \ params ip="172.16.16.254" cidr_netmask="32" clusterip_hash="sourceip-sourceport" \ op monitor interval="30s" \ meta target-role="Started" primitive cluster_ip_wks ocf:heartbeat:IPaddr2 \ params ip="192.168.1.254" cidr_netmask="32" clusterip_hash="sourceip-sourceport" \ op monitor interval="30s" \ meta target-role="Started" primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ params ip="172.16.15.254" cidr_netmask="32" \ op monitor interval="10s" \ meta target-role="Started" primitive dlm ocf:pacemaker:controld \ op monitor interval="120s" primitive gfs_control ocf:pacemaker:controld \ params daemon="gfs_controld.pcmk" args="-g 0" \ op monitor interval="120s" primitive shared_drbd ocf:linbit:drbd \ params drbd_resource="shared" \ op monitor interval="60s" primitive shared_fs ocf:heartbeat:Filesystem \ params device="/dev/drbd/by-res/shared" directory="/shared" fstype="gfs2" primitive squid3 lsb:squid3 \ op start interval="0" timeout="120s" \ op stop interval="0" timeout="120s" \ op monitor interval="20s" timeout="30s" \ meta target-role="Started" ms shared_data_clone shared_drbd \ meta master-max="2" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" target-role="Started" clone dlm_clone dlm \ meta interleave="true" target-role="Started" clone gfs_clone gfs_control \ meta interleave="true" target-role="Started" clone shared_fs_clone shared_fs \ meta target-role="Started" location cli-prefer-bind9 bind9 \ rule $id="cli-prefer-rule-bind9" inf: #uname eq daphne location cli-prefer-cluster_ip_dmz cluster_ip_dmz \ rule $id="cli-prefer-rule-cluster_ip_dmz" inf: #uname eq daphne location cli-prefer-cluster_ip_snoop cluster_ip_snoop \ rule $id="cli-prefer-rule-cluster_ip_snoop" inf: #uname eq apollo location cli-prefer-cluster_ip_wks cluster_ip_wks \ rule $id="cli-prefer-rule-cluster_ip_wks" inf: #uname eq daphne location cli-prefer-squid3 squid3 \ rule $id="cli-prefer-rule-squid3" inf: #uname eq daphne colocation cluster_ips0 inf: cluster_ip_dmz cluster_ip_wks colocation cluster_ips1 inf: cluster_ip_wlan cluster_ip_wks colocation cluster_ips2 inf: cluster_ip_patton cluster_ip_wks colocation cluster_ips3 inf: cluster_ip_snoop cluster_ip_wks colocation fs_on_drbd inf: shared_fs_clone shared_data_clone:Master colocation gfs_with_dlm inf: gfs_clone dlm_clone colocation services_with_ips inf: cluster_ip_wks squid3 bind9 colocation shared_fs_with_gfs_control inf: shared_fs_clone gfs_clone order shared_fs_after_shared_data inf: shared_data_clone:promote shared_fs_clone:start order start_gfs_after_dlm inf: dlm_clone gfs_clone order start_services_after_cluster_ips inf: cluster_ip_wks bind9 squid3 order start_shared_fs_after_gfs_control inf: gfs_clone shared_fs_clone property $id="cib-bootstrap-options" \ dc-version="1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" \ stop-all-resources="false" \ last-lrm-refresh="1382949596" r
Re: [Pacemaker] IPaddr2 started but "not working"
hi, i am not sure but i am using the nic parameter,too. it should be used the nic from the routing table but maybe that´s the problem. primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ params ip="172.16.15.254" cidr_netmask="32" nic="" \ op monitor interval="10s" \ op timeout="20s" \ meta target-role="Started" regards, beo 2013/10/28 Lars Marowsky-Bree > On 2013-10-28T09:38:34, Francesco Namuri wrote: > > > Hi, > > I've a problem with a IPaddr2 resource, it appears to be started > > correctly and it works for a while, but after it appears "to be hanged", > > it doesn't work until I send it a restart. > > Does anyone has experienced similar issue? > > You're running it in cluster-ip mode; why? > > > --code-- > > primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ > > params ip="172.16.15.254" cidr_netmask="32" > > clusterip_hash="sourceip-sourceport" \ > > op monitor interval="10s" \ > > meta target-role="Started" > > > > I'd suggest to drop the "clusterip_hash" parameter, unless you're also > running it as a clone. (In which case seeing your full configuration > would be needed.) > > > Regards, > Lars > > -- > Architect Storage/HA > SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix > Imendörffer, HRB 21284 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > > ___ > Pacemaker mailing list: Pacemaker@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 > ___ Pacemaker mailing list: Pacemaker@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
Re: [Pacemaker] IPaddr2 started but "not working"
On 2013-10-28T09:38:34, Francesco Namuri wrote: > Hi, > I've a problem with a IPaddr2 resource, it appears to be started > correctly and it works for a while, but after it appears "to be hanged", > it doesn't work until I send it a restart. > Does anyone has experienced similar issue? You're running it in cluster-ip mode; why? > --code-- > primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ > params ip="172.16.15.254" cidr_netmask="32" > clusterip_hash="sourceip-sourceport" \ > op monitor interval="10s" \ > meta target-role="Started" > I'd suggest to drop the "clusterip_hash" parameter, unless you're also running it as a clone. (In which case seeing your full configuration would be needed.) Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde ___ Pacemaker mailing list: Pacemaker@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
[Pacemaker] IPaddr2 started but "not working"
Hi, I've a problem with a IPaddr2 resource, it appears to be started correctly and it works for a while, but after it appears "to be hanged", it doesn't work until I send it a restart. Does anyone has experienced similar issue? Best Regards, Francesco Namuri --code-- primitive cluster_ip_wlan ocf:heartbeat:IPaddr2 \ params ip="172.16.15.254" cidr_netmask="32" clusterip_hash="sourceip-sourceport" \ op monitor interval="10s" \ meta target-role="Started" ___ Pacemaker mailing list: Pacemaker@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
