crsd problem

Hi,

if anybody knowledgable is still listening.

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.

Does anybody have a suggestion what could be the cause?

This is the type of log message we get:

Thu Jun  5 11:05:25.149 <N crsd crs 681:0 crsd_main.c:200> Crsd restarted.
Thu Jun  5 11:08:32.159 <W crsd ipc 681:0 ipc_serv.c:859> CI_IPCERR_NOCONN, ipcserv_pulse(): Client already closed connection.
Thu Jun  5 11:08:32.159 <W crsd ipc 681:0 ipc_serv.c:735> CI_IPCERR_NOCONN, ipcserv_recvcheck(): Client failed to pulse 
Thu Jun  5 11:08:33.169 <W crsd crs 681:0 crsd_local.c:142> CI_FAILURE, Client 0x804cc39 moves to DEREGISTERED state due to broken connection.
Thu Jun  5 11:12:30.744 <W crsd ipc 681:0 ipc_serv.c:859> CI_IPCERR_NOCONN, ipcserv_pulse(): Client already closed connection.
Thu Jun  5 11:12:30.744 <W crsd ipc 681:0 ipc_serv.c:735> CI_IPCERR_NOCONN, ipcserv_recvcheck(): Client failed to pulse 
Thu Jun  5 11:14:32.039 <W crsd crs 681:0 crsd_local.c:142> CI_FAILURE, Client 0x804cc39 moves to DEREGISTERED state due to broken connection.
Thu Jun  5 11:21:31.817 <W crsd ipc 681:0 ipc_serv.c:859> CI_IPCERR_NOCONN, ipcserv_pulse(): Client already closed connection.
Thu Jun  5 11:21:31.817 <W crsd ipc 681:0 ipc_serv.c:735> CI_IPCERR_NOCONN, ipcserv_recvcheck(): Client failed to pulse 
Thu Jun  5 11:21:32.206 <W crsd crs 681:0 crsd_local.c:142> CI_FAILURE, Client 0x804cc39 moves to DEREGISTERED state due to broken connection.

Thanks,

Roland