Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
|
Since Windows Vista, it has been necessary to run an instance of the KBDD as the logged-in user on the user's desktop. A KBDD started by the condor_master runs on the services desktop and cannot see keyboard and mouse activity.
Consequently on Windows, you don't want to put the KBDD into the DAEMON_LIST. If it is there, then the master will start the KBDD, but the only thing that instance of KBDD can do is update the registry so that when a user logs in a second KBDD that
can see the keyboard and mouse will be started.
Once the registry has been updated, either by the installer, by your own code, or by hack_kbdd_registry(),
you can remove the KBDD from the DAEMON_LIST, to stop hack_kbdd_registry() from being run again.
Taking KBDD out of the DAEMON_LIST is the "knob" that disables the registry updating behavior. If you want to actually stop the KBDD from being started whenever a user logs in, you must take the KBDD out of the registry and also delete the CONDOR_KBDD registry
key at HKLM\Software\Microsoft\Windows\CurrentVersion\Run
-tj
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Hitchen, Greg (IM&T, Kensington WA) <Greg.Hitchen@xxxxxxxx>
Sent: Sunday, August 29, 2021 7:55 PM To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx> Subject: Re: [HTCondor-users] [ExternalEmail] Re: Issues with HTCondor 9.0.x MSI installer on Windows Hi John
Yes, we’ve been using c:\progra~1\condor as the release and local dir’s since day 1 way back in 2005! Our deployment system (using kix32) also creates a symlink to c:\progra~2\condor, and we have (and still) are using the 32bit HTCondor version as our production system.
The test 64 bit version (8.8.12) and install I have been fiddling with seems to handle the folder name space OK for jobs, i.e. from a 32 bit HTCondor submit node. I guess I should test that it also works from a 64bit HTCondor version on a submit node.
On a slightly different subject, a few months ago I was tracking down why we had 2 condor_kbbd entries in the registry (32 bit and 64 bit), and why the entry would return after deleting it. I must have missed it in the version changelog, but google eventually found me the source code with the hack_kbdd_registry() function to insert the condor_kbdd into: HKLM\Software\Microsoft\Windows\CurrentVersion\Run Our deployment software was already doing this, but because it was running under kix32 (32bit) it ended up in the WOW6432Node registry section whereas the hack_kbdd_registry() function was placing it into the “normal” 64bit registry section. We have since disabled adding the entry this in our deployment code. For interests sake, is it possible to disable the hack_kbdd_registry() function in some way? It didn’t look like it from the source code, but is there a knob to control it?
Thanks
Cheers
Greg
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of John M Knoeller
Yes. Condor itself now tolerates spaces in the paths to the condor daemons, but jobs frequently do not, so we still recommend that Condor be installed in a directory without a space in the path.
You can mitigate the issue for jobs if you configure EXECUTE to be a directory without a space in the path, including by using a short pathname like
EXECUTE = C:\PROGRA~1\Condor\Execute
-tj From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Hitchen, Greg (IM&T, Kensington WA) <Greg.Hitchen@xxxxxxxx>
I did notice however the following errors in the StarterLog which is unhappy with the space in the directory name.
08/27/21 18:02:22 (pid:2292) my_popen: CreateProcess failed err=2 08/27/21 18:02:22 (pid:2292) JavaDetect: failed to execute java -classpath C:\Program;Files\Condor\bin;C:\Program;Files\Condor\bin/scimark2lib.jar;. CondorJavaInfo old 2 08/27/21 18:02:22 (pid:2292) Failed to read results from 'docker -v': 'No such file or directory' (2) 08/27/21 18:02:22 (pid:2292) DockerAPI::detect() failed to detect the Docker version; assuming absent. 08/27/21 18:02:22 (pid:2292) my_popen: CreateProcess failed err=2 08/27/21 18:02:22 (pid:2292) FILETRANSFER: Failed to execute C:\Program, ignoring 08/27/21 18:02:22 (pid:2292) FILETRANSFER: failed to add plugin "C:\Program" because: FILETRANSFER:1:Failed to execute C:\Program, ignoring 08/27/21 18:02:22 (pid:2292) my_popen: CreateProcess failed err=2 08/27/21 18:02:22 (pid:2292) FILETRANSFER: Failed to execute Files\Condor\bin\curl_plugin.exe, ignoring 08/27/21 18:02:22 (pid:2292) FILETRANSFER: failed to add plugin "Files\Condor\bin\curl_plugin.exe" because: FILETRANSFER:1:Failed to execute Files\Condor\bin\curl_plugin.exe, ignoring|FILETRANSFER:1:"C:\Program -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring 08/27/21 18:02:22 (pid:2292) my_popen: CreateProcess failed err=2 08/27/21 18:02:22 (pid:2292) FILETRANSFER: Failed to execute C:\Program, ignoring 08/27/21 18:02:22 (pid:2292) FILETRANSFER: failed to add plugin "C:\Program" because: FILETRANSFER:1:Failed to execute C:\Program, ignoring|FILETRANSFER:1:"Files\Condor\bin\curl_plugin.exe -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute Files\Condor\bin\curl_plugin.exe, ignoring|FILETRANSFER:1:"C:\Program -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring 08/27/21 18:02:22 (pid:2292) my_popen: CreateProcess failed err=2 08/27/21 18:02:22 (pid:2292) FILETRANSFER: Failed to execute Files\Condor\bin\data_plugin.exe, ignoring 08/27/21 18:02:22 (pid:2292) FILETRANSFER: failed to add plugin "Files\Condor\bin\data_plugin.exe" because: FILETRANSFER:1:Failed to execute Files\Condor\bin\data_plugin.exe, ignoring|FILETRANSFER:1:"C:\Program -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring|FILETRANSFER:1:"Files\Condor\bin\curl_plugin.exe -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute Files\Condor\bin\curl_plugin.exe, ignoring|FILETRANSFER:1:"C:\Program -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring 08/27/21 18:02:22 (pid:2292) WARNING: Initializing plugins returned: FILETRANSFER:1:"Files\Condor\bin\data_plugin.exe -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute Files\Condor\bin\data_plugin.exe, ignoring|FILETRANSFER:1:"C:\Program -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring|FILETRANSFER:1:"Files\Condor\bin\curl_plugin.exe -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute Files\Condor\bin\curl_plugin.exe, ignoring|FILETRANSFER:1:"C:\Program -classad" does not support any methods, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring
Cheers
Greg
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Hitchen, Greg (IM&T, Kensington WA)
Just as an FYI John, I had a similar error when installing from the msi file for version 8.8.12 but only when installing into c:\program files\condor.
It worked OK if I installed into c:\condor
I could then uninstall it, reinstall it into c:\program files\condor, copy the condor_config file from the c:\condor install (the uninstall does not remove this) into c:\program files\condor and change the item: RELEASE_DIR = C:\Condor to RELEASE_DIR = C:\Program Files\Condor and everything seemed to work OK.
I hadn’t tried this for a while, but it was pleasing to see that HTCondor is now happy to handle the space in C:\Program Files\Condor
Cheers
Greg
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of John M Knoeller
Hi Fabrice.
From an Administrator command prompt can you run the installer with logging enabled ?
msiexec /log inst905.1.log /i condor-9.0.5-Windows-x64.msi
Once installation is complete (or failed) can you then query the ACLs on the files in the install directory?
icacls c:\condor
and
icacls c:\condor\*
and send me the output?
I have tried a fresh install and I think I'm seeing the same thing that you did. It looks like the recent Windows update has disabled the ability of installers to run _vbscript_, which is what we use to take the questions the installer asks and use the answers to customize the condor config files.
The good news is that Condor is actually installed, and once you fix the ACLs on condor_config and condor_config.local and edit the config as needed, Condor will work.
The bad news is that the questions that the installer asked aren't doing any good. condor_config will not have any of those customizations, and it will also not be readable by ordinary users.
You can fix the ACL's of the condor_config files by running this command from an administrator command prompt
icacls condor_config* /grant BUILTIN\Users:RX
After that you have will have to configure condor by editing the condor config files by hand.
It is probably still less work to do this than to use the tarball installer.
I have added this as a bug ticket to our ticket tracking system.
-tj
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Fabrice Bouye <FabriceB@xxxxxxx>
Hi, I am starting preliminary tests to see how condor 9.0.x behave before attempting further upgrades to our 8.8.x flock. As part of the tests I am setting up HTCondor anew on a test Linux CM and a couple of selected Windows/Linux/macOS submit/execute machine to form a new mini test flock. However I have issues with the provided MSI installer which fails to install properly on Windows 10.
Note: I have searched the issue before and some had it occurring in previous versions when attempting to install HTCondor in directories containing space in their name. Here I am just installing into c:\condor\ Installation was done with an account that has administrative permissions on the computer. Also the HTCondor 8.8.12 MSI installer just installs fine without any error on the same Windows 10 machine.
The HTCondor 9.0.5 MSI installer proceeds OK through the license, pool, behavior, accounting domain, email settings, Java settings, permissions settings, universe settings, destination folder and ready to install screens. It then asked for elevated access and proceeds with installation, but, near the end of the installation, it fails and issues the following error:
> There is a problem with this Windows Install package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.
The install wizard then lands on the following screen:
> condor-9.0.5 Setup Wizard ended prematurely > > condor-9.0.5 Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard.
However at this stage, modifications have been made to the system:
* the c:\condor\ has been created and filled * The condor service has been registered * the condor uninstallation has been registered (and working) * some files, such as condor_config and condor_config.local seem to have incoherent access permissions (ie: they are not accessible by the account who performed the installation).
I will have a look into deploying the ZIP archive as an alternative even tough it’s not what the manual recommends and the instructions at https://htcondor.readthedocs.io/en/latest/admin-manual/windows-installer.html#manual-installation-of-htcondor-on-windows are a bit lacking…
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– As part of our emissions reduction strategy, please only print this email if necessary
|
