Problem with carbon...
 
Notifications
Clear all

[Solved] Problem with carbonio-message-dispatcher after a fresh install

5 Posts
4 Users
2 Reactions
105 Views
 Hugo
(@hugo)
New Member
Joined: 1 month ago
Posts: 1
Topic starter  

I’m performing a fresh installation of Carbonio CE 25.6.0 on Ubuntu 24.04.3.
After installing Ubuntu and completing the prerequisite tasks, I run the script install_carbonio_ce_singleserver_ubuntu.sh, which finishes successfully (I can access without problems to the webmail interface and the Carbonio administration web interface.

Next, I reboot the server, and during the shutdown process the service carbonio-message-dispatcher takes 4 minutes to stop, until it is eventually killed by a timeout.

What could be causing this issue, and how can I resolve it?


   
Quote
(@itguy)
Eminent Member
Joined: 11 years ago
Posts: 55
 

I have noticed the same. What i have been doing is as follows:

In a terminal:

systemctl stop carbonio-message-dispatcher.service

thereafter I do a shutdown 0

It still takes about a minute and a half.

 


   
Hugo reacted
ReplyQuote
(@vladki)
New Member
Joined: 2 weeks ago
Posts: 5
 

I have the same problem. I suspect there is some timing issue, and some service stops too early. I was fiddling with systemd dependencies, and I had two quick reboots, but then it went wrong again. IMHO there is a lot of missing systemd dependancies (i.e. After= and Wants=).

There are many services that are WantedBy=multi-user.target, while they should be WantedBy carbonio.target or some of the sub-targets. This is demonstrated by many failing services during the startup, which eventually come up after 2 or 3 retries.

I have added After=carbonio-configd.service to all carbonio services, except:

carbonio-configd is After=carbonio-openldap.service

carbonio-openldap is After=postgresql.service.

Also for the services that have a corresponding "sidecar" service, I've added that they start After their sidecar service.

I'm still struggling with:

2025-09-19T16:43:03.151059+02:00 carbonio systemd[1]: carbonio-user-management.service: Failed with result 'exit-code'.
2025-09-19T16:43:08.482686+02:00 carbonio systemd[1]: carbonio-files.service: Failed with result 'exit-code'.
2025-09-19T16:43:08.726230+02:00 carbonio systemd[1]: carbonio-tasks.service: Failed with result 'exit-code'.
2025-09-19T16:43:13.882246+02:00 carbonio systemd[1]: carbonio-ws-collaboration.service: Failed with result 'exit-code'.
2025-09-19T16:43:19.777983+02:00 carbonio systemd[1]: carbonio-user-management.service: Failed with result 'exit-code'.
2025-09-19T16:43:35.507435+02:00 carbonio systemd[1]: carbonio-videoserver.service: Failed with result 'exit-code'.

These probably depend on some more services.


   
ReplyQuote
(@sharif)
Reputable Member Admin
Joined: 3 years ago
Posts: 773
 

@hugo @vladki

Don't worry about it. Basically after resolving the dependent services, carbonio-message-dispatcher takes that time to stop gracefully. But I will take note of it to discuss with our devs.

Meanwhile, possible faster workaround could what @itguy shared 🙏


   
ReplyQuote
(@vladki)
New Member
Joined: 2 weeks ago
Posts: 5
 

I forgot to add that also all "sidecar" services should be After=service-discover.service


   
ReplyQuote