KEVIN Hamner

SystemEDGE unable to connect to socket - 'No socket to select on'

Blog Post created by KEVIN Hamner Employee on Nov 12, 2014

Issue: No socket to select on

Agent Version: 5.8.1 (12.8.1)

Platform: Windows

Resolved: 5.8.2 (12.8.2)

 

SystemEDGE unable to connect to socket - 'No socket to select on'

 

On Windows Servers running SystemEDGE 5.8.1 (12.8.1) user may see the following lines repeating in the sysedge.log:

 

    

1496961 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496962 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496963 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496964 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496965 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496966 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496967 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496968 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496969 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496970 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496971 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496972 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

1496973 2014-10-07 08:37:42.14 [W]-2004- AWM_SocketSelect           : No socket to select on.

 

The agent is unable to bind to the desired port regardless of the fact that the port is open.

 


If seen, the agent should be upgraded to 5.8.2 which resolves the issue,

Outcomes