Connection Error 4161
Support Search GitHub This repository Watch 47 Star 663 Fork 153 nsqio/go-nsq Code Issues 13 Pull requests 0 Projects 0 Pulse Graphs New issue consumer: unexpected re-connection attempts #177 Closed imjoshholloway opened this Issue Apr 29, 2016 · 20 comments Projects None yet Labels bug Milestone No milestone Assignees No one assigned 3 participants imjoshholloway commented Apr 29, 2016 I'm currently investigating an issue where even after calling either DisconnectFromNSQLookupd or DisconnectFromNSQD on a host that is already disconnected, re-connection attempts still occur. In our scenario we are consuming from 3 hosts: 10.0.0.1/10.0.0.2/10.0.0.3 and the host 10.0.0.1 becomes unhealthy (service stopped) we remove it from the list of nodes and call DisconnectFromNSQLookupd or DisconnectFromNSQD. As you can see from the following log output, the connection to host 10.0.0.1 was lost and re-connection attempts are made. The host is then removed from our list and DisconnectFromNSQLookupd is called. However, the re-connection attempts still occur: 2016-04-29 14:35:26 [INF] (10.0.0.1:4150) connecting to nsqd (consumer.go 508) 2016-04-29 14:35:26 [DBG] IDENTIFY response: &{MaxRdyCount:2500 TLSv1:false Deflate:false Snappy:false AuthRequired:false} (conn.go 328) 2016-04-29 14:35:29 [ERR] IO error - EOF (conn.go 471) 2016-04-29 14:35:29 [INF] beginning close (conn.go 611) 2016-04-29 14:35:29 [INF] readLoop exiting (conn.go 528) 2016-04-29 14:35:29 [INF] breaking out of writeLoop (conn.go 535) 2016-04-29 14:35:29 [INF] writeLoop exiting (conn.go 581) 2016-04-29 14:35:29 [INF] finished draining, cleanup exiting (conn.go 660) 2016-04-29 14:35:29 [INF] clean close complete (conn.go 668) 2016-04-29 14:35:29 [DBG] there are 2 connections left alive (consumer.go 741) 2016-04-29 14:35:29 [DBG] (10.0.0.1:4150) re-connecting in 15 seconds... (consumer.go 776) 2016-04-29 14:35:44 [INF] (10.0.0.1:4150) connecting to nsqd (consumer.go 508) 2016-04-29 14:35:44 [ERR] (10.0.0.1:4150) error connecting to nsqd - dial tcp 10.0.0.1:4150: getsockopt: connection refused (consumer.go 790) 2016-04-29 14:35:44 [DBG] (10.0.0.1:4150) re-connecting in 15 seconds... (consumer.go 776) 2016-04-29 14:35:59 [INF] (10.0.0.1:4150) connecting to nsqd (consumer.go 508) 2016-04-29 14:35:59 [ERR] (10.0.0.1:4150) error connecting to nsqd - dial tcp 10.0.0.1:4150: getsockopt: connection refused (consumer.go 790) 2016-04-29 14:35:59 [DBG] (10.0.0.1:4150) re-connecting in 15 seconds... (consumer.go 776) 2016-04-29 14:36:14 [INF] (10.
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsSupportCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: SSMA for Sybase connection error. SQL Server https://github.com/nsqio/go-nsq/issues/177 > SQL Server Tools Question 0 Sign in to vote Hi, I am trying to use SSMA for Sybase and keep getting this error when connecting to a ASE 15.0 https://social.msdn.microsoft.com/Forums/netframework/en-US/08773ac7-f530-4161-bfb7-741512a41431/ssma-for-sybase-connection-error?forum=sqltools server. "Error parsing connection parameters. See the inner exception for details." Where can I see the inner exceptions on SSMA? Any pointers are greatly appreciated. Wednesday, July 22, 2009 6:24 PM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.Would you like to participate? Privacy statement © 2016 Microsoft. All rights reserved.Terms of Use|Trademarks|Privacy Statement|Site Feedback
attempt; connecting via ssl; Mapping SSL error -5000 to 4176 Technote (FAQ) Question An application fails http://www-01.ibm.com/support/docview.wss?uid=swg21198731 to connect to a Lotus Domino server using SSL. This failure could be for any protocol: HTTP, LDAP, SMTP, etc. The connection might have worked before or the application could be connecting for the first time. If you work with IBM Support to enable debug, such as Debug_SSL_All=1, the following output is observed: 12:28:54.63 PM int_MapSSLError> Mapping connection error SSL error 0 to 0 12:28:54.64 PM SSL_Handshake> Enter 12:28:54.64 PM SSL_Handshake> Current Cipher 0x0000 (Unknown Cipher) 12:28:54.64 PM SSL_Handshake> SSL Undetermined attempt 12:28:54.64 PM SSL_Handshake> After handshake state= 11 Status= -5000 12:28:54.64 PM SSL_Handshake> Exit Status = -5000 12:28:54.64 PM int_MapSSLError> Mapping SSL error -5000 to 4176 Answer This error can occur when the connecting application connection error 4161 finds one of the following is true about the Domino key ring file: The certificate is stamped by a Certificate Authority that the application does not trust The host name in the certificate does not match the host name used to connect to Domino The certificate has expired To resolve the problem, consider the following options: If the Certificate Authority is not trusted, import the trusted root certificate into the application. If the host name does not match that in the certificate, set the application to connect using the appropriate host name. If the certificate has expired, you might need to replace the certificate with a new certificate with an expiration in the future. For any of the three cases, it may be possible to set the application to accept the certificate despite the apparent problem. Document information More support for: IBM Domino LDAP Software version: 6.5, 7.0, 8.0, 8.5 Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS Software edition: All Editions Reference #: 1198731 Modified date: 2007-01-10