The mailing list for listmasters using Sympa

["Lorenz, Sabine (SCC)" <address@concealed>]

Hi Riccardo,

 

thank you very much for your answer.

 

Is it possible to use the init.d-startup scripts although Sympa is provided with systemd-scripts in the Debian package?

On our server the init.d-script is bent to systemd (via /lib/lsb/init-functions.d/40-systemd) and systemd prefers the existing service unit instead o finit-scripts.

 

Any ideas how we can fix that?

 

Best regards,

Sabine

 

Von: Riccardo Veraldi [mailto:address@concealed]
Gesendet: Montag, 1. Februar 2016 12:18
An: Lorenz, Sabine (SCC) <address@concealed>
Betreff: Re: [sympa-users] problems installing Sympa Version 6.1.23 as Debian package on Jessie and starting sequence in systemd

 

Hello,
we use sympa as a INFN wide mauling list systema.
We use CentOS 7 and we have smae problem.
anyway sympa has the standard chkconfig startup script and it is still working on CentOS 7
in the old way.

chkconfig --list | grep -i sympa

---
Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

      If you want to list systemd services use 'systemctl list-unit-files'.
      To see services enabled on particular target use
      'systemctl list-dependencies [target]'.

sympa              0:off    1:off    2:on    3:on    4:on    5:on    6:off
--

I guess you should still use the old method until they upgrade the startup script.

looking at their script in ./src/etc/script/sympa (the one which gets installed into init.d)
it is dated 27/07/2000 looks like it has never  been upgraded.


Cheers

Rick



On 01/02/16 10:24, Lorenz, Sabine (SCC) wrote:

Dear all,

 

does anyone have experience in Sympa Version 6.1.23~dfsg-2 as Debian package on a Debian GNU/Linux 8 server?

 

After installing Sympa 6.1.23 as package on a Debian Jessie server we noticed that there was no systemd-command in postinst-script and that sympa was not enabled (we expected something like systemctl enable sympa in the scripts and couldn’t find a systemd-file in the upstream code).

So we had to enable it manually.
Did anyone have the same problem? Is that a bug in Debian package or is it a fault on our part?

 

Additionally we see messages in /var/log/daemon.log after every reboot that show that initially sympa can’t be started by systemd because the mysql database is not reachable.

I suppose that these messages occur because the database is not started before.

On our productive Server (Debian Squeeze and Sympa 6.0.1+dfsg-4+squeeze3) we use start-scripts in /etc/init.d we to start the daemons and the database is started first and the sympa daemon is started after the database.

Shouldn‘t this also be the same order in systemd? Should there be an entry like „after mysql“ in /lib/systemd/system/sympa.service?

Or is it ok and normal that Sympa is started first in systemd and  that we have this messages in /var/log/daemon.log after every reboot ?

 

Thank you very much for any hints,

Sabine Lorenz

 

----------

Sabine Lorenz
Karlsruher Institut für Technologie (KIT)
Steinbuch Centre for Computing

Hermann von Helmholtz Platz 1
76344 Eggenstein-Leopoldshafen
Telefon: +49 721 608-28633

E-Mail: address@concealed
www.kit.edu/scc

KIT - Universität des Landes Baden-Württemberg und
nationales Großforschungszentrum in der Helmholtz-Gemeinschaft

Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

 

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature