[bitnami/rabbitmq] Not_Authorized when using existingClaim

default-doe commented 1 year ago

Name and Version

bitnami/rabbitmq 11.15.5

What architecture are you using?

amd64

What steps will reproduce the bug?

$ helm upgrade --install rabbitmq bitnami/rabbitmq --version 11.15.5 --namespace rabbitmq-qa --set persistence.enabled=true --set persistence.existingClaim=$MY_EXISTING_CLAIM --set auth.username=csmqadmin --set auth.password=test1234

Are you using any custom parameters or values?

No response

What is the expected behavior?

I should authenticate with the custom credentials passed as values.

What do you see instead?

Getting invalid credentials when using the existingClaim. 2023-06-05 10:11:07.035675+00:00 [warning] <0.1133.0> HTTP access denied: user 'csmqadmin' - invalid credentials

Additional information

I have double checked that $RABBITMQ_PASSWORD is the one as expected.

Mauraza commented 1 year ago

Hi @default-doe,

Could you add more information about the persistence are you using? Where are you deploying the chart?

default-doe commented 1 year ago

Hola @Mauraza,

These are the PV & PVC that I'm manually creating.

apiVersion: v1
kind: PersistentVolume
metadata:
  name: application-pv-development-rabbitmq
  annotations:
spec:
  accessModes:
    - ReadWriteMany
  capacity:
    storage: 10G
  csi:
    driver: cephfs.manila.csi.openstack.org
    volumeHandle: volume-development-rabbitmq
    nodeStageSecretRef:
      name:  os-trustee
      namespace: kube-system
    nodePublishSecretRef:
      name:  os-trustee
      namespace: kube-system
    volumeAttributes:
      shareID: $MY_SHARE_ID
      shareAccessID: $MY_SHARE_ACCESS_ID

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: application-pvc-rabbitmq
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10G
  storageClassName: ""

The chart is being deployed in a K8s cluster with version v1.25.3, deployed in the OpenStack cloud.

Mauraza commented 1 year ago

Hi @default-doe,

if you check the values.yaml 🔽 appears that the access mode is ReadWriteOnce. Could you update the value or update the PVC? https://github.com/bitnami/charts/blob/1b86d3bbc335202697a155b6d9738b4f01328a40/bitnami/rabbitmq/values.yaml#L899-L925

kevinp89 commented 1 year ago

Hello! im getting the same error as well. The existing PVC is attached to the pod correctly and is RWO. I have provided rabbitmq the auth.username and auth.password but it keeps outputting this error:

2023-06-14 20:34:37.231105+00:00 [warning] <0.717.0> HTTP access denied: user 'rabbit' - invalid credentials
2023-06-14 20:35:07.241837+00:00 [warning] <0.725.0> HTTP access denied: user 'rabbit' - invalid credentials
2023-06-14 20:35:21.928360+00:00 [warning] <0.729.0> HTTP access denied: user 'rabbit' - invalid credentials
2023-06-14 20:35:37.290757+00:00 [warning] <0.735.0> HTTP access denied: user 'rabbit' - invalid credentials

However, when i go into the pod and do a change_password

rabbitmqctl change_password rabbit <same_password_as_before>

it changes password and pod terminates, restarts and pod comes up fine. Hope this comment helps figuring out the issue

kevinp89 commented 1 year ago

regarding my above comment, I went ahead and removed the persistence.storageClass that i had set and it seems like volume got attached and user was authenticated just fine. Hope this helps!

Mauraza commented 1 year ago

Hi @kevinp89,

Could you try again the command with erlangCookie?

$ helm upgrade --install rabbitmq bitnami/rabbitmq --version 11.15.5 --namespace rabbitmq-qa \
  --set persistence.enabled=true --set persistence.existingClaim=$MY_EXISTING_CLAIM \
  --set auth.username=csmqadmin --set auth.password=test1234 --set auth.erlangCookie=secretcookie

Please check https://github.com/bitnami/charts/tree/main/bitnami/rabbitmq#upgrading

kevinp89 commented 1 year ago

Hello, i have tried that has well. i got the erlang cookie and set it in the values file, but the error still persists. It is still unable to authenticate user

Mauraza commented 1 year ago

Hi @kevinp89,

Could you add to the deploy image.debug=true and check if appears something more in the logs?

gregory-pierre commented 1 year ago

Hi @Mauraza I reproduced the same problem. I could not find anything relevant in the logs produced by the container (see below). The authentication errors at the end of the logs are caused by readiness probe failures. I believe that Kubernetes is using the right password specified by auth.password but the container generated a different password randomly. It doesn't happen when persistence is disabled. If I manually change the password using "rabbitmqctl change_password" as @kevinp89 said, it works but this is a workaround. Thank you

[38;5;6mrabbitmq [38;5;5m20:44:07.97 [0m
[38;5;6mrabbitmq [38;5;5m20:44:07.97 [0m[1mWelcome to the Bitnami rabbitmq container[0m
[38;5;6mrabbitmq [38;5;5m20:44:07.97 [0mSubscribe to project updates by watching [1mhttps://github.com/bitnami/containers[0m
[38;5;6mrabbitmq [38;5;5m20:44:07.97 [0mSubmit issues and feature requests at [1mhttps://github.com/bitnami/containers/issues[0m
[38;5;6mrabbitmq [38;5;5m20:44:07.97 [0m
[38;5;6mrabbitmq [38;5;5m20:44:07.97 [0m[38;5;2mINFO [0m ==> ** Starting RabbitMQ setup **
[38;5;6mrabbitmq [38;5;5m20:44:07.99 [0m[38;5;2mINFO [0m ==> Validating settings in RABBITMQ_* env vars..
[38;5;6mrabbitmq [38;5;5m20:44:08.00 [0m[38;5;2mINFO [0m ==> Initializing RabbitMQ...
[38;5;6mrabbitmq [38;5;5m20:44:08.01 [0m[38;5;5mDEBUG[0m ==> Creating environment file...
[38;5;6mrabbitmq [38;5;5m20:44:08.01 [0m[38;5;5mDEBUG[0m ==> Creating enabled_plugins file...
[38;5;6mrabbitmq [38;5;5m20:44:08.02 [0m[38;5;5mDEBUG[0m ==> Creating Erlang cookie...
[38;5;6mrabbitmq [38;5;5m20:44:08.02 [0m[38;5;5mDEBUG[0m ==> Ensuring expected directories/files exist...
[38;5;6mrabbitmq [38;5;5m20:44:08.06 [0m[38;5;2mINFO [0m ==> Persisted data detected. Restoring...
[38;5;6mrabbitmq [38;5;5m20:44:08.06 [0m[38;5;2mINFO [0m ==> No custom scripts in /docker-entrypoint-initdb.d

[38;5;6mrabbitmq [38;5;5m20:44:08.07 [0m[38;5;2mINFO [0m ==> ** RabbitMQ setup finished! **
[38;5;6mrabbitmq [38;5;5m20:44:08.08 [0m[38;5;2mINFO [0m ==> ** Starting RabbitMQ **
2023-07-10 20:44:10.985710+00:00 [notice] <0.44.0> Application syslog exited with reason: stopped
2023-07-10 20:44:10.990064+00:00 [notice] <0.235.0> Logging: switching to configured handler(s); following messages may not be visible in this log output
2023-07-10 20:44:10.991043+00:00 [notice] <0.235.0> Logging: configured log handlers are now ACTIVE
2023-07-10 20:44:11.357638+00:00 [info] <0.235.0> ra: starting system quorum_queues
2023-07-10 20:44:11.357790+00:00 [info] <0.235.0> starting Ra system: quorum_queues in directory: /bitnami/rabbitmq/mnesia/rabbit@my-rabbitmq-0.my-rabbitmq-headless.default.svc.cluster.local/quorum/rabbit@my-rabbitmq-0.my-rabbitmq-headless.default.svc.cluster.local
2023-07-10 20:44:11.398852+00:00 [info] <0.319.0> ra system 'quorum_queues' running pre init for 0 registered servers
2023-07-10 20:44:11.418656+00:00 [info] <0.322.0> ra: meta data store initialised for system quorum_queues. 0 record(s) recovered
2023-07-10 20:44:11.439983+00:00 [notice] <0.327.0> WAL: ra_log_wal init, open tbls: ra_log_open_mem_tables, closed tbls: ra_log_closed_mem_tables
2023-07-10 20:44:11.464861+00:00 [info] <0.235.0> ra: starting system coordination
2023-07-10 20:44:11.464925+00:00 [info] <0.235.0> starting Ra system: coordination in directory: /bitnami/rabbitmq/mnesia/rabbit@my-rabbitmq-0.my-rabbitmq-headless.default.svc.cluster.local/coordination/rabbit@my-rabbitmq-0.my-rabbitmq-headless.default.svc.cluster.local
2023-07-10 20:44:11.468985+00:00 [info] <0.334.0> ra system 'coordination' running pre init for 0 registered servers
2023-07-10 20:44:11.471590+00:00 [info] <0.335.0> ra: meta data store initialised for system coordination. 0 record(s) recovered
2023-07-10 20:44:11.471799+00:00 [notice] <0.340.0> WAL: ra_coordination_log_wal init, open tbls: ra_coordination_log_open_mem_tables, closed tbls: ra_coordination_log_closed_mem_tables
2023-07-10 20:44:11.488311+00:00 [info] <0.235.0> 
2023-07-10 20:44:11.488311+00:00 [info] <0.235.0>  Starting RabbitMQ 3.12.1 on Erlang 26.0.1 [jit]
2023-07-10 20:44:11.488311+00:00 [info] <0.235.0>  Copyright (c) 2007-2023 VMware, Inc. or its affiliates.
2023-07-10 20:44:11.488311+00:00 [info] <0.235.0>  Licensed under the MPL 2.0. Website: https://rabbitmq.com

  ##  ##      RabbitMQ 3.12.1
  ##  ##
  ##########  Copyright (c) 2007-2023 VMware, Inc. or its affiliates.
  ######  ##
  ##########  Licensed under the MPL 2.0. Website: https://rabbitmq.com

  Erlang:      26.0.1 [jit]
  TLS Library: OpenSSL - OpenSSL 1.1.1n  15 Mar 2022
  Release series support status: supported

  Doc guides:  https://rabbitmq.com/documentation.html
  Support:     https://rabbitmq.com/contact.html
  Tutorials:   https://rabbitmq.com/getstarted.html
  Monitoring:  https://rabbitmq.com/monitoring.html

  Logs: <stdout>

  Config file(s): /opt/bitnami/rabbitmq/etc/rabbitmq/rabbitmq.conf

  Starting broker...2023-07-10 20:44:11.489697+00:00 [info] <0.235.0> 
2023-07-10 20:44:11.489697+00:00 [info] <0.235.0>  node           : rabbit@my-rabbitmq-0.my-rabbitmq-headless.default.svc.cluster.local
2023-07-10 20:44:11.489697+00:00 [info] <0.235.0>  home dir       : /opt/bitnami/rabbitmq/.rabbitmq
2023-07-10 20:44:11.489697+00:00 [info] <0.235.0>  config file(s) : /opt/bitnami/rabbitmq/etc/rabbitmq/rabbitmq.conf
2023-07-10 20:44:11.489697+00:00 [info] <0.235.0>  cookie hash    : BpjKCr3VR4ml80bxvnBZxQ==
2023-07-10 20:44:11.489697+00:00 [info] <0.235.0>  log(s)         : <stdout>
2023-07-10 20:44:11.489697+00:00 [info] <0.235.0>  data dir       : /bitnami/rabbitmq/mnesia/rabbit@my-rabbitmq-0.my-rabbitmq-headless.default.svc.cluster.local
2023-07-10 20:44:14.817365+00:00 [info] <0.235.0> Running boot step pre_boot defined by app rabbit
2023-07-10 20:44:14.817435+00:00 [info] <0.235.0> Running boot step rabbit_global_counters defined by app rabbit
2023-07-10 20:44:14.818036+00:00 [info] <0.235.0> Running boot step rabbit_osiris_metrics defined by app rabbit
2023-07-10 20:44:14.818142+00:00 [info] <0.235.0> Running boot step rabbit_core_metrics defined by app rabbit
2023-07-10 20:44:14.818558+00:00 [info] <0.235.0> Running boot step rabbit_alarm defined by app rabbit
2023-07-10 20:44:14.822043+00:00 [info] <0.359.0> Memory high watermark set to 2325 MiB (2438081740 bytes) of 5812 MiB (6095204352 bytes) total
2023-07-10 20:44:14.830697+00:00 [info] <0.361.0> Enabling free disk space monitoring (disk free space: 2543766470656, total memory: 6095204352)
2023-07-10 20:44:14.830755+00:00 [info] <0.361.0> Disk free limit set to 50MB
2023-07-10 20:44:14.835284+00:00 [info] <0.235.0> Running boot step code_server_cache defined by app rabbit
2023-07-10 20:44:14.835365+00:00 [info] <0.235.0> Running boot step file_handle_cache defined by app rabbit
2023-07-10 20:44:14.835522+00:00 [info] <0.364.0> Limiting to approx 1048479 file handles (943629 sockets)
2023-07-10 20:44:14.835658+00:00 [info] <0.365.0> FHC read buffering: OFF
2023-07-10 20:44:14.835691+00:00 [info] <0.365.0> FHC write buffering: ON
2023-07-10 20:44:14.836296+00:00 [info] <0.235.0> Running boot step worker_pool defined by app rabbit
2023-07-10 20:44:14.836402+00:00 [info] <0.342.0> Will use 2 processes for default worker pool
2023-07-10 20:44:14.836431+00:00 [info] <0.342.0> Starting worker pool 'worker_pool' with 2 processes in it
2023-07-10 20:44:14.836612+00:00 [info] <0.235.0> Running boot step database defined by app rabbit
2023-07-10 20:44:14.842915+00:00 [info] <0.235.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2023-07-10 20:44:14.844878+00:00 [info] <0.235.0> Successfully synced tables from a peer
2023-07-10 20:44:14.865645+00:00 [info] <0.235.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2023-07-10 20:44:14.865789+00:00 [info] <0.235.0> Successfully synced tables from a peer
2023-07-10 20:44:14.866206+00:00 [info] <0.235.0> Will register with peer discovery backend rabbit_peer_discovery_k8s
2023-07-10 20:44:14.889728+00:00 [info] <0.235.0> Running boot step tracking_metadata_store defined by app rabbit
2023-07-10 20:44:14.889857+00:00 [info] <0.382.0> Setting up a table for connection tracking on this node: tracked_connection
2023-07-10 20:44:14.889912+00:00 [info] <0.382.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost
2023-07-10 20:44:14.890073+00:00 [info] <0.382.0> Setting up a table for per-user connection counting on this node: tracked_connection_per_user
2023-07-10 20:44:14.890151+00:00 [info] <0.382.0> Setting up a table for channel tracking on this node: tracked_channel
2023-07-10 20:44:14.890305+00:00 [info] <0.382.0> Setting up a table for channel tracking on this node: tracked_channel_per_user
2023-07-10 20:44:14.890543+00:00 [info] <0.235.0> Running boot step networking_metadata_store defined by app rabbit
2023-07-10 20:44:14.890718+00:00 [info] <0.235.0> Running boot step feature_flags defined by app rabbit
2023-07-10 20:44:14.891034+00:00 [info] <0.235.0> Running boot step codec_correctness_check defined by app rabbit
2023-07-10 20:44:14.891110+00:00 [info] <0.235.0> Running boot step external_infrastructure defined by app rabbit
2023-07-10 20:44:14.891137+00:00 [info] <0.235.0> Running boot step rabbit_event defined by app rabbit
2023-07-10 20:44:14.891777+00:00 [info] <0.235.0> Running boot step rabbit_registry defined by app rabbit
2023-07-10 20:44:14.891902+00:00 [info] <0.235.0> Running boot step rabbit_auth_mechanism_amqplain defined by app rabbit
2023-07-10 20:44:14.892019+00:00 [info] <0.235.0> Running boot step rabbit_auth_mechanism_cr_demo defined by app rabbit
2023-07-10 20:44:14.892235+00:00 [info] <0.235.0> Running boot step rabbit_auth_mechanism_plain defined by app rabbit
2023-07-10 20:44:14.892496+00:00 [info] <0.235.0> Running boot step rabbit_exchange_type_direct defined by app rabbit
2023-07-10 20:44:14.892679+00:00 [info] <0.235.0> Running boot step rabbit_exchange_type_fanout defined by app rabbit
2023-07-10 20:44:14.892861+00:00 [info] <0.235.0> Running boot step rabbit_exchange_type_headers defined by app rabbit
2023-07-10 20:44:14.893055+00:00 [info] <0.235.0> Running boot step rabbit_exchange_type_topic defined by app rabbit
2023-07-10 20:44:14.893160+00:00 [info] <0.235.0> Running boot step rabbit_mirror_queue_mode_all defined by app rabbit
2023-07-10 20:44:14.893289+00:00 [info] <0.235.0> Running boot step rabbit_mirror_queue_mode_exactly defined by app rabbit
2023-07-10 20:44:14.893523+00:00 [info] <0.235.0> Running boot step rabbit_mirror_queue_mode_nodes defined by app rabbit
2023-07-10 20:44:14.893649+00:00 [info] <0.235.0> Running boot step rabbit_priority_queue defined by app rabbit
2023-07-10 20:44:14.893807+00:00 [info] <0.235.0> Priority queues enabled, real BQ is rabbit_variable_queue
2023-07-10 20:44:14.893946+00:00 [info] <0.235.0> Running boot step rabbit_queue_location_client_local defined by app rabbit
2023-07-10 20:44:14.894098+00:00 [info] <0.235.0> Running boot step rabbit_queue_location_min_masters defined by app rabbit
2023-07-10 20:44:14.894264+00:00 [info] <0.235.0> Running boot step rabbit_queue_location_random defined by app rabbit
2023-07-10 20:44:14.894451+00:00 [info] <0.235.0> Running boot step kernel_ready defined by app rabbit
2023-07-10 20:44:14.894574+00:00 [info] <0.235.0> Running boot step rabbit_sysmon_minder defined by app rabbit
2023-07-10 20:44:14.894807+00:00 [info] <0.235.0> Running boot step rabbit_epmd_monitor defined by app rabbit
2023-07-10 20:44:14.895731+00:00 [info] <0.390.0> epmd monitor knows us, inter-node communication (distribution) port: 25672
2023-07-10 20:44:14.895983+00:00 [info] <0.235.0> Running boot step guid_generator defined by app rabbit
2023-07-10 20:44:14.914501+00:00 [info] <0.235.0> Running boot step rabbit_node_monitor defined by app rabbit
2023-07-10 20:44:14.915058+00:00 [info] <0.394.0> Starting rabbit_node_monitor
2023-07-10 20:44:14.915171+00:00 [info] <0.235.0> Running boot step delegate_sup defined by app rabbit
2023-07-10 20:44:14.915710+00:00 [info] <0.235.0> Running boot step rabbit_memory_monitor defined by app rabbit
2023-07-10 20:44:14.915940+00:00 [info] <0.235.0> Running boot step rabbit_fifo_dlx_sup defined by app rabbit
2023-07-10 20:44:14.916079+00:00 [info] <0.235.0> Running boot step core_initialized defined by app rabbit
2023-07-10 20:44:14.916137+00:00 [info] <0.235.0> Running boot step rabbit_channel_tracking_handler defined by app rabbit
2023-07-10 20:44:14.916228+00:00 [info] <0.235.0> Running boot step rabbit_connection_tracking_handler defined by app rabbit
2023-07-10 20:44:14.916468+00:00 [info] <0.235.0> Running boot step rabbit_definitions_hashing defined by app rabbit
2023-07-10 20:44:14.916590+00:00 [info] <0.235.0> Running boot step rabbit_exchange_parameters defined by app rabbit
2023-07-10 20:44:14.917258+00:00 [info] <0.235.0> Running boot step rabbit_mirror_queue_misc defined by app rabbit
2023-07-10 20:44:14.917598+00:00 [info] <0.235.0> Running boot step rabbit_policies defined by app rabbit
2023-07-10 20:44:14.918013+00:00 [info] <0.235.0> Running boot step rabbit_policy defined by app rabbit
2023-07-10 20:44:14.918074+00:00 [info] <0.235.0> Running boot step rabbit_queue_location_validator defined by app rabbit
2023-07-10 20:44:14.918110+00:00 [info] <0.235.0> Running boot step rabbit_quorum_memory_manager defined by app rabbit
2023-07-10 20:44:14.918139+00:00 [info] <0.235.0> Running boot step rabbit_stream_coordinator defined by app rabbit
2023-07-10 20:44:14.918376+00:00 [info] <0.235.0> Running boot step rabbit_vhost_limit defined by app rabbit
2023-07-10 20:44:14.918522+00:00 [info] <0.235.0> Running boot step rabbit_mgmt_reset_handler defined by app rabbitmq_management
2023-07-10 20:44:14.918647+00:00 [info] <0.235.0> Running boot step rabbit_mgmt_db_handler defined by app rabbitmq_management_agent
2023-07-10 20:44:14.918810+00:00 [info] <0.235.0> Management plugin: using rates mode 'basic'
2023-07-10 20:44:14.919214+00:00 [info] <0.235.0> Running boot step recovery defined by app rabbit
2023-07-10 20:44:14.920013+00:00 [info] <0.431.0> Making sure data directory '/bitnami/rabbitmq/mnesia/rabbit@my-rabbitmq-0.my-rabbitmq-headless.default.svc.cluster.local/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists
2023-07-10 20:44:14.943294+00:00 [info] <0.431.0> Starting message stores for vhost '/'
2023-07-10 20:44:14.943544+00:00 [info] <0.441.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2023-07-10 20:44:14.975687+00:00 [info] <0.431.0> Started message store of type transient for vhost '/'
2023-07-10 20:44:14.976166+00:00 [info] <0.445.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2023-07-10 20:44:15.005784+00:00 [info] <0.431.0> Started message store of type persistent for vhost '/'
2023-07-10 20:44:15.006108+00:00 [info] <0.431.0> Recovering 0 queues of type rabbit_classic_queue took 77ms
2023-07-10 20:44:15.006148+00:00 [info] <0.431.0> Recovering 0 queues of type rabbit_quorum_queue took 0ms
2023-07-10 20:44:15.006171+00:00 [info] <0.431.0> Recovering 0 queues of type rabbit_stream_queue took 0ms
2023-07-10 20:44:15.008128+00:00 [info] <0.235.0> Running boot step empty_db_check defined by app rabbit
2023-07-10 20:44:15.008182+00:00 [info] <0.235.0> Will not seed default virtual host and user: have definitions to load...
2023-07-10 20:44:15.008219+00:00 [info] <0.235.0> Running boot step rabbit_observer_cli defined by app rabbit
2023-07-10 20:44:15.008268+00:00 [info] <0.235.0> Running boot step rabbit_looking_glass defined by app rabbit
2023-07-10 20:44:15.008455+00:00 [info] <0.235.0> Running boot step rabbit_core_metrics_gc defined by app rabbit
2023-07-10 20:44:15.008596+00:00 [info] <0.235.0> Running boot step background_gc defined by app rabbit
2023-07-10 20:44:15.008860+00:00 [info] <0.235.0> Running boot step routing_ready defined by app rabbit
2023-07-10 20:44:15.008887+00:00 [info] <0.235.0> Running boot step pre_flight defined by app rabbit
2023-07-10 20:44:15.008902+00:00 [info] <0.235.0> Running boot step notify_cluster defined by app rabbit
2023-07-10 20:44:15.008923+00:00 [info] <0.235.0> Running boot step networking defined by app rabbit
2023-07-10 20:44:15.009022+00:00 [info] <0.235.0> Running boot step definition_import_worker_pool defined by app rabbit
2023-07-10 20:44:15.009089+00:00 [info] <0.342.0> Starting worker pool 'definition_import_pool' with 2 processes in it
2023-07-10 20:44:15.009767+00:00 [info] <0.235.0> Running boot step cluster_name defined by app rabbit
2023-07-10 20:44:15.010124+00:00 [info] <0.235.0> Running boot step direct_client defined by app rabbit
2023-07-10 20:44:15.010456+00:00 [info] <0.235.0> Running boot step rabbit_maintenance_mode_state defined by app rabbit
2023-07-10 20:44:15.010675+00:00 [info] <0.235.0> Creating table rabbit_node_maintenance_states for maintenance mode status
2023-07-10 20:44:15.011306+00:00 [info] <0.235.0> Running boot step rabbit_management_load_definitions defined by app rabbitmq_management
2023-07-10 20:44:15.011600+00:00 [info] <0.480.0> Resetting node maintenance status
2023-07-10 20:44:15.035321+00:00 [info] <0.539.0> Management plugin: HTTP (non-TLS) listener started on port 15672
2023-07-10 20:44:15.035614+00:00 [info] <0.567.0> Statistics database started.
2023-07-10 20:44:15.036012+00:00 [info] <0.566.0> Starting worker pool 'management_worker_pool' with 3 processes in it
2023-07-10 20:44:15.043245+00:00 [info] <0.582.0> Peer discovery: enabling node cleanup (will only log warnings). Check interval: 10 seconds.
2023-07-10 20:44:15.043758+00:00 [info] <0.586.0> rabbit_stomp: default user 'guest' enabled
2023-07-10 20:44:15.044644+00:00 [info] <0.605.0> started STOMP TCP listener on [::]:61613
2023-07-10 20:44:15.047273+00:00 [info] <0.614.0> Prometheus metrics: HTTP (non-TLS) listener started on port 15692
2023-07-10 20:44:15.047467+00:00 [info] <0.480.0> Ready to start client connection listeners
2023-07-10 20:44:15.049714+00:00 [info] <0.658.0> started TCP listener on [::]:5672
 completed with 7 plugins.
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0> Server startup complete; 7 plugins started.
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0>  * rabbitmq_prometheus
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0>  * rabbitmq_peer_discovery_k8s
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0>  * rabbitmq_stomp
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0>  * rabbitmq_peer_discovery_common
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0>  * rabbitmq_management
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0>  * rabbitmq_web_dispatch
2023-07-10 20:44:15.130552+00:00 [info] <0.480.0>  * rabbitmq_management_agent
2023-07-10 20:44:28.844130+00:00 [warning] <0.662.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:44:58.824406+00:00 [warning] <0.667.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:45:28.809852+00:00 [warning] <0.672.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:45:38.681973+00:00 [warning] <0.675.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:45:58.806260+00:00 [warning] <0.680.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:46:28.828416+00:00 [warning] <0.690.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:46:28.871181+00:00 [warning] <0.692.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:46:46.696514+00:00 [warning] <0.696.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:46:58.809454+00:00 [warning] <0.699.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:46:58.859766+00:00 [warning] <0.701.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:47:28.812174+00:00 [warning] <0.707.0> HTTP access denied: user 'user' - invalid credentials
2023-07-10 20:47:28.849480+00:00 [warning] <0.709.0> HTTP access denied: user 'user' - invalid credentials

Mauraza commented 1 year ago

Hi @default-doe,

I'm glad that the workaround fixes the issue. I think the error is related to this info appearing in the logs.

�[38;5;6mrabbitmq �[38;5;5m20:44:08.06 �[0m�[38;5;2mINFO �[0m ==> Persisted data detected. Restoring...

The application detects that already exists persisted data, so the application tries to restore it instead to create it.

github-actions[bot] commented 1 year ago

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

github-actions[bot] commented 1 year ago

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

FrantisekSidak commented 1 year ago

I can confirm both @kevinp89 hints works! Thank you!

bitnami / charts