(imported topic written by MariuszTyszkiewicz)
Hello,
This is my first post so please forgive me any gaffes. I’m a new to TEM. Last weeks I started long journey with it. As a new project I installed TEM primary server on Windows 2008 R2 virtual machine and 2 TEM relays on identical AIX 6.1 PPC physical machines. Since then I observe one huge problem for me: after few hours of work one of 2 relays suddenly doesn’t respond. In /var/log/BESRelay.log file on affected server I can see following messages:
Thu, 10 May 2012 12:06:04 +0300 - 1 - BES Relay version 8.2.1175.0 starting
Thu, 10 May 2012 12:06:04 +0300 - 1 - OpenSSL Initialized (Non-FIPS Mode)
Thu, 10 May 2012 16:51:46 +0300 - 2057 - PostResultsForwarder: Failed to post results to parent.
Thu, 10 May 2012 16:52:22 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:37 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:40 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:43 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:46 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:49 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:52 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:55 +0300 - 1 - PumpSockets accept error: SocketFileLimit
Thu, 10 May 2012 16:52:55 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:52:58 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:53:01 +0300 - 2057 - PostResultsForwarder: File error “CreateUniqueFileLocationFailed”
Thu, 10 May 2012 16:53:05 +0300 - 1 - PumpSockets accept error: SocketFileLimit
To quickly confirm that TEM software on affected server is “crashed” I go to following link (link is not completed to get server response):
http://relay1:52311/cgi-bin/bfenterprise/clientregister.exe?
and got the response: “Internet Explorer cannot display the webpage” => server doesn’t respond
To quickly confirm that TEM software on second server is “not crashed” I go to link (link is not completed to get server response):
http://relay2:52311/cgi-bin/bfenterprise/clientregister.exe?
and got the response: “Error: unknown request type” => server responds => it indicates that request is corrupted => OK
I see that on both servers process which listens on port 52311 is BESClient, for instance:
lsof -i -n -P |grep -i besclient
BESClient 7471208 root 5u IPv6 0xf10005000277ac00 0t0 UDP *:52311
So, in theory, all is OK. Both relay names are resolved by DNS system without any problems. The only solution is “BES Client/BES Relay” services restart on affected server (every few hours). Clean agent/relay re-installation didn’t fix my problem. There is no firewall between all 3 TEM servers. Any suggestions how to fix this ? I appreciate any hint 
Best regards,
Mariusz Tyszkiewicz