Welcome, Guest
Please Login or Register.    Lost Password?

Fatal signal 11 - pam auth (ldap)
(1 viewing) (1) Guest
Go to bottomPage: 1
TOPIC: Fatal signal 11 - pam auth (ldap)
#3466
Fatal signal 11 - pam auth (ldap) 6 Years, 6 Months ago Karma: 0
Hi,
i have installed GO-Global_for_UNIX-RedHat_Enterprise_Linux-5.0-x86_64.bin with demo license for now.
When I connect to the server it asks me about username and password, after I provide credentials it shows in status bar that connection to server has ended and window with credentials seems to be hung up.

Like in the topic I use pam/ldap auth.

So the question is what may I did wrong? or what should I check?

Here is the fragment of gold log (I can provide full if needed):

(t:DF51A750) (master) [11 May 06:43:38]: master[5]: leader(24118) started
(t:DF51A750) (master) [11 May 06:43:38]: leader[5]: client connection to 192.168.1.30:28429 established
(t:DF51A750) (master) [11 May 06:43:38]: leader[5]: pam-login: authenticating user
(t:DF51A750) (master) [11 May 06:43:43]: utility[3]: Fatal signal: 11
---- SYSTEM FAULT DIAGNOSTICS ----
Time Stamp: Wed May 11 06:43:43 2011
Process ID: 24118
Process: GraphonProcess
User ID: root (0)

#0 0x0000003a786c5f00 in __read_nocancel () from /lib64/libc.so.6
#1 0x0000003a7866cc07 in _IO_new_file_underflow () from /lib64/libc.so.6
#2 0x0000003a7866d5ce in _IO_default_uflow_internal () from /lib64/libc.so.6
#3 0x0000003a786626b4 in _IO_getline_info_internal () from /lib64/libc.so.6
#4 0x0000003a78661559 in fgets () from /lib64/libc.so.6
#5 0x00000000004db480 in go_generic_getStackTrace(int) ()
#6 0x00000000004db337 in go_GLIBC_getStackTrace(int) ()
#7 0x00000000004db319 in go_StandardSigSEGVHandler ()
#8 <signal handler called>
#9 0x0000003fa4e23ccc in ssl23_connect () from /lib64/libssl.so.6
#10 0x00000000004f69d5 in SSL_connect ()
#11 0x0000003fa622c0ac in ldap_int_tls_start () from /usr/lib64/libldap-2.3.so.0
#12 0x0000003fa620c25f in ldap_int_open_connection () from /usr/lib64/libldap-2.3.so.0
#13 0x0000003fa621d5bc in ldap_new_connection () from /usr/lib64/libldap-2.3.so.0
#14 0x0000003fa620c0ea in ldap_open_defconn () from /usr/lib64/libldap-2.3.so.0
#15 0x0000003fa621df0e in ldap_send_initial_request () from /usr/lib64/libldap-2.3.so.0
#16 0x0000003fa6214299 in ldap_sasl_bind () from /usr/lib64/libldap-2.3.so.0
#17 0x0000003fa6214779 in ldap_simple_bind () from /usr/lib64/libldap-2.3.so.0
#18 0x00002b5ce0aad0b4 in ?? () from /lib64/security/pam_ldap.so
#19 0x00002b5ce0aad85f in ?? () from /lib64/security/pam_ldap.so
#20 0x00002b5ce0aaee8c in ?? () from /lib64/security/pam_ldap.so
#21 0x00002b5ce0aaf176 in pam_sm_authenticate () from /lib64/security/pam_ldap.so
#22 0x0000003a7d602dc7 in _pam_dispatch () from /lib64/libpam.so.0
#23 0x0000003a7d6026d2 in pam_authenticate () from /lib64/libpam.so.0
#24 0x00000000004ae454 in PAMAuthenticator::collectCredentials(AuthServer*) ()
#25 0x00000000004abb05 in Authenticator::Authenticate() ()
#26 0x000000000049c1b5 in SessionLeader::startup() ()
#27 0x000000000049abb6 in SessionLeader::SessionLeader(graphon::Socket*, GoldOptions&) ()
#28 0x0000000000491c7d in Gold::runLeader(graphon::Socket*) ()
#29 0x0000000000491b6c in Gold::acceptClientConnection(graphon::ServerSocket*) ()
#30 0x0000000000491724 in Gold::processConnections() ()
#31 0x000000000048fdc9 in main ()
(t:DF51A750) (master) [11 May 06:43:44]: utility[3]: debug_info: [Thread debugging using libthread_db enabled]
(t:DF51A750) (master) [11 May 06:43:44]: utility[3]: debug_info: 0x0000003a786c5f00 in __read_nocancel () from /lib64/libc.so.6
(t:DF51A750) (master) [11 May 06:43:44]: utility[3]: debug_info: Saved corefile /root/.graphon/core-GraphonProcess.24118
----- END DIAGNOSTICS -----
(t:DF51A750) (master) [11 May 06:43:44]: utility[3]: Fatal signal: 11, 28 stack frames follow:
(t:DF51A750) (master) [11 May 06:43:44]: utility[3]: /usr/local/graphon/bin/gold(_Z22go_GLIBC_getStackTracei+0x24) [0x4db344]

and few lines more..
Stan
Fresh Boarder
Posts: 3
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#3467
Re:Fatal signal 11 - pam auth (ldap) 6 Years, 6 Months ago Karma: 6
Try changing your authentication from PAM to password. PAM is the default authentication.

In /usr/local/graphon/etc/ locate the gold.conf file.
Open/edit the file and find the line starting with "auth".

Change it from
auth = pam
to
auth = pass

Save and restart the goglobalux service.
Erikt
Administrator
Posts: 591
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#3468
Re:Fatal signal 11 - pam auth (ldap) 6 Years, 6 Months ago Karma: 0
auth = pass => it works ok but only for accounts that exist on that machine.

But I need ldap for authentication and I have read that it is already supported, so what in that case?
Stan
Fresh Boarder
Posts: 3
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#3489
Re:Fatal signal 11 - pam auth (ldap) 6 Years, 5 Months ago Karma: 2
Stan,

We think this is a conflict between the SSL version we include with GO-Global and the SSL version on the system used by the PAM LDAP libraries. We have an engineering build that does NOT link against our own SSL and uses the system version if you want to try it. The caveat is that since it's based on a Red Hat Enterprise 3.x build, you'll need to install the openssl097a package to provide the libraries that are compatible.

The build is available from our FTP site at:

ftp://ftp.graphon.com/private/troy/engineering/GO-Global_for_UNIX-RedHat_Linux_WS-3.0-x86_64.bin

(I am assuming that you're running 64-bit and not 32-bit, let me know if that's not the case.)

We are still evaluating a final fix for the problem, but hopefully this engineering build will confirm that we understand the issue and allow you to use the product in the meantime.

Thanks,
Troy
troy
Administrator
Posts: 231
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Birthday: 01/14
Last Edit: 2011/06/10 17:51 By troy.Reason: forgot to include link to file.
The administrator has disabled public write access.
 
#3496
Re:Fatal signal 11 - pam auth (ldap) 6 Years, 5 Months ago Karma: 0
Ok i have downloaded and installed this package:
ftp://ftp.graphon.com/private/troy/engineering/GO-Global_for_UNIX-RedHat_Linux_WS-3.0-x86_64.bin

But I use Red Hat Enterprise Linux Client release 5.2 (Tikanga) and got openssl-0.9.8b-10.el5 installed on it, so installation of openssl097a is kind of problematic.
But I did soft links:
libcrypto.so.4 -> libcrypto.so.0.9.8b
libssl.so.4 -> libssl.so.0.9.8b
and server has started up.

And again auth = pass works fine but auth = pam gives errors (fragment of gold log below):

(t:9190AF60) (master) [15 Jun 10:29:24]: master[5]: leader(9722) started
(t:9190AF60) (master) [15 Jun 10:29:24]: leader[5]: client connection to 192.168.1.86:65038 established
(t:9190AF60) (master) [15 Jun 10:29:24]: leader[5]: pam-login: authenticating user
(t:9190AF60) (master) [15 Jun 10:29:24]: leader[5]: pam-login: Authentication failed: Authentication Error: Authentication f
ailure(7)
(t:9190AF60) (master) [15 Jun 10:29:27]: leader[3]: SessionLeader(pid:9722)::startup got exception: Authentication Error: Au
thentication failure(7)
(t:9190AF60) (master) [15 Jun 10:29:27]: leader[3]: error running leader: Authentication Error: Authentication failure(7)
(t:9190AF60) (master) [15 Jun 10:29:27]: master[5]: leader(9722) exited

Since I made those links for openssl, I dont know if this help you anyhow, but if you want me to check/change anything else please let let me know.

Thanks,
Stan
Stan
Fresh Boarder
Posts: 3
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 1
Moderators: troy, Andyl