Memory Issues

[knuwanga91]

I have recently installed a cacti server in a Debian 10.0 buster server and it was working fine in the beginning. after I started adding some devices and graphs it suddenly had a spike on memory and keep dropping automatically. I have posted some graphs of the server it self to show how it behaves when the memory spikes. It happens in a pattern and I can't figure out why. I'm new to cacti and this is the first time I'm installing a cacti server. Therefore I do not have any particular background knowledge on this. I have installed the server by doing so many researches and there could be a possibility that I may have made a mistake during the installation. If anyone can help me figuring out what is going on that would be greatly appreciated.

Cacti.png (517.99 KiB) Viewed 419 times

[copemi]

I have recently installed a cacti server in a Debian 10.0 buster server and it was working fine in the beginning. after I started adding some devices and graphs it suddenly had a spike on memory and keep dropping automatically. I have posted some graphs of the server it self to show how it behaves when the memory spikes. It happens in a pattern and I can't figure out why. I'm new to cacti and this is the first time I'm installing a cacti server. Therefore I do not have any particular background knowledge on this. I have installed the server by doing so many researches and there could be a possibility that I may have made a mistake during the installation. If anyone can help me figuring out what is going on that would be greatly appreciated.
Cacti.png

Hello, I will try to help you, however I need more information about it, for example:

1.) What version of cacti did you install?
2.) Do you have some errors in the log tab of web cacti?

[camerabob]

Just a hunch. If you are polling on a five minute cycle, then adding devices will cause the server load to spike every five minutes as the graphs show.

[knuwanga91]

The version I'm currently using is the 1.2.19 and i think I found the solution for the problem. I think there is a bug in 1.2.19 that is causing this issue so there for we have replaced the poller.php to 1.2.16 version and the problem went away.