Red Hat Bugzilla – Bug 1004170
Condor service cannot start after installation and machine restart
Last modified: 2016-05-26 15:33:29 EDT
Description of problem:
After installation and restart the machine the condor service cannot start (it is not started automatically and it is not possible to start it manually). The error message appears after attempting to start the condor service:
"Windows could not start the condor service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion."
There are two error messages in the Windows logs:
"A timeout was reached (30000 milliseconds) while waiting for the condor service to connect."
"The condor service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
This issue was appeared on Windows Server2008-x86 and Windows Server 2008-x64 only, not on Windows Server2008 R2 or another Windows platform.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the msi package.
2. Restart the machine.
3. Wait several minutes and look at if the condor service is running; if it is not, try to run it manually.
The condor service cannot run and the error message is displayed.
The condor service should be running and if it is not currently running, it should be possible to run it manually.
This issue did not occur on condor-win-7.8.9-0.2 (condor-win-7.8.9-0.4 was added into brew the same day as the package condor-win-7.8.9-0.5, so it was not tested).
Installed condor-win-7.8.9-0.5 cannot start only on Windows Server2008-x86 and x64; it runs normally on other Windows platforms.
If I can help with anything, write me, please.
The condor service can be installed and run on all supported Windows platforms.
Verified on condor-win-7.8.9-0.8 on platforms:
- Windows7-x86 and x64
- Windows Server2003-x86 and x64
- Windows Server2008-x86, x64 and R2
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.