I'm having trouble getting BBWin to run on my Windows 7-SP1 64-bit machine. The bbwincmd command works fine from the command line, so I'm guessing that there may be a problem with my BBWin.cfg. Could someone take a look at it, and tell me what I'm doing wrong?
Here's what happens when I run bbwincmd:
C:\Program Files (x86)\BBWin\bin>bbwincmd BasementServer status BigShot cpu green Test bbdisplay defined to : BasementServer port defined to : 1984 hostname defined to: BigShot Sending status ...
Sending to BasementServer : status BigShot.cpu green Test
And I see on my Xymon server that the test appears. However, nothing reaches the server from my bbwin service. In fact, I've watched port 1984 using Wireshark, and I see the traffic when I run bbwincmd, but nothing from the bbwin service. Bbwin logs that it starts up, and logs "The agent externals generated this event message : No externals have been specified", and sends nothing to the Xymon server.
Here's my BBWin.cfg file. I modified it from the default to set the bbdisplay and hostname. Later, I added the loglevel. I've modes of central and local, and see the same results.
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="BasementServer" /> <setting name="hostname" value="BigShot" /> <setting name="loglevel" value="4" /> <!-- <setting name="bbdisplay" value="yoursecondbbdisplay:port" />--> <!-- BB Pager Part --> <!--<setting name="usepager" value="false" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="bbpager" value="yourfirstbbpager" /> <setting name="pagerlevels" value="red yellow" /> -->
<!-- proxy connection settings -->
<!--
<setting name="useproxy" value="false" />
<setting name="proxy" value="[user:password@]host[:port]'/>
-->
<!-- bbwin mode local or central -->
<setting name="mode" value="central" />
<setting name="configclass" value="win32" />
<setting name="autoreload" value="true" />
<setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/>
<load name="disk" value="disk.dll"/>
<load name="externals" value="externals.dll"/>
<load name="filesystem" value="filesystem.dll"/>
<load name="memory" value="memory.dll"/>
<load name="msgs" value="msgs.dll"/>
<load name="procs" value="procs.dll"/>
<load name="stats" value="stats.dll"/>
<load name="svcs" value="svcs.dll"/>
<load name="uptime" value="uptime.dll"/>
<load name="who" value="who.dll"/>
<setting name="loglevel" value="3" />
<setting name="logpath" value="C:\Program Files\BBWin\logs\BBWin.log"/>
<!-- If true, the agent will report reporting failures as warningevents --> <setting name="logreportfailure" value="true" /> </bbwin> <cpu> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="default" warnlevel="90" paniclevel="95" delay="3" /> </cpu> <disk> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- Level can be given by % or size unit mb, gb, tb --> <setting name="default" warnlevel="85%" paniclevel="95%" /> <!-- custom rules examples <setting name="C" warnlevel="70%" paniclevel="400mb" /> <setting name="E" ignore="true" /> --> <!-- If true, the agent will check remote drives --> <setting name="remote" value="false" /> <!-- If true, the agent will check that cd/dvdrom drives are empty --> <setting name="cdrom" value="false" /> </disk> <externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <!-- externals launch examples <load value="cscript mybbscript.vbs" /> <load value="myexternal.exe" /> <load value="cscript wlbs.vbs" timer="15m" /> <load value="cluster.exe" timer="90s" /> --> </externals> <memory> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <setting name="physical" warnlevel="78" paniclevel="98" /> <setting name="page" warnlevel="70" paniclevel="90" /> <setting name="virtual" warnlevel="78" paniclevel="90" /> </memory> <msgs> <setting name="alwaysgreen" value="false" /> <setting name="delay" value="1h" /> <match logfile="System" type="error" alarmcolor="red" /> <match logfile="System" type="warning" alarmcolor="yellow" /> <match logfile="Application" type="error" alarmcolor="red" /> <match logfile="Application" type="warning" alarmcolor="yellow" /> <match logfile="Security" type="fail" />
<!-- Some ignore rules examples
<ignore logfile="Application" eventid="1030" />
<ignore logfile="System" source="W32Time" />
--></msgs> <procs> <!-- some procs rules example <setting name="drwtsn" rule="-1" alarmcolor="red" /> <setting name="pageant.exe" rule="=1" comment="Putty agent deamon" /> --> </procs> <svcs> <!-- If true, the agent will always report with green status --> <setting name="alwaysgreen" value="false" /> <!-- If true, the agent will restart all "automatic services" which would be stopped--> <setting name="autoreset" value="false" /> <setting name="alarmcolor" value="yellow" /> <!-- The line bellow show you svcs rules. If the "Automatic Updates" service is stopped, it will be automatically restarted and a red status will be sent until the service get it's correct status <setting name="Automatic Updates" value="started" autoreset="true" alarmcolor="red" /> --> </svcs> <uptime> <setting name="delay" value="30m" /> <setting name="maxdelay" value="365d" /> </uptime> </configuration>
Thanks!
David
I'm having trouble getting BBWin to run on my Windows 7-SP1 64-bit machine.
[snip]
Things I've discovered (through trial, oops and doh!):
1 - make sure the service is started (the installer doesn't start it automatically). 2 - make sure the hostname in the registry is correct. 3 - check your ghost clients.
Bbwin logs that it starts up, and logs "The agent externals generated this event message : No externals have been specified", and sends nothing to the Xymon server.
Here's one of my bbwin.cfg files - this one doesn't get the error that you mention (it did, until I moved the external tests outside the <bbwin>):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="10.239.96.100" />
<!-- bbwin mode local or central -->
<setting name="mode" value="central" />
<setting name="configclass" value="win32" />
<setting name="autoreload" value="true" />
<setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/>
<load name="disk" value="disk.dll"/>
<load name="externals" value="externals.dll"/>
<load name="filesystem" value="filesystem.dll"/>
<load name="memory" value="memory.dll"/>
<load name="msgs" value="msgs.dll"/>
<load name="procs" value="procs.dll"/>
<load name="stats" value="stats.dll"/>
<load name="svcs" value="svcs.dll"/>
<load name="uptime" value="uptime.dll"/>
<load name="who" value="who.dll"/>
<setting name="loglevel" value="3" />
<setting name="logpath" value="C:\BBWin.log"/>
<!-- If true, the agent will report reporting failures aswarning events --> <setting name="logreportfailure" value="true" /> </bbwin>
<externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load name="winUpdates" value="cscript //nologo //B winUpdates.vbs" /> <load name="winupd" value="cscript //nologo //B winupd.vbs" timer="120s" /> </externals>
</configuration>
Hope this helps.
Regards,
Carl
Carl Inglis Systems Administrator
Thanks, Carl. Unfortunately, I get the same results with your config file (with my own bbdisplay replacing yours).
I have my Windows7 desktop system sending its syslogs to a Linux syslog server, and I noticed the following when I started the service:
Mar 2 07:22:43 BIGSHOT bigbrotherhobbitclient[warning] 17 externals No externals have been specified
Since your BBWin.cfg specifies externals, this suggests that BBWin is not actually reading my BBWin.cfg at all. How does it find out where the config file is?
The .msi file installed information such as the location of the config file in my registry in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin. The documentation that came with BBWin says it should have installed it in HKEY_LOCAL_MACHINE\SOFTWARE\BBWin. Does the .msi file put this in the wrong place (on Win7 64-bit machines)? Do I need to move or recreate the registry entries in the right place?
dbr
On 3/2/2011 3:29 AM, Carl Inglis wrote:
I'm having trouble getting BBWin to run on my Windows 7-SP1 64-bit machine.
[snip]
Things I've discovered (through trial, oops and doh!):
1 - make sure the service is started (the installer doesn't start it automatically). 2 - make sure the hostname in the registry is correct. 3 - check your ghost clients.
Bbwin logs that it starts up, and logs "The agent externals generated this event message : No externals have been specified", and sends nothing to the Xymon server. Here's one of my bbwin.cfg files - this one doesn't get the error that you mention (it did, until I moved the external tests outside the <bbwin>):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="10.239.96.100" />
<!-- bbwin mode local or central --> <setting name="mode" value="central" /> <setting name="configclass" value="win32" />
<setting name="autoreload" value="true" /> <setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/>
<setting name="loglevel" value="3" /> <setting name="logpath" value="C:\BBWin.log"/>
<!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="true" /> </bbwin>
<externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load name="winUpdates" value="cscript //nologo //B winUpdates.vbs" /> <load name="winupd" value="cscript //nologo //B winupd.vbs" timer="120s" /> </externals>
</configuration>
Hope this helps.
Regards,
Carl
Hi David,
I've just looked at a 64bit Win 2k3 machine and the BBWin key is indeed in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin
I don't have a 64bit W7 machine to experiment with.
Are you sure the service is started?
Have you tried replacing the bbdisplay host with it's IP address? I'm not sure why, but I have a feeling that BBWin doesn't do DNS - but I could be wrong.
Hope that helps.
Carl
-----Original Message----- From: David B. Ritch [mailto:david.ritch at gmail.com] Sent: 02 March 2011 12:53 To: Carl Inglis Cc: xymon at xymon.com Subject: Re: [Xymon] BBWin on Windows 7 64-bit
Thanks, Carl. Unfortunately, I get the same results with your config file (with my own bbdisplay replacing yours).
I have my Windows7 desktop system sending its syslogs to a Linux syslog server, and I noticed the following when I started the service:
Mar 2 07:22:43 BIGSHOT bigbrotherhobbitclient[warning] 17 externals No externals have been specified
Since your BBWin.cfg specifies externals, this suggests that BBWin is not actually reading my BBWin.cfg at all. How does it find out where the config file is?
The .msi file installed information such as the location of the config file in my registry in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin. The documentation that came with BBWin says it should have installed it in HKEY_LOCAL_MACHINE\SOFTWARE\BBWin. Does the .msi file put this in the wrong place (on Win7 64-bit machines)? Do I need to move or recreate the registry entries in the right place?
dbr
On 3/2/2011 3:29 AM, Carl Inglis wrote:
I'm having trouble getting BBWin to run on my Windows 7-SP1 64-bit machine.
[snip]
Things I've discovered (through trial, oops and doh!):
1 - make sure the service is started (the installer doesn't start it automatically). 2 - make sure the hostname in the registry is correct. 3 - check your ghost clients.
Bbwin logs that it starts up, and logs "The agent externals generated this event message : No externals have been specified", and sends nothing to the Xymon server. Here's one of my bbwin.cfg files - this one doesn't get the error that you mention (it did, until I moved the external tests outside the <bbwin>):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="10.239.96.100" />
<!-- bbwin mode local or central --> <setting name="mode" value="central" /> <setting name="configclass" value="win32" />
<setting name="autoreload" value="true" /> <setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/>
<setting name="loglevel" value="3" /> <setting name="logpath" value="C:\BBWin.log"/>
<!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="true" /> </bbwin>
<externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load name="winUpdates" value="cscript //nologo //B winUpdates.vbs" /> <load name="winupd" value="cscript //nologo //B winupd.vbs" timer="120s" /> </externals>
</configuration>
Hope this helps.
Regards,
Carl
Yes, I did try using the IP address. I also tried ip_address:1984. And I restarted the service after each change. I really think it's not reading the BBWin.cfg file.
I'm much more comfortable with Linux/Unix than Windows. Under LInux, I'd run strace, to follow the system calls, and look to see what BBWin is actually doing - what files it's opening, etc. Do you know if there is an equivalent tool I can use to trace its activity under Windows? Or some other way to get it to work?
Thanks!
dbr
On 3/2/2011 8:16 AM, Carl Inglis wrote:
Hi David,
I've just looked at a 64bit Win 2k3 machine and the BBWin key is indeed in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin
I don't have a 64bit W7 machine to experiment with.
Are you sure the service is started?
Have you tried replacing the bbdisplay host with it's IP address? I'm not sure why, but I have a feeling that BBWin doesn't do DNS - but I could be wrong.
Hope that helps.
Carl
-----Original Message----- From: David B. Ritch [mailto:david.ritch at gmail.com] Sent: 02 March 2011 12:53 To: Carl Inglis Cc: xymon at xymon.com Subject: Re: [Xymon] BBWin on Windows 7 64-bit
Thanks, Carl. Unfortunately, I get the same results with your config file (with my own bbdisplay replacing yours).
I have my Windows7 desktop system sending its syslogs to a Linux syslog server, and I noticed the following when I started the service:
Mar 2 07:22:43 BIGSHOT bigbrotherhobbitclient[warning] 17 externals No externals have been specified
Since your BBWin.cfg specifies externals, this suggests that BBWin is not actually reading my BBWin.cfg at all. How does it find out where the config file is?
The .msi file installed information such as the location of the config file in my registry in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin. The documentation that came with BBWin says it should have installed it in HKEY_LOCAL_MACHINE\SOFTWARE\BBWin. Does the .msi file put this in the wrong place (on Win7 64-bit machines)? Do I need to move or recreate the registry entries in the right place?
dbr
On 3/2/2011 3:29 AM, Carl Inglis wrote:
I'm having trouble getting BBWin to run on my Windows 7-SP1 64-bit machine.
[snip]
Things I've discovered (through trial, oops and doh!):
1 - make sure the service is started (the installer doesn't start it automatically). 2 - make sure the hostname in the registry is correct. 3 - check your ghost clients.
Bbwin logs that it starts up, and logs "The agent externals generated this event message : No externals have been specified", and sends nothing to the Xymon server. Here's one of my bbwin.cfg files - this one doesn't get the error that you mention (it did, until I moved the external tests outside the <bbwin>):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="10.239.96.100" />
<!-- bbwin mode local or central --> <setting name="mode" value="central" /> <setting name="configclass" value="win32" />
<setting name="autoreload" value="true" /> <setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/>
<setting name="loglevel" value="3" /> <setting name="logpath" value="C:\BBWin.log"/>
<!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="true" /> </bbwin>
<externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load name="winUpdates" value="cscript //nologo //B winUpdates.vbs" /> <load name="winupd" value="cscript //nologo //B winupd.vbs" timer="120s" /> </externals>
</configuration>
Hope this helps.
Regards,
Carl
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
David,
Yes, I did try using the IP address. I also tried ip_address:1984. And I restarted the service after each change. I really think it's not reading the BBWin.cfg file.
Check the 'etcpath' registry value in HKLM:\SOFTWARE\BBWin
Also, try putting full path names in to the externals definitions. My externals section looks like:
<externals> <setting name="timer" value="5m" /> <setting name="logstimer" value="60s" /> <load value='c:\perl\bin\perl.exe "C:\Program Files\BBWin\ext\bb-tsusers.pl"' timer="5m" /> <load value='c:\perl\bin\perl.exe "C:\Program Files\BBWin\ext\bb-clust.pl"' timer = "1m" /> </externals>
I'm much more comfortable with Linux/Unix than Windows. Under LInux, I'd run strace, to follow the system calls, and look to see what BBWin is actually doing - what files it's opening, etc. Do you know if there is an equivalent tool I can use to trace its activity under Windows? Or some other way to get it to work?
Try the old sysinternals.com utilities (now part of Microsoft)
Process Explorer is handy - I've used that for the XymonPSClient debugging.
David.
Thanks!
dbr
On 3/2/2011 8:16 AM, Carl Inglis wrote:
Hi David,
I've just looked at a 64bit Win 2k3 machine and the BBWin key is indeed in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin
I don't have a 64bit W7 machine to experiment with.
Are you sure the service is started?
Have you tried replacing the bbdisplay host with it's IP address? I'm not sure why, but I have a feeling that BBWin doesn't do DNS - but I could be wrong.
Hope that helps.
Carl
-----Original Message----- From: David B. Ritch [mailto:david.ritch at gmail.com] Sent: 02 March 2011 12:53 To: Carl Inglis Cc: xymon at xymon.com Subject: Re: [Xymon] BBWin on Windows 7 64-bit
Thanks, Carl. Unfortunately, I get the same results with your config file (with my own bbdisplay replacing yours).
I have my Windows7 desktop system sending its syslogs to a Linux syslog server, and I noticed the following when I started the service:
Mar 2 07:22:43 BIGSHOT bigbrotherhobbitclient[warning] 17 externals No externals have been specified
Since your BBWin.cfg specifies externals, this suggests that BBWin is not actually reading my BBWin.cfg at all. How does it find out where the config file is?
The .msi file installed information such as the location of the config file in my registry in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin. The documentation that came with BBWin says it should have installed it in HKEY_LOCAL_MACHINE\SOFTWARE\BBWin. Does the .msi file put this in the wrong place (on Win7 64-bit machines)? Do I need to move or recreate the registry entries in the right place?
dbr
On 3/2/2011 3:29 AM, Carl Inglis wrote:
I'm having trouble getting BBWin to run on my Windows 7-SP1 64-bit machine.
[snip]
Things I've discovered (through trial, oops and doh!):
1 - make sure the service is started (the installer doesn't start it automatically). 2 - make sure the hostname in the registry is correct. 3 - check your ghost clients.
Bbwin logs that it starts up, and logs "The agent externals generated this event message : No externals have been specified", and sends nothing to the Xymon server. Here's one of my bbwin.cfg files - this one doesn't get the error that you mention (it did, until I moved the external tests outside the <bbwin>):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="10.239.96.100" />
<!-- bbwin mode local or central --> <setting name="mode" value="central" /> <setting name="configclass" value="win32" />
<setting name="autoreload" value="true" /> <setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/>
<setting name="loglevel" value="3" /> <setting name="logpath" value="C:\BBWin.log"/>
<!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="true" /> </bbwin>
<externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load name="winUpdates" value="cscript //nologo //B winUpdates.vbs" /> <load name="winupd" value="cscript //nologo //B winupd.vbs" timer="120s" /> </externals>
</configuration>
Hope this helps.
Regards,
Carl
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
-- David Baldwin - IT Unit Australian Sports Commission www.ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
I tried a different approach - I installed XymonPSClient, and it just worked. I think I'll just use that for now, and not worry too much more about BBWin.
Thank you for your help on this, and for the work on XymonPSClient!
David
On 3/3/2011 12:01 AM, David Baldwin wrote:
David,
Yes, I did try using the IP address. I also tried ip_address:1984. And I restarted the service after each change. I really think it's not reading the BBWin.cfg file.
Check the 'etcpath' registry value in HKLM:\SOFTWARE\BBWin
Also, try putting full path names in to the externals definitions. My externals section looks like:
<externals> <setting name="timer" value="5m" /> <setting name="logstimer" value="60s" /> <load value='c:\perl\bin\perl.exe "C:\Program Files\BBWin\ext\bb-tsusers.pl"' timer="5m" /> <load value='c:\perl\bin\perl.exe "C:\Program Files\BBWin\ext\bb-clust.pl"' timer = "1m" /> </externals>
I'm much more comfortable with Linux/Unix than Windows. Under LInux, I'd run strace, to follow the system calls, and look to see what BBWin is actually doing - what files it's opening, etc. Do you know if there is an equivalent tool I can use to trace its activity under Windows? Or some other way to get it to work?
Try the old sysinternals.com utilities (now part of Microsoft)
Process Explorer is handy - I've used that for the XymonPSClient debugging.
David.
Thanks!
dbr
On 3/2/2011 8:16 AM, Carl Inglis wrote:
Hi David,
I've just looked at a 64bit Win 2k3 machine and the BBWin key is indeed in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin
I don't have a 64bit W7 machine to experiment with.
Are you sure the service is started?
Have you tried replacing the bbdisplay host with it's IP address? I'm not sure why, but I have a feeling that BBWin doesn't do DNS - but I could be wrong.
Hope that helps.
Carl
-----Original Message----- From: David B. Ritch [mailto:david.ritch at gmail.com] Sent: 02 March 2011 12:53 To: Carl Inglis Cc: xymon at xymon.com Subject: Re: [Xymon] BBWin on Windows 7 64-bit
Thanks, Carl. Unfortunately, I get the same results with your config file (with my own bbdisplay replacing yours).
I have my Windows7 desktop system sending its syslogs to a Linux syslog server, and I noticed the following when I started the service:
Mar 2 07:22:43 BIGSHOT bigbrotherhobbitclient[warning] 17 externals No externals have been specified
Since your BBWin.cfg specifies externals, this suggests that BBWin is not actually reading my BBWin.cfg at all. How does it find out where the config file is?
The .msi file installed information such as the location of the config file in my registry in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BBWin. The documentation that came with BBWin says it should have installed it in HKEY_LOCAL_MACHINE\SOFTWARE\BBWin. Does the .msi file put this in the wrong place (on Win7 64-bit machines)? Do I need to move or recreate the registry entries in the right place?
dbr
On 3/2/2011 3:29 AM, Carl Inglis wrote:
I'm having trouble getting BBWin to run on my Windows 7-SP1 64-bit machine.
[snip]
Things I've discovered (through trial, oops and doh!):
1 - make sure the service is started (the installer doesn't start it automatically). 2 - make sure the hostname in the registry is correct. 3 - check your ghost clients.
Bbwin logs that it starts up, and logs "The agent externals generated this event message : No externals have been specified", and sends nothing to the Xymon server. Here's one of my bbwin.cfg files - this one doesn't get the error that you mention (it did, until I moved the external tests outside the <bbwin>):
<?xml version="1.0" encoding="utf-8" ?> <configuration> <bbwin> <setting name="bbdisplay" value="10.239.96.100" />
<!-- bbwin mode local or central --> <setting name="mode" value="central" /> <setting name="configclass" value="win32" />
<setting name="autoreload" value="true" /> <setting name="timer" value="5m" />
<load name="cpu" value="cpu.dll"/> <load name="disk" value="disk.dll"/> <load name="externals" value="externals.dll"/> <load name="filesystem" value="filesystem.dll"/> <load name="memory" value="memory.dll"/> <load name="msgs" value="msgs.dll"/> <load name="procs" value="procs.dll"/> <load name="stats" value="stats.dll"/> <load name="svcs" value="svcs.dll"/> <load name="uptime" value="uptime.dll"/> <load name="who" value="who.dll"/>
<setting name="loglevel" value="3" /> <setting name="logpath" value="C:\BBWin.log"/>
<!-- If true, the agent will report reporting failures as warning events --> <setting name="logreportfailure" value="true" /> </bbwin>
<externals> <setting name="timer" value="3m" /> <setting name="logstimer" value="60s" /> <load name="winUpdates" value="cscript //nologo //B winUpdates.vbs" /> <load name="winupd" value="cscript //nologo //B winupd.vbs" timer="120s" /> </externals>
</configuration>
Hope this helps.
Regards,
Carl
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
participants (3)
-
Carl.Inglis＠rakon.com
-
david.baldwin＠ausport.gov.au
-
david.ritch＠gmail.com