Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect() call blocks (issue with nsca-ng server?) #4

Open
falzm opened this issue Jul 12, 2015 · 1 comment
Open

Connect() call blocks (issue with nsca-ng server?) #4

falzm opened this issue Jul 12, 2015 · 1 comment

Comments

@falzm
Copy link

falzm commented Jul 12, 2015

Hi

It looks like there is a problem trying to connect to a nsca-ng server: when calling NSCAServer.Connect(), the code blocks. On the server side, it looks like this (IP address redacted):

nsca-ng: [DEBUG] Initializing connection context
nsca-ng: [DEBUG] Creating buffer (address: 0x7ea930)
nsca-ng: [DEBUG] Creating buffer (address: 0x7ea900)
nsca-ng: [DEBUG] Accepted connection from 88.x.y.z
nsca-ng: [DEBUG] Cannot accept connection right now
nsca-ng: [DEBUG] TLS handshake with 88.x.y.z not (yet) successful
nsca-ng: [DEBUG] Waiting for input from 88.x.y.z

I've tracked down the blocking point up to the nsca package, and the culprit is located at https://github.com/Syncbak-Git/nsca/blob/master/packet.go#L169

I've tried with ENCRYPT_NONE encryption and with ENCRYPT_XOR, same results... Have you any idea what could cause this problem?

@aerostitch
Copy link

Same issue, but nsca_ng has a different protocol which uses TLS connections and requires TLS_PSK_WITH_AES_256_CBC_SHA, and golang lib don't support this cipher suite yet. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants