[Condor-users] Condor Segmentation Fault

[Ibad Kureshi U0850037 <U0850037@xxxxxxxxx>]

Hello All,

I am kind of new to the Condor Admin side of things. We have recently added a condor pool to our HPC network and are now trying to integrate the condor pool with our existing LSF and TORQUE clusters by adding the main Grid Access point as a submit node to the pool. The problem we are getting is that if a user who is authenticated on the LDAP tries to run ANY condor based command e.g. condor_q or condor_status the error reported is 'SEGMENTATION FAULT'.

Currently as this is a test we have kept the security settings minimum and UID domains to the $(FULL_HOSTNAME) and have seen that jobs go across to the nodes if submitted from a machines local user base rather than an LDAP authenticated user. i.e. if the user exists in /etc/passwd it works if the USER is in the LDAP it gives a SEGMENTATION FAULT.

I am guessing as the system is set to $(FULL_HOSTNAME) the LDAP entries are not being invoked. The reason we have kept it as $(FULL_HOSTNAME) is that the Submit nodes and the Master node are not in the same domain as the execute nodes. Either way the SEGMENTATION FAULT error seems misleading.

I did find this: https://partner-bugzilla.redhat.com/show_bug.cgi?id=571804 but I do not think it is now relevant.  Googling does not bring much up either. There was this (bottom of the page): http://www.dice.inf.ed.ac.uk/units/research_and_teaching/documentation/unit/beowulf/condor.html but Memory is not an issue as the submit node has 24GB of RAM and if pretty empty.

Our Network is a CENTOS box as a master node and the same as a submit node (authenticated on LDAP). The execute nodes are a mix of WinXP WinXP64 and Win7 systems (in an AD network)

Any help is greatly appreciated.

Ibad Kureshi


---
This transmission is confidential and may be legally privileged. If you receive it in error, please notify us immediately by e-mail and remove it from your system. If the content of this e-mail does not relate to the business of the University of Huddersfield, then we do not endorse it and will accept no liability.