Hi! I've sent an email to the BBWin list but am wondering if troubleshooting this client is done on this list instead. (I've read Jason Chambers quick plea for help from a few hours ago.)
Just want to make sure I'm addressing the right list for the right job ;-)
P.S. Hobbit ROCKS! This weekend I did an install of the latest BB, was about to install BBGen then discover the Hobbit project. An immediate switchover to Hobbit later and I'm a happy camper!
-Roger Alterskjær
On Mon, Jun 05, 2006 at 11:13:45PM +0200, Roger WJ Alterskjær wrote:
I've sent an email to the BBWin list but am wondering if troubleshooting this client is done on this list instead. (I've read Jason Chambers quick plea for help from a few hours ago.)
I believe Etienne who does the work on BBWin has asked that you use the BBWin mailinglist for questions about that piece of software. I dont have the adress for it, but I'm sure it's on the bbwin pages.
P.S. Hobbit ROCKS! This weekend I did an install of the latest BB, was about to install BBGen then discover the Hobbit project. An immediate switchover to Hobbit later and I'm a happy camper!
Thanks :-)
Henrik
Hi Roger,
Well, I didn't receive any message from the BBWin mailinglist. You may explain your problem here (I have Henrik agreement :) ) for the moment so I can help you faster.
Regards,
2006/6/5, Roger WJ Alterskjær <Roger.Alterskjaer at vm.ntnu.no>:
Hi! I've sent an email to the BBWin list but am wondering if troubleshooting this client is done on this list instead. (I've read Jason Chambers quick plea for help from a few hours ago.)
Just want to make sure I'm addressing the right list for the right job [image: ;-)]
P.S. Hobbit ROCKS! This weekend I did an install of the latest BB, was about to install BBGen then discover the Hobbit project. An immediate switchover to Hobbit later and I'm a happy camper!
-Roger Alterskjær
-- Etienne GRIGNON
On Mon, 2006-06-05 at 23:59 +0200, Etienne Grignon wrote:
Well, I didn't receive any message from the BBWin mailinglist. You may explain your problem here (I have Henrik agreement :) ) for the moment so I can help you faster.
Thanks! Here's what I sent to the BBWin-list. :-)
-Roger
Hi! I'm new to the list and BB/Hobbit. Just did a fresh (and successful) install of BB server and clients (linux and windows servers) when I discovered Hobbit. Installed Hobbit only to find out that the lates BB client couldn't talk to Hobbit.
After that I found out about this project and the the cool BBWin version 0.7. The transition from BB client to BBWin went smoothly on Windows 2003 Server. The VBS-script for generating BBWin.cfg is brilliant. However, the script didn't like running on a 64-bit Windows 2003 Server. FYI, I had to tweak the HKLM-registery line to read something like this: ...\Software\Wow6432Node\BBWin\... Problem solved!
Got a problem, though: My one and only Windows 2000 Server seems to not like the service. Trying to restart the service couldn't stop it; had to resort to 'pskill'. Still, it's not reporting to my Hobbit server and I've gone over it from the registery settings to my bb-hosts file. Everything says it 'should' be working. But I'm a bit suspicious since the service is so difficult to do a restart. (The old BB client to BB server did work perfectly...)
Other than that, I have to say this is a fantastic utility!! Thank you!!!
-Roger Alterskjær
Hi Roger,
2006/6/6, Roger WJ Alterskjær <Roger.Alterskjaer at vm.ntnu.no >:
On Mon, 2006-06-05 at 23:59 +0200, Etienne Grignon wrote:
Well, I didn't receive any message from the BBWin mailinglist. You may explain your problem here (I have Henrik agreement :) ) for the moment so I can help you faster.
Thanks! Here's what I sent to the BBWin-list. [image: :-)]
Indeed, I see in the mailing list archive your mail. I think some settings are not well configured yet in my mailman settings because I didn't get your mail which is not very useful for a mailing list :-)
Hi! I'm new to the list and BB/Hobbit. Just did a fresh (and successful) install of BB server and clients (linux and windows servers) when I discovered Hobbit. Installed Hobbit only to find out that the lates BB client couldn't talk to Hobbit.
After that I found out about this project and the the cool BBWin version 0.7. The transition from BB client to BBWin went smoothly on Windows 2003 Server. The VBS-script for generating BBWin.cfg is brilliant. However, the script didn't like running on a 64-bit Windows 2003 Server. FYI, I had to tweak the HKLM-registery line to read something like this: ...\Software\Wow6432Node\BBWin\... Problem solved!
For the moment, I have no server with 64-bit Windows 2003 at work, so that's why I didn't confirm the support to it. I'm glad that you succeed to install it. As you said, it seems that I have to arrange some parts of the registry source code part which is different from the 32bit way. The msdn contains interesting articles about that part.
Simple question : is every BBwin agent working on your 64-bits Windows once you modified the registry ? I'm really interested of the BBWin behavior on your 64bits Windows server.
Got a problem, though: My one and only Windows 2000 Server seems to not
like the service. Trying to restart the service couldn't stop it; had to resort to 'pskill'. Still, it's not reporting to my Hobbit server and I've gone over it from the registery settings to my bb-hosts file. Everything says it 'should' be working. But I'm a bit suspicious since the service is so difficult to do a restart. (The old BB client to BB server did work perfectly...)
Some users still report me that sometimes, they can't stop the service. In reality, it seems that one agent never starts successfuly, which mean that one of the agent is breaking the all threads at startup and that's why you can't stop it after and why it never reports. For this bug, I'm still figure out what's happen in this case because for the moment, I never succeed to reproduce this behavior in Visual C++ debugger on my Windows XP station. However, the agent cpu is for the moment the suspicious agent which may cause this strange crash. You may try starting BBWin on your Win2000 without the cpu loading directive.
Other than that, I have to say this is a fantastic utility!! Thank you!!!
-Roger Alterskjær
Thank you for your report.
Best regards,
-- Etienne GRIGNON
On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:
Some users still report me that sometimes, they can't stop the service. In reality, it seems that one agent never starts successfuly, which mean that one of the agent is breaking the all threads at startup and that's why you can't stop it after and why it never reports. For this bug, I'm still figure out what's happen in this case because for the moment, I never succeed to reproduce this behavior in Visual C ++ debugger on my Windows XP station. However, the agent cpu is for the moment the suspicious agent which may cause this strange crash. You may try starting BBWin on your Win2000 without the cpu loading directive.
Hi! Okay, looks like I found it: Externals was set to load even though I didn't have any defined. On Windows 2003 servers this popped up in the Event Log as a warning. Since the daemons worked I thought nothing of it. But on the 2000 server I had to take out the loading of the externals dll. Now I can stop and start the daemon as much as I please. :-)
BTW, on the 64-bit servers it looks like all daemons are working. Not bad!
-Roger
On Tue, 2006-06-06 at 16:28 +0200, Roger WJ Alterskjær wrote:
On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:
Some users still report me that sometimes, they can't stop the service. In reality, it seems that one agent never starts successfuly, which mean that one of the agent is breaking the all threads at startup and that's why you can't stop it after and why it never reports. For this bug, I'm still figure out what's happen in this case because for the moment, I never succeed to reproduce this behavior in Visual C++ debugger on my Windows XP station. However, the agent cpu is for the moment the suspicious agent which may cause this strange crash. You may try starting BBWin on your Win2000 without the cpu loading directive.
Spoke too soon. It work for a few minutes and now my Hobbit server isn't getting anything from the client. Crap!
Gonna take a closer look at it and let you know what I find.
-Roger
On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:
Some users still report me that sometimes, they can't stop the service. In reality, it seems that one agent never starts successfuly, which mean that one of the agent is breaking the all threads at startup and that's why you can't stop it after and why it never reports. For this bug, I'm still figure out what's happen in this case because for the moment, I never succeed to reproduce this behavior in Visual C ++ debugger on my Windows XP station. However, the agent cpu is for the moment the suspicious agent which may cause this strange crash. You may try starting BBWin on your Win2000 without the cpu loading directive.
Okay, it looks like you were right about the cpu agent. I disabled it yesterday and it BBWin looks pretty stable. Even restarted the entire server early this morning without any incident: BBWin shutdown and restarted nicely.
Don't know how much time and effort should be put into the Win 2k problem. For me, this is our last W2K server and it will be retired within a years time. Though having an unsolved bug can be pretty frustrating. :-)
-Roger
Hi Roger,
2006/6/7, Roger WJ Alterskjær <Roger.Alterskjaer at vm.ntnu.no >:
On Tue, 2006-06-06 at 09:18 +0200, Etienne Grignon wrote:
Some users still report me that sometimes, they can't stop the service. In reality, it seems that one agent never starts successfuly, which mean that one of the agent is breaking the all threads at startup and that's why you can't stop it after and why it never reports. For this bug, I'm still figure out what's happen in this case because for the moment, I never succeed to reproduce this behavior in Visual C++ debugger on my Windows XP station. However, the agent cpu is for the moment the suspicious agent which may cause this strange crash. You may try starting BBWin on your Win2000 without the cpu loading directive.
Okay, it looks like you were right about the cpu agent. I disabled it yesterday and it BBWin looks pretty stable. Even restarted the entire server early this morning without any incident: BBWin shutdown and restarted nicely.
Don't know how much time and effort should be put into the Win 2k problem. For me, this is our last W2K server and it will be retired within a years time. Though having an unsolved bug can be pretty frustrating. [image: :-)]
Thank you very much for your report. This bug is not an easy one but it is important to resolve it anyway. It may has a link with the trouble that existed on the original bbnt with the setting ForceRegClose on the performance data registry.
Let me know if you get other troubles,
Regards,
-- Etienne GRIGNON
participants (3)
-
etienne.grignon＠gmail.com
-
henrik＠hswn.dk
-
Roger.Alterskjaer＠vm.ntnu.no