Re: [HTCondor-users] Failed to start non-blocking update to <127.0.1.1:9618>

[Jaime Frey <jfrey@xxxxxxxxxxx>]

The logs show that the HTCondor daemons are trying to connect to hostname head.econets.org to join your HTCondor pool. But that hostname is resolving to IP address 127.0.1.1, which points to the local machine. The daemons need to be connecting to the machine thatâs running the collector daemon.

 - Jaime

On Apr 14, 2022, at 10:48 AM, Daniel L. Stuardo S. <daniel.stuardo@xxxxxxxxx> wrote:

Hello.
First of all, I apologize for my "Google English".
We have a cluster with 11 nodes, and suddenly, one of them, node06, stopped being seen by Condor: the node exists in the network, it can be accessed normally (the LDPA connection seems to be fine, because it loads "home" and NFS file shares), but Condor does not consider it to be one of its nodes.
a week before, 2 nodes were added to the network (they were not added to Condor), and it is possible that node 6 had started having problems since then, until Condor lost sight of it.
I must emphasize that I am a user of HTCondor, I am not the administrator: it is not available at the moment, and a solution is urgently needed.
I have searched for a solution, but the work has been unsuccessful. I will appreciate your help.
I put here an extract of the last LOG files.