Angelo Venera wrote: > Hi at all, > > i'm new about this list and about HA. I'm trying to build a HA Active/Passive > for this service: > > amavisd clamd.amavisd dhcpd dovecot httpd mysqld named postfix smb > spamassassin squid > > On start the heartbeat run this service and became primary. But when i try > the command nmap on my IPcluster i have this: > > nmap -P0 ha > > Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-04-10 11:28 CEST > Nmap finished: 1 IP address (0 hosts up) scanned in 0.224 seconds > > seem that the clusterip is down without service, instead if i run nmap on the > node ip: > > nmap -P0 nodo1 > > Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-04-10 12:38 CEST > Interesting ports on nodo1 (192.168.1.200): > Not shown: 1678 closed ports > PORT STATE SERVICE > 22/tcp open ssh > 10000/tcp open snet-sensor-mgmt > > Nmap finished: 1 IP address (1 host up) scanned in 0.091 seconds > > all services are down for node ip, and it is ok. > > there are my files configuration: > > drbd.conf > > # > # drbd.conf > # > resource r0 > { > protocol C; > incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; > halt -f"; > startup > { > degr-wfc-timeout 120; # 2 minutes. > } > disk > { > on-io-error detach; > } > net > { > } > syncer > { > rate 100M; > group 1; > al-extents 257; > } > on nodo1 > { > device /dev/drbd0; > disk /dev/hdc2; > address 192.168.1.5:7788; > meta-disk internal; > } > on nodo2 > { > device /dev/drbd0; > disk /dev/hda2; > address 192.168.1.4:7788; > meta-disk internal; > } > } > > > ha.cf > > debugfile /var/log/ha-debug > logfile /var/log/ha-log > logfacility local0 > keepalive 2 > deadtime 30 > bcast eth1 > auto_failback off > node nodo1 nodo2 > crm no > debug 3 > > haresources > > # > # haresources > # > nodo1 IPaddr::192.168.1.210/24/eth0 drbddisk::r0 > Filesystem::/dev/drbd0::/cluster::ext3 amavisd clamd.amavisd dhcpd dovecot > httpd mysqld named postfix smb spamassassin squid > > and my ifconfig is: > > eth0 Link encap:Ethernet HWaddr 00:E0:4C:39:65:E4 > inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::2e0:4cff:fe39:65e4/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:182005 errors:0 dropped:0 overruns:0 frame:0 > TX packets:537446 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:36397105 (34.7 MiB) TX bytes:438135340 (417.8 MiB) > Interrupt:18 Base address:0x4000 > > eth0:0 Link encap:Ethernet HWaddr 00:E0:4C:39:65:E4 > inet addr:192.168.1.210 Bcast:192.168.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:18 Base address:0x4000 > > eth1 Link encap:Ethernet HWaddr 00:0E:2E:AE:DF:4F > inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::20e:2eff:feae:df4f/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:485293 errors:0 dropped:0 overruns:0 frame:0 > TX packets:148794 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:38443850 (36.6 MiB) TX bytes:31554489 (30.0 MiB) > Interrupt:19 Base address:0x6000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:20708 errors:0 dropped:0 overruns:0 frame:0 > TX packets:20708 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1011054 (987.3 KiB) TX bytes:1011054 (987.3 KiB) > > > why this ? And why my service are filtered ?? > > Thank for all. > > P.S. Sorry for my bad english
At the end of every email on this mailing list is > See also: http://linux-ha.org/ReportingProblems This is mostly about sending logs. You didn't send any. You have a pretty complicated configuration. There's no way we can figure anything out without logs. This is why every single email to the mailing lists mentions this ReportingProblems link. Since I've never used nmap, I don't have any idea what to expect from it. In one place you called a node "ha" and in another you called a node "nod01". I would use the ip command or the ifconfig command to see what IP addresses are up or down. That's the usual way to detect that - because it works regardless of whether you're running a firewall or not. You mention that something in the evidence you looked at made you think something was filtered. In general, all Linux distros default to starting firewalls - and they break heartbeat. However, I would assume someone familiar with nmap would already know that. -- Alan Robertson <[EMAIL PROTECTED]> "Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions." - William Wilberforce _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
