The problem was a sebool that needed to be set. Setsebool -P cobbler_can_network_connect
1.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Stuart J. Newman
Engineer 4; Systems
Solar Dynamics Observatory (SDO)
Honeywell Technology Solutions Inc
NASA/Goddard Space Flight Center
Building 14, Room E222
Mail Stop 428.2
Greenbelt, MD 20771
Office: (301) 286-5145
Mobile: (443) 878-0280
E-Mail: Stuart.J.Newman@nasa.gov
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: This communication, including any attachment, contains information that may be
confidential or privileged, and is intended solely for the entity or individual to whom it
is addressed. If you are not the intended recipient, please notify the sender at once,
and you should delete this message and are hereby notified that any disclosure, copying,
or distribution of this message is strictly prohibited. Nothing in this email, including
any attachment, is intended to be a legally binding signature.
-----Original Message-----
From: Nishanth Aravamudan [mailto:nacc@linux.vnet.ibm.com]
Sent: Thursday, January 16, 2014 13:13
To: Newman, Stuart J. (GSFC-444.0)[HONEYWELL TECHNOLOGY SOLUTIONS INC]
Cc: cobbler mailing list
Subject: Re: [cobbler] Login issue
On 16.01.2014 [15:23:50 +0000], Newman, Stuart J. (GSFC-444.0)[HONEYWELL TECHNOLOGY
SOLUTIONS INC] wrote:
I am not a python programmer, so I don't know how to debug this.
Here's my rough guide to what I'd look for:
The traceback.print_exc() call in
/usr/lib/python2.6/site-packages/cobbler/modules/authn_ldap.py::authenticate()
line 104 in v2.4, is:
tls = str(tls).lower()
if port != '636':
if tls in [ "on", "true", "yes", "1" ]:
try:
dir.start_tls_s()
except:
traceback.print_exc()
return False
Which I think means that tls is still on, but tls fails to connect. So you might have
changed the setting without restarting cobblerd.
Thanks,
Nish