BI Platform Support Tool Issue: E2E wizard does not collect logs

[mhf]

Hello

we use BIPST 2.0.4 with SAP Host Agent 7.21 and BIP 4.1 SP6 Patch 2.

When running the E2E wizard no logs were collected, but the wizard shows a success message for both application server and web application server.

We had this issue with every BIPST 2.0.x version, but i did not have the time to find the root cause.

Every option for "Create report" works.

The already know issue mentioned in the Release Notes does not apply to us.

Log entries from SAP Host Agent when executing the E2E trace are the following.

[Thr 15496] Thu Jun 30 11:17:03 2016

[Thr 15496] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD4685BA0D558C8/0

[Thr 15496] ***LOG Q0I=> NiIWrite: P=XXXXXX:64087; L=XXXXXX:1128: send (10058: WSAESHUTDOWN: Can't send after socket shutdown) [nixxi.cpp 4599]

[Thr 15496] *** ERROR => NiIWrite: SiSend failed for hdl 13/sock 1032

    (SI_ECONN_BROKEN/10058; I4; ST; P=XXXXXX:64087; L=XXXXXX:1128) [nixxi.cpp    4599]

[Thr 3384] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD4685BA0D558C8/0

[Thr 3384] Thu Jun 30 11:17:16 2016

[Thr 3384] Operation 9C8E992821DC1ED68FD4685BA0D558C8 finished! Remove from OperationManager

[Thr 1832] Thu Jun 30 11:17:27 2016

[Thr 1832] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD46DF08720D8C8/0

[Thr 1832] ***LOG Q0I=> NiIWrite: P=XXXXXXX:64092; L=XXXXXXXX:1128: send (10058: WSAESHUTDOWN: Can't send after socket shutdown) [nixxi.cpp 4599]

[Thr 1832] *** ERROR => NiIWrite: SiSend failed for hdl 19/sock 1148

    (SI_ECONN_BROKEN/10058; I4; ST; P=XXXXXX:64092; L=XXXXXXXX:1128) [nixxi.cpp    4599]

[Thr 14296] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD46DF08720D8C8/0

Let me know if you need further information

Thanks & BR,

Michael

[Toby_Johnston · Accepted solution]

Hi Michael,

Thanks for posting!

In the case of E2E Trace log collections, it is trying to stream a potentially very large .SAR file from the server to the client.  I've seen in one case before, it appeared that the socket connection was closed at some point during this process (we suspect it was due to some proxy, firewall, or router timeout or size limitation).

Check in your E2E work directory as the log collection is running C:\Users\<user>\AppData\Roaming\BISupportTool\e2e_workdir.  Do you see a .SAR file being created in this location?  Keep refreshing this directory and let me know if the .SAR continutes to grow in size.

Also, send me the BISupportTool tracelogs generated under BIPST_INSTALL/bin/logging to my email toby.johnston@sap.com

As a side note, we are currently making some improvements to the E2E Wizard which help to speed up the log collection (parallel collections), ability to gracefully cancel after log collection has started, and also will be improving the accuracy of the Success / Fail report at the end of the trace session.  These improvements are targeted for 2.0.5

I'll look forward to your reply.

Thanks

Toby

[mfoeken · Accepted solution]

Hi Toby,

Please keep me posted on the solution ;-).

With kind regards,

Martijn

[Toby_Johnston · Accepted solution]

Hi Martijn,

I will be sure to loop back with you on this again

Cheers

Toby

[Toby_Johnston]

Hi Michael,

The E2E Trace Wizard has been greatly improved for the next patch release 2.0.5.  Here's a summary:

• Support for parallel log collections (max concurrent collections is configurable in BIPST preferences)
• Filtering by last modified date occurs on BI server side (# days since last modified is configurable in BIPST preferences).  This results in only relevant logs being collected from server and much quicker collection times
• Graceful cancelling now possible during log collection process
• More accurate progress bar timings
• More checks to make sure BO_trace.ini is restored to default state
• More accurate E2E summary report (showing what failed and what was successful)
• Many other bug fixes

Would you have some time to have a quick meeting to test the beta?  Send me an email at toby.johnston@sap.com and we can setup a time.

Thanks

Toby

[mhf]

Hi Toby,

due to issues on our BIP i hadn't time to test the beta. But i tested now the final version. Sadly still the logs won't be collected. In a first test i even did not see a *.sar file being created when collecting the logs.

Any ideas?

BR,

Michael

[Toby_Johnston]

Hey Michael,

How many hosts in your BI landscape?

In the E2E Summary report (at the end), does it show this node as "Failed"?  Do any hosts succeed?

Did you update the operations.d folder on the server with the Patch 5 operations files?

If you want to email me the tracelogs from BIPST/bin/logging that would be helpful.  I'm also still willing to have a Citrix GoToMeeting with you if you have availability.

Thanks
Toby