I have fixed the problem by null the appstatus when status is noping for 
nodestat -u.  You can see the defect and follow the instruction there to 
download and replace the nodestat.pm file.
https://sourceforge.net/p/xcat/bugs/4652/

Ling

Ling Gao
Poughkeepsie Unix Development Lab
IBM Systems and Technology Group
Internal: T/L 293-5692 
External: [email protected], 845-433-5692

"I never worry about the future. It comes soon enough." --- Albert 
Einstein 



From:   Daniel Letai <[email protected]>
To:     xCAT Users Mailing list <[email protected]>
Date:   04/21/2015 12:44 PM
Subject:        Re: [xcat-user] nodestat -u differs from nodels 
nodelist.appstatus



Yes, always the same 4 nodes.

-f doesn't produce anything, just returns immediately, possibly due to
the fact fping is not installed.

I have performed the following sanity check:
# rpower n01 off
# nodestat -up n01
noping(off)
# nodels n01 nodelist.appstatus nodelist.status
n01: nodelist.appstatus: 
xend=down,sshd=up,rdp=down,https=up,pbs=down,msrpc=down
n01: nodelist.status: noping(off)
# tabch node=n01 nodelist.appstatus=""
# nodels n01 nodelist.appstatus nodelist.status
n01: nodelist.appstatus:
n01: nodelist.status: noping(off)
# nodestat -up n01
noping(off)
# nodels n01 nodelist.appstatus nodelist.status
n01: nodelist.appstatus:
n01: nodelist.status: noping(off)
# rpower n01 on
# nodestat -up n01
sshd,https
# nodels n01 nodelist.appstatus nodelist.status
n01: nodelist.appstatus: 
xend=down,sshd=up,rdp=down,https=up,pbs=down,msrpc=down
n01: nodelist.status: ping

So it seems when a node is not responding (noping), the appstatus
field doesn't update. I assume some kind of code optimization (why
bother checking appstatus for a noping node) but it does present a
slightly more complex logic to my monitoring code,
How hard would it be to modify the code to update the appstatus
regardless of status=noping (or even automatically set everything to
'down')?

On Tue, Apr 21, 2015 at 5:34 PM, Ling Gao <[email protected]> wrote:
> Do you consistently get the sshd=down for the same 4 nodes and their 
status
> is "sshd"?  Can you try "nodestat -up -f compute" and see if you get the
> same result? (Can you clear the appstatus field for each try and compare 
the
> result.?
>
> Ling
>
> Ling Gao
> Poughkeepsie Unix Development Lab
> IBM Systems and Technology Group
> Internal: T/L 293-5692
> External: [email protected], 845-433-5692
>
> "I never worry about the future. It comes soon enough." --- Albert 
Einstein
>
>
>
> From:        Daniel Letai <[email protected]>
> To:        xCAT Users Mailing list <[email protected]>
> Date:        04/21/2015 09:59 AM
> Subject:        [xcat-user] nodestat -u differs from nodels
> nodelist.appstatus
> ________________________________
>
>
>
> Hi,
>
> I'm trying to implement some kind of basic liveness test for nodes in
> the cluster based on results from nodestat -p:
> 1. noping(off) - powered off node
> 2. noping(on) - zombie node
> 3. noping - dead node (both os and ipmi non-responsive)
> 4. sshd - live node
> 5. all else (installing prep etc.)
>
> I have put "nodestat -up" into cron, and nodelist table gets updated
> as expected, however when trying to get the same results I notice some
> big differences.
> For example:
> # nodestat -up compute | grep -v sshd | wc -l
> 48
> # nodels compute nodelist.appstatus=~"sshd=down" | wc -l
> 4
>
> I have confirmed all 4 nodes are a subset of the 48 nodes from nodestat.
> The status column does provide the ping/noping(on|off) info, but for
> most nodes with status noping the appstatus field shows "sshd=up"
>
> Am I missing something?
>
> The xCAT version is 2.8.3
> An upgrade to 2.9.x is not practical at this time (it is scheduled),
> but in any event I hadn't seen anything in the release notes that
> might be relevant.
>
> 
------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live 
exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- 
event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> xCAT-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>
>
>
> 
------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live 
exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- 
event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> xCAT-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live 
exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- 
event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user


------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to