Cacti 1.1.38 not creating rrd files

[dalamir]

Our cronjob lists www-data as the user to execute the poller.
Doublechecked the permissions on the folder (/usr/share/cacti/site/rra is a symlink to /var/lib/cacti/rra).
Results for adjusted debug attached.

/usr/share/cacti/site/rra# ls -lha
total 40K
drwxrwxrwx 2 www-data www-data 12K Nov 27 11:22 .
drwxr-xr-x 4 root root 4.0K Nov 8 09:56 ..
-rwxrwxrwx 1 www-data www-data 11K Nov 27 11:22 zuidas_spaces_core01_traffic_in_405.rrd
-rwxrwxrwx 1 www-data www-data 5 Nov 27 11:17 zuidas_spaces_core01_traffic_in_406.rrd
-rwxrwxrwx 1 www-data www-data 5 Nov 27 11:17 zuidas_spaces_core01_traffic_in_407.rrd
-rwxrwxrwx 1 www-data www-data 5 Nov 27 11:17 zuidas_spaces_core01_traffic_in_408.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:34 zuidas_spaces_core01_traffic_in_409.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:35 zuidas_spaces_core01_traffic_in_410.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:35 zuidas_spaces_core01_traffic_in_411.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:35 zuidas_spaces_core01_traffic_in_412.rrd
etcetera

ls -lha /var/lib/cacti/rra
total 40K
drwxrwxrwx 2 www-data www-data 12K Nov 27 11:22 .
drwxr-xr-x 4 root root 4.0K Nov 8 09:56 ..
-rwxrwxrwx 1 www-data www-data 11K Nov 27 11:22 zuidas_spaces_core01_traffic_in_405.rrd
-rwxrwxrwx 1 www-data www-data 5 Nov 27 11:17 zuidas_spaces_core01_traffic_in_406.rrd
-rwxrwxrwx 1 www-data www-data 5 Nov 27 11:17 zuidas_spaces_core01_traffic_in_407.rrd
-rwxrwxrwx 1 www-data www-data 5 Nov 27 11:17 zuidas_spaces_core01_traffic_in_408.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:34 zuidas_spaces_core01_traffic_in_409.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:35 zuidas_spaces_core01_traffic_in_410.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:35 zuidas_spaces_core01_traffic_in_411.rrd
-rwxrwxrwx 1 www-data www-data 0 Nov 16 10:35 zuidas_spaces_core01_traffic_in_412.rrd

[netniV]

409 to 412 appear to be zero length RRD files. That seems wrong to me, I would remove them and let the system recreate them. I'm guessing the higher numbers are the same too.

If you see a zero length file, remove it.

[netniV]

Also, check your disk space, df -h

[dalamir]

The whole problem is the fact that new rrd's aren't created at all.
The reason the files are there to begin with, is because I created them manually.
The only files present are for the switch, the firewall files were not made manually and are thus still not present.
Diskspace is plentyfull at this time.

[netniV]

Right but as I think I've said previously, you can not manually create those files. They need to be removed, once removed, run the sudo command I suggested and lets see what happens.

[dalamir]

No joy, see attached file for details.

[netniV]

OK, so there looks to be a clear problem opening/creating those RRD's. Lets dig deeper by running spine manually.

Code: Select all

sudo -u cacti /usr/sbin/spine -C /etc/cacti/spine.conf --poller=1 --first=1 --last=1 --mibs -V 5

Replace the "cacti" with your poller user if its different and increment the numbers in the first/last parameters (I believe your last device is 6). One of these will hopefully give us more information. When you find the one producing the above errors, post that log.

[dalamir]

Morning,

No error from this. See attached file.

[netniV]

I noticed that you ran that as www-data, is that the user that is configured to run poller.php?

[dalamir]

Yes it is, I checked the job within cron.d.

[netniV]

Is SELinux enabled?

[dalamir]

No, apparmor is in use.

[netniV]

Just wondering if it blocking Cacti for some reason. Logically, I can see no reason why the RRDTool can't create the file it needs to. I'll be checking the code to see what commands are used to create the file if it does not exist, if you can run those successfully as the user, that's quite puzzling then.

[dalamir]

Well thanks for all the thoughts and insights, but management has decided to end the life of this particular server.
So this riddle will not be solved.
Till the next one

[Osiris]

App Armor is the SLES version of SELinux. It was likely your culpret.