Re: [HTCondor-users] Failed to fetch ads from:

[hasanbaigg@xxxxxxxxx]

Please discard the previous mail and consider this one containing more messaged copied from SchedLog file.

Hi Max,

Thanks for your response. Please see the output of the commands you suggested

 First off, can you make sure your condor_schedd is

running at all?
I made sure that it is running by checking its presence in the DAEMON_LIST and verified it by running
condor_config_val DAEMON_LIST

ps aux | grep condor_schedd

cloudco+   988  0.0  0.0 112816   980 pts/7    S+   22:19   0:00 grep --color=auto condor_schedd
cloudco+  7928  0.0  0.0  49868  7404 ?        Ss   13:16   0:00 condor_schedd
cloudco+  8521  0.0  0.0  50040  7736 ?        Ss   12:05   0:00 condor_schedd
cloudco+ 10759  0.0  0.0  46692  7072 ?        Ss   12:09   0:00 condor_schedd -f

cd `condor_config_val LOG`

$

tail -f SchedLog

now running condor_q give the following message in SchedLog file

03/19/21 22:45:24 (pid:7928) SharedPortEndpoint: did not successfully find SharedPortServer address. Will retry in 60s.

03/19/21 22:46:24 (pid:7928) SharedPortEndpoint: failed to open /tmp/condor-lock.0.891890495157899/shared_port_ad: No such file or directory

03/19/21 22:46:24 (pid:7928) SharedPortEndpoint: did not successfully find SharedPortServer address. Will retry in 60s.

03/19/21 22:47:18 (pid:7928) condor_write(): Socket closed when trying to write 4096 bytes to collector cloud-copasi-new.cam.uchc.edu:11000?sock=collector, fd is 14, errno=104 Connection reset by peer

03/19/21 22:47:18 (pid:7928) Buf::write(): condor_write() failed

03/19/21 22:47:18 (pid:7928) Can't open directory "/etc/condor/passwords.d" as PRIV_ROOT, errno: 2 (No such file or directory)

Thus it is still not working.

regards
hasan

On Mar 19, 2021, at 4:05 PM, Mark Coatsworth <coatsworth@xxxxxxxxxxx> wrote:

Hi Hasan,

There should be some information in your SchedLog related to these
failed connections. First off, can you make sure your condor_schedd is
running at all?

ps aux | grep condor_schedd

Assuming it is running, try tailing your log:

cd `condor_config_val LOG`
tail -f SchedLog

Then run a few `condor_q` commands and see what comes up. Hopefully
the problem is obvious, if not then let us know what messages you're
seeing. If the condor_q is not running, there should still be some
useful information in the log file.

Mark


On Fri, Mar 19, 2021 at 12:09 PM <hasanbaigg@xxxxxxxxx> wrote:

Hi,

HT Condor on my linux centos 7 system had been working fine until I upgraded the version to 8.9.10. When i try to run âcondor_qâ command, it gives me the following error:

-- Failed to fetch ads from: <127.0.0.1:0?alias=cloud-copasi-new.cam.uchc.edu&sock=schedd_2739_9e65> : cloud-copasi-new.cam.uchc.edu
CEDAR:6001:Failed to connect to <127.0.0.1:0?alias=cloud-copasi-new.cam.uchc.edu&sock=schedd_2739_9e65>


Any help is appreciated

regards
Hasan

_______________________________________________
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://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

--
Mark Coatsworth
Systems Programmer
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin-Madison

_______________________________________________
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://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/