cPanel update 132.0.14 -> how to fix the broken dovecot issue
Good day,
I had that issue and finally figured out the solution. Your update does not migrate the configuration (v2.3) to the new format (v2.4). It happens when solr is activated.
In /etc/dovecot you will find the file "fts.conf". At the same time you will find "fts-2.4.conf". That file is the new syntax. Replace the old file content with new file content and replace the url with the url from the old file, save "fts.conf" and restart dovecot (service dovecot start), check status (service dovecot status).
Following that uninstall and install the solr plugin, so that the url gets replaced with the correct one. dovecot should be running normal again. If that fails, execute "apt --fix-broken install" and retry.
exim has to be restarted via /scripts/restartsrv_exim after that. For some reason that failed too and only works properly again if dovecot is fixed properly.
-
I'm keeping a list of the Dovecot issues over at https://support.cpanel.net/hc/en-us/community/posts/36924766387607
0 -
Surely, I just was providing a solution for that issue after I woke up to 300+ emails that the services were down and most people just wrote "revert the update" for the "fatal error in configuration file" problem. I cannot find that specific case in your linked topic.
At the very least, the server is working fine now. The other server I have somehow has a broken auto-update. So lucky me I only had to fix one server today.
0 -
I also haven't heard of any issues with the fts portion of the config file on my end.
0 -
I can just tell what happened on my end.. I don't know if the Ubuntu branch is different to the Alma branch. On one server I am forced to use Ubuntu due to the hoster's hardware and that one has failed me over night.
Maybe you can have a look if there is a specific case when that mentioned file would not be updated for whatever reason?
I for sure have two template files (2.3 and 2.4), as well as that configuration file which was based on 2.3 and was not updated in the process.
0 -
Nope, I don't have anything on my end for that specific entry, so we'd likely need to see this in action through a ticket if you have a server where you can make this happen.
0 -
Well, I see the issue in the update log.
I created a customer request ticket. Somehow the technical support ticket mask does not load after I enter my IP. The ticket id is #95864691 . The update log is attached.
0 -
Sounds good!
0
Please sign in to leave a comment.
Comments
7 comments