The mailing list for listmasters using Sympa

[Rance Hall <address@concealed>]

Sending message again as I forgot the attachment last time.

 

Sympa folks:

 

I’m faced with an interesting problem and looking for an answer.

 

I’m running 6.2.36 from packages at the sympa-ja centos/redhat repo in a docker container that is configured to stop and shutdown if any of the critical sympa services (or postfix or nginx, or …) stop for some reason.

 

We run rancher as a docker hosting environment and the sympa docker container works wonders except for one nagging issue.

 

When you update a list owner or moderator something behind the scenes that should be happening isn’t.

 

The database and list definition is properly updated, but the environment is not recreated/rebuilt.  I suspect a cache related issue, but I could be way off.

 

Symptoms:

 

1. The list menu on the right side of the web ui does not update with the changes.
2. Permissions in the running instance are not updated with the changes.

 

Fix: Restart sympa, but in a docker/rancher environment this is less than ideal.

 

Questions:

 

1. What is it that isn’t happening that should be?
2. Is there a trigger that we can use to force this magic thing to happen without an interruption in service.

 

I’ve attached a screenshot with illustrating the issue in symptom 1 above with the emails and names obfuscated for obvious reasons, take note of the two moderators listed but not in the right hand menu.

 

Thoughts and requests to go jump in a lake are all considered but may not be acted upon.

 

Thanks all for your time.

 

Rance

 

 

-- 

Rance Hall

ESU 10 Application Specialist

O: 308-698-1919

F: 308-233-9066

Attachment: fcs_-_FCS_-_review.png
Description: fcs_-_FCS_-_review.png