[Linux-HA] cl_status returns empty string

[Nathan Price]

Hi,

At 12:56 PM 10/24/2005 -0500, Guochun Shi <gshi at ncsa.uiuc.edu> wrote:
>can you post the heartbeat log when you run the cl_status command?


Sure. Things have gotten stranger in that 'cl_status rscstatus' has now 
gone back to giving me a value ('all' or 'none' depending on which cluster 
node I'm on). However, this morning, when cl_status was failing, this is 
what I got in /var/log/ha-log:


[root at shaker-n2 backup]# cl_status rscstatus

heartbeat: 2005/10/23_09:42:00 WARN: duplicate client add request 
[cl_status] [18165]
heartbeat: 2005/10/23_09:42:00 ERROR: api_process_registration_msg: cannot 
add client(1)
heartbeat: 2005/10/23_09:42:00 ERROR: api_process_registration_msg: found 
wrong client


Now, it's back to normal, and 'cl_status rscstatus' gives us this:
[root at shaker-n2 backup]# cl_status rscstatus

heartbeat: 2005/10/24_14:06:18 info: EOF from client pid 31617
heartbeat: 2005/10/24_14:06:18 info: Client pid 31617 died (input)
heartbeat: 2005/10/24_14:06:18 info: api_send_client: client 31617 died

Thanks very much,
Nathan

>At 09:40 AM 10/24/2005 -0400, you wrote:
> >Hi -
> >
> >I have been using heartbeat 1.2.3 on a Redhat ES 3 cluster for several 
> months now. Recently I started using 'cl_status rscstatus' to confirm 
> whether a particular node is primary or not. Last week, this command 
> started returning nothing. No answer. It's behaving as if 'rscstatus' is 
> an invalid subcommand, and it's the same on both cluster nodes.  Can 
> anyone offer a suggestion as to why this might be happening?
> >
> >Thanks,
> >Nathan
> >-----------------------------------------------------------------
> >Nathan Price                    Department of Laboratory Medicine
> >System Administrator            Yale-New Haven Hospital
> >nathan.price at yale.edu           New Haven, CT
> >
> >
> >--------------- YNHH/YSM Disclaimer ---------------------------
> >This message originates from Yale New Haven Health System.
> >The information contained in this message may be privileged
> >and confidential. If you are the intended recipient, you must
> >maintain this message in a secure and confidential manner.
> >If you are not the intended recipient, please notify the
> >sender immediately and destroy this message. Thank you.
> >
> >
> >
> >_______________________________________________
> >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

--------------- YNHH/YSM Disclaimer ---------------------------
This message originates from Yale New Haven Health System.
The information contained in this message may be privileged
and confidential. If you are the intended recipient, you must
maintain this message in a secure and confidential manner.
If you are not the intended recipient, please notify the
sender immediately and destroy this message. Thank you.