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

Intentions SPOA gives expected capabilities error #1

Open
NickMRamirez opened this issue Sep 18, 2019 · 3 comments
Open

Intentions SPOA gives expected capabilities error #1

NickMRamirez opened this issue Sep 18, 2019 · 3 comments
Labels

Comments

@NickMRamirez
Copy link
Contributor

Currently, the SPOA that checks Intentions is giving me an error when a request is received:

echo_1           | time="2019-09-18T20:02:40Z" level=info msg="spoe: hello from @: map[capabilities:pipelining engine-id:54DB81E3-F4EA-4899-BE8D-5F6F1EC62A1A max-frame-size:16380 supported-versions:2.0]"
echo_1           | time="2019-09-18T20:02:40Z" level=error msg="spoe: error handling connection: hello: expected capabilities [async pipelining]"
echo_1           | 127.0.0.1:52874 | GET /
echo_1           | time="2019-09-18T20:02:40Z" level=info msg="spoe: hello from @: map[capabilities:pipelining engine-id:54DB81E3-F4EA-4899-BE8D-5F6F1EC62A1A max-frame-size:16380 supported-versions:2.0]"
@bedis
Copy link
Contributor

bedis commented Sep 18, 2019

Hi Nick,

This looks like related to this: criteo/haproxy-spoe-go#3
Please enforce nbthread to 1 for now

@NickMRamirez
Copy link
Contributor Author

Yes, setting nbthread to 1 fixes the error. To do that, I can set the environment variable GOMAXPROCS = 1 and it sets nbthread to 1.

@bedis
Copy link
Contributor

bedis commented Sep 18, 2019

Ok cool.
I know @Aestek is aware of the problem and will fix it ;)

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

No branches or pull requests

3 participants