[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] STARTER at 192.168.22.18 failed to send file(s) to <192.168.178.102:27682>; SHADOW ...
- Date: Mon, 01 Aug 2016 08:39:55 -0500
- From: Brian Bockelman <bbockelm@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] STARTER at 192.168.22.18 failed to send file(s) to <192.168.178.102:27682>; SHADOW ...
This part of the error message caught my eye:
SHADOW at 192.168.178.102 failed to write to file â
that makes me think the directory permissions on the schedd are problematic - and, as arc probably interacts with this schedd, I would also examine that too.
> On Aug 1, 2016, at 7:59 AM, Stephen Jones <sjones@xxxxxxxxxxxxxxxx> wrote:
> On 08/01/2016 01:40 PM, Brian Bockelman wrote:
>> Hi Stephen,
>> Is it possible that the interaction of arc and HTCondor is causing permission change on the directory itself? I would look at the spool directory permissions.
> Thanks Brian.
> I'll check all that.
> But please check I'm right on this:
> I'm assuming the STARTER on the worker node at the end of the job tries to output send files (in this case, *stdout* and *stderr*) to the SHADOW on the head node.
> (BTW: I don't know how STARTER knows the names of these specific files: perhaps they are specified in the job, or the wrapper or otherwise inferred from the names which contain stdout/err...). Anyway, STARTER tries to send the files back and gets permission denied.
> And I don't know whether STARTER gets permission denied because it can't read the files, or whether SHADOW gets permission denied because it can't write the files.
> So I guess that's my first question. I wonder which side is complaining? Hm...
> I'll check the logs.
> Steve Jones sjones@xxxxxxxxxxxxxxxx
> Grid System Administrator office: 220
> High Energy Physics Division tel (int): 43396
> Oliver Lodge Laboratory tel (ext): +44 (0)151 794 3396
> University of Liverpool http://www.liv.ac.uk/physics/hep/
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: