Error Creating Connection Connection-forced Authentication Failed
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 Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back 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 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 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 日本語 português 中文 (中国) русский Customer Portal Search Products & Services Back View All Products Infrastructure and Management Back Red Hat Enterprise Linux Red Hat Virtualization Red Hat Identity Management Red Hat Directory Server Red Hat Certificate System Red Hat Satellite Subscription Ass
arguments, to the prescribed order, i am running into an Authentication failed message. the same connection URL (without the ssl='true') used to work fine. why does the same thing fail once i enabled SSL? I see this error message in the broker's console output: " 2012-09-04 08:03:58 warning Failed to retrieve sasl username " Now if i turn on authentication by https://access.redhat.com/solutions/76003 updating the qpidd.conf file(auth=yes), the above mentioned message disappears, but the client side error remains. The client side trace can be found below: " verify_data: { 208, 246, 102, 70, 193, 230, 117, 14, 240, 106, 93, 3 } *** IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, WRITE: TLSv1 Handshake, length = http://osdir.com/ml/users-qpid.apache.org/2012-09/msg00029.html 32 IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, READ: TLSv1 Change Cipher Spec, length = 1 IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, READ: TLSv1 Handshake, length = 32 *** Finished verify_data: { 186, 100, 120, 68, 136, 96, 84, 109, 230, 123, 195, 41 } *** %% Cached client session: [Session-1, SSL_RSA_WITH_RC4_128_MD5] main, WRITE: TLSv1 Application Data, length = 8 IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, WRITE: TLSv1 Application Data, length = 12 IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, WRITE: TLSv1 Application Data, length = 308 IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, WRITE: TLSv1 Application Data, length = 12 IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, WRITE: TLSv1 Application Data, length = 4 IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, called closeOutbound() IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, closeOutboundInternal() IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, SEND TLSv1 ALERT: warning, description = close_notify IoReceiver - ec2-XXX.us-west-1.compute.amazonaws.com/127.0.0.1:5674, WRITE: TLSv1 Alert, length = 18 javax.jms.JMSException: Error creating connection: connection-forced: Authentication failed at org.apache.qpid.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:119) at org.apache.qpid.example.Hello.runTest(Hello.java:51) at org.apache.qpid.example.Hello.main(Hello.java:40) Caused by: org.apache.qpid.AMQConnectionFailureException: connection-forced: Authentication failed [error cod
Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, http://forum.spring.io/forum/spring-projects/integration/jms/128502-reply-listener-may-not-recover-from-network-outage monitor. Announcement Announcement Module Collapse No announcement yet. reply-listener may not recover from network outage Page Title Module Move Remove Collapse X Conversation Detail Module Collapse http://stackoverflow.com/questions/18664074/getting-error-peer-authentication-failed-for-user-postgres-when-trying-to-ge Posts Latest Activity Search Forums Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links error creating only Polls only Filtered by: Clear All new posts rlperry Junior Member Join Date: Apr 2012 Posts: 2 #1 reply-listener may not recover from network outage Jun 13th, 2013, 09:03 AM I am using an outbound-gateway and reply-listener with Tibco EMS. If EMS is bounced the outbound-gateway and reply-listener reconnect perfectly fine. error creating connection However, if a request occurs while the there is a network disconnect (e.g. I unplug the ethernet cable from my EMS server) the outbound-gateway seems to recover and resume sending messages but the reply-listeners does not consistently do so. When the reply-listener fails to realize it has been disconnected, the result is the outbound-gateways sending requests with reply to destination that no longer exists. Thus all requests timeout. Interestingly, not only will bouncing the client correct this situation, but so will bouncing EMS. If I remove the reply-listener and allow the outbound-gateway to create a new reply to destination with every request then recovery is very consistent. Does anyone have any ideas about how this may be overcome, outside of removing the reply-listener? The offending outbound-gateway: Code:
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Getting error: Peer authentication failed for user “postgres”, when trying to get pgsql working with rails up vote 276 down vote favorite 86 Im getting FATAL: Peer authentication failed for user "postgres" when I try to make postgres work with Rails. Here's my pg_hba.conf: http://pastebin.com/4V1sMS01 and my database.yml: http://pastebin.com/mS0G6Srp And a dump of the full trace: http://pastebin.com/bXg1Pkr5 I changed authentication to md5 in pg_hba and tried different things, but none seem to work. I also tried creating a new user and database as per Rails 3.2, FATAL: Peer authentication failed for user (PG::Error) But they don't show up on pgadmin or even when I run sudo -u postgres psql -l Any idea where I'm going wrong? ruby-on-rails postgresql share|improve this question edited May 7 '15 at 13:46 Freedom_Ben 4,56142253 asked Sep 6 '13 at 18:15 orderof1 1,5362717 1 1): Make sure you have a user named "postgres" created and having right on your Database 2): Make sure he has a password 3): Make sure your config/database.yml contains the rights credentials (username + password) –MrYoshiji Sep 6 '13 at 18:19 1 need everyplace peer and indent set to md5 –Artem.Borysov Jul 28 '15 at 8:55 3 See also this answer - connection may fail on localhost but succeed on 127.0.0.1. –uvsmtid Aug 26 '15 at 7:13 1 In my case I needed to add host: localhost in the database.yml file. –Mihail Velikov Mar 16 at 6:50 add a comment| 12 Answers 12 active oldest votes up vote 408 down vote accepted The problem is still your pg_hba.conf file (/etc/postgresql/9.1/main/pg_hba.conf). This line: local all postgres peer Should be local all postgres md5 These are brief descriptions of both options according to the official PostgreSQL docs on authentication met