powerapi process dies with no apparent reason

[ghost]

Hi there!

I'm running powerapi v4.2 in 6 different RHEL machines. I created a systemd service that runs powerapi and sends the output to an influxdb database. I noticed a strange behaviour that I would like to share.

In two of these six machines I had, since beginning, 4 processors and 6GB of RAM. Powerapi runs fine but from times to times the process dies and my grafana lacks a lot of data that was not sent to the influxdb since the process has died. After some time the systemd is able to restart the process and the situation normalizes.

In the other four machines I had, in the beginning, one processor and 1GB of RAM. In these machines powerapi sometimes started and sometimes did not. The command line just hang, it seemed to me that the process was waiting to something.

After a lot of analyses, I decided to upgrade the hardware to 2 processors and 4GB of RAM. With this new configuration powerapi started right after I ran the command and everything seemed to work perfectly but after some hours I noticed the same behaviour that I described in the other two machines: from times to times the process simple dies.

I tried v4.0 and after creating the database at influxdb and the retention policy, again, the process starts and from time to time it dies with no apparent reason.

I tried v3.4 and in this version the command line seems more 'responsive'. The process starts right after I hit the enter key in the command line. 3.4 seems ok to me but I noticed that this version doesn't have influxdb support.

In all the tests I ran, I used the same configuration in the powerapi.conf file: powerapi.cpu.tdp = 130

I made some adjustments and started powerapi with more heap memory alocated to the JVM but the behaviour is the same.

So, in the newest version, is there a specific hardware / software requirement to use powerapi? Some clue about this behaviour?