Skip to main content
Solved

403 random error on api


Forum|alt.badge.img+7

Hi guys, could not open old thread here: 

 

So creating new one.. Still same problem, I’ve increased debugging and file versions on webserver.log and couple more, but I think webserver.log is relevant here now as I see some strange lines in the logs.

First of all - login is actually successful, afterwards I can see connection being aborted!

login OK

Does someone have the knowledge to comment on those here?

ABORT connection
ABORT connection 2



Log lines:

18824 397c  07/26 12:52:34 ### XMLSerializer::serialize() - Serialized xml is : [<?xml version="1.0" encoding="UTF-8" standalone="no" ?><CNSession_PAbortRequest time="0"><status close="2" errnum="0" errtype="2"/></CNSession_PAbortRequest>]
18824 397c  07/26 12:52:34 ### BinarySerializer::serialize() - [<?xml version="1.0" encoding="UTF-8" standalone="no" ?><CNSession_PAbortRequest time="0"><status close="2" errnum="0" errtype="2"/></CNSession_PAbortRequest>]

18824 3224  07/26 12:53:28 ### CCvNetwork::Reset() - Network object is not disconnected. Please disconnect before deleting the network object. Aborting the connection
18824 3224  07/26 12:53:28 ### CCvNetwork::AbortConnection() - Aborting session with error : 2:0
18824 3224  07/26 12:53:28 ### CCvNetwork::SendXMLMessage() - CCvNetwork::Sending Object: CNSession_PAbortRequest, Remote Host:xxxx, Timeout:5, Flags:4, Remote Process:cvd.exe, Remote Pid:4688, Remote ThreadId:166c, Remote Service Name:JobControlCVD, Remote MAC:xxxx, Remote IP:xxxx

18824 3224  07/26 12:53:28 ### CCvNetwork::AbortConnection() - Connection aborted
18824 3224  07/26 12:53:28 ### info() - EvEvent message id - [23000777], job id - [0], flags - [2]

 

 

Was trying to google anything related to ‘EvEvent message id - [23000777]’ - but could not find anything.

Best answer by Mike Struening RETIRED

Sharing case solution:

Finding Details:

- Customer is report API to extract data from multiple CommCell
- Randomly gets an error 404

Solution:

- Suggested to implement Qlogoff which customer confirmed it already part of the code
- On remote session, noticed that the login issue did not occur for multiple attmpts
- Issue seems to have resolved.

View original
Did this answer your question?

4 replies

Damian Andre
Vaulter
Forum|alt.badge.img+23

Might have to cross reference the logs from cvd and qsdk to troubleshoot this further.

 

18824 3224  07/26 12:53:28 ### CCvNetwork::SendXMLMessage() - CCvNetwork::Sending Object: CNSession_PAbortRequest, Remote Host:xxxx, Timeout:5, Flags:4, Remote Process:cvd.exe, Remote Pid:4688, Remote ThreadId:166c, Remote Service Name:JobControlCVD, Remote MAC:xxxx, Remote IP:xxxx

 

You have the hostname - open cvd on that machine and filter on thread ID 166c or whatever it displays when you reproduce the error.


Forum|alt.badge.img+7
  • Author
  • Byte
  • 37 replies
  • July 26, 2022

@Damian Andre 
Looked into the cvd log and found this:

 

4688  3478  07/26 14:15:23 ### AutoDisconnect() - Handle 4574 is not disconnected by the application layer. Disconnecting the session

4688  3478  07/26 14:15:23 ### CCvNetwork::AbortConnection() - Aborting session with error : -818416048:51
4688  3478  07/26 14:15:23 ### CCvNetwork::SendXMLMessage() - CCvNetwork::Sending Object: CNSession_PAbortRequest, Remote Host:xxxx, Timeout:1, Flags:4, Remote Process:dotnet.exe, Remote Pid:18824, Remote ThreadId:4b98, Remote Service Name:, Remote MAC:3c:a8:2a:15:b6:a4, Remote IP:10.87.14.228


Also the Remote ThreadId ‘4b98’ popped up, so checked it and it also is in the filter for Remote ThreadId 166c.

Does not make sense to me :|


Mike Struening
Vaulter
Forum|alt.badge.img+23

@benjaminas , what does CVD.log show at the time in the log file @Damian Andre posted?  CVD.log generally has no Job IDs so it’s a bit tough to make direct connections if lots of jobs are running.


Mike Struening
Vaulter
Forum|alt.badge.img+23

Sharing case solution:

Finding Details:

- Customer is report API to extract data from multiple CommCell
- Randomly gets an error 404

Solution:

- Suggested to implement Qlogoff which customer confirmed it already part of the code
- On remote session, noticed that the login issue did not occur for multiple attmpts
- Issue seems to have resolved.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings