Problem with the poller, the data collection and the Cacti graphs

[NeperUser]

Hi all,
I am new to cacti and I have read some documentation to solve my problems but I have not found anything to correct my problems.

I am currently on version 1.2.23, in a fresh installation, the only difference being that I added 2 devices and the graphs are not displayed with "Failed to open data file, poller may not have run yet" with a "(RRA Folder: Root)" error, when I go to my rra directory of /var/www/html/cacti, it is empty.

I noticed that when I go to the cacti GUI and go to Data collectors, the main poller is in "Heartbeat" status and I can't add a thread.
In my logs, no alert, just a "Graph not added due to no default value for overridable field.".

May I ask if anyone can help me?

[phalek]

You do have a cronjob that starts the poller ?

[NeperUser]

Hey,
as I said above, I'm new (a noob) despite reading the cacti docs, what is a "cronjob"? and does the user have to do it himself? Because in this case, I don't think I have one

[phalek]

Not sure which guide you followed. Here's a link to mine for a RockyLinux / RHEL 8 install:
https://www.urban-software.com/cacti-ho ... kylinux-8/

Basically you are probably missing this step:

Code: Select all

echo "*/1 * * * * apache php /var/www/html/cacti/poller.php &>/dev/null" >> /etc/cron.d/cacti

Make sure to set the cron interval in the cacti settings to "1 Minute" as well.

[TheWitness]

There is a bug in spine that was recently fixed. You might want to pull a fresh copy.

[NeperUser]

Hi, thanks for this answer,

I wanted to know how to pull a fresh copy, because I used the wget command to take the packet from cacti and spine and I wanted to know what exactly I should do.

[keitsi]

Hi, I have Cacti Version 1.2.23 freshly installed, all worked fine until the next morning when I noticed that but Main Poller is in idle state. In the logs I found this:

02-02-2023 06:00:10 - SYSTEM DSDEBUG STATS: Type:poller, ChecksPerformed:1, TotalIssues:4, Time:0.0891
02-02-2023 06:00:10 - CMDPHP PHP ERROR NOTICE Backtrace: (/poller.php[819]:dsdebug_poller_bottom(), /lib/dsdebug.php[223]:rrdtool_cacti_compare(), /lib/rrd.php[2782]:CactiErrorHandler())
02-02-2023 06:00:10 - ERROR PHP NOTICE: Undefined index: step in file: /usr/share/cacti/lib/rrd.php on line: 2782
02-02-2023 06:00:10 - CMDPHP PHP ERROR WARNING Backtrace: (/poller.php[819]:dsdebug_poller_bottom(), /lib/dsdebug.php[196]:filegroup(), CactiErrorHandler())
02-02-2023 06:00:10 - ERROR PHP WARNING: filegroup(): stat failed for /usr/share/cacti/rra/local_linux_machine_sscpusystem_18.rrd in file: /usr/share/cacti/lib/dsdebug.php on line: 196

02-02-2023 04:35:07 - POLLER: Poller[Main Poller] PID[62791] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 304.3 seconds have passed since the last poll!

Can you help me to fix it? Thanks in advance.

[TheWitness]

Well, that's weird... Checking.

[TheWitness]

Okay, on second thought, does your poller have access to the RRA directory? It seems like a permission issue. But still looking.

[TheWitness]

Just took a dig on the code, and yea, your RRDfiles have not been created yet, and if the poller is running, that means that there is a permissions problem.

In the mean time, you found a bug that I'm logging. So, congrats! As a rookie, you found a bug!!!

[alexvelitsky]

Hi guys, I also see such logs:

Cacti Add Graphs Utility, Version 1.2.23 (DB: 1.2.23), Copyright (C) 2004-2023 The Cacti Group

2023-02-21 14:05:06 - POLLER: Poller[1] PID[624922] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 303.8 seconds have passed since the last poll!
2023-02-21 14:10:13 - POLLER: Poller[1] PID[625457] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 307.5 seconds have passed since the last poll!
2023-02-21 15:25:10 - POLLER: Poller[1] PID[643371] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 305.6 seconds have passed since the last poll!
2023-02-21 15:30:13 - POLLER: Poller[1] PID[645391] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 303.0 seconds have passed since the last poll!
2023-02-21 15:55:06 - POLLER: Poller[1] PID[656703] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 305.5 seconds have passed since the last poll!
2023-02-21 16:20:05 - POLLER: Poller[1] PID[669914] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 303.4 seconds have passed since the last poll!
2023-02-21 17:15:06 - POLLER: Poller[1] PID[707809] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 304.2 seconds have passed since the last poll!
2023-02-21 17:50:05 - POLLER: Poller[1] PID[736202] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 304.0 seconds have passed since the last poll!
2023-02-21 18:40:06 - POLLER: Poller[1] PID[783725] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 304.4 seconds have passed since the last poll!
2023-02-21 19:50:06 - POLLER: Poller[1] PID[852157] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 304.9 seconds have passed since the last poll!

is that a problem or I can ignore that carefully?
Thanks!

P.S. Nothing was changed in cacti/server config.

[TheWitness]

You did not include enough info. If you are running spine, you might want to grab a fresh pull of 1.2.x as there was a serious bug. Until you post more infor, I don't have a clue.

[alexvelitsky]

You did not include enough info. If you are running spine, you might want to grab a fresh pull of 1.2.x as there was a serious bug. Until you post more infor, I don't have a clue.

I'm not sure of I'm running spine. How can I check that? What additional info do you need for further investigation?

Thanks.

[TheWitness]

Read the doco. You'll get there.

[alexvelitsky]

Read the doco. You'll get there.

No, I use cmd.php. So which additional data do you need for further investigation?
Thanks.