Quantcast
Channel: VMware Communities : All Content - VMware View
Viewing all articles
Browse latest Browse all 9103

Security Servers Crashing - Old version of View Clients Issue

$
0
0

We are having an issue were it seems our security servers randomly stop responding and our load balancer (F5) sends an alert out.

 

When verifying the logs we see the following:

 

2015-11-28T15:43:59.794-05:00 WARN  (0E24-05AC) <pool-1-thread-15> [PooledProcessor] Problem processing HTTP connection: Read timed out

2015-11-28T15:43:59.794-05:00 DEBUG (0E24-05AC) <pool-1-thread-15> [PooledProcessor] Problem processing HTTP connection from /74.110.122.XXX:53923: java.net.SocketTimeoutException: Read timed out

2015-11-28T15:43:59.794-05:00 WARN  (0E24-0CD8) <pool-1-thread-4> [PooledProcessor] Problem processing HTTP connection: Read timed out

2015-11-28T15:43:59.794-05:00 DEBUG (0E24-0CD8) <pool-1-thread-4> [PooledProcessor] Problem processing HTTP connection from /74.110.122.XX:53924: java.net.SocketTimeoutException: Read timed out

2015-11-28T15:43:59.810-05:00 WARN  (0E24-0EC0) <pool-1-thread-17> [PooledProcessor] Problem processing HTTP connection: Read timed out

 

or

 

2015-11-28T13:23:51.216-05:00 DEBUG (0E68-057C) <pool-1-thread-9> [PooledProcessor] Problem processing HTTP connection from /68.10.113.xx:54527: java.net.SocketTimeoutException: Read timed out

2015-11-28T13:23:51.216-05:00 WARN  (0E68-0CD4) <pool-1-thread-1> [PooledProcessor] Problem processing HTTP connection: Read timed out

2015-11-28T13:23:51.216-05:00 WARN  (0E68-05A0) <pool-1-thread-6> [PooledProcessor] Problem processing HTTP connection: Read timed out

2015-11-28T13:23:51.216-05:00 DEBUG (0E68-0CD4) <pool-1-thread-1> [PooledProcessor] Problem processing HTTP connection from /68.10.113.xx:54525: java.net.SocketTimeoutException: Read timed out

2015-11-28T13:23:51.216-05:00 DEBUG (0E68-05A0) <pool-1-thread-6> [PooledProcessor] Problem processing HTTP connection from /68.10.113.xx:54533: java.net.SocketTimeoutException: Read timed out

2015-11-28T13:23:51.232-05:00 DEBUG (0E68-0338) <pool-1-thread-11> [PooledProcessor] SSL handshake exception for /167.114.229.xx:32937, error was: no cipher suites in common

2015-11-28T13:23:51.232-05:00 DEBUG (0E68-0338) <pool-1-thread-11> [PooledProcessor] SSL handshake exception for /167.114.229.xx:32927, error was: no cipher suites in common

2015-11-28T13:23:51.232-05:00 DEBUG (0E68-0F00) <pool-1-thread-17> [PooledProcessor] SSL handshake exception for /167.114.229.xx:56650, error was: Remote host closed connection during handshake

2015-11-28T13:23:51.232-05:00 DEBUG (0E68-0338) <pool-1-thread-11> [PooledProcessor] SSL handshake exception for /167.114.229.xx:32943, error was: Remote host closed connection during handshake

 

 

I opened a ticket with VMware and they told me that this is related to old version of the view client and that the only way is upgrading the clients.... Great..... I asked them if there are ways to block old client and they said there is none...

 

So now I'm trying to find a way of notifying the users with old clients to upgrade.

 

Being this in a university, we can't control the versions students have installed so what I would like to do is to create a script that somehow will verify their client version and spit out a message asking them to upgrade.

 

Does anyone know of a way to identify the client version? I check the Volatile Environment and there does not seem to be an entry there..


Viewing all articles
Browse latest Browse all 9103

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>