Re: [HTCondor-users] Jobs Becoming Idle SharedPortClient Error

["Skrzypczyk, Matthew" <matthew.skrzypczyk@xxxxxxxx>]

Thanks for the reply, the problem with our setup was that these jobs would include the following requirements:

target.machine =!= MachineAttrMachine1 && target.machine =!= MachineAttrMachine2

So when the job went into Idle the first time it would be unable to be scheduled back onto our single execute node.  Removing this requirement has allowed the jobs to continue, so this solution will have to suffice.

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cs.wisc.edu%2Fmailman%2Flistinfo%2Fhtcondor-users&data=01%7C01%7C%7Cdba2ed6997454fcf687608d4efc78937%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=%2FwC58gszDvJ3sk4bepoKhN5Plr%2BtkzkWhXVgcJjsTME%3D&reserved=0

The archives can be found at:
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.cs.wisc.edu%2Farchive%2Fhtcondor-users%2F&data=01%7C01%7C%7Cdba2ed6997454fcf687608d4efc78937%7C6d4034cd72254f72b85391feaea64919%7C1&sdata=5hXV3bOnZZe20nGKazCgFE87dDX6%2BOwJUYS%2FqWmzUiU%3D&reserved=0