The mailing list for listmasters using Sympa

["True, James Scott" <address@concealed>]

Sympa Friends,

After a reboot of the VM the wwsympa.service started failing. It had been working fine. The error looks like this:

[root@xxxx-list-app system]# systemctl -l status wwsympa

● wwsympa.service - WWSympa - Web interface for Sympa mailing list manager

   Loaded: loaded (/usr/lib/systemd/system/wwsympa.service; enabled; vendor preset: disabled)

   Active: failed (Result: exit-code) since Wed 2020-11-11 15:09:24 EST; 8s ago

  Process: 5689 ExecStart=/usr/bin/spawn-fcgi -F $FCGI_CHILDREN -P /run/sympa/wwsympa.pid -s /run/sympa/wwsympa.socket -u $FCGI_USER -g $FCGI_GROUP $FCGI_OPTS -- /usr/libexec/sympa/wwsympa.fcgi (code=exited, status=0/SUCCESS)

 Main PID: 5690 (code=exited, status=1/FAILURE)

Nov 11 15:09:23 xxxx-list-app.uits.iu.edu systemd[1]: Starting WWSympa - Web interface for Sympa mailing list manager...

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu systemd[1]: Started WWSympa - Web interface for Sympa mailing list manager.

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu spawn-fcgi[5689]: spawn-fcgi: child spawned successfully: PID: 5690

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu spawn-fcgi[5689]: spawn-fcgi: child spawned successfully: PID: 5691

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu spawn-fcgi[5689]: spawn-fcgi: child spawned successfully: PID: 5692

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu spawn-fcgi[5689]: spawn-fcgi: child spawned successfully: PID: 5693

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu spawn-fcgi[5689]: spawn-fcgi: child spawned successfully: PID: 5694

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu systemd[1]: wwsympa.service: main process exited, code=exited, status=1/FAILURE

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu systemd[1]: Unit wwsympa.service entered failed state.

Nov 11 15:09:24 xxxx-list-app.uits.iu.edu systemd[1]: wwsympa.service failed.

I remembered that I had this happed once before. I dug back through my notes. In my notes I tried several things with the /usr/lib/systemd/system/wwsympa.service file and after trying several systemctl daemon-reloads and systemctl reset-failed wwsympa.service, nothing worked. Then I found the while making a backup I had the accidentally changed the ownership of the /etc/sympa/sympa.conf. Changing this back to sympa.sympa fixed the issue.

This time unfortunately the ownership is correct and wwsympa.service is failing.

[root@xxxx-list-app ~]# ls -la /etc/sympa/sympa.conf

-rw-r----- 1 sympa sympa 6298 Nov 11 12:42 /etc/sympa/sympa.conf

Any information or suggestions as to what is the cause of the wwsympa.service failing would be greatly appreciated.

Thanks in advance,

Jim True 
Campus Communications Infrastructure
Indiana University

address@concealed
812-855-7519 (Office)