Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
|
I have submitted a bug report for the MSI installer issue https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=7058,0 But Iâm sure there is going to be a long tail of bugs (probably many of them on Linux as well) if you install HTCondor into a directory with spaces in the pathnames.
Your workaround, to install to C:\Progra~1\Condor seems like the the best thing to do for now, but I should point out that you really need to be sure to use the *correct* short path name for âC:\Program Filesâ, it may not be C:\Progra~1
on all machines, you will need to check it first. Alternatively, you could install into C:\Program Files\Condor. Then create the configuration files by hand, and set the RELEASE_DIR configuration variable to the short pathname of âC:\Program Files\Condorâ. The bug ticket above suggests
that doing this automatically is the best way to fix this problem. When you install into c:\Progam Files. rather than into C:\Condor There is another problem
that you will have to deal with â The permissions on C:\Program Files does not allow for low privilege processes to write into that directory or directories. under it. But the default for HTCondor is to create the job sandbox directories
in $(RELEASE_DIR)\execute, and log files into $(RELEASE_DIR)\log You will need to create these directories somewhere that is writable, perhaps c:\ProgramData\Condor\Execute and c:\ProgramData\Condor\Log, and then adjust the HTCondor configuration to point to these directories. The need for these to be writable is actually the primary reason we donât install in the usual places on Windows.
Incidentally. I thought that a Windows 10 installation would create c:\Progams rather than c:\Program Files. Is this perhaps a Windows 7 install that was upgraded to Win10? From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of Hitchen, Greg (IM&T, Kensington WA) Hi Everyoneâs probably at HTCondor Week, but here goes anyway!
😉
😊
(All references here are to 8.6.13 64 bit BUT the same happens with 8.6.13 32 bit and 8.8.2 64 and 32 bit) When using the msi install file for 64 bit HTCondor 8.6.13 I get the following (Win10 machine):
Event Viewer â Windows Logs â Application shows: Product: condor-8.6.13 -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to
complete could not be run. Contact your support personnel or package vendor. Custom action CondorConfigLocal script error -2146828218, Microsoft _vbscript_ runtime error: Permission denied Line 1, Column 1,
IMPORTANT - FYI, I am installing into c:\program files as our org does not want it installed in c:\condor Iâm guessing this may possibly have something to do with trying to put/create the config files into c:\program files\condor ? The actual install seems to go mostly OK though. Itâs just that no config files are created. So I did another install on a different machine into c:\condor, copied the config files across, and changed the reference to: RELEASE_DIR = C:\Program files\condor and HTCondor seemed ââââââ sort of happy.
At least now (compared with much earlier versions, e.g. 8.0.6) it handles the long filenames OK in condor_config and can use: RELEASE_DIR = C:\Program Files\Condor rather than previously needing to use: RELEASE_DIR = C:\PROGRA~1\condor However there still seems to be issues specifically to do with spaces in folder names. e.g in StarterLog and StarterLog.slot1 the following errors occur: 05/21/19 13:19:45 (pid:8804) my_popen: CreateProcess failed err=2 05/21/19 13:19:45 (pid:8804) JavaDetect: failed to execute java -classpath C:\Program;Files\Condor\bin;C:\Program;Files\Condor\bin/scimark2lib.jar;. CondorJavaInfo old 2 05/21/19 13:19:45 (pid:8804) Failed to read results from 'docker -v': 'No such file or directory' (2) 05/21/19 13:19:45 (pid:8804) DockerAPI::detect() failed to detect the Docker version; assuming absent. 05/21/19 13:19:45 (pid:8804) my_popen: CreateProcess failed err=2 05/21/19 13:19:45 (pid:8804) FILETRANSFER: Failed to execute C:\Program, ignoring 05/21/19 13:19:45 (pid:8804) FILETRANSFER: failed to add plugin "C:\Program" because: FILETRANSFER:1:Failed to execute C:\Program, ignoring 05/21/19 13:19:45 (pid:8804) my_popen: CreateProcess failed err=2 05/21/19 13:19:45 (pid:8804) FILETRANSFER: Failed to execute Files\Condor\bin\curl_plugin.exe, ignoring 05/21/19 13:19:45 (pid:8804) 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:Failed
to execute C:\Program, ignoring 05/21/19 13:19:45 (pid:8804) my_popen: CreateProcess failed err=2 05/21/19 13:19:45 (pid:8804) FILETRANSFER: Failed to execute C:\Program, ignoring 05/21/19 13:19:45 (pid:8804) FILETRANSFER: failed to add plugin "C:\Program" because: FILETRANSFER:1:Failed to execute C:\Program, ignoring|FILETRANSFER:1:Failed to execute Files\Condor\bin\curl_plugin.exe,
ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring 05/21/19 13:19:45 (pid:8804) my_popen: CreateProcess failed err=2 05/21/19 13:19:45 (pid:8804) FILETRANSFER: Failed to execute Files\Condor\bin\data_plugin.exe, ignoring 05/21/19 13:19:45 (pid:8804) 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:Failed
to execute C:\Program, ignoring|FILETRANSFER:1:Failed to execute Files\Condor\bin\curl_plugin.exe, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring 05/21/19 13:19:45 (pid:8804) WARNING: Initializing plugins returned: FILETRANSFER:1:Failed to execute Files\Condor\bin\data_plugin.exe, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring|FILETRANSFER:1:Failed
to execute Files\Condor\bin\curl_plugin.exe, ignoring|FILETRANSFER:1:Failed to execute C:\Program, ignoring From StartLog, it seems partially happy with long filenames but not for everything: 05/21/19 13:19:44 ****************************************************** 05/21/19 13:19:44 ** condor_startd.exe (CONDOR_STARTD) STARTING UP 05/21/19 13:19:44 ** C:\Program Files\Condor\bin\condor_startd.exe 05/21/19 13:19:44 ** SubsystemInfo: name=STARTD type=STARTD(7) class=DAEMON(1) 05/21/19 13:19:44 ** Configuration: subsystem:STARTD local:<NONE> class:DAEMON 05/21/19 13:19:44 ** $CondorVersion: 8.6.13 Oct 30 2018 BuildID: 453497 $ 05/21/19 13:19:44 ** $CondorPlatform: x86_64_Windows10 $ 05/21/19 13:19:44 ** PID = 204 05/21/19 13:19:44 ** Log last touched time unavailable (No such file or directory) 05/21/19 13:19:44 ****************************************************** 05/21/19 13:19:44 Using config source: C:\Program Files\condor\condor_config 05/21/19 13:19:44 Using local config sources:
05/21/19 13:19:44 C:\Program 05/21/19 13:19:44 Files\Condor\condor_config.local 05/21/19 13:19:44 config Macros = 54, Sorted = 54, StringBytes = 1668, TablesBytes = 1984 05/21/19 13:19:44 CLASSAD_CACHING is ENABLED In addition, the registry entry for starting condor_kbdd in the user session at logon time doesnât seem to work: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run condor_kbdd REG_SZ âC:\Program files\condor\bin\condor_kbdd.exeâ No condor_kbdd daemon is appearing. Things worked better if I told the installer to install into c:\progra~1\condor Still got the install gui error popup shown above, still no config files created, still no condor_kbdd started at logon Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run condor_kbdd REG_SZ âC:\progra~1\condor\bin\condor_kbdd.exeâ BUT, none of the above errors in StarterLog, etc. Is it possible to look at fixing these sort of issues for the Windows builds? Thanks. Cheers Greg P.S. Just reiterating that there are NO issues at all if installing into c:\condor, only if installing into c:\program files |
