TG Servers
2018-Feb-02 03:09 UTC
Problem with CentOS package for 2.3.0 and old dependency in systemd with clean install
Hi, you definitely have a problem with the packages out of your own repo for version 2.3.0 and CentOS. And this is only if you do a clean install, meaning there was no lower dovecot version ever running on the system. If you want to 'systemctl start dovecot' it breaks with a dependency error which comes from dovecot-init.service. dovecot-init.service : [Unit] Description=One-time Dovecot init service ConditionPathExists=|!/var/lib/dovecot/ssl-parameters.dat ConditionPathExists=|!/etc/pki/dovecot/certs/dovecot.pem [Service] Type=oneshot RemainAfterExit=no ExecStart=/bin/sh -c '\ if [ ! -f /etc/pki/dovecot/certs/dovecot.pem ]; \ then\ ? SSLDIR=/etc/pki/dovecot/ OPENSSLCONFIG=/etc/pki/dovecot/dovecot-openssl.cnf /usr/libexec/dovecot/mkcert.sh /dev/null 2>&1;\ fi;\ if [ ! -f /var/lib/dovecot/ssl-parameters.dat ]; \ then\ ? /usr/libexec/dovecot/ssl-params >/dev/null 2>&1; \ fi' It wants to call /usr/libexec/dovecot/ssl-params if /var/lib/dovecot/ssl-parameters.dat (which is deprecated now as I understood) is not existing. The problem is in 2.3.0 /usr/libexec/dovecot/ssl-params is not existent anymore. This error does not occur if you for instance install 2.2.x from the base repo, start it once, and then update the version from your repo. This is because the ssl-parameters.dat was created with the old version then. But this should not be the expected behaviour I think. It should be possible to do a fresh install of 2.3.0 on a fresh system. Can you please get back to me on that? Thanks, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180202/62316c1c/attachment.html>
Aki Tuomi
2018-Feb-02 08:26 UTC
Problem with CentOS package for 2.3.0 and old dependency in systemd with clean install
<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p><br></p><blockquote
type="cite">On February 2, 2018 at 5:09 AM TG Servers
wrote:<br><br><br>Hi,<br><br>you definitely have a
problem with the packages out of your own repo for<br>version 2.3.0 and
CentOS.<br>And this is only if you do a clean install, meaning there was
no lower<br>dovecot version ever running on the
system.<br><br>If you want to 'systemctl start dovecot' it
breaks with a dependency<br>error which comes from
dovecot-init.service.<br><br>dovecot-init.service
:<br>[Unit]<br>Description=One-time Dovecot init
service<br>ConditionPathExists=|!/var/lib/dovecot/ssl-parameters.dat<br>ConditionPathExists=|!/etc/pki/dovecot/certs/dovecot.pem<br><br>[Service]<br>Type=oneshot<br>RemainAfterExit=no<br>ExecStart=/bin/sh
-c '\<br>if [ ! -f /etc/pki/dovecot/certs/dovecot.pem ];
\<br>then\<br>
SSLDIR=/etc/pki/dovecot/<br>OPENSSLCONFIG=/etc/pki/dovecot/dovecot-openssl.cnf<br>/usr/libexec/dovecot/mkcert.sh
/dev/null 2>&1;\<br>fi;\<br>if [ ! -f
/var/lib/dovecot/ssl-parameters.dat ]; \<br>then\<br>
/usr/libexec/dovecot/ssl-params >/dev/null 2>&1;
\<br>fi'<br><br>It wants to call
/usr/libexec/dovecot/ssl-params if<br>/var/lib/dovecot/ssl-parameters.dat
(which is deprecated now as I<br>understood) is not existing.<br>The
problem is in 2.3.0 /usr/libexec/dovecot/ssl-params is not
existent<br>anymore.<br><br>This error does not occur if you
for instance install 2.2.x from the<br>base repo, start it once, and then
update the version from your repo.<br>This is because the
ssl-parameters.dat was created with the old
version<br>then.<br><br>But this should not be the expected
behaviour I think. It should be<br>possible to do a fresh install of 2.3.0
on a fresh system.<br><br>Can you please get back to me on
that?<br><br>Thanks,<br>Thomas</blockquote><p><br></p><p>Thank
you for reporting this, we'll look into it.</p><p
class="io-ox-signature">---<br>Aki Tuomi</p><p
class="io-ox-signature">Dovecot
oy</p></body></html>
TG Servers
2018-Feb-14 20:10 UTC
Problem with CentOS package for 2.3.0 and old dependency in systemd with clean install
Hi, are there any news on this? Or do we have to go the way install old dovecot/remove it or upgrade instead of clean install? Because as the ssl-params executab?e is missing in 2.3.0 I don't know how else I should create it. If this file isn't even needed for 2.3.0 can it be a file with any content eg 'touch /var/lib/dovecot/ssl-parameters.dat' so that the file is just there and dovecot-init.servive doesn't want to call the /usr/libexec/dovecot/ssl-params executable? Thanks, Thomas Am 02.02.2018 um 09:26 schrieb Aki Tuomi:> >> On February 2, 2018 at 5:09 AM TG Servers wrote: >> >> >> Hi, >> >> you definitely have a problem with the packages out of your own repo for >> version 2.3.0 and CentOS. >> And this is only if you do a clean install, meaning there was no lower >> dovecot version ever running on the system. >> >> If you want to 'systemctl start dovecot' it breaks with a dependency >> error which comes from dovecot-init.service. >> >> dovecot-init.service : >> [Unit] >> Description=One-time Dovecot init service >> ConditionPathExists=|!/var/lib/dovecot/ssl-parameters.dat >> ConditionPathExists=|!/etc/pki/dovecot/certs/dovecot.pem >> >> [Service] >> Type=oneshot >> RemainAfterExit=no >> ExecStart=/bin/sh -c '\ >> if [ ! -f /etc/pki/dovecot/certs/dovecot.pem ]; \ >> then\ >> SSLDIR=/etc/pki/dovecot/ >> OPENSSLCONFIG=/etc/pki/dovecot/dovecot-openssl.cnf >> /usr/libexec/dovecot/mkcert.sh /dev/null 2>&1;\ >> fi;\ >> if [ ! -f /var/lib/dovecot/ssl-parameters.dat ]; \ >> then\ >> /usr/libexec/dovecot/ssl-params >/dev/null 2>&1; \ >> fi' >> >> It wants to call /usr/libexec/dovecot/ssl-params if >> /var/lib/dovecot/ssl-parameters.dat (which is deprecated now as I >> understood) is not existing. >> The problem is in 2.3.0 /usr/libexec/dovecot/ssl-params is not existent >> anymore. >> >> This error does not occur if you for instance install 2.2.x from the >> base repo, start it once, and then update the version from your repo. >> This is because the ssl-parameters.dat was created with the old version >> then. >> >> But this should not be the expected behaviour I think. It should be >> possible to do a fresh install of 2.3.0 on a fresh system. >> >> Can you please get back to me on that? >> >> Thanks, >> Thomas > > > Thank you for reporting this, we'll look into it. > > --- > Aki Tuomi > > Dovecot oy >
Maybe Matching Threads
- Problem with CentOS package for 2.3.0 and old dependency in systemd with clean install
- Problem with CentOS package for 2.3.0 and old dependency in systemd with clean install
- Problem with CentOS package for 2.3.0 and old dependency in systemd with clean install
- Current thinking on backups ?
- Bug#821254: systemd[1]: xendomains.service start operation timed out.