Pandora FMS Community

[Solved] - Pandora_Module_Exec: TCP_Connections did not executed well (retcode: 255)

dvs-ag · 22 oct 2020, 18:53 · 2 mensajes · 54 visitas

  1. Inicio del debate

    Hello everybody, a few days ago I started installing and configuring Pandora FMS Community (PandoraFMS7.0NG.749.x86_64). The Setup of the many Windows Server 2012 R2 Agents (Pandora FMS Windows Agent v7.0NG.749_x86_64) worked perfectly, except for one server. As with the other servers before, I installed the Agent, but not all basic modules are transferred to the server. The only basic module that has been transferred is the module "CPU Load". But it is possible to add some WMI modules via Pandora FMS GUI which are working without any issues. The "pandora_agent.conf" is unchanged and has not been modified. So I looked in the "pandora_agent.log", in which the following was recorded:

    2020-10-22 15:08:36 Pandora agent stopped 2020-10-22 15:09:08 Pandora agent started 2020-10-22 15:09:09 Pandora_Module_Exec: TCP_Connections did not executed well (retcode: 255) 2020-10-22 15:09:09 Pandora_Module_Exec: plugin did not executed well (retcode: 1) 2020-10-22 15:09:09 Pandora_Module_Exec: plugin did not executed well (retcode: 1) 2020-10-22 15:09:09 Pandora_Module_Exec: plugin did not executed well (retcode: 1) 2020-10-22 15:09:10 Pandora_Module_Exec: plugin did not executed well (retcode: -1)

    I've googled quite a bit, but couldn't find a solution to the problem. In connection with the return code 255 I read various things on the Internet, such as problems with the environment path etc. but everything looks fine on this server. Can anyone help me with some ideas?

    Thank you in advance.

  2. Problem solved. The issues was caused due to a false registry entry. The registry key for the environment path was set as "reg_sz" but to work properly with entrys like "%systemroot%" it has to be set as "reg_expand_sz". We got a backup system which was cloned from this server and on this clone the registry key is set properly, so I don't know how this could happened...

Entra en tu cuenta para publicar.