lpar2rrd-agent.pl 7.90 starts wlmstat on an lpar

apw
apw
edited July 19 in LPAR2RRD

A collegae noticed that wlmstat is started on an lpar. This results in an exitcode <> 0.

We see a test for this in the code but we think the test is wrong.

on lines 2625 and 3918 it says:

if ( $os =~ /AIX/ && ( $wpar_id eq '' || !$wpar_id > 0 || !isdigit($wpar_id) ) ) {

We think it should be converted to:

if ( $os =~ /AIX/ && ( $wpar_id eq '' || $wpar_id > 0 || !isdigit($wpar_id) ) ) {

Notice the exclamation mark on the second $wpar_id I am not a perl programmer so I cannot realy say if this is the rigth solution.

I hope this is the right place to post this. I couldn't find a bug tracker

Comments

  • Pavel
    Pavel

    is there any problem with WLM data?

    Do you see WLM graphs under lpar2rrd UI?

  • apw
    apw
    edited July 24


    https://forum.xorux.com/discussion/comment/6335#Comment_6335

    This is an lpar without a running wlm. We don's see output wlm output in the gui.

    This is what I see when I start wlmstat:

    [root]:/root # wlmstat

    1495-104 WLM must be started.

    [root]:/root # echo $?

    1

    We run lpar2rrd-agent from cron and we see these errors in /var/adm/cron/log

    root   : CMD ( /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl <removed>:8162 >> /var/log/lpar2rrd-agent.out 2>&1 ) : PID ( 13042166 ) : Wed Jul 24 09:59:00 2024

    <lines removed>

    Cron Job with pid: 13042166 Failed

  • Pavel
    Pavel

    and this causes the agent to exit with uncorrrectly? No ...

    what happens when you make the change you suggested, any difference in cronlog?

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Categories

In this Discussion