Re: [HTCondor-users] debug-cli.{user}.log

[Larry Martell <larry.martell@xxxxxxxxx>]

On Tue, Mar 7, 2023 at 11:30 AM John M Knoeller via HTCondor-users
<htcondor-users@xxxxxxxxxxx> wrote:
>
> From that error message, I would expect to see
>
>
>
> debug-cli.lmartell.log
>
>
>
> show up as a file in the jobâs TransferOutput or Out attribute,  can you check and see if that is true?

No it is not in either. I do see this in the startd_history log:

SpooledOutputFiles = "debug-cli.lmartell.log"

> From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Larry Martell
> Sent: Monday, March 6, 2023 4:53 PM
> To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
> Subject: [HTCondor-users] debug-cli.{user}.log
>
>
>
> A few months ago we started seeing files named debug-cli.{user}.log (e.g. debug-cli.lmartell.log) showing up in our Iwd dir. They are always zero length. No place in any of our code do we mention a file like that. What is creating them and is there a way to prevent them from being created? We have jobs failing with messages like this:
>
>
>
> HoldReason = "Error from slot1_1@xxxx@yyyy.com: STARTER at 10.232.160.146 failed to send file(s) to <10.232.160.128:9618>; SHADOW at 10.232.160.128 failed to write to file /inst/common/Cluster/tmp/debug-cli.lmartell.log: (errno 13) Permission denied"