The mailing list for listmasters using Sympa

[Thomas Berry <address@concealed>]

Your situation is different.  As you mentioned earlier in the thread, it 
has to do with the "update" parameter and its "email" attribute.  Other 
than being related to the list's config, I don't think you're 
experiencing the same issue or symptoms.  My family-based list config 
does not have the "update" parameter.  It must be something new in 
6.0.1; I could not find it in the Sympa docs.

You might try removing the "update" setting and try running 
reload_list_config again.

Thomas


Miles Fidelman wrote:
> Well... I just went and looked in the database, and the owners and 
> editors sure seem to be in the database, and the lists are actually 
> sending traffic.  This is sort of a mystery!
>
> Miles
>
> Thomas Berry wrote:
>   
> > Miles,
> >
> > When the list related owners and editors are not found in the 
> > admin_table, task_manager.pl sets the list to error_config which 
> > effectively disables the list.
> >
> > Thomas
> >
> > Miles Fidelman wrote:
> >     
> > > Which leads to three questions:
> > >
> > > 1. does it cause problems if the info is missing from admin_table, 
> > > and, if yes,
> > >
> > > 2. what kinds of problems (I'm not seeing any), and,
> > >
> > > 3. how does one fix this?
> > >
> > > Miles
> > >
> > > Thomas Berry wrote:
> > >       
> > > > Sorry.  I forgot that I checked the config.bin files (strings 
> > > > config.bin) and found that it does contain the owner entries; it is 
> > > > only the admin_table that is missing the owner and editor entries 
> > > > when this issue occurs, and the owner entries are only missing for 
> > > > the list that is having the problem.
> > > >
> > > > I'm thinking I might disable the code that sets the list to 
> > > > error_config until this issue has been addressed, or run 
> > > > admin::update_list before the owner check is performed.
> > > >
> > > > Thomas
> > > >
> > > >
> > > > Thomas Berry wrote:
> > > >         
> > > > > That is interesting and disconcerting.  I'm not familiar with the 
> > > > > "update" configuration; it's not a setting that we use.   Our issue 
> > > > > is specific to "owner" setting in the list config.
> > > > >
> > > > > I later traced the problem to the record keeping in the 
> > > > > admin_table; the owners and editor entries in the admin_table are 
> > > > > getting removed which results in the error about the owner missing, 
> > > > > not the list config.  But, this still could be an issue with the 
> > > > > config.bin, which is why a reload_list_config fixes the problem.
> > > > >
> > > > > Thomas
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Miles Fidelman wrote:
> > > > >           
> > > > > > Interesting, because I'm seeing the same kinds of log entries, but 
> > > > > > the error does NOT go away when I run
> > > > > > sympa.pl --reload_list_config --list=
> > > > > >
> > > > > > When I run the command, I get error messages about the missing 
> > > > > > parameter(s).
> > > > > >
> > > > > > For example:
> > > > > >
> > > > > > server1:/home/sympa/bin# ./sympa.pl --reload_list_config 
> > > > > > --address@concealed
> > > > > > Loading list address@concealed...
> > > > > > List::_load_admin_file() Missing key "email" in param "update" in 
> > > > > > /home/sympa/expl/lists.fusn.org/business/config
> > > > > >
> > > > > > and I can't find anything out of the ordinary about those specific 
> > > > > > list config files
> > > > > >
> > > > > > Miles
> > > > > >
> > > > > > Thomas Berry wrote:
> > > > > >             
> > > > > > > As mentioned earlier, running sympa.pl --reload_list_config 
> > > > > > > --address@concealed corrects the condition.
> > > > > > >
> > > > > > > Thomas
> > > > > > >
> > > > > > > Thomas Berry wrote:
> > > > > > >               
> > > > > > > > After upgrading from 5.4 to 6.0.1 over the weekend, I'm 
> > > > > > > > occasionally seeing sympa report that some lists are "Missing 
> > > > > > > > parameter".  The error is specific to "owner".  When I look at 
> > > > > > > > the config for the lists, I find that the owner parameter is 
> > > > > > > > properly defined per the family they belong.  The error only 
> > > > > > > > goes away when sympa.pl --reload_list_config --list... is run.  
> > > > > > > > This is after I had already ran sympa.pl with reload_list_config 
> > > > > > > > on all mailing lists this morning.
> > > > > > > >
> > > > > > > > Any ideas?
> > > > > > > >
> > > > > > > > Thomas
> > > > > > > >
> > > > > > > >                 
> > >       
>
>
>