[HTCondor-users] Error executing condor_history remotely (version 8.5.5)

[Carles Acosta <cacosta@xxxxxx>]

Dear all,

I'm using version 8.5.5 in a dual-stack pool. I'm not sure if this is a known issue or bug, but I've discovered that I cannot run condor_history remotely since the update of the SCHEDDs to 8.5.5.

When I execute condor_history remotely, I obtain:

# condor_history -n ce13.pic.es
ÂIDÂÂÂÂ OWNERÂÂÂÂÂÂÂÂÂ SUBMITTEDÂÂ RUN_TIMEÂÂÂÂ ST COMPLETEDÂÂ CMDÂÂÂÂÂÂÂÂÂÂÂ
Failed to recieve remote ad.

Going to the SCHEDD, ce13.pic.es, in the logs, I see a core dump file and a file "2>":

-rw-r--r-- 1 condor condorÂÂÂ 1728 Jun 30 18:00 2>
-rw------- 1 rootÂÂ rootÂÂÂ 643072 Jun 30 18:00 core.HISTORY_HELPERÂÂÂ

In the logs, I see a core dump file and a file "2>":

[root@ce13 condor]# cat 2\>
Stack dump for process 189325 at timestamp 1467212911 (6 frames)
/usr/lib64/libcondor_utils_8_5_5.so(dprintf_dump_stack+0x12d)[0x3bad388add]
/usr/lib64/libcondor_utils_8_5_5.so(_Z18linux_sig_coredumpi+0x40)[0x3bad489bd0]
/lib64/libpthread.so.0[0x3baa60f7e0]
/usr/lib64/libcondor_utils_8_5_5.so(_ZN4ListIcED1Ev+0x27)[0x3bad386777]
/lib64/libc.so.6(__cxa_finalize+0x9d)[0x3baa235ebd]
/usr/lib64/libcondor_utils_8_5_5.so[0x3bad2f0dc6]
Stack dump for process 189835 at timestamp 1467213844 (6 frames)
/usr/lib64/libcondor_utils_8_5_5.so(dprintf_dump_stack+0x12d)[0x3bad388add]
/usr/lib64/libcondor_utils_8_5_5.so(_Z18linux_sig_coredumpi+0x40)[0x3bad489bd0]
/lib64/libpthread.so.0[0x3baa60f7e0]
/usr/lib64/libcondor_utils_8_5_5.so(_ZN4ListIcED1Ev+0x27)[0x3bad386777]
/lib64/libc.so.6(__cxa_finalize+0x9d)[0x3baa235ebd]
/usr/lib64/libcondor_utils_8_5_5.so[0x3bad2f0dc6]
Stack dump for process 195756 at timestamp 1467220135 (6 frames)
/usr/lib64/libcondor_utils_8_5_5.so(dprintf_dump_stack+0x12d)[0x3bad388add]
/usr/lib64/libcondor_utils_8_5_5.so(_Z18linux_sig_coredumpi+0x40)[0x3bad489bd0]
/lib64/libpthread.so.0[0x3baa60f7e0]
/usr/lib64/libcondor_utils_8_5_5.so(_ZN4ListIcED1Ev+0x27)[0x3bad386777]
/lib64/libc.so.6(__cxa_finalize+0x9d)[0x3baa235ebd]
/usr/lib64/libcondor_utils_8_5_5.so[0x3bad2f0dc6]
Stack dump for process 262508 at timestamp 1467302411 (6 frames)
/usr/lib64/libcondor_utils_8_5_5.so(dprintf_dump_stack+0x12d)[0x3bad388add]
/usr/lib64/libcondor_utils_8_5_5.so(_Z18linux_sig_coredumpi+0x40)[0x3bad489bd0]
/lib64/libpthread.so.0[0x3baa60f7e0]
/usr/lib64/libcondor_utils_8_5_5.so(_ZN4ListIcED1Ev+0x27)[0x3bad386777]
/lib64/libc.so.6(__cxa_finalize+0x9d)[0x3baa235ebd]
/usr/lib64/libcondor_utils_8_5_5.so[0x3bad2f0dc6]

On the other hand, I can run condor_history without problems locally:

[root@ce13 ~]# condor_history
ÂIDÂÂÂÂ OWNERÂÂÂÂÂÂÂÂÂ SUBMITTEDÂÂ RUN_TIMEÂÂÂÂ ST COMPLETEDÂÂ CMDÂÂÂÂÂÂÂÂÂÂÂ
 4.0 maprd009 6/29 19:03 0+03:33:52 X ??? test.shÂÂÂÂÂÂÂ
 3.0 maprd009 6/29 10:41 0+11:03:51 X ??? test.shÂÂÂÂÂÂÂ
ÂÂ 2.0ÂÂ dteam004ÂÂÂÂÂÂÂ 6/27 11:58ÂÂ 0+04:00:01 CÂÂ 6/27 16:03 test.shÂÂÂÂÂÂÂ
ÂÂ 1.0ÂÂ dteam004ÂÂÂÂÂÂÂ 6/27 11:50ÂÂ 0+04:00:03 CÂÂ 6/27 15:51 test.shÂÂÂ

Downgrading the SCHEDD to 8.5.4, condor_history starts to work remotely again.

# condor_history -n ce13.pic.es
ÂIDÂÂÂÂ OWNERÂÂÂÂÂÂÂÂÂ SUBMITTEDÂÂ RUN_TIMEÂÂÂÂ ST COMPLETEDÂÂ CMDÂÂÂÂÂÂÂÂÂÂÂ
 4.0 maprd009 6/29 19:03 0+03:33:52 X ??? test.shÂÂÂÂÂÂÂ
 3.0 maprd009 6/29 10:41 0+11:03:51 X ??? test.shÂÂÂÂÂÂÂ
ÂÂ 2.0ÂÂ dteam004ÂÂÂÂÂÂÂ 6/27 11:58ÂÂ 0+04:00:01 CÂÂ 6/27 16:03 test.shÂÂÂÂÂÂÂ
ÂÂ 1.0ÂÂ dteam004ÂÂÂÂÂÂÂ 6/27 11:50ÂÂ 0+04:00:03 CÂÂ 6/27 15:51 test.shÂÂÂÂÂ

Thanks in advance.

Cheers,

Carles

-- 
Carles Acosta i Silva
PIC (Port d'Informacià CientÃfica)
Campus UAB, Edifici D
E-08193 Bellaterra, Barcelona
Tel: +34 93 581 33 22
Fax: +34 93 581 41 10
http://www.pic.es 
AvÃs - Aviso - Legal Notice: http://www.ifae.es/legal.html