00-aet Absent Member.
Absent Member.
1820 views

poa crash

8.0.2 POA on SLES 10 crashed and would not restart tonite with the following error in my log.

Error with GWEvent notification [8906]: http://<my datasync server>/:4500

Shutting down the datasync server allowed my POA to start back up. I restarted the datasync server after and it's all running again.

Thoughts? 8906 is a comm error from what I can find.

-andy
Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: poa crash

Hmmm, thats weird Unable to connect to DataSync server should not hamper the
POA's ability to start. Can you please try posting your POA log files
here?

Waiting for your response.

Regards
MJ

>>> On Friday, July 23, 2010 at 06:16 PM, in message

<00-aet.4ekv4n@no-mx.forums.novell.com>,
00-aet<00-aet@no-mx.forums.novell.com>
wrote:

> 8.0.2 POA on SLES 10 crashed and would not restart tonite with the
> following error in my log.
>
> Error with GWEvent notification [8906]: http://<my datasync
> server>/:4500
>
> Shutting down the datasync server allowed my POA to start back up. I
> restarted the datasync server after and it's all running again.
>
> Thoughts? 8906 is a comm error from what I can find.
>
> -andy

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: poa crash

mj@novell.com wrote:
> Hmmm, thats weird Unable to connect to DataSync server should not hamper the
> POA's ability to start. Can you please try posting your POA log files
> here?
>
> Waiting for your response.
>
> Regards
> MJ
>
>>>> On Friday, July 23, 2010 at 06:16 PM, in message

> <00-aet.4ekv4n@no-mx.forums.novell.com>,
> 00-aet<00-aet@no-mx.forums.novell.com>
> wrote:
>
>> 8.0.2 POA on SLES 10 crashed and would not restart tonite with the
>> following error in my log.
>>
>> Error with GWEvent notification [8906]: http://<my datasync
>> server>/:4500
>>
>> Shutting down the datasync server allowed my POA to start back up. I
>> restarted the datasync server after and it's all running again.
>>
>> Thoughts? 8906 is a comm error from what I can find.
>>
>> -andy


Here's the tail of the log file before the crash

19:44:19 448 SOAP allocated remote list 1 for user 1
19:44:19 448 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:19 248 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Here's the relevant tail from the restart with DS running

19:44:50 024 Starting GWSOAP-MHCP-Handler_2
19:44:50 640 Starting GWSOAP-MHCP-Handler_3
19:44:50 256 Starting GWSOAP-MHCP-Handler_4
19:44:50 872 Starting GWSOAP-MHCP-Handler_5
19:44:50 024 SOAP allocated remote list 1 for user 1
19:44:50 024 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 488 Starting GWSOAP-MHCP-Handler_6
19:44:50 640 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 872 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 392 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

All references in there are for the same user. Maybe something with
that account?

thanks

-andy
0 Likes
stanleytee Absent Member.
Absent Member.

Re: poa crash

Hello

Not sure how you got on with this but we had a similar issue here recently. Our mobility server died so we construction a new one with a different IP address. When we looked at our POA logs we were still getting the 8906 error pointing to the old IP address despite the fact that the server was long gone. Essentially from the POA console under

configuration - SOAP Notification list

we could see the soap details for the users and the new server, however when we looked at

configuration - event configuration list

we could see threads for the old server, these contained many thousands of events and were causing our POA to grind to a halt. Once these old event configuration lists were deleted the 8906 errors in the logs stopped and the POA was able to function properly. I would say that several of the event config lists kept re-appearing, if you get these then it is worth running a structural scan and fix on the user in question. you will find these old dead events appear as "101 errors event without configuration" or something along those lines. The fix should be able to handle these, you may have to do this several times to flush out all the old rubbish.

Even if your situation is slightly different it is worth looking at the event configuration lists and clearing them down if there is a backlog, the "help" details on the POA web window were quite, well, "helpful" with this.

From what I have read this is an 802 flaw rather than a data sync issue. I hope this helps.

regards



QUOTE=Andy Thompson;2004445]mj@novell.com wrote:
> Hmmm, thats weird Unable to connect to DataSync server should not hamper the
> POA's ability to start. Can you please try posting your POA log files
> here?
>
> Waiting for your response.
>
> Regards
> MJ
>
>>>> On Friday, July 23, 2010 at 06:16 PM, in message

> <00-aet.4ekv4n@no-mx.forums.novell.com>,
> 00-aet<00-aet@no-mx.forums.novell.com>
> wrote:
>
>> 8.0.2 POA on SLES 10 crashed and would not restart tonite with the
>> following error in my log.
>>
>> Error with GWEvent notification [8906]: http://<my datasync
>> server>/:4500
>>
>> Shutting down the datasync server allowed my POA to start back up. I
>> restarted the datasync server after and it's all running again.
>>
>> Thoughts? 8906 is a comm error from what I can find.
>>
>> -andy


Here's the tail of the log file before the crash

19:44:19 448 SOAP allocated remote list 1 for user 1
19:44:19 448 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:19 248 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Here's the relevant tail from the restart with DS running

19:44:50 024 Starting GWSOAP-MHCP-Handler_2
19:44:50 640 Starting GWSOAP-MHCP-Handler_3
19:44:50 256 Starting GWSOAP-MHCP-Handler_4
19:44:50 872 Starting GWSOAP-MHCP-Handler_5
19:44:50 024 SOAP allocated remote list 1 for user 1
19:44:50 024 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 488 Starting GWSOAP-MHCP-Handler_6
19:44:50 640 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 872 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 392 SOAP command:[loginRequest] requested from 192.168.1.236
User session(<user1>)
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
19:44:50 512 Error with GWEvent notification [8906]:
http://192.168.1.236/:4500
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

All references in there are for the same user. Maybe something with
that account?

thanks

-andy
0 Likes
9011483 Absent Member.
Absent Member.

Re: poa crash

I have also POA crashes on suse 10.2, I needed to make an auto-restart script...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.