-
Datas are inconsistency
Hi All,
I’ve installed Pandora FMS console v5.1 SP3
My problem is when I’m opening Tree view, the agents are listed. For example the numbers next to agent name show that there are 3 Normal and 5 Critical modules.
When I’m opening the agent to watch the modules, I can see only 3 critical agent, however the agent shows there are 5 critical modules, because this datas came from another SQL request..The problem is, that I can filter to critical agents, so I can see the agents with at leats one critical module. I’m opening this agent to watch
which is the critical module, but I can see only Normal modules.Is there a good solution for this?
(sorry for my bad english)
Best regards,
Gadge -
7 Replies
-
Hello gadge,
The Pandora FMS version that you are using is too old, and many bugs in older versions have been fixed in the latest. I recommend you to update to the last version (Pandora FMS v6.0SP3) but you said in a different post that this version “is not good for you” (one more time I ask you, why is not good for you Pandora 6.0? Maybe we can help you with this version).
Anyway you can update at least to the latest version of 5.1 (Pandora FMS v5.1SP4) but there is no warranty that this bug is fixed.
Kind regards,
Enrique. -
Hello Enrique,
We have made a lot of modifying and fixed many bugs in the version of 5.1.
The biggest problem was with the ‘Tags’. They don’t working well. When we added a tag to a module (to the other user shoudnt see it), when this module went to critical status
the agent status also changed to critical, so the user saw that the agent status is critical but all of the modules are normal.
This bug is fixed in version of 6.0?Kind regards,
Gadge -
Hello Enrique,
I’ve tried the version of 6.0, and the bug of inconsistency is exist in this version, too.
There is an picture from this bug in the attachment.The agent shows that there is at least one critical module. When I opened the node I cant see any critical module, because meanwhile the module status changed.
I must be better, if this second sql request (nodes of modules, when I’m clicking on agent name) working with the same datas as the first request (nodes of agents, when I’m clicking on agent group), because the datas might be changed after the listing of agents status, and it causes inconsistency.Kind regards,
Gadge
-
Hello Enrique,
I’ve also tested the module tags in the version of 6.0, and it doesn’t work well in this version, too.
There is an picture from this bug in the attachment.In the agent (01) there are two modules: n1 and n2.
Module n2 has got a tag, so the user can see this modul.
Module n1 is invisible for this user, and it is in critical status. However the user cant see any critical module, but the agent status changed to critical. In version 5.1 we have fixed this problem with the tags, but the other bug, the inconsistency in tree view what I’ve written earlier we can’t fix it.Kind regard,
Gadge
-
Hello Gadge,
First of all, the behaviour described of the tags is the normal behaviour of Pandora. The agent status is defined by the worst status of all its modules, so although some modules couldn’t be seen by some agents it can’t affect the agent status (that would be data inconsistency).
Respecting to the tree view I’m trying to replicate your issue, so could you please tell me the user configuration (profiles assigned and tags) and the agent and modules tags?
Kind regards,
Enrique. -
Hello Enrique,
Yes, we modified the source code to avoid the data inconsistency with module tags, so our modified version checks module tags before defines the agent status, it works perfect now.
But the issue with the tree view is an other inconsistency. To replicate this issue is doesnt need any tags or user configuration.
1, If I opened the agent groups in tree view (first sql request) I can see the agents with the numbers of modules statuses (for example Total:13, Critcal:1, Normal:12).
2, Than I open this agent to see modules (second sql request). Now I cant see any critical modules, because after the opening agent group, but before opening agent node the module datas changed in database. So the first and the second request are working with different datas, that causes inconsistency.
Here is an picture, I hope it is understandable.
Thank you for your helping!Kind regards
Gadge
-
Hi gadge,
I can see now what were you saying. The problem with this issue is that its solution could cause performance issues in this view. Bear in mind that some people can have over 100000 modules, and it can take a long time to load the view if we query all this information at the same time.
It isn’t usual that the data change while you are viewing the tree view unless you have this view opened for a long time, and anyway you can reload the page if the data are “inconsistency”.
As the solution would cause more problems, this behaviour will work as it does now.
Kind regards,
Enrique.
