Skip to content

st2sensorcontainer behaves differently in Docker vs standalone #5743

Answered by ip-sf
ip-sf asked this question in Operations
Discussion options

You must be logged in to vote

Finally making some good headway... and I think I found smoke.

What appears to be happening is; pika is having issues with resolution running inside st2sensorcontainer inside docker.

Changing the sensor config to use an IP instead of a hostname now allows me to start/stop st2sensorcontainer binary, as well as restart (in place) the docker container. I can toggle host: "rabbitmq" to and from host: "<ip>" and replicate reliably.

I need to dive into pika's resolution logic next to try and see whats going on and how it may be getting chomped by st2sensorcontainer. I think ill be starting here based on this is where the logic seems to be halting

[-] process_timeouts: invoking callback=<bound …

Replies: 9 comments 9 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
4 replies
@ip-sf
Comment options

@ip-sf
Comment options

@arm4b
Comment options

@ip-sf
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@arm4b
Comment options

@ip-sf
Comment options

Comment options

You must be logged in to vote
3 replies
@arm4b
Comment options

@ip-sf
Comment options

@arm4b
Comment options

Answer selected by ip-sf
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 participants