Hi,
I have a job description file which has these settings:
log = BusyThreads.$(Cluster).$(Process).log
output = BusyThreads.$(Cluster).$(Process).stdout
Error = BusyThreads.$(Cluster).$(Process).stderr
Initialdir = C:\condor\usr\scratch
This works fine. All files (.log, .stdout, .stderr) are written correctly to C:\condor\usr\scratch.
Then I changed initialdir to an UNC path:
initialdir = \\QNAP-STORAGE\Data\JasonL\htcondor\scratch
Then the .log is OK, but .stdout and .stderr are both created but have 0 byte. The .log shows the following error:
007 (054.000.000) 03/23 11:45:40 Shadow exception!
Error from slot1@S3C-MASTER1: STARTER at 192.168.46.11 failed to send file(s) to <192.168.46.22:52247>; SHADOW at 192.168.46.22 failed to write to file \\QNAP-STORAGE\Data\JasonL\htcondor\scratch\BusyThreads.54.0.stdout:
(errno 22) Invalid argument
195 - Run Bytes Sent By Job
353 - Run Bytes Received By Job
Then I mapped the UNC path \\QNAP-STORAGE\Data to Y: drive, but to no avail. Basically the same error:
initialdir = Y:\JasonL\htcondor\scratch
The .log is still OK, but .stdout and .stderr are both created but have 0 byte. The .log shows the following error:
007 (055.000.000) 03/23 11:53:22 Shadow exception!
Error from slot1@S3C-MASTER1: STARTER at 192.168.46.11 failed to send file(s) to <192.168.46.22:52295>; SHADOW at 192.168.46.22 failed to write to file \\QNAP-STORAGE\Data\JasonL\htcondor\scratch\BusyThreads.55.0.stdout:
(errno 22) Invalid argument
195 - Run Bytes Sent By Job
353 - Run Bytes Received By Job
It looks like htcondor has unmapped my Y: drive back to UNC path.
Iâve tried various other things, including:
My question: is UNC path not working for initialdir or am I not doing something right?
The fact that .log file is written OK to the correct location means the initialdir must have been parsed correctly. The 0-byte .stdout and .stderr are strange though.
I am running htcondor 8.4.4 on Windows Server 2008 R2.
Thanks
Jason
PRIVACY AND CONFIDENTIALITY NOTICE |