Impacts to http file transfers from SQUID resolved

[chtc-users@xxxxxxxxxxx]

Greetings CHTC users,Â

This message is for users of our high throughput computing (HTC) system.

We have identified and fixed the problem with our SQUID servers that was causing jobs to go on hold this morning.Â

If you have jobs that have gone on hold due to this issue, you can release them using the following HTCondor command:

condor_release -constraint '(HoldReasonCode == 12) && (HoldReasonSubCode == 0)'

Please direct any questions or concerns to chtc@xxxxxxxxxxx.Â

Best,

Your CHTC Team

On Thu, Jan 28, 2021 at 11:15 AM chtc-users--- via CHTC-users <chtc-users@xxxxxxxxxxx> wrote:

Greetings CHTC users,

This message is for users of our high throughput computing (HTC) system.

CHTC staff have identified an issue causing http transfers from our SQUID server to fail and jobs to go on hold as a result. Affected jobs will have a hold message like this (visible in job log files, or by running âcondor_q -holdâ):Â

Error from slot1_0@xxxxxxxxxxxxxxxxxx: FILETRANSFER:1:non-zero exit (1) from /usr/libexec/condor/curl_plugin. Error: Callback aborted (http://proxy.chtc.wisc.edu/SQUID/filename)

We are working to resolve the issue; in the meantime, please refrain from submitting new batches of jobs that depend on files from SQUID. We will send an update to this list when SQUID capabilities are stable again and affected jobs can be released.Â

Please direct any questions or concerns to chtc@xxxxxxxxxxx.

Best,

Your CHTC Team

_______________________________________________
CHTC-users mailing list
CHTC-users@xxxxxxxxxxx
To unsubscribe send an email to:
chtc@xxxxxxxxxxx