GSKIT error 420: GSK_ERROR_SOCKET_CLOSED messages in HTEMS logs

Body

GSKIT error 420: GSK_ERROR_SOCKET_CLOSED messages in HTEMS logs

Have recently be looking at an issue where there were GSKIT error 420: GSK_ERROR_SOCKET_CLOSED messages
in the HUB TEMS log.

for example like this:

kdeberx.c,69,"KDEBE_Receive") GSKit error 420: GSK_ERROR_SOCKET_CLOSED
kdeberx.c,69,"KDEBE_Receive") GSKit error 420: GSK_ERROR_SOCKET_CLOSED

Timing wise there were no errors round them that could be linked with these calls.

There were also no issues with the running of ITM that caused concern.

It was suggested that there might be a firewall that was closing sockets, but it was not case in this environment.

 
The conclusion is that this particular message is not diagnostic.  

This message is issued when the socket is found to be closed, which is almost always the result
of some event and not the cause of some event.

 
"GSK ERROR SOCKET CLOSED" means GSKit has found the socket closed so there will be no more processing of this socket. 

Therefore this is a report that a socket has closed, it does not indicate an error or problem.

Usually if a socket is closed another is opened with no issue.

If there is a problem with the sockets there will other messages seen and possibly some function loss.