FAILED to Synchronize - winsock error -23 on AIX 5.3 clients

Usage and Config Platform
1

(imported topic written by SystemAdmin)

I’m having a Tivoli Endpoint Manager setup with a TEM servers, a few Relays and about 350 client in total.

Recently we have added new servers on a new network segment and for at least 3 clients the installation seems to work alright in the beginning, but after a short period the clients stops reporting to the TEM server.

Looking in the logfiles all reveal the following error:

"Error building or posting report: FileIOError

…

FAILED to Synchronize - Transport reports unknown failure - winsock error -23 - gather url - http://:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url="

On another server there are similar symptoms but in the logfile I’m only able to find “Error building or posting report: FileIOError” and no winsock error.

On yet another 26 servers (4 on AIX 5.3 and 22 on AIX 6.1) installed on similar conditions the clients are working fine and keeps reporting to the server.

I’m not able to find much information on “winsock error -23” apart from “err_THREAD_EXCEPTION Informational error should not see in production”.

The installation package has been downloaded from http://support.bigfix.com/install/besclients-nonwindows.html on the 15th on Now 2012. Server and client version are 8.2.1310.

OS on failing clients are all AIX 5.3

Can someone please help me get a clue on what can cause this error - thanks in advance.

2

(imported comment written by SystemAdmin)

The client literally got an exception when trying to gather, and it seemed to have gotten an error on generating a report.

On these AIX 5.3 machines, how big is the /var volume? Its possible that adding a relay has exhausted the space available on /var. If that is the case you can stop the components and move the contents for the /var/opt/BESClient and/or /var/opt/BESRelay directories to a larger volume and create symlinks to the new directories in the /var/opt locations, or you could enlarge the /var volume etc.

If its not that I’d suggest contacting support as we would need to see more of the logs and information that would make it hard to diagnose on the forum

3

(imported comment written by SystemAdmin)

Hi Alan

Thanks for your quick reply.

/var was out of space and after extending the volume everything works fine now - thanks!