Comments (11)
@motmot80 - Everything works fine when I use my test project, which is what I used to reproduce the problem last time.
- Are you using the cache backend as is indicated in this comment
- Could you please attach your complete RabbitMQ configuration file?
from rabbitmq-server.
@motmot80 everything works fine when I use the cache backend -
https://github.com/lukebakken/rabbitmq-server-9031/blob/main/rabbitmq.conf
We will need more information! If you could provide REST-Mock and RabbitMQ debug logs that would be great.
from rabbitmq-server.
I also confirmed the following, using my test project:
- RMQ 3.11.10 - fails
- RMQ 3.11.21 - works
- RMQ 3.13.2 - works
from rabbitmq-server.
@lukebakken I am on it!
from rabbitmq-server.
Sorry for the delay. I needed to remove project specific information.
Here are the k8s cluster definitions. As you can see the only difference is changing the RMQ image version.
3.11 is working. 3.12 not.
k8s-rmq-cluster-definition-3-12-fail.yml.txt
k8s-rmq-cluster-definition-3-11-ok.yml.txt
from rabbitmq-server.
@motmot80
I cannot reproduce it against 3.12.13 docker image (more specifically rabbitmq:3.12.13-management). Can you try that image? and also, could you please send us your logs after enabling debug level?
from rabbitmq-server.
@MarcialRosales @lukebakken note that the most recent 3.12 release is 3.12.14
.
from rabbitmq-server.
Yep, I have been testing using the rabbitmq:3.12-management
image, which is 3.12.14
from rabbitmq-server.
@michaelklishin I have even tested against v3.12.x and v3.13.x branches. I picked 3.12.13 because that is what the customer is using.. well, not exactly, they are using rabbitmq:3.12.13-debian-12-r2-main
.. so i suggest them to use 3.12.13.
from rabbitmq-server.
is the image used in the example.
We will change the image to 3.12.14-management on an isolated environment and extract the debug logs.
But I think that will take until Tuesday, May 28th.
from rabbitmq-server.
Good news - as you already found out - the issue does not occur on the 3.12.14 RabbitMQ from RabbitMQ.
We tested several setups by changing just the docker image.
We were probably very unlucky that exactly this error pattern reappeared in 3.12.+-bitnami debian version.
Because in this case it's related to the base image and not RabbitMQ we can close the issue.
So I think we need to change to image base.
Maybe vmware(tanzu/pivotal) can interally address this issue to the vmware(bitnami) colleagues.
vmware/bitnami 3.11.21-debian-11-r0
OK
2024-05-27 17:27:13.394747+00:00 [info] <0.2126.0> accepting AMQP connection <0.2126.0> (127.0.0.1:33584 -> 127.0.0.1:5672)
2024-05-27 17:27:13.547123+00:00 [debug] <0.2126.0> User 'TESTUSER' failed authentication by backend rabbit_auth_backend_internal
2024-05-27 17:27:13.547440+00:00 [debug] <0.2126.0> auth_backend_http: GET https://AUTHSERVICE/auth/user?username=USER&password=PWD
2024-05-27 17:27:13.547541+00:00 [debug] <0.2126.0> auth_backend_http: request timeout: 15000, connection timeout: 15000
2024-05-27 17:27:13.708774+00:00 [debug] <0.2126.0> auth_backend_http: response code is 200, body: "allow"
2024-05-27 17:27:13.708909+00:00 [debug] <0.2126.0> User 'TESTUSER' authenticated successfully by backend rabbit_auth_backend_cache
2024-05-27 17:27:13.709293+00:00 [debug] <0.2126.0> auth_backend_http: GET https://AUTHSERVICE/auth/user?username=USER&password=PWD
2024-05-27 17:27:13.709390+00:00 [debug] <0.2126.0> auth_backend_http: request timeout: 15000, connection timeout: 15000
2024-05-27 17:27:13.791276+00:00 [debug] <0.2126.0> auth_backend_http: response code is 200, body: "allow"
2024-05-27 17:27:13.791475+00:00 [info] <0.2126.0> AMQP 1.0 connection <0.2126.0>: user 'TESTUSER' authenticated
vmware/bitnami 3.12.13-debian-12-r2
NOT OK
2024-05-27 17:38:54.347834+00:00 [info] <0.1111.0> accepting AMQP connection <0.1111.0> (127.0.0.1:43424 -> 127.0.0.1:5672)
2024-05-27 17:38:54.522839+00:00 [debug] <0.1111.0> User 'TESTUSER' failed authentication by backend rabbit_auth_backend_internal
2024-05-27 17:38:54.523212+00:00 [debug] <0.1111.0> auth_backend_http: GET https://AUTHSERVICE/auth/user?username=USER&password=PWD
2024-05-27 17:38:54.523378+00:00 [debug] <0.1111.0> auth_backend_http: request timeout: 15000, connection timeout: 15000
2024-05-27 17:39:00.525899+00:00 [error] <0.1111.0> closing AMQP connection <0.1111.0> (127.0.0.1:43424 -> 127.0.0.1:5672):
2024-05-27 17:39:00.525899+00:00 [error] <0.1111.0> {handshake_error,starting,0,
2024-05-27 17:39:00.525899+00:00 [error] <0.1111.0> {'v1_0.error',{symbol,<<"amqp:unauthorized-access">>},
2024-05-27 17:39:00.525899+00:00 [error] <0.1111.0> {utf8,<<"PLAIN login refused: rabbit_auth_backend_cache failed authenticating TESTUSER: {failed_connect,\n [{to_address,\n {\"AUTHSERVICE\",\n 443}},\n {inet,\n [inet],\n {option,\n server_only,\n fail_if_no_peer_cert}}]}">>},
2024-05-27 17:39:00.525899+00:00 [error] <0.1111.0> undefined}}
vmware/bitnami 3.12.14-debian-12-r1
NOT OK
2024-05-27 18:16:34.323787+00:00 [info] <0.1418.0> accepting AMQP connection <0.1418.0> (127.0.0.1:53436 -> 127.0.0.1:5672)
2024-05-27 18:16:34.496925+00:00 [debug] <0.1418.0> User 'TESTUSER' failed authentication by backend rabbit_auth_backend_internal
2024-05-27 18:16:34.497238+00:00 [debug] <0.1418.0> auth_backend_http: GET https://AUTHSERVICE/auth/user?username=USER&password=PWD
2024-05-27 18:16:34.497348+00:00 [debug] <0.1418.0> auth_backend_http: request timeout: 15000, connection timeout: 15000
2024-05-27 18:16:37.467018+00:00 [debug] <0.1422.0> accepting AMQP connection <0.1422.0> (127.0.0.6:51729 -> 192.168.2.56:5672)
2024-05-27 18:16:37.467182+00:00 [debug] <0.1422.0> closing AMQP connection <0.1422.0> (127.0.0.6:51729 -> 192.168.2.56:5672):
2024-05-27 18:16:37.467182+00:00 [debug] <0.1422.0> connection_closed_with_no_data_received
2024-05-27 18:16:40.499074+00:00 [error] <0.1418.0> closing AMQP connection <0.1418.0> (127.0.0.1:53436 -> 127.0.0.1:5672):
2024-05-27 18:16:40.499074+00:00 [error] <0.1418.0> {handshake_error,starting,0,
2024-05-27 18:16:40.499074+00:00 [error] <0.1418.0> {'v1_0.error',{symbol,<<"amqp:unauthorized-access">>},
2024-05-27 18:16:40.499074+00:00 [error] <0.1418.0> {utf8,<<"PLAIN login refused: rabbit_auth_backend_cache failed authenticating TESTUSER: {failed_connect,\n [{to_address,\n {\"AUTHSERVICE\",\n 443}},\n {inet,\n [inet],\n {option,\n server_only,\n fail_if_no_peer_cert}}]}">>},
2024-05-27 18:16:40.499074+00:00 [error] <0.1418.0> undefined}}
vmware/rabbitmq 3.12.14-management
OK
2024-05-27 17:27:13.394747+00:00 [info] <0.2126.0> accepting AMQP connection <0.2126.0> (127.0.0.1:33584 -> 127.0.0.1:5672)
2024-05-27 17:27:13.547123+00:00 [debug] <0.2126.0> User 'TESTUSER' failed authentication by backend rabbit_auth_backend_internal
2024-05-27 17:27:13.547440+00:00 [debug] <0.2126.0> auth_backend_http: GET https://AUTHSERVICE/auth/user?username=USER&password=PWD
2024-05-27 17:27:13.547541+00:00 [debug] <0.2126.0> auth_backend_http: request timeout: 15000, connection timeout: 15000
2024-05-27 17:27:13.708774+00:00 [debug] <0.2126.0> auth_backend_http: response code is 200, body: "allow"
2024-05-27 17:27:13.708909+00:00 [debug] <0.2126.0> User 'TESTUSER' authenticated successfully by backend rabbit_auth_backend_cache
2024-05-27 17:27:13.709293+00:00 [debug] <0.2126.0> auth_backend_http: GET https://AUTHSERVICE/auth/user?username=USER&password=PWD
2024-05-27 17:27:13.709390+00:00 [debug] <0.2126.0> auth_backend_http: request timeout: 15000, connection timeout: 15000
2024-05-27 17:27:13.791276+00:00 [debug] <0.2126.0> auth_backend_http: response code is 200, body: "allow"
2024-05-27 17:27:13.791475+00:00 [info] <0.2126.0> AMQP 1.0 connection <0.2126.0>: user 'TESTUSER' authenticated
Thank you very much for your support.
Best regards
Thomas
from rabbitmq-server.
Related Issues (20)
- Streams: consider allowing non-numerical values for publishingId HOT 3
- Log tls handshake timeouts HOT 1
- Include x-death header in Stream messages HOT 1
- 4.x: reduce default maximum message size further (e.g. to 64 or 50 MiB) HOT 14
- Publish `amqp_client` 3.13.x GA versions to hex
- Emit event if configured queue length is reached HOT 1
- Don't close connection if channel without finished publish is closed HOT 3
- [Prometheus] Reduce number of series for per-exchange/per-queue metrics HOT 9
- Logout action does not fully work on management UI
- Consul peer discovery: nodes can leave behind a service record in case of an unresolvable address HOT 2
- Output "last write" time for Streams
- Peer Discovery with DNS record wont cluster HOT 2
- 3.13.2: "x-opt-rabbitmq-received-time" only available for new messages HOT 5
- Allow Khepri post-migration step to not delete certain files or dirs HOT 1
- k8s peer discovery : rabbitmq pods are booting as a standalone nodes on ipv6 environment. HOT 4
- prometheus.filter_aggregated_queue_metrics_pattern has no effect HOT 3
- Shovels cant be deleted if they dont connect HOT 2
- rabbit_heartbeat.erl compile error with erlang OTP 27 HOT 2
- x-death header count is no longer incremented from RabbitMQ version 3.13.0+ HOT 14
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rabbitmq-server.