Download Rrdtool For Cacti Windows
Cameron Cortez
If under "RRDTool Says:" you see something about not existing file, then you should check permissions to your rra folder. In my case it is: "/var/lib/cacti/rra/". So this folder should have write permissions for www-data user (or your web server user).
5.Click on Finish ,after that it will gives you a login windows.
6.Login using the username and password of admin/admin.
7.Next it will be required to change this password immediately so set the New password.
Hi, i have converted rrd files to xml on my old debian 6 32 bits machine and transfered them to the new debian 6 64 bits machine.
when i tried to restored them to rrd, i received lot of errors and most of them where not converted.
I can see some graphs displayed but not all of them.
Also my poller on the new machine is not working at all knowing that the cron file is exactly the same as the old machine.
i had rebuild poller cash and in the cacti log file i see nothing.
please help.
Hi Remi,
Can you please send me your email in order to attach the folder since it contains lot of files.
please see also the cacti crontab job for the poller:
MAILTO=root
*/1 * * * * www-data php /usr/share/cacti/site/poller.php >/dev/null 2>/var/log/cacti/poller-error.log
it is exactly the same as on the old machine but i see no logs in the cacti as if it is not polling.
So far i was able to transfer cacti config files and cacti database to the new machine, i can see that the settings are the same as the old one.
the only problem is the graphs and the poller not working.
PS: i didnt mentioned any file with spaces in the xml files.
Please make note that the syntax of rrdtool changes with the packageversion. We highly suggest using RRDtool v1.2.x which require very fewdependancies compared to v1.4.x. To install rrdtool on OpenBSD, use "pkg_add -irrdtool". For FreeBSD 9.x and 10.x use "portmaster databases/rrdtool12" or "pkginstall rrdtool-1.2.30_2".
Working directory. We will being putting all of the files into aworking directory we made up called, "/tools/rrdtool/latency/". This is wherethe three(3) scripts, the database and the graph will reside. Once the graph ismade it can be copied to a web directory like, "/var/www/htdocs/" for easyviewing through our web server.
The following scrollable window contains the command we used to make the rrdfile. Cut and paste the script into a file called,"initialize_database.sh" and make it executable with "chmod 755update_rrd_database.sh". The rrdtool lines in the file are one command, but wehave put line breaks ( \ is a line break ) in to create multiple lines so it iseasier to read and explain.user@machine# cat initialize_database.sh### change to the script directorycd /tools/rrdtool/latency/rrdtool create latency_db.rrd \--step 60 \DS:pl:GAUGE:120:0:100 \DS:rtt:GAUGE:120:0:10000000 \RRA:MAX:0.5:1:1500 \
rrdtool create latency_db.rrd -- here we are calling the rrdtoolbinary and telling it to "create" the rdd database we have named"latency_db.rrd". This file is created in the current working directory.
The "update_rrd_database.sh" script will change to the working directory,"/tools/rrdtool/latency/". Then, the get_data method will run and ping the ipdefined in the hosttoping variable; gawk is used to separate out the data andcollect it using regular expressions. The last line to run will update thelatency_db.rrd database with the pl and rtt values in order and separated by acolon.
NOTE: before using this script make sure you set the proper paths of thevariables at the top of the script. These paths are for OpenBSD and Linux isslightly different. Update the paths for bash, ping, gwak and rrdtool. Thereason we use full paths is because CRON may not be setup with the full pathenvironment. Also, if you do not have gawk it can be easily installed using thepackage manager (apt-get, yum, pkg_add) of your choice in most *nix os's.Finally, the variable "hosttoping" should contain the ip address or hostname ofthe machine we want to ping. For this example 192.168.0.1 will be a machine weconsider to be our default gateway on our network.
Create a CRON job to collect the dataThe best way to collect the data is to run a cron job every minute. We setthe step to 60 in the initialization of the database and we will update thedatabase every 60 seconds using a cron job.user@machine# crontab -e#minute (0-59)# hour (0-23)# day of the month (1-31)# month of the year (1-12)# day of the week (0-6 with 0=Sun)# commands# #### rrdtool ping statistics* * * * * /tools/rrdtool/latency/update_rrd_database.sh
--slope-mode -- says rrdtool should smooth the graph and create amore organic looking lines. This option uses anti-aliasing and gives thegraphs a smooth hand drawn look. Using slope also creates the faded sharp linesin the peaks of the graph.
GPRINT:roundtrip:LAST:"Cur\: %5.2lf" -- GPRINT is used to print tothe legend. It will do a calculation using only the data that is in the currentgraph. This is very useful if you want to see the minimum and maximum valuesfor a certain time frame and not all the values in the database. The GPRINTvalues used here print out the current, average, maximum and minimum round trip(rtt) times according to the current graphed data set.
- GPRINT may stand for graphics print. Not very descriptive really.
- roundtrip are the values we are using.
- LAST is the last value seen when the graph was made. In effect, this iscurrent value in the database when the "rrdtool graph" command was called.
- "Cur\: %5.2lf" is the label in the legend. This is the "Cur"rent value andthe print format is floating 5 values on the left and 2 on he right of thedecimal.
Add to the cron job to collect the data and create the graphAdding the create_graph.sh script as the second line to the cron job willnow collect the data and create a graph. This example will continue to collectdata every minute. The create_graph.sh script will run on the 1st and 31stminute of the hour between the hours of 10am and 10pm (22:00).user@machine# crontab -e#minute (0-59)# hour (0-23)# day of the month (1-31)# month of the year (1-12)# day of the week (0-6 with 0=Sun)# commands# #### rrdtool latency check* * * * * /tools/rrdtool/latency/update_rrd_database.sh1,31 10-22 * * * /tools/rrdtool/latency/create_graph.sh >> /dev/null 2>&1
Explaining the graphs. The example picture shows 3 graphs in total,but they are used together to see patterns in Pf. The top graph shows thebandwidth in bytes per second on the left side and total states per second onthe right. The second graph displays the packet rate. We have packets passed inand out per second on the left and packets which are blocked in and out on theright.The third graph is for pf states. Inserts and removal per second aregraphed on the left and searches of the state table per second on the right. Thetitle is in black at the top and at the bottom in a watermark (light gray) isthe date and time the graph was created. When reading the graph remember thatnew data is on the right and the oldest data is on the left. The "calomel.org"watermark is not part of rrdtool and just used to identify our site.
Working directory. We will being putting all of the files into aworking directory we made up called, "/tools/rrdtool/pf_stats/". This is wherethe three(3) scripts, the database and the three(3) graphs will reside. Oncethe graph is made it can be copied to a web directory like,"/var/www/htdocs/".
Add to the cron job to collect the data and create the graphThis example will continue to collect data every minute in accordance thestep 60 we specified in the database. The create_graph.sh script will run onthe 1st and 31st minute of the hour between the hours of 10am and 10pm (22:00).user@machine# crontab -e#minute (0-59)# hour (0-23)# day of the month (1-31)# month of the year (1-12)# day of the week (0-6 with 0=Sun)# commands# #### rrdtool pf firewall statistics* * * * * /tools/rrdtool/pf_stat/update_rrd_database.sh1,31 10-22 * * * /tools/rrdtool/pf_stat/create_graph.sh >> /dev/null 2>&1
The title is in black at the top and at the bottom in a watermark (lightgray) is the date and time the graph was created. When reading the graphremember that new data is on the right and the oldest data is on the left. The"calomel.org" watermark is not part of rrdtool and just used to identify oursite.
Working directory. Put all of the files into a working directorycalled, "/tools/rrdtool/health/". This is where the three(3) scripts, thedatabase and the graph will reside. Once the graph is made it can be copied toa web directory like, "/var/www/htdocs/".
Add to the cron job to collect the data and create the graphThis example will continue to collect data every minute. The create_graph.shscript will run on the 1st and 31st minute of the hour between the hours of10am and 10pm (22:00).user@machine# crontab -e#minute (0-59)# hour (0-23)# day of the month (1-31)# month of the year (1-12)# day of the week (0-6 with 0=Sun)# commands# #### rrdtool latency check* * * * * /tools/rrdtool/health/update_rrd_database.sh1,31 10-22 * * * /tools/rrdtool/health/create_graph.sh >> /dev/null 2>&1
Explaining the graph. This graph shows SMTP traffic as reported byboth OpenBSD's Spamd and Postfix. The vertical center line of the graph iszero; positive values are data collected from Spamdb and negative data isPostfix. Data is collected every hour and this explains why the graph looks more"step like" compared to our other examples. The blue area fill is the amount oftime spamd has trapped spammers. The other colors are lines and defined clearlyin the legend. The title is in black at the top and at the bottom in awatermark (light gray) is the date and time the graph was created. When readingthe graph remember that new data is on the right and the oldest data is on theleft. The "calomel.org" watermark is not part of rrdtool and just used toidentify our site.
df19127ead