[Linux-cluster] CS4 update 2 / question again about another "clustat stalled" situation

[Jie Gao]

On Mon, 24 Jul 2006, Lon Hohberger wrote:

> Date: Mon, 24 Jul 2006 17:01:57 -0400
> From: Lon Hohberger <lhh at redhat.com>
> Reply-To: linux clustering <linux-cluster at redhat.com>
> To: linux clustering <linux-cluster at redhat.com>
> Subject: Re: [Linux-cluster] CS4 update 2 / question again about another
>     "clustat stalled" situation
>
> On Mon, 2006-07-24 at 10:18 +0200, Alain Moulle wrote:
> > Hi
> >
> > Another "clustat stalled" situation :
> >
> > It seems that sometimes clustat remains stalled on
> > a recv() on a socket previously opened by clurgmgrd,
> > it it a known bug ? is there a fix ?
> >
> > stack traces of clurgmgrd :
> >  thread 3
> > ??()
> > __GC____select()
> > vf_event_loop()
> > vf_server ()
> > start_thread ()
> > __clone2 ()
> > thread 2
> > ??()
> > pthread_rwlock_wrlock()
> > clu_lock()
> > rg_lock()
> > svc_status ()
> > resgroup_thread ()
> > start_thread()
> > __clone2()
> > thread 1
> > ?? ()
> > __GC___select ()
> > wait_for_dlm_event ()
> > sm_lock()
> > cp_lock ()
> > clu_lock ()
> > rg_lock ()
> > do_status_checks ()
> > event_loop ()
> > main()
> >
> > so why clurgmgrd does not sometimes respond anymore to clustat ?
> >
>
> This is fixed in U4 as well, and packages should be available in the
> beta channel.

As detailed in my previous posts, clurgmgrd does not responde to "kill -TERM"
on one of my U4 nodes.

What should I do without risking a corrput gfs system?

Regards,



Jie