Hi all

I have investigate this a little further, and found something more curious which does seem to point to a bug either in the Hobbit code, or the BB-Win patch code. (I need my C guy to get back from leave to investigate which)

In hobbit-clients.cfg If I have a config like HOST=winhost01 SVC "Service1" startup=automatic status=started color=red Then everything is good.

However, if I leave out the startup clause and have this HOST=winhost01 SVC "Service1" status=started color=red # (I don't care how it starts, just make sure it is started) Then it starts dumping core.

Cheers V

From: Everett, Vernon Sent: Monday, 8 September 2008 4:02 PM To: hobbit at hswn.dk Subject: RE: [hobbit] RE: Hobbit/BBWin bug? hobbit_client dumping core.

Interesting. It is coring with both. Server1 Microsoft Windows Server 2003, Standard Edition Service Pack 1 (build 3790) Server2 Microsoft Windows 2000 Server Service Pack 4 (build 2195)

Makes me think there is a problem with my config, but I don't see it. Anybody with sharper eyes than myself spot anything?

If it is my config, why would this cause Hobbit to keel over? Surely it should report an error in the logs, and ignore the bad part of the config?

Regards Vernon

From: Everett, Vernon Sent: Monday, 8 September 2008 1:37 PM To: hobbit at hswn.dk Subject: [hobbit] RE: Hobbit/BBWin bug? hobbit_client dumping core.

Hi all

I was mistaken. Even with the 3 hosts defined seperately, I still get the cores. I also get this in clientdata.log 2008-09-08 13:25:28 Worker process died with exit code 134, terminating

This is easily reproduced, and goes away if I comment out the 3 hosts.

I will uncomment them one at a time, and let you know if it is confined to only one.

Regards Vernon

From: Everett, Vernon Sent: Monday, 8 September 2008 10:43 AM To: 'hobbit at hswn.dk' Subject: Hobbit/BBWin bug? hobbit_client dumping core.

Hi all

Had a problem with Hobbit over the weekend, which may be a bug. The dev guys might want to have a look at it.

We are monitoring a number of Windoze servers, all running BBWin - Latest edition. Server1 Microsoft Windows Server 2003, Standard Edition Service Pack 1 (build 3790) Server2 Microsoft Windows 2000 Server Service Pack 4 (build 2195) Server3 Microsoft Windows 2000 Server Service Pack 4 (build 2195)

Hobbit server is running 4.2.0 with all-in-one patch applied on Red Hat Linux 2.6.18-92.1.1.el5 We also have the required BBWin patch applied.

In hobbit-client.cfg I had the servers configured as HOST=server1,server2,server3 SVC "AppStart" startup=automatic status=started color=red SVC "AppServer" status=started color=red PROC AppStart.exe 1 -1 red PROC Appserver.exe 1 -1 red PROC AppHelper.exe 1 -1 red

Hobbit started core dumping, and many tests went purple. Under the hobbit server, a new column "hobbitd_client" appeared as red.

Changed the entries to

HOST=server1 SVC "AppStart" startup=automatic status=started color=red SVC "AppServer" status=started color=red PROC AppStart.exe 1 -1 red PROC Appserver.exe 1 -1 red PROC AppHelper.exe 1 -1 red

HOST=server2 SVC "AppStart" startup=automatic status=started color=red SVC "AppServer" status=started color=red PROC AppStart.exe 1 -1 red PROC Appserver.exe 1 -1 red PROC AppHelper.exe 1 -1 red

HOST=server3 SVC "AppStart" startup=automatic status=started color=red SVC "AppServer" status=started color=red PROC AppStart.exe 1 -1 red PROC Appserver.exe 1 -1 red PROC AppHelper.exe 1 -1 red

Ran ~/server/bin/bb 127.0.0.1 "drop hobbit hobbitd_client" And all was well.

I have saved a few of the cores if anybody is interested in investigating this one.

Regards Vernon

NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.

NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.