topic Re: TA-nmon failed to stay running on some servers in All Apps and Add-ons

TA-nmon failed to stay running on some servers

samstar — Tue, 29 Sep 2020 19:25:46 GMT

We deployed TA-nmon on 200+ servers and there are 13 servers failed to collect data and the error message as below.
I have tried to change the interval to a much bigger number, but it still fail.

4/30/18
11:59:24.000 PM
30-04-2018 23:59:24, syxxxx02 INFO: found Nmon running with PID 27814
host = syxxxx02 source = nmon_collect sourcetype = nmon_collect
4/30/18
11:59:24.000 PM
30-04-2018 23:59:24, syxxxx02 INFO: Nmon process is 47678 sec old, a new process will be spawned when this value will be greater than estimated end in seconds (86160 sec based on parameters)
host = syxxxx02 source = nmon_collect sourcetype = nmon_collect

Re: TA-nmon failed to stay running on some servers

guilmxm — Mon, 07 May 2018 13:05:15 GMT

Hello,

From the logs you shared, it looks like the nmon process is starting correctly, if you cannot find metrics data for these 13 failing servers, the issue might be failing requirements for them.

Please have a look at the trouble shooting guide: link text

The TA-nmon requirements are here: link text

Certainly these system are reverting to Perl intepreter (No Python 2.7.x locally available) but the perl-Time-HiRes perl module would not be available.

Have a look at splunkd logs:

index=_internal sourcetype=splunkd host=<you server>

If requirements are not meet, you will see Perl exceptions here.
This would be visible as well in notable events from the home page.

Feel free to let me know.

Kind regards,

Guilhem

Re: TA-nmon failed to stay running on some servers

samstar — Tue, 08 May 2018 04:31:29 GMT

Thanks a lot Guilhem.

That exactly the problem is. After installing the perl module. getting the data now.

Sam