Update to 769 broke Execution_Time module

[Sergio]

Like it

Up

0

Down

Drop it

::

Hello,

Thanks for letting us know about this issue.

We were able to replicate the problem and we’ll proceed now to open a ticket with our development team.

Thank you very much for the feedback, we’ll let you know once it is solved.

Kind regards,

Sergio B.

[aeleus]

Like it

Up

0

Down

Drop it

::

Thanks Sergio.

I installed version v7.0NG.770 2 days ago hoping that would fix the problem with Execution_Time.

Instead, the problem has expanded to include 6 more modules:

Execution_Time N/A – N/A 180,006 us 2 months

Performance

RECONSERVER Consumer #1 Processing Rate N/A – N/A 0 tasks/second 2 days

RECONSERVER Consumer #2 Processing Rate N/A – N/A 0 tasks/second 2 days

RECONSERVER Producer Processing Rate N/A – N/A 0 tasks/second 2 days

System

RECONSERVER Consumer #1 Status N/A – N/A 1 2 days

RECONSERVER Consumer #2 Status N/A – N/A 1 2 days

RECONSERVER Producer Status N/A – N/A 1 2 days

[Sergio]

Like it

Up

0

Down

Drop it

::

Hello Aeleus,

Yes, we are aware of this new modules being unknown now.

The Reconserver is now called Discovery sever so those modules you can delete them as this was a change made by our dev team.

The Execution_Time Module will be fixed for the next LTS release v772.

Thanks for your information on this!

Kind regards,

Sergio B.

[David]

Like it

Up

0

Down

Drop it

::

Hello Sergio.

I have the same problem in the execution_time module since the update to version 769.

I have updated to version 772 this week but the problem continues.

kind regards.

[Sergio]

Like it

Up

0

Down

Drop it

::

Hello David,

Finally the Execution_Time module has been deprecated and removed from PandoraFMS.

You can now simple delete that module and you will no longer have the Unknown.

Kind regards,

Sergio B.