Pam Auth Error Ricci

Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing Back saslauthd pam auth error Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red

Saslauthd 0 No Authentication Failed Ldap

Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back 0 no authentication failed testsaslauthd Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red saslauthd do_auth : auth failure: Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux

Debug: Auth_pam: Pam_authenticate Failed: Authentication Failure

Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back English español Deutsch italiano 한국어 français æ—¥æœ

redhat com> Subject: Re: [Linux-cluster] conga: luci authentication issues - SOLVED Date: Thu, 13 Dec 2007 15:45:09 +0000 I was running luci-0.10.0-6.el5.centos.1.i386.rpm on the CentOS server and ricci-0.9.3-2.fc6.i386.rpm authentication to the ricci agent at :11111 failed on the Fedora 7 boxes. I've updated the ricci rpms to ricci-0.10.0-6.el5.centos.1.i386.rpm smtpd_sasl_type and it works great! Cheers, Pedro Bandim Faustino email/sip: pedro faustino fccn pt Pedro Bandim Faustino wrote: Hi all, I'm running luci on a CentOS 5.1 and trying to connect to ricci agents on a two node cluster of Fedora 7. When on luci I try to "Add an https://access.redhat.com/solutions/730793 existing cluster", and tick the checkbox "View system certificates before ...", luci shows the fingerprint of the host. But when trying to add the host, the error I'm getting is "Unable to authenticate to the ricci agent on a.b.c.d" On the ricci side, this is the error on /var/log/messages: Dec 13 13:09:00 a.b.c.d saslauthd[25858]: do_auth : auth failure: [user=root] [service=ricci] [realm=] https://www.redhat.com/archives/linux-cluster/2007-December/msg00138.html [mech=pam] [reason=PAM auth error] Does someone know how to solve this? Thank you, Pedro Bandim Faustino email/sip: pedro faustino fccn pt FCCN - Fundação para a Computação Científica Nacional Av. do Brasil, n.º 101 1700-066 Lisboa Tel: +351 21 844 0100 Fax: +351 21 847 2167 www.fccn.pt Aviso de Confidencialidade Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218440100 devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218440100 and delete it immediately. -- Linux-cluster mailing list Linux-cluster redhat com https://www.redhat.com/mailman/listinfo/linux-cluster Attachment: smime.p7s Description: S/MIME Cryptographic Signature References: Re: [Linux-cluster] File system checking From: Lon Hohberger Re: [Linux-cluster] File system checking From: Scott Becker [Linux-cluster] conga: problems getting luci up and running From: Pedro Bandim Fau

:-| General support questions including new installations Post Reply Print view Search Advanced search 11 http://www.centos.org/forums/viewtopic.php?t=13560 posts 1 2 Next Eisofen Posts: 4 Joined: 2007/11/07 10:31:29 Cluster with conga :-| Quote Postby Eisofen » 2009/06/05 15:33:19 Hello,I'm trying to setup a Cluster, mainly for GFS2 which is hosted on SAN connected to both nodes via FC.Both nodes are pingeable from the mamangement host and each other, pam auth all are in the same subnet, both nodes are in /etc/hostsWhen I try to setup an new Cluster with that nodes I'll get this messages:The following errors occurred:Unable to connect to dscln01.renzel.de.isb: Unable to establish an SSL connection to dscln01.renzel.de.isb:11111: The SSL certificate for dscln01.renzel.de.isb:11111 is not trustedUnable to connect to pam auth error dscln02.renzel.de.isb: Unable to establish an SSL connection to dscln02.renzel.de.isb:11111: The SSL certificate for dscln02.renzel.de.isb:11111 is not trustedI tried to debug it with starting ricci -f -d:Code: Select all[root@dscln01 ~]# ricci -u 101 -f -d
failed to load authorized CAs
failed to load authorized CAs
client added
exception: SSL_read() error: SSL_ERROR_ZERO_RETURN: Success
request completed in 83 milliseconds
client added
exception: SSL_read() error: SSL_ERROR_ZERO_RETURN: Success
request completed in 41 milliseconds
client removed
client removed
client added
exception: SSL_read() error: SSL_ERROR_ZERO_RETURN: Success
request completed in 163 milliseconds
client added
exception: SSL_read() error: SSL_ERROR_ZERO_RETURN: Success
request completed in 78 milliseconds
client removed
client removed
the same happen when I only use IPsCode: Select allpingtest:
[root@bexmaster lib]# ping dscln01.renzel.de.isb
PING dscln01.renzel.de.isb (10.0.0.41) 56(84) bytes of data.
64 bytes from dscln01.renzel.de.isb (10.0.0.41): icmp_seq=1 ttl=64 time=0.618 ms