The mailing list for listmasters using Sympa

[Alban Rodriguez <address@concealed>]

Hello

I also installed Sympa from source following the manual.

Looking through my notes, I can see I ran the configure script with option --with-unitsdir=/lib/systemd/system.

The configure script help shows the default is ’no’:

 --with-unitsdir=DIR     install Systemd unit files [no]

Maybe that’s the reason why systemd units file were not installed on your system.

Also, I had to create manually two additional units for running wwsympa (the web interface) and sympasoap (SOAP web service) because there are different installation options.

I also had to create an override config manually in order to make sure MariaDB is ready when Sympa starts:

/etc/systemd/system/sympa.service.d/dependencies.conf:

[Unit]

Requires=mariadb.service

After=mariadb.service

Finally, this was in the release notes for version 6.2.70:

For the users of Systemd: The unit files described in Using Systemd socket have been added to the source distribution. Some packagers (at least Debian and RPM) have adopted these and no longer use the setuid wrappers for the FastCGI servers. Also, when using these unit files, stopping the web service requires stopping the wwsympa.socket unit instead of the wwsympa.service unit (same for sympasoap).

So if you’re using systemd sockets for wwsympa and sympasoap service (which I’m not), you don’t need to create the corresponding systemd units manually anymore.

I hope this helps …

Alban

Le 19 févr. 2025 à 23:49, Ralph Ballier <address@concealed> a écrit :

Hello Joe,

there are only sympa.service (under /etc/systemd/system) and wwsympa.service (under /usr/lib/systemd/system).

These are also the two services mentioned in the documentation.

What is interesting is the content of syspa.service (see below). There you find all the daemons, but they are not set up as services.

I am very surprised that this is not mentioned in the documentation.

Best regards,

Ralph

------ Content of sympa.service -------------------------------------

[Unit]

Description=Sympa mailing list manager

After=syslog.target

Wants=sympa-outgoing.service

Before=sympa-outgoing.service

Wants=sympa-archive.service

Before=sympa-archive.service

Wants=sympa-bounce.service

Before=sympa-bounce.service

Wants=sympa-task.service

Before=sympa-task.service

 

[Service]

Type=forking

PIDFile=/usr/local/var/run/sympa/sympa_msg.pid

ExecStartPre=/bin/mkdir -p /usr/local/var/run/sympa

ExecStartPre=/bin/chown sympa:sympa /usr/local/var/run/sympa

ExecStartPre=/usr/local/sbin/sympa check

ExecStart=/usr/local/sbin/sympa_msg.pl

 

[Install]

WantedBy=multi-user.target

------------------------------------------------------------------------

Am 19.02.2025 22:58, schrieb Joe Meslovich:

That makes sense.  The section in the manual named "Automate Startup" only references the main sympa.service.  On my Rocky system installed from a package I have the following services running:

sympa-archive.service
sympa-bounce.service
sympa-outgoing.service
sympa-task.service
sympa.service
sympasoap.service
wwwsympa.service


So I'm not certain where those systemd files would come from in the source.  You may want to hunt for them in the source code and see what you do or don't have running.

 

<Outlook-wlwmpfh3.png>

Joseph Meslovich Network Administrator & IT Security Officer Information Technology Center Bridgewater College Phone: 540-828-5343 | bridgewater.edu

 

---

From: Ralph Ballier <address@concealed>
Sent: Wednesday, February 19, 2025 4:47 PM
To: Joe Meslovich <address@concealed>
Cc: En <address@concealed>
Subject: Re: [en@sympa] Questions about daemons

 

Hi Joe,

thank you very much for the quick response.

I installed from source because my Ubuntu distribution only came with an older version of Sympa.

By the way, I proceeded as described here. But perhaps I overlooked something? This has happened before.

Best regards,

Ralph

<cc0cb1dc.png>

Am 19.02.2025 22:28, schrieb Joe Meslovich:

We run Sympa on Rocky Linux 9 and there is just a systemd service for archiving, and I don't recall ever having to do anything specifically to add or enable it.  

[root@lists01 srv-joe]# systemctl status sympa-archive.service

● sympa-archive.service - Sympa mailing list manager (archiving)

     Loaded: loaded (/usr/lib/systemd/system/sympa-archive.service; static)

     Active: active (running) since Thu 2025-02-06 11:42:30 EST; 1 week 6 days >

    Process: 3102 ExecStart=/usr/sbin/archived.pl (code=exited, status=0/SUCCES>

   Main PID: 3784 (archived.pl)

      Tasks: 1 (limit: 48464)

     Memory: 107.5M

        CPU: 52.465s

     CGroup: /system.slice/sympa-archive.service

             └─3784 /usr/bin/perl /usr/sbin/archived.pl

Did you install from a pre-built package or did you install by some other means?

 

 

<Outlook-a4ekxm2s.png>

Joseph Meslovich Network Administrator & IT Security Officer Information Technology Center Bridgewater College Phone: 540-828-5343 | bridgewater.edu

 

---

From: address@concealed <address@concealed> on behalf of Ralph Ballier <address@concealed>
Sent: Wednesday, February 19, 2025 4:04 PM
To: En <address@concealed>
Subject: [en@sympa] Questions about daemons

 

Hello,

I have the following question: I have noticed that no archives are being created, even though archiving is enabled in the web interface.

After some searching, I discovered that the archived.pl daemon is not running. Once I started it from the command line, an archive was created.

This leads me to the question: why was it not running? What is the concept behind starting it? I haven't read anything about it. Do I need to create a unit in systemd myself?

And what about the other daemons: bounced, bulk, sympa_automatic, sympa_msg, and task_manager?

Best regards
Ralph