| 374 | = Debugging = |
| 375 | |
| 376 | It is possible to get HLK into strange states. For example: |
| 377 | |
| 378 | * HLK clients / support machines do not get into "Ready" state |
| 379 | * Launching two-machine tests fail with duplicate database key errors |
| 380 | |
| 381 | Some things you can try to get past these errors: |
| 382 | |
| 383 | * Restart the "hlksvc" Windows service |
| 384 | * Reboot HLK nodes (controller, clients, support machine) |
| 385 | * Reinstall HLK client software and reboot HLK client |
| 386 | * Create a new HLK project |
| 387 | * Create a new pool and move HLK client machines there |
| 388 | * Delete HLK clients from the pool |
| 389 | |
| 390 | The are known to work sometimes, but so far I have not been able to establish any logic here. |
| 391 | |