Hi list,
Even we faced the same problem with HA 2.0.8 (CentOS release) on
RHEL4. This was resolved by flushing IP chains using command #iptables
-F
One can suggests which all ports CRM uses for communication, and how to
perform selective port openings of those ports. We can even think of
automating these ports opening during installation.
Regards,
Arun.
On 1/26/07, Enrico Morelli <enrico.morelli[at]gmail.com> wrote:
> Dear all,
>
> I have two server using HA 2.0.8 and DRBD named newbeta and newbeta2.
> No firewall is running.
> I had read other messages with the same errors, without found a
solution for me.
> When HA2.0.8 starts on the secondary server I have the following log:
>
> heartbeat[22416]: 2007/01/26_13:17:41 info: **************************
> heartbeat[22416]: 2007/01/26_13:17:41 info: Configuration validated.
> Starting heartbeat 2.0.8
> heartbeat[22417]: 2007/01/26_13:17:42 info: heartbeat: version 2.0.8
> heartbeat[22417]: 2007/01/26_13:17:42 info: Heartbeat generation: 21
> heartbeat[22417]: 2007/01/26_13:17:42 info: G_main_add_TriggerHandler:
> Added signal manual handler
> heartbeat[22417]: 2007/01/26_13:17:42 info: G_main_add_TriggerHandler:
> Added signal manual handler
> heartbeat[22417]: 2007/01/26_13:17:42 info: Removing
> /var/run/heartbeat/rsctmp failed, recreating.
> heartbeat[22417]: 2007/01/26_13:17:42 info: glib: ucast: write socket
> priority set to IPTOS_LOWDELAY on bond0
> heartbeat[22417]: 2007/01/26_13:17:42 info: glib: ucast: bound send
> socket to device: bond0
> heartbeat[22417]: 2007/01/26_13:17:42 info: glib: ucast: bound receive
> socket to device: bond0
> heartbeat[22417]: 2007/01/26_13:17:42 info: glib: ucast: started on
> port 694 interface bond0 to 192.168.0.2
> heartbeat[22417]: 2007/01/26_13:17:42 info: G_main_add_SignalHandler:
> Added signal handler for signal 17
> heartbeat[22417]: 2007/01/26_13:17:42 info: Local status now set to:
'up'
> heartbeat[22417]: 2007/01/26_13:17:44 info: Link newbeta:bond0 up.
> heartbeat[22417]: 2007/01/26_13:17:44 info: Status update for node
> newbeta: status active
> harc[22533]: 2007/01/26_13:17:44 info: Running /etc/ha.d/rc.d/status
status
> heartbeat[22417]: 2007/01/26_13:18:31 info: all clients are now paused
> heartbeat[22417]: 2007/01/26_13:18:56 ERROR: Message hist queue is
> filling up (151 messages in queue)
> heartbeat[22417]: 2007/01/26_13:18:57 ERROR: Message hist queue is
> filling up (152 messages in queue)
> heartbeat[22417]: 2007/01/26_13:18:57 ERROR: Message hist queue is
> filling up (153 messages in queue)
> heartbeat[22417]: 2007/01/26_13:18:58 ERROR: Message hist queue is
> filling up (154 messages in queue)
> heartbeat[22417]: 2007/01/26_13:18:58 ERROR: Message hist queue is
> filling up (155 messages in queue)
> .
> .
> My haresource:
>
> newbeta drbddisk::drbd0 Filesystem::/dev/drbd0::/db_data::xfs
> drbddisk::drbd1 Filesystem::/dev/drbd1::/web_resources::xfs
> drbddisk::drbd2 Filesystem::/dev/drbd2::/lsf1::xfs drbddisk::drbd3
> Filesystem::/dev/drbd3::/proarchive::xfs 150.xxx.xxx.xx apache2
>
>
> My ha.cf:
>
> logfile /var/log/ha-log
> logfacility local0
> deadtime 60
> warntime 50
> ucast bond0 192.168.0.2
> auto_failback on
> node newbeta
> node newbeta2
> respawn root /etc/init.d/apache2
>
> Where I have to check to solve the problem?
> Thanks
> Enrico
> _______________________________________________
> Linux-HA mailing list
> Linux-HA[at]lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
Linux-HA[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
