Diagnosing Driver Issues
The following section gives some information about reading logs related to Drivers, and solutions to some common issues.
Driver Cannot Log In to Manager
When a Driver cannot log in to a Manager, messages similar to the following appears in the Manager log:
LoginPlugin Can't log in to PrivateBrokerConnection
LoginPlugin Failed login on http://162.60.27.152:8000/livecluster/director/PublicDriverChannel so trying next. Error:
File not found: http://162.60.27.152:8000/livecluster/director/PublicDriverChannel
When this happens, try the following:
| • | Ping and telnet to the Manager and port number to test network connectivity. |
| • | Check the user name, password, and Director values in the driver.properties file (or values coded in application). |
| • | If using SSL, make sure the certificate is valid. |
Client Timeout Issues
You might see timeout error messages in the Driver log similar to the following:
java.io.IOException: Unexpected exception while reading data from http://172.24.68.49:1667/ds-6353115010724789381/job.tasklet: com.livecluster.util.threadpool.TimeoutException: Thread DefaultPool-6:
http://172.24.68.49:1667/ds-6353115010724 789381/job.tasklet timed out
The Client Timeout setting allows for the Driver to log back in after logging off due to temporary network issues, without interrupting Services. Go to Admin > System Admin > Manager Configuration > Communication; under the HTTP Connections heading, you can increase read and write timeout values for Drivers.
Also, the Driver must not failover to another Broker too quickly. This is set in DSBrokerTimeout in the driver.properties file. The default is 300 seconds, or five minutes.
To ensure your tasks are not lost in the event of Broker failure, set Engine Timeout Minutes (at Admin > System Admin > Manager Configuration > Engines and Clients, under the Engine Login heading) for a period of time longer than the Client Timeout Minutes on the same page, under the Client Management heading. For example, if Client Timeout Minutes is set to five minutes, a good number for Engine Timeout Minutes is eight minutes. Note that changes to this value are only applied at the next Engine Login.
Manager Turning Away Clients
By default, Drivers are turned away if there is a version mismatch between Client and Manager. A message similar to the following appears in the Manager log:
[BrokerLoginManager] Turning away client: Client module version mismatch: ClientJavaVersion version: 7.0.0: should be 7.1.0.
To override this, go to Admin > System Admin > Manager Configuration > Admin, and under the Version Management heading, set Allow Driver Version Mismatch to true until the Client can be upgraded.