Notifications
Clear all
Topic starter
10/25/2024 12:43
Following the instructions at: https://docs.zextras.com/carbonio-ce/html/release/upgrade.html which is labeled as upgrade to 24.9.1
I had to manually install carbonio-message-broker. Running
pending-setups -a
produced the following output:
Executing /etc/zextras/pending-setups.d/carbonio-message-broker.sh
Insert the cluster credential password:
ID: 4eceb2a1-a75c-1dc9-7675-69abe7cab2f3
Name: carbonio-message-broker-policy
Description: Carbonio message broker policy for service and sidecar proxy
Datacenters:
Rules:
{
"key_prefix": [
{
"carbonio-message-broker/": {
"policy": "write"
},
"carbonio-message-broker-clustered/": {
"policy": "write"
}
}
],
"node_prefix": [
{
"": {
"policy": "read"
}
}
],
"service": [
{
"carbonio-message-broker-sidecar-proxy": {
"policy": "write"
},
"carbonio-message-broker": {
"policy": "write"
},
"carbonio-message-broker-clustered": {
"policy": "write"
}
}
],
"session_prefix": [
{
"": {
"policy": "write"
}
}
]
}
Config entry written: service-defaults/carbonio-message-broker
Config entry written: service-intentions/carbonio-message-broker
Configuration reload triggered
Job for carbonio-message-broker.service failed because the control process exited with error code.
See "systemctl status carbonio-message-broker.service" and "journalctl -xeu carbonio-message-broker.service" for details.
Script for message broker terminated with error
Setup script failed, keeping it
Of course systemctl restart carbonio-message-brokder failed with journalctl -xeu carbonio-message-broker.service producing the following:
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.312784+03:00 [info] <0.473.0> sysmon_handler
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.312784+03:00 [info] <0.473.0> osiris
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.312784+03:00 [info] <0.473.0> mnesia
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.312784+03:00 [info] <0.473.0>
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.312953+03:00 [info] <0.473.0> Stopping application 'rabbitmq_management'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.313014+03:00 [info] <0.473.0> Stopping application 'rabbitmq_management_agent'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.314424+03:00 [notice] <0.44.0> Application rabbitmq_management_agent exited with reason: stopped
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.314520+03:00 [info] <0.473.0> Stopping application 'rabbitmq_web_dispatch'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.315541+03:00 [notice] <0.44.0> Application rabbitmq_web_dispatch exited with reason: stopped
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.315597+03:00 [info] <0.473.0> Stopping application 'cowboy'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.316613+03:00 [notice] <0.44.0> Application cowboy exited with reason: stopped
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.316671+03:00 [info] <0.473.0> Stopping application 'cowlib'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.316702+03:00 [notice] <0.44.0> Application cowlib exited with reason: stopped
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.316735+03:00 [info] <0.473.0> Stopping application 'amqp_client'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.317781+03:00 [notice] <0.44.0> Application amqp_client exited with reason: stopped
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.317851+03:00 [info] <0.473.0> Stopping application 'rabbitmq_peer_discovery_consul'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.317961+03:00 [info] <0.473.0> Stopping application 'rabbitmq_peer_discovery_common'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.318017+03:00 [info] <0.473.0> Stopping application 'rabbit'
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.318289+03:00 [info] <0.255.0> Peer discovery: will unregister with peer discovery backend rabbit_peer_discovery_consul
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.320909+03:00 [info] <0.255.0> Consul's response to the unregistration attempt: []
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.324266+03:00 [notice] <0.44.0> Application rabbit exited with reason: stopped
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: 2024-10-25 13:28:28.446448+03:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: stopped
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: Runtime terminating during boot ({5157,{error,{rabbitmq_management,{bad_return,{{rabbit_mgmt_app,start,[normal,[]]},{'EXIT',{{could_not_start_listener,[{cowboy_opts,[{sendfile,false}]},{ip,"127.0.0.1"},{port,10001}],{shutdown>
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]:
Oct 25 13:28:28 carb.home.local rabbitmq-server[6154]: Crash dump is being written to: /var/log/carbonio/message-broker/erl_crash.dump...done
Oct 25 13:28:28 carb.home.local rabbitmq-server[6191]: [os_mon] cpu supervisor port (cpu_sup): Erlang has closed
Oct 25 13:28:28 carb.home.local rabbitmq-server[6190]: [os_mon] memory supervisor port (memsup): Erlang has closed
Oct 25 13:28:28 carb.home.local systemd[1]: carbonio-message-broker.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░
░░ An ExecStart= process belonging to unit carbonio-message-broker.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Oct 25 13:28:28 carb.home.local systemd[1]: carbonio-message-broker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░
░░ The unit carbonio-message-broker.service has entered the 'failed' state with result 'exit-code'.
Oct 25 13:28:28 carb.home.local systemd[1]: Failed to start Carbonio message broker daemon.
░░ Subject: A start job for unit carbonio-message-broker.service has failed
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░
░░ A start job for unit carbonio-message-broker.service has finished with a failure.
░░
░░ The job identifier is 21777 and the job result is failed.
Oct 25 13:28:28 carb.home.local systemd[1]: carbonio-message-broker.service: Consumed 3.824s CPU time.
░░ Subject: Resources consumed by unit runtime
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░
░░ The unit carbonio-message-broker.service completed and consumed the indicated resources.
Topic starter
10/25/2024 12:51
I would have loved to have uploaded the log files, but I do not see a way to do that.
Topic starter
10/25/2024 13:14
Oh... almost forgot this is the contents of /etc/carbonio/message-broker/rabbitmq.conf. As you can see it includes a weird ip that does not exist on my system. Also after adding the ip shown in the config fileas an additional loop back ip pending setups still does not work.
cluster_formation.peer_discovery_backend = rabbit_peer_discovery_consul cluster_formation.consul.host = 127.0.0.1 cluster_formation.consul.port = 8500 cluster_formation.consul.scheme = http cluster_formation.consul.svc = carbonio-message-broker-clustered cluster_formation.consul.svc_addr = 127.78.0.18 cluster_formation.consul.svc_port = 10000 cluster_formation.consul.svc_addr_auto = false listeners.tcp.local = 127.78.0.18:10000 management.tcp.ip = 127.78.0.18 management.tcp.port = 10001 loopback_users.guest = true log.console = true log.file.level = info load_definitions = /etc/carbonio/message-broker/default_schema.json auth_backends.1 = dummy auth_backends.2 = internal
Topic starter
10/25/2024 18:40
Please ignore this thread. The problem was solved when I read the instructions correctly. Installing message broker was not relevant to my usage scenario. I am really sorry about the noise