I am deployed Librenms with 25 Cores, 50GB RAM and 500GB of space.
We have completed migrating devices into this instance and I saw that the CPU was hitting 90%. I deployed another poller just with Librenms without the NGINX or the Database and wanted it to be as a poller to the main instance. Ever since that deployment the graphs are broken. I thought it may have been because a misconfig on the poller and I commented out the RRDCACHED config statements and removed the necessary commands from the poller .env file.
Even after this the main instance still has broken graphs.
Jan 27 15:47:27 dc5lp-vlibrenms01 rrdcached[1857526]: * rrdcached started
Jan 27 15:47:27 dc5lp-vlibrenms01 systemd[1]: Started LSB: start or stop rrdcached.
Jan 27 15:59:25 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Jan 27 16:04:02 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Jan 27 17:23:39 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Jan 27 17:58:05 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Jan 27 18:13:46 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Jan 27 18:23:41 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Jan 27 18:28:38 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Jan 27 18:57:34 dc5lp-vlibrenms01 rrdcached[1857616]: handle_request_update: Could not read RRD file.
Have you followed the instructions for running distributed polling? You canβt disable rrdcached in that type of setup and their are some pre-requisites to follow.
Yes. I followed the documentation when I was setting up the main poller and everything was just fine. No issues at all. We had about 1500 devices on that single instance and it was putting up just fine.
Until I setup a poller and configured the .env file. Things started to break and I took off the poller. Now I am trying to get the main instance to work as it was earlier.