Re: crsd problem

[email protected] wrote:
> 
> >>>>> "Lars" == Lars Marowsky-Bree <[email protected]> writes:
> 
>     Lars> On 2003-06-06T21:43:06, [email protected] said:
> 
>     >> We have a problem with the crsd daemon. What happens is that always
>     >> after a certain amount of time (approx. 6 days) after the crsd has
>     >> started, there is a problem with its ipc communication. This can have
>     >> the unfortunate effect, that resetting will not work anymore when a
>     >> failover has to be done. The fact that this always happens after the
>     >> same time period suggests that some integer counter is overflowing.
> 
>     Lars> Does anything cleanout the /tmp directory and remove the IPC
>     Lars> socket...?
> 
> No, the ipc file is still there after the error message (it is not a socket but
> a mmapped file):
> 
> -rwx------    1 root     root         8220 Jun  4 19:14 /var/run/failsafe/comm/crsd-ipc_ha-test-1

This is a bug in libcrs.so.

Workaround is to restart cluster processes.

or make the following source change and rebuild

FailSafe/cluster_services/lib/libcrs/src/crsl_register.c


@@ -137,7 +137,7 @@
        goto done;
 
     /* Make the handle nonblocking so we do not block trying to connect. */
-    ipcclnt_ctl(newchan->ipchdl, CI_IPC_NON_BLOCK|CI_IPC_NON_PULSE);
+    ipcclnt_ctl(newchan->ipchdl, CI_IPC_NON_BLOCK);
 
     if ((err = ipcclnt_connect(newchan->ipchdl, crslsp->ipc_conn_file,
                               CRS_DAEMON, CI_IPC_NOSIG)) != CI_SUCCESS)


Paddy
> _______________________________________________
> LinuxFailSafe mailing list
> [email protected]
> http://lists.community.tummy.com/mailman/listinfo/linuxfailsafe