Bes 9.x relay crashing after upgrade

system · April 2, 2013, 10:42pm

(imported topic written by jfschafer)

I upgraded a Windows 2003 server to the new Bes 9.0 relay and now the relay service crashes on the server with 1000’s of popup error windows that you have to hit cancel on 1 at a time. I uninstalled the relay agent and reinstalled and the problem returns. Only happened since upgrading relay to 9.x. Error on the popup window is "The instruction at “0x005804e3” referenced memory at “0x000000008”. The memory could not be “read”. Click OK to terminate the program. Click CANCEL to debug the program. Not sure if this is a new bug in the 9.x release or not and was wondering if anyone else saw this issue.

system · April 2, 2013, 10:52pm

(imported comment written by jfschafer)

Here’s a few entries from the logfile.txt in the relay folder that may point to issue:

hu, 28 Mar 2013 05:34:26 +1000 - 4500 - 10: class NotASignedMessage

Thu, 28 Mar 2013 07:30:57 +1000 - 3260 - 10: class NotASignedMessage

Thu, 28 Mar 2013 07:38:04 +1000 - 1284 - 10: class NotASignedMessage

Thu, 28 Mar 2013 07:40:57 +1000 - 1936 - 10: class NotASignedMessage

Thu, 28 Mar 2013 07:48:52 +1000 - 5168 - 10: class NotASignedMessage

Thu, 28 Mar 2013 08:18:24 +1000 - 5960 - 10: class NotASignedMessage

Thu, 28 Mar 2013 15:04:46 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:04:54 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:05:19 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:05:45 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:06:35 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:07:36 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:08:50 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:09:52 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:10:54 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:11:55 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:12:57 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:13:58 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:15:00 +1000 - 1460 - PostResultsForwarder: Failed to post results to parent.

Thu, 28 Mar 2013 15:26:07 +1000 - 6088 - 10: class NotASignedMessage

Thu, 28 Mar 2013 16:25:53 +1000 - /cgi-bin/bfenterprise/clientregister.exe (5668) - GetExpectedVersionOfParent: Parent response did not contain a site version.

Thu, 28 Mar 2013 16:25:54 +1000 - /cgi-bin/bfenterprise/clientregister.exe (5668) - GetExpectedVersionOfParent: Parent response did not contain a site version.

Thu, 28 Mar 2013 16:25:55 +1000 - /cgi-bin/bfenterprise/clientregister.exe (5668) - GetExpectedVersionOfParent: Parent response did not contain a site version.

Thu, 28 Mar 2013 16:25:56 +1000 - /cgi-bin/bfenterprise/clientregister.exe (5668) - GetExpectedVersionOfParent: Parent response did not contain a site version.

Thu, 28 Mar 2013 16:25:57 +1000 - /cgi-bin/bfenterprise/clientregister.exe (5668) - GetExpectedVersionOfParent: Parent response did not contain a site version.

Thu, 28 Mar 2013 17:53:58 +1000 - 1268 - BES Relay received stop request

Thu, 28 Mar 2013 17:53:58 +1000 - 1276 - BES Relay shutting down

Thu, 28 Mar 2013 17:54:11 +1000 - 3968 - BES Relay version 9.0.586.0 starting

Thu, 28 Mar 2013 17:54:13 +1000 - 3968 - OpenSSL Initialized (FIPS Mode)

Thu, 28 Mar 2013 17:54:13 +1000 - 3968 - Using OpenSSL crypto library libBEScrypto_1_0_0_1 - OpenSSL 0.9.8f-fips-dev xx XXXX xxxx

Thu, 28 Mar 2013 17:54:21 +1000 - 3968 - No client certificate exists at C:\Program Files\BigFix Enterprise\BES Client\KeyStorage__ClientCertificate.crt

Fri, 29 Mar 2013 07:30:02 +1000 - /cgi-bin/bfenterprise/BESGatherMirror.exe (3700) - GetExpectedVersionOfParent Error: HTTP Error 28: Timeout was reached: Connection timed out after 10000 milliseconds

Wed, 03 Apr 2013 02:55:59 +1000 - 3012 - BES Relay version 9.0.586.0 starting

Wed, 03 Apr 2013 02:56:01 +1000 - 3012 - OpenSSL Initialized (FIPS Mode)

Wed, 03 Apr 2013 02:56:01 +1000 - 3012 - Using OpenSSL crypto library libBEScrypto_1_0_0_1 - OpenSSL 0.9.8f-fips-dev xx XXXX xxxx

Wed, 03 Apr 2013 03:46:51 +1000 - 1272 - BES Relay version 9.0.586.0 starting

Wed, 03 Apr 2013 03:46:53 +1000 - 1272 - OpenSSL Initialized (FIPS Mode)

Wed, 03 Apr 2013 03:46:53 +1000 - 1272 - Using OpenSSL crypto library libBEScrypto_1_0_0_1 - OpenSSL 0.9.8f-fips-dev xx XXXX xxxx

Wed, 03 Apr 2013 03:50:58 +1000 - 6028 - BES Relay version 9.0.586.0 starting

Wed, 03 Apr 2013 03:50:59 +1000 - 6028 - OpenSSL Initialized (FIPS Mode)

Wed, 03 Apr 2013 03:50:59 +1000 - 6028 - Using OpenSSL crypto library libBEScrypto_1_0_0_1 - OpenSSL 0.9.8f-fips-dev xx XXXX xxxx

Wed, 03 Apr 2013 04:24:30 +1000 - 5492 - BES Relay version 9.0.586.0 starting

Wed, 03 Apr 2013 04:24:33 +1000 - 5492 - OpenSSL Initialized (FIPS Mode)

system · April 3, 2013, 1:26am

(imported comment written by jfschafer)

Our other relay agent, now on 9 isn’t crashing but a done of these messages appear in the log files:

Tue, 02 Apr 2013 11:36:33 -0600 - 3480 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:01:31 -0600 - 4940 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:06:32 -0600 - 5248 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:08:11 -0600 - 5884 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:36:12 -0600 - 904 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:36:15 -0600 - 4888 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:36:33 -0600 - 1228 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:45:19 -0600 - 1656 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:49:29 -0600 - 5580 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:49:59 -0600 - 1952 - 7: class NotASignedMessage

Tue, 02 Apr 2013 12:55:09 -0600 - 2884 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:04:56 -0600 - 4788 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:05:29 -0600 - 6108 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:13:27 -0600 - 3440 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:22:59 -0600 - 1956 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:35:52 -0600 - 1908 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:36:12 -0600 - 6068 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:36:15 -0600 - 5288 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:36:34 -0600 - 6096 - 7: class NotASignedMessage

Tue, 02 Apr 2013 13:49:21 -0600 - 5664 - 7: class NotASignedMessage

Tue, 02 Apr 2013 14:27:23 -0600 - 3024 - 7: class NotASignedMessage

Tue, 02 Apr 2013 14:28:12 -0600 - 244 - 7: class NotASignedMessage

Tue, 02 Apr 2013 14:36:13 -0600 - 3428 - 7: class NotASignedMessage

Tue, 02 Apr 2013 14:36:16 -0600 - 4260 - 7: class NotASignedMessage

Tue, 02 Apr 2013 14:36:31 -0600 - 1344 - 7: class NotASignedMessage

Tue, 02 Apr 2013 14:44:22 -0600 - 704 - 7: class NotASignedMessage

Tue, 02 Apr 2013 15:05:02 -0600 - 1328 - 7: class NotASignedMessage

Tue, 02 Apr 2013 15:07:11 -0600 - 460 - 7: class NotASignedMessage

Tue, 02 Apr 2013 15:23:27 -0600 - 4360 - 7: class NotASignedMessage

system · April 3, 2013, 1:57am

(imported comment written by jfschafer)

I uninstalled and reinstalled the BESClient and BESRelay on the server in question (by the way all the BES tools available for download only work for version 8.2 and below still and they haven’t updated links to download tools for version 9 yet).

After restalling Besclient and Besrelay on server having issues, all I see in the relay log file now is:

Wed, 03 Apr 2013 07:42:46 +1000 - 1876 - 8: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:42:48 +1000 - 2624 - 9: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:42:52 +1000 - 4868 - 10: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:42:55 +1000 - 1660 - 11: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:42:58 +1000 - 2240 - 12: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:01 +1000 - 3020 - 13: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:04 +1000 - 5960 - 14: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:07 +1000 - 2656 - 15: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:10 +1000 - 5244 - 16: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:14 +1000 - 4752 - 17: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:16 +1000 - 1340 - 6: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:18 +1000 - 5416 - 18: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:21 +1000 - 5204 - 19: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:24 +1000 - 5596 - 20: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:27 +1000 - 5508 - 21: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:31 +1000 - 2228 - 22: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:33 +1000 - 1616 - 23: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:37 +1000 - 372 - 24: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:43:39 +1000 - 5096 - 25: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:49:15 +1000 - 864 - 11: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:49:18 +1000 - 5788 - 2: class NoMastheadMatchesURL

Wed, 03 Apr 2013 07:53:17 +1000 - 1096 - 11: class NoMastheadMatchesURL

system · June 6, 2013, 6:23pm

(imported comment written by Rafael Rodriguez)

look
http://www-01.ibm.com/support/docview.wss?uid=swg21636785

dhtorsdc · April 3, 2013, 6:45pm

(imported comment written by dhtorsdc)

Getting the “class NotASignedMessage” all over. Can’t even do a send refresh to an endpoint. Working with support for over a week. No real progress. Welcome to the version 9 upgrade nightmare.

system · July 26, 2013, 6:39pm

(imported comment written by VipulSri)

What is the complete version of TEM on which you upgraded it to??

As per IBM if you have CPM installed on your server and you upgrade your environment to TEM 9.0.586 then you will see issues with Relay crashing randomly, however this issue has been fixed by IBM in TEM 9.0.649.

And I completely agree with you that Upgrade 9 is a total nightmare.

jgstew · October 21, 2013, 11:34pm

(imported comment written by jgstew)

We had some similar major issues with the version 9 relay service, but after working with support and getting a special build, it seems fixed. The fix for our particular issue should be in the newest build.

system · October 24, 2013, 9:44pm

(imported comment written by ShaunKelley)

Do any of you use a network Intrusion Prevention System?

system · October 25, 2013, 10:04am

(imported comment written by jfschafer)

Just wanted to update those watching this thread. I no longer have any issues with this error since subsequent releases of IEM. It’s running quite smooth. Currently on latest release 9.0.787.0 and no issues with relays.