CODEWITHSUNDEEP
azuredockerdockerfileazureservicebusazure-eventhub
Preethi
Preethi

Reputation: 11

Azure service bus fails connecting to kubernetes docker

When I try to access my sb endpoint in my local machine/local docker it fetches the data without any issue but when I try to access it across kubernetes cluster(docker) the connection to socket fails. Is there any SDK/configs/dependencies that I would have to install in my docker to access the SB. The error looks like below.

Found /start.sh, running...
Initializing Client...
[INFO] [2020-07-14 16:00:06] 'eventhub.pysdk-b0fab61b': Created the Event Hub client
[INFO] [2020-07-14 16:00:06] Connection b'bc610657-4dbf-4bc2-aa39-38b6889e6047' state changed from <ConnectionState.UNKNOWN: 999> to <ConnectionState.START: 0>
[INFO] [2020-07-14 16:00:16] b'Failure: select failure.' (b'/data/src/vendor/azure-uamqp-c/deps/azure-c-shared-utility/adapters/socketio_berkeley.c':b'wait_for_connection':370)
[INFO] [2020-07-14 16:00:16] b'wait_for_connection failed' (b'/data/src/vendor/azure-uamqp-c/deps/azure-c-shared-utility/adapters/socketio_berkeley.c':b'socketio_open':770)
[INFO] [2020-07-14 16:00:16] b'Closing tlsio from a state other than TLSIO_STATE_EXT_OPEN or TLSIO_STATE_EXT_ERROR'
[INFO] [2020-07-14 16:00:16] b'Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.' (b'/data/src/vendor/azure-uamqp-c/deps/azure-c-shared-utility/adapters/tlsio_openssl.c':b'on_underlying_io_open_complete':760)
[INFO] [2020-07-14 16:00:16] b'Failed opening the underlying I/O.' (b'/data/src/vendor/azure-uamqp-c/deps/azure-c-shared-utility/adapters/tlsio_openssl.c':b'tlsio_openssl_open':1258)
[INFO] [2020-07-14 16:00:16] b'xio_open failed' (b'/data/src/vendor/azure-uamqp-c/src/saslclientio.c':b'saslclientio_open_async':1097)
[INFO] [2020-07-14 16:00:16] b'Opening the underlying IO failed' (b'/data/src/vendor/azure-uamqp-c/src/connection.c':b'connection_open':1344)
[INFO] [2020-07-14 16:00:16] Connection b'bc610657-4dbf-4bc2-aa39-38b6889e6047' state changed from <ConnectionState.START: 0> to <ConnectionState.END: 13>
[INFO] [2020-07-14 16:00:16] Connection with ID b'bc610657-4dbf-4bc2-aa39-38b6889e6047' unexpectedly in an error state. Closing: False, Error: None
[INFO] [2020-07-14 16:00:16] b'Begin session failed' (b'/data/src/vendor/azure-uamqp-c/src/link.c':b'link_attach':1282)
[INFO] [2020-07-14 16:00:16] b'Link attach failed' (b'/data/src/vendor/azure-uamqp-c/src/message_receiver.c':b'messagereceiver_open':381)
[INFO] [2020-07-14 16:00:16] b'AMQP management instance not open' (b'/data/src/vendor/azure-uamqp-c/src/amqp_management.c':b'amqp_management_close':1029)
[INFO] [2020-07-14 16:00:16] CBS for connection b'bc610657-4dbf-4bc2-aa39-38b6889e6047' completed opening with status: 1
[INFO] [2020-07-14 16:00:16] b'Failed opening message receiver' (b'/data/src/vendor/azure-uamqp-c/src/amqp_management.c':b'amqp_management_open_async':990)
/start.sh complete - exit status_code=1

Upvotes: 0

Views: 1036

Answers (1)

Kibrantn
Kibrantn

Reputation: 609

while I can't claim deep familiarity with docker (Am however one of the ServiceBus sdk maintainers for Python) this appears to be in the broad category of "network totally unavailable" error. I would first make sure that the standard AMQP ports (5671/15671) are open and properly exposed (potentially bidirectionally) for the container+local network.

Apologies if this would be better suited as a comment, karma makes me unable to do so, don't hesitate to shout if this doesn't seem to help.

Upvotes: 2

Related Questions