LPAR2RRD - PowerVM hmc_rest_api.pl errors

sedstr

Long time user of LPAR2RRD - newly built LPAR2RRD/STOR2RRD Debian 10/Buster build.
LPAR2RRD version 7.10-1

OS info Linux

Perl version v5.28.1

Web server info Apache/2.4.38 (Debian)

RRDTOOL version 1.7.1

SQLite version 3.27.2

IBM Power System 20

Few issues - lpar2rrd daemon is listening, and tests resolve OK, but data from OS agents is not appearing, may be related to 42242 lines in error.log-hmc_rest_api

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $poolName in hash element at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1912.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $poolName in string eq at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1919.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $borrowedPoolProcUnits in string at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1927.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $borrowedPoolProcUnits in subtraction (-) at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1928.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $maxProcUnits in subtraction (-) at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1928.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $poolName in hash element at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1912.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $poolName in string eq at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1919.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $borrowedPoolProcUnits in string at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1927.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $borrowedPoolProcUnits in subtraction (-) at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1928.

[Tue Apr 13 10:20:11 2021] hmc_rest_api.pl: Use of uninitialized value $maxProcUnits in subtraction (-) at /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl line 1928.

Tue Apr 13 10:20:37 2021 500:java.lang.NullPointerException File: /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl:2776

Tue Apr 13 10:20:39 2021 500:java.lang.NullPointerException File: /home/lpar2rrd/lpar2rrd/bin/hmc_rest_api.pl:2776

error.log-daemon reports:

[Tue Apr 13 09:56:18 2021] lpar2rrd-daemon.pl: RRDp::end can only be called after RRDp::start at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 6778.

Australian TZ, recently changed to daylight savings, I probably should check all components are on the correct time.

daemon.out

<h1>Software error:</h1>

<pre>RRDp::end can only be called after RRDp::start at /home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl line 6778.

</pre>

<p>

For help, please send mail to this site's webmaster, giving this error message

and the time and date of the error.

</p>

Tue Apr 13 10:00:03 2021: LPAR2RRD server (344169) waiting for client connections on 0.0.0.0:8162

lpar2rrd@tca-infrarrd:~/lpar2rrd/logs$

I've gone though the docs, all pre-req's exist, including the downgrade of liblwp-protocol-https-perl to 6.07-2
I'm sure its something trivial I've missed

If you have any tips, off the top of your head, which I should look for, that'd be appreciated

Pavel

Hi,

1. is HMC test connection working?

2. the agent side, run the agent with "-d" option to force send data immediatelly, any error?

$ /usr/bin/perl /opt/lpar2rrd-agent/lpar2rrd-agent.pl -d <LPAR2RRD-SERVER>

sedstr

HMC connectiosn are working fine, I'm getting all the hypervisor stats, but its producing a lot of events in the log. The HMC is managing several full system Power7 IBM i LPARs as well as Power7s with VIOs plus Power8s with VIOs
Regarding the daemon, yes, I can run the lpar2rrd-agent.pl -d on the VIO servers and it successfully transfers the data, but the daemon on the server is not populating lpar2rrd's files with the data its receiving.
I'll take another look at it later today

Just checked and its all looking good now, the data is showing up in the lpar2rrd interface now. I'll review the logs and see if those errors have gone away. Thanks for checking this out.