The mailing list for listmasters using Sympa

[Robert McNicholas <address@concealed>]

We have had similar problems, also running 6.2.14 on RedHat 7.  On the 
list that was having the problem, I noticed if I clicked refresh 
repeatedly on the list's home page, the list of moderators would 
sometimes show all moderators, and sometimes not. The ones that were 
occasionally missing were defined as part of an "owner_include" 
paragraph, including members from an LDAP group via a custom data 
source.  There was a "sync_include_admin" error logged in the sympa log 
whenever this happened.  You might grep for these in your logs.

This was the source of our problem.  It turned out we were having 
problems with our LDAP server and the query for the admins was 
occasionally timing out. That left the owners occasionally not 
completely defined.  It seems that query runs on ever owner reference 
and is not cached.

Are your moderators defined in an external data source by any chance?

-Rob

On 1/5/17 10:29 AM, Matt Goebel wrote:
>   Running 6.2.14 and haven't had a lot of moderated lists until
> recently and now sympa seems to be exhibiting odd behavior?
>
>   If the moderator clicks on the link included in the
> sympa generated approval message about 1/2 the time it comes back
> with a privilege error, and then logs the following ::
>
> Jan  5 13:23:17 atari wwsympa[12411]: info main::check_action_parameters() 
> [robot atari.emich.edu] [session 89931080474503] [client 164.76.108.11] [user 
> address@concealed] [list matt-moderated-test] Authorization failed, 
> insufficient privileges
> Jan  5 13:23:17 atari wwsympa[12411]: err main::#1632 [robot atari.emich.edu] [session 
> 89931080474503] [client 164.76.108.11] [user address@concealed] Missing required 
> parameters for action "modindex"
>
>   The other half of the time it shows them the message that need to be
> moderated.  When I mean 1/2 the time I mean when I click on any
> such link it works 1/2 the time and breaks 1/2 the time, but will
> work if click on a second or third time?  Some kind of odd timing issue?
>
>
> Thanks,
> Matt