Pandora FMS Community

Parameter values do not display for plugins in 770 (v7.0NG.770)

aeleus · 16 abr 2023, 22:08 · 8 mensajes · 72 visitas

  1. Inicio del debate

    I previously created a plugin that is a script with parameters. I later updated the plugin by adding more parameters.

    Since I updated to version v7.0NG.770:

    When I edit an existing module that was configured with the plugin before I added more parameters, I see the plugin listed but *none* of the parameters are visible (see first attachment).

    I can select a different plugin and then reselect the original plugin. The parameters are now visible, but the values are blank (see second attachment).

    I can recreate the modules, but I need the parameter values. Is there a way to extract what the parameters are from existing modules when they don't show?

    Untitled-1.png6.3 KB · PNG
    Untitled-1.png
    Untitled-2.png11 KB · PNG
    Untitled-2.png
  2. Hi aeleus,

    We have not been able to replicate your issue, did you update the MR of the machine correctly?

    However, I leave you a SQL query so that you can observe the values of the plugin modules.

    SELECT id_agente AS 'AGENT_ID', nombre AS 'MODULE_NAME',  macros AS 'PLUGIN_FIELDS'FROM tagente_modulo WHEREid_agente = XXX AND nombre LIKE 'YYY';
    

    Don't forget to replace the values XXX (agent ID) and YYYY (module name) for the query to succeed.

    Let us know if you were able to solve the problem and if the SQL query helped you.

  3. Thanks for the quick reply, Vic.

    The sql query works great to get the information out.

    I can create a new module, fill in the fields, and save it. When I open it to edit the fields, they are no longer visible in the console. :-(

    This installation has been running for a while. I've updated it using various methods. I have been using the Warp Update (online) since it has been available - without skipping any.

    Here is the current version:

    From the console, about:

    Pandora FMS

    Version v7.0NG.770 - Community

    MR version MR62

    Build PC230413

    Database status info

    DB Schema Version (first installed)

    6.0dev

    DB Schema Version (actual)

    6.0RC1

    DB Schema Build

    PD150908

    PHP system

    PHP Version

    8.2.3

    PHP Max execution time

    0

    PHP Max input time

    -1

    PHP Memory limit

    800M

    Session cookie lifetime

    0

    yum list installed | grep pandorafms_server

    pandorafms_server.noarch 7.0NG.769-230217 @Artica

    mysql> SELECT * FROM tconfig WHERE token LIKE 'current%';

    +-----------+----------------------------+-------+

    | id_config | token | value |

    +-----------+----------------------------+-------+

    | 87 | current_package_enterprise | 755 |

    | 18681 | current_package | 770 |

    +-----------+----------------------------+-------+

  4. Hi aeleus,

    As far as I can see the settings in the About section are correct.

    I recommend the following:

    Download the Opensource console package and install it again.

    http://firefly.artica.es/pandorafms/770/

    Then I recommend you to clear your browser cache.

    ( The token "| 87 | current_package_enterprise | 755 |" is old, so you can delete it if you want).

    Best regards,

    Víctor.

  5. Before I reinstall, I found this when editing the plugin that is giving me problems.

    Plugin command:

    /usr/share/pandora_server/util/plugin/wget_string.sh

    Plugin parameters:

    _field1_ _field2_ _field3_ _field4_

    Command preview

    /usr/share/pandora_server/util/plugin/wget_string.sh _field1_ _field2_ 0 _field4_

    Notice the "0" where "_field3_" should be. I can retype the parameters, but the "0" just comes back.

    Untitled-1-1.png46 KB · PNG
    Untitled-1-1.png
  6. I am able to reproduce the same behavior in the latest versions of both Edge (chromium) and Firefox on different computers with different profiles as well as in private/incognito.

  7. Hi aeleus,

    The behaviour is normal as the "0" is overriding the _field3_ macro, if you notice it is set to the default values.

    Best regards,

    Víc.

  8. Of course. That's not it then.

    Given the other problems 770 has with inverse intervals, I'd rather roll back to 769 or 767 LTS.

    What's the best way to do that?

Entra en tu cuenta para publicar.