BBWin on Windows 7 64-bit

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:user-23cafa473f8d@xymon.invalid]
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