Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
chewy009 wrote:OK, so i installed this on my "production" cacti box and it seems like it's working. Why is the Required (SLA) showing up as 0.0000%? Will the rest of the graph items fill in over time or should they already be there? I rebooted this box yesterday, hence the 0.98 days of uptime. What do you think?
I've got the same problem - debugging cacti tells that cacti only sees some of the output vars...
Do the maintainer use cactid och php?
Same problem here.
When I run the CMD from the command prompt, I do get good results. All values are returned. But when cacti does it, it only shows "uptime since last reboot" in the graph.
proohu01 wrote:I see youre post on the wrapper but I don't get it. How does this work on a windows server?
Should this wrapper replace any files? Could you explain how this helps?
The reason cacti does'nt read all input fields from the script (win_uptime.cmd) is that, AFAIK, the output is buffered in sections instead of a whole string.
So my solution was tell cacti call another script which basically call the original script and echo the output at one time.
proohu01 wrote:I see youre post on the wrapper but I don't get it. How does this work on a windows server?
Should this wrapper replace any files? Could you explain how this helps?
The reason cacti does'nt read all input fields from the script (win_uptime.cmd) is that, AFAIK, the output is buffered in sections instead of a whole string.
So my solution was tell cacti call another script which basically call the original script and echo the output at one time.
Royce,
Not to be completely dumb here, but can give me a step-by-step on what you did. I don't fully understand what you mean here. Is there a file you can post? I have to use cactid due to the number of graphs I have. Thx.
This is the script you can use under windows to call the original win_uptime.cmd script.
this new script must be declared in the "data input method" in place of win_uptime:
@echo off
set templog=C:\bvra\cacti\scripts\uptime\tempo_%1.log
call C:/bvra/cacti/scripts/uptime/win_uptime.cmd %1 %2 > %templog%
type %templog%
del C:\bvra\cacti\scripts\uptime\tempo_%1.log
I am having permission issues. If I run the script as a domain admin I get data. If I let system run it from the cacti poller I get no data. One of the notes on the install for win2003 was to not use a domain account becauce of issues. They suggest using the local system account. Anyone have any ideas on which direction I should go.
I used a domain account and placed that account into the local administrators group on the remote servers. That way the account should have the right permissions to query WMI from a remote host.
Use that domain account to schedule the poller. The problem you may see with that is that the poller pops up many time when logged on to the cacti server with that same account. I suggest you us an account that you would not normally use when you logon to the server.