All Apps and Add-ons

Can switch back to the old mechanism instead of the new fifo implementation in TA-nmon 1.3.x?

whung_splunk
Splunk Employee
Splunk Employee

May I check if there any configuration available to switch back to the old mechanism instead of the new fifo implementation in TA-nmon 1.3.x ?

In my case, some how the nmon is very unstable and stop output 30mins - 4 hours after it start.

It happens on 4 of my servers, but not all (more than 15 in total).

0 Karma
1 Solution

guilmxm
SplunkTrust
SplunkTrust

Hi,

The new release of the TA-nmon with the version 1.3.17 allows you to switch back to the file mode instead of the fifo mode using an option in "nmon.conf" file.

The release is currently in testing but has been qualified already, you can get a copy of it in Git:

UPDATE from 24/05/2017: The release is now under qualification and it is now 1.3.18:

https://github.com/guilhemmarchand/TA-nmon/tree/release

The option to be used is:

`# This option will deactivate the auto switch to fifo mode, in other words the TA-nmon will use the file mode and the old mechanism

unless you encounter unexpected issues, you should not switch to the old mechanism as the foot print is much higher

Default is "1" which means write to fifo

mode_fifo="1"`

This can be set globally a local/nmon.conf to be deployed to your hosts, or on a per server basis by creating the relevant "/etc/nmon.conf" in the servers.

In the meantime, could you please contact me and provide some information about your deployment such that I can try to reproduce the issues you encountered ?

Thank you.

Guilhem

View solution in original post

guilmxm
SplunkTrust
SplunkTrust

Hi,

The new release of the TA-nmon with the version 1.3.17 allows you to switch back to the file mode instead of the fifo mode using an option in "nmon.conf" file.

The release is currently in testing but has been qualified already, you can get a copy of it in Git:

UPDATE from 24/05/2017: The release is now under qualification and it is now 1.3.18:

https://github.com/guilhemmarchand/TA-nmon/tree/release

The option to be used is:

`# This option will deactivate the auto switch to fifo mode, in other words the TA-nmon will use the file mode and the old mechanism

unless you encounter unexpected issues, you should not switch to the old mechanism as the foot print is much higher

Default is "1" which means write to fifo

mode_fifo="1"`

This can be set globally a local/nmon.conf to be deployed to your hosts, or on a per server basis by creating the relevant "/etc/nmon.conf" in the servers.

In the meantime, could you please contact me and provide some information about your deployment such that I can try to reproduce the issues you encountered ?

Thank you.

Guilhem

whung_splunk
Splunk Employee
Splunk Employee

Thank you for your great work!!

I will try upgrade and test the new add-on version later.

0 Karma

guilmxm
SplunkTrust
SplunkTrust

Hi,

Thank for you for your answer.
I try to test and qualify at the most TA-nmon releases, but we're never exempted of unexpected issue specially with old systems.

Feel free to let me know if you encounter any issue.

Kind regards,

Guilhem

0 Karma

leo_wang
Path Finder

Hi,
In nmon.conf :
If I want to switch back to the file mode, So I set :
mode_fifo="0"

What should I set in "nmon2csv_options" ?
(because the default value for this parameter is "--mode fifo" )

0 Karma

guilmxm
SplunkTrust
SplunkTrust

Hello,

I suggest you give a try to the last TA-nmon version before switching back to non fifo.
The last version is release 1.3.21, many issues have been fixed and I don't expect trouble with it.

Any way, to answer your question, yes you set the "mode_fifo=0".
The nmon2csv_options is only used for the sutff behind the fifo mode (basically the fifo_consumer.sh script), if you switch it will just be ignored.

Let me know how this goes for you.

Regards,

Guilhem

0 Karma

guilmxm
SplunkTrust
SplunkTrust

Hi !

Sorry for late reply, it seems I missed the notification of your message.

Well, to answer your question, I have not (yet) anticipated this case, technically everything is in place, and the old mechanism can be easily used.

This would rely in modifying the "bin/nmon_helper.sh" and replace:

    # since release 1.3.0, writing to fifo
    write_to_fifo="true"

By:

    # since release 1.3.0, writing to fifo
    write_to_fifo="false"

After deployment, killing (or wait for its end), and the old mechanism would be used.

However... I would be interested in having some information about the servers that encounter issues, that's unexpected, all systems have been intensively tested and no issues of that kind could be reported, that's weird.

Could you tell me please:

  • The type of OS and version
  • the python version in use (run: python --version)
  • the type and version of Splunk (full vs UF and version)

As well, when the collection stops, are the nmon processes running as expected ?

Thank for your help.

Guilhem

0 Karma

guilmxm
SplunkTrust
SplunkTrust

Additionally, I will add the option in nmon.conf to allow properly switching back to old mechanism if required.

As the nmon.conf can be read on a per server basis as well (/etc/nmon.conf), any one having the same issue could fall back by server.

If you can give some inputs, I am trying to understand what could happen for you.

0 Karma

whung_splunk
Splunk Employee
Splunk Employee

Thanks Guilmxm, about the servers with issue:

The type of OS and version:
A very old version of RedHat Linux (2.6 kernel)

The python version in use (run: python --version):
Should be Python 2.4.6 or something older, so the add-on is using Perl instead of Python.

The type and version of Splunk (full vs UF and version)
Splunk Enterprise 6.5.3 with Splunk Forwarder 6.5.3

TA-nmon-1.2.48 is running stable on the servers with interval around 10 seconds.
(I created different TA-nmon with create_agent.py for different server type)

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...