Hello all
we are still using our Ubuntu 14.04 LTS Cacti release 0.8.8b+dfsg-5ubuntu0.2 and I know there are newer releases but we were not yet able to upgrade to a newer server.
And this release has all we would need, so maybe this is a reason why we didn't make our upgrade.
Ok, maybe there has to be a problem to start working on. And there we are.
I don't think about a solution more if it could be a known bug on this rather old release.
I added a new generic SNMP enabled host and started typical things from a Linux server.
Placed the server as a new leaf on the tree and added all graphs.
Then it happened, the tree gets completely corrupted. Serverleafs vanished and graphs moved to other leafs.
Even if the parent folder is root the leaf can be drawn within an other leaf.
It happened now the second time and I ask me why.
Could it be when two persons work on the tree at the same time or are there symbols that mustn't be used on the tree?
The positive thing, it's only the tree. All graphs are ok. So I have to clear the tree and rebuild it host by host.
Regards GGA
Graph tree gets corrupt on 0.8.8b
Moderators: Developers, Moderators
Re: Graph tree gets corrupt on 0.8.8b
Probably just a bug. I don't see anything in the changelog offhand that may reference it, except possibly this in 0.8.8d
bug#0002402: Subtree must not have the same header as the parent header
but its been over 5 years since that version, so I don't recall what the issue with that was.
bug#0002402: Subtree must not have the same header as the parent header
but its been over 5 years since that version, so I don't recall what the issue with that was.
Re: Graph tree gets corrupt on 0.8.8b
Hello cigamit
Ah, time is running fast, I see.
I don't think it has to do with that but thank you for your time to check the changelog. I could have thought of that too.
I've checked the mysql db and found the following:
At the corrupt state there are host_id-entries in graph_tree_items-table starting with an 'x'.
I can remove this leading x to fix the entry. It seems so. I didn't make the test with the whole table I've just restored a backup.
Maybe somebody has seen something similar and can remember.
Regards GGA
Ah, time is running fast, I see.
I don't think it has to do with that but thank you for your time to check the changelog. I could have thought of that too.
I've checked the mysql db and found the following:
At the corrupt state there are host_id-entries in graph_tree_items-table starting with an 'x'.
I can remove this leading x to fix the entry. It seems so. I didn't make the test with the whole table I've just restored a backup.
Maybe somebody has seen something similar and can remember.
Regards GGA
Who is online
Users browsing this forum: No registered users and 1 guest