Cacti RRD sizes

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

frist44 wrote:Data source Debug:

/usr/bin/rrdtool create \
/var/www/cacti/rra/pnm9_traffic_out_89.rrd \
--step 300 \
DS:traffic_in:COUNTER:600:0:100000000 \
DS:traffic_out:COUNTER:600:0:100000000 \
RRA:AVERAGE:0.5:1:288000 \
The path is quite uncommon. You do have all rrd files under /var/www/cacti/rra, not /var/www/html/cacti/rra?
Reinhard
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

yes, that's where I placed the cacti folder. In debian, there's where my default html is by default.

When I add a device, all the rra's are created in that folder, except the one I configured with the larger bucket size. I'm just unsure why it doesn't create that one.

any idea?

The file /var/www/cacti/rra/pnm9_traffic_out_89.rrd is what's missing.

~$ ls -lh /var/www/cacti/rra
total 5.6M
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev5_cpu_28.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev5_cpu_29.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev5_cpu_30.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev5_cpu_31.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev5_hdd_used_25.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev5_hdd_used_26.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 09:25 dev5_hdd_used_27.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev5_hdd_used_45.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev5_proc_24.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev5_traffic_in_32.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev5_users_48.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev6_cpu_40.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev6_cpu_41.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev6_cpu_42.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev6_cpu_43.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev6_hdd_used_35.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev6_hdd_used_36.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev6_hdd_used_37.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev6_hdd_used_38.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev6_hdd_used_39.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev6_hdd_used_46.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev6_proc_34.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev6_traffic_in_44.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev6_users_33.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev7_cpu_19.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev7_cpu_20.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev7_cpu_21.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev7_cpu_22.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev7_hdd_used_14.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev7_hdd_used_15.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev7_hdd_used_16.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev7_hdd_used_17.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev7_hdd_used_18.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev7_hdd_used_47.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev7_proc_12.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev7_proc_9.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 dev7_traffic_in_23.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 dev7_users_8.rrd
-rw-r--r-- 1 root root 139K 2009-02-14 10:30 localhost_load_1min_5.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 localhost_mem_buffers_3.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 localhost_mem_swap_4.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 localhost_proc_7.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 localhost_users_6.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 pnm12_cpu_66.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 pnm12_cpu_67.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 pnm12_hdd_used_63.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 pnm12_hdd_used_64.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 pnm12_hdd_used_65.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 pnm12_proc_70.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 pnm12_traffic_in_68.rrd
-rw-r--r-- 1 root root 47K 2009-02-14 10:30 pnm12_users_69.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_54.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_55.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_56.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_57.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_58.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_59.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_60.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_cpu_61.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_77.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_78.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_79.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_80.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_81.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_82.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_83.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_cpu_84.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 15:15 pnm9_hdd_used_51.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 15:15 pnm9_hdd_used_52.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 15:15 pnm9_hdd_used_53.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 16:00 pnm9_hdd_used_74.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 16:00 pnm9_hdd_used_75.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 16:00 pnm9_hdd_used_76.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 pnm9_hdd_used_86.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 pnm9_hdd_used_87.rrd
-rw-r--r-- 1 root root 93K 2009-02-14 10:30 pnm9_hdd_used_88.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_proc_50.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_proc_73.rrd
-rw-r--r-- 1 root root 93K 2009-02-13 15:10 pnm9_traffic_in_62.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 15:15 pnm9_users_49.rrd
-rw-r--r-- 1 root root 47K 2009-02-13 16:00 pnm9_users_72.rrd
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

Your crontab runs the poller as root?
This is NOT recommended. But all rrd files are created this way. Assuming, that only root can create new files in rra/ folder, running the poller as cactiuser will result in such a behaviour
Reinhard
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

The poller is running as root. I entered it manually.
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

I ran this command manually

/usr/bin/rrdtool create \
/var/www/cacti/rra/pnm9_traffic_out_89.rrd \
--step 300 \
DS:traffic_in:COUNTER:600:0:100000000 \
DS:traffic_out:COUNTER:600:0:100000000 \
RRA:AVERAGE:0.5:1:288000 \

and got a file size of 4.4M, which makes sense as the size is significantly increased.

So i guess the question now is why isn't initially created when the device is added.
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

Answer to this question is usually derived from cacti.log when running in debug mode. But as the file is created now, this part will be skipped. I just asked myself, if "System Utilities -> View Poller cache" shows an entry related to that rrd file. This would be a reason why the file is not created.
Reinhard
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

There is no entry in the poller cache for that file.
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

gandalf wrote:Answer to this question is usually derived from cacti.log when running in debug mode. But as the file is created now, this part will be skipped. I just asked myself, if "System Utilities -> View Poller cache" shows an entry related to that rrd file. This would be a reason why the file is not created.
Reinhard
how do you enter debug mode? I know about the data source debug and graph debug, but are you referring to a system debug?
User avatar
gandalf
Developer
Posts: 22383
Joined: Thu Dec 02, 2004 2:46 am
Location: Muenster, Germany
Contact:

Post by gandalf »

See 2nd link of my sig. It's the poller DEBUG
Reinhard
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

These are the lines associated with that device:

02/14/2009 12:25:08 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'1146', SQL:"SELECT name, file, function FROM plugin_hooks WHERE status = 1 AND hook = 'poller_bottom'"
02/14/2009 12:25:08 PM - SYSTEM STATS: Time:7.1529 Method:cmd.php Processes:1 Threads:N/A Hosts:7 HostsPerProcess:7 DataSources:78 RRDsProcessed:53
02/14/2009 12:25:08 PM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/cacti/rra/pnm9_hdd_used_88.rrd --template hdd_used:hdd_total 1234632307:1168834560:2146500608
02/14/2009 12:25:08 PM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/cacti/rra/pnm9_hdd_used_87.rrd --template hdd_total:hdd_used 1234632307:127138152448:105861898240
02/14/2009 12:25:08 PM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/cacti/rra/pnm9_hdd_used_86.rrd --template hdd_used:hdd_total 1234632307:12453052416:32267772928
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'1146', SQL:"SELECT name, file, function FROM plugin_hooks WHERE status = 1 AND hook = 'poller_on_demand'"
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] ERROR: SQL Assoc Failed!, Error:'1146', SQL:"SELECT name, file, function FROM plugin_hooks WHERE status = 1 AND hook = 'poller_output'"
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] Time: 6.3023 s, Theads: N/A, Hosts: 6
02/14/2009 12:25:08 PM - PHPSVR: Poller[0] DEBUG: PHP Script Server Shutdown request received, exiting
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] Host[8] DS[86] SERVER: /var/www/cacti/scripts/ss_host_disk.php ss_host_disk 10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get used 1, output: 12453052416
02/14/2009 12:25:08 PM - PHPSVR: Poller[0] DEBUG: INC: '/var/www/cacti/scripts/ss_host_disk.php' FUNC: 'ss_host_disk' PARMS: '10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get used 1'
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] Host[8] DS[86] SERVER: /var/www/cacti/scripts/ss_host_disk.php ss_host_disk 10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get total 1, output: 32267772928
02/14/2009 12:25:08 PM - PHPSVR: Poller[0] DEBUG: INC: '/var/www/cacti/scripts/ss_host_disk.php' FUNC: 'ss_host_disk' PARMS: '10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get total 1'
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] Host[8] DS[87] SERVER: /var/www/cacti/scripts/ss_host_disk.php ss_host_disk 10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get total 2, output: 127138152448
02/14/2009 12:25:08 PM - PHPSVR: Poller[0] DEBUG: INC: '/var/www/cacti/scripts/ss_host_disk.php' FUNC: 'ss_host_disk' PARMS: '10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get total 2'
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] Host[8] DS[87] SERVER: /var/www/cacti/scripts/ss_host_disk.php ss_host_disk 10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get used 2, output: 105861898240
02/14/2009 12:25:08 PM - PHPSVR: Poller[0] DEBUG: INC: '/var/www/cacti/scripts/ss_host_disk.php' FUNC: 'ss_host_disk' PARMS: '10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get used 2'
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] Host[8] DS[88] SERVER: /var/www/cacti/scripts/ss_host_disk.php ss_host_disk 10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get used 7, output: 1168834560
02/14/2009 12:25:08 PM - PHPSVR: Poller[0] DEBUG: INC: '/var/www/cacti/scripts/ss_host_disk.php' FUNC: 'ss_host_disk' PARMS: '10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get used 7'
02/14/2009 12:25:08 PM - CMDPHP: Poller[0] Host[8] DS[88] SERVER: /var/www/cacti/scripts/ss_host_disk.php ss_host_disk 10.10.10.9 8 2:161:500:1:10:pnmmon:admin:cacti:MD5::DES: get total 7, output: 2146500608

There's no mention of the interface traffic....what gives?
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

Just to clarify, I manually created the RRD on another machine just to test the file size and compare. So I haven't actually gotten the rrd to create itself on the production cacti server.

I deleted the device and created just one graph of the interface traffic using the larger RRA and still no RRD file created.

any other ideas?
frist44
Posts: 30
Joined: Wed Feb 11, 2009 5:07 pm

Post by frist44 »

any idea why the rrd isn't being created?
Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests