apache2 fails to start. After upgrade to Debian 13. did sudo apt update sudo apt upgrade -y sudo apt full-upgrade -y sudo apt autoremove --purge -y apt update apt upgrade --without-new-pkgs apt full-upgrade #apache still works as expected reboot #apache fails to start apt-get install php8.4 php8.4-cli php8.4-cgi php8.4-fpm php8.4-gd php8.4-mysql php8.4-curl php8.4-intl php8.4-pspell php8.4-sqlite3 php8.4-tidy php8.4-xsl php8.4-zip php8.4-mbstring php8.4-soap php8.4-opcache libonig5 php8.4-common php8.4-readline php8.4-xml curl #apache still fails to start #rolled back to snapshot everything works but debian 12
Did you find any info on Apache problems in Debian 13 Release Notes? It is difficult to find the cause now after host was restored to Debian 12. Apache logs should have shown why it was not starting. Did you perhaps copy the log files so they are still available?
Hello Till, Taleman, do you have any news on upgrading debian 12 to 13 with ispconfig ? I found many errors on dovecot configuration migration ( tried also dovecot's migration scripts, but not working, at least for me ). Is there any indicatopn on how to proceed ?
When you do a dist upgrade, you must always run an ISPConfig update afterward. Let the ISPConfig updater write the new config.
Tilli, I actually di that just after upgrade, but dovecot refused to start, claiming errors in config anyway, I'll retry and check again. Just to be aligned, the steps I performed were: 1) upgrade debian from 12 to 13 ( no reboot) 2) set default php cli 8.3 3) force ispconfig update Is there anything you would advise to perform more? Any order change? Thanks
How did you do the upgrade from Debian 12 to 13? Why no reboot? There are instructions on how that update should be done in Debian 13 Release Notes.
Hello Taleman, here the list of packages i issue for an upgrade: # apt update # apt upgrade # apt dist-upgrade # apt clean # apt autoremove # apt --fix-broken install # dpkg --configure -a # sed -i 's/bookworm/trixie/g' /etc/apt/sources.list # find /etc/apt/sources.list.d -name "*.list" -exec sed -i 's/bookworm/trixie/g' {} \; # apt update # apt upgrade --without-new-pkgs # apt full-upgrade # apt autoremove # apt autoclean About "reboot" question, I found some guides telling to reboot just after the substitution "bookworm/trixie" in configuration files , but I avoided that. After the reboot , then I performed "ispconfig_update.sh --force"
No. It's just important that you let the ISPConfig updater reconfigure services when it asks if it should do that. It will then write a new dovecot config file which is compatible with the new Dovecot version. Do not try to let dovecot convert the old one; let ISPConfig updater write a fresh version that matches the used Dovecot version.
If it does not work, please post the generated dovecot.conf file and also the errors you get from dovecot, so we can try to track down what the issue is. Maybe a dovecot module is missing after the update or something similar.
