Windows uptime statistics

[royce]

Here is what happens ...

[wvr120364]

[royce]

fixed this.. seems to be another buffer-ouput-problem.

Bound my scripts through a executer-wrapper wich is a basic script that outputs the information in one buffer.

A shell script might look like this one - not that I've converted this to linux instead.

[proohu01]

[xphu]

Hi,

I got your nice uptime script working only locally in my Windows 2003 std Server where I am also runnig cacti.

I was not able to get it working with other Devices i.e. Windows Servers which are graphing with cacti.

Please see how the win_uptime.cmd is showing it up.

First with localhost which is working (returns good result) and after even a local host ip 127.0.0.1 does not return a correct result?

C:\Inetpub\wwwroot\scripts\uptime>win_uptime.cmd localhost 99.95
cur_uptime:3569 mean_days:1.59 tot_uptime:5856027 tot_blue:0 tot_downtime:194810
tot_reb:44 avail:96.7804 sla_avail:99.95

C:\Inetpub\wwwroot\scripts\uptime>win_uptime.cmd localhost 99.95
cur_uptime:3570 mean_days:1.59 tot_uptime:5856029 tot_blue:0 tot_downtime:194810
tot_reb:44 avail:96.7804 sla_avail:99.95

C:\Inetpub\wwwroot\scripts\uptime>win_uptime.cmd 172.16.10.251 99.95
tot_blue:1 tot_reb:1 sla_avail:99.95

C:\Inetpub\wwwroot\scripts\uptime>win_uptime.cmd 172.0.0.1 99.95
tot_blue:1 tot_reb:1 sla_avail:99.95

C:\Inetpub\wwwroot\scripts\uptime>

With not working graph I see tot-blue:1 tot-reb:1 sla-avail:99.95 nothing else?

What can be the problem. I cannot use fully qualified domain names for http url? I am not connecting to my cacti server form internet at all.

\xphu

[royce]

[proohu01]

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?

[royce]

[xphu]

Hi,

I think I found the solution for my earlier post.

http://support.microsoft.com/kb/q232243/

So I need to set up correct user privileges for my cacti network.

\xphu

[proohu01]

It's working now.

The only thing I did was to change the poller from cactid to cmd.php. Somehow the CMD.PHP works better for this script.

[chewy009]

[magoo95]

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

and it works fine now:

[fishgod]

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.

Michael

[proohu01]

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.

[BSOD2600]

If you read my faq, I recently created one on how to properly set up WMI so a normal user can query a remote computer.