The mailing list for listmasters using Sympa

[Gerard Ranke <address@concealed>]

Hi Racke,

Yes, I thought of that too, but all spool dirs (under ~sympa) are owned
and writeable by sympa.

drwxr-xr-x 17 sympa sympa  285 12 aug 10:23 ./
drwxr-xr-x 16 sympa sympa 4096 12 aug 10:25 ../
drwxr-xr-x  2 sympa sympa   10 19 aug  2014 auth/
drwxr-x---  3 sympa sympa   25 11 aug 20:32 automatic/
drwxr-x---  3 sympa sympa   25 18 jul 16:40 bounce/
drwxr-xr-x  5 sympa sympa   55  9 sep  2016 bulk/
drwxr-xr-x  2 sympa sympa   10 10 aug 21:43 digest/
drwxr-x---  3 sympa sympa   25 21 aug  2014 distribute/
drwxr-xr-x  2 sympa sympa   10 19 aug  2014 expire/
drwxr-xr-x  2 sympa sympa   10 25 jul  2020 moderation/
drwxr-xr-x  4 sympa sympa   42 11 aug 13:11 msg/
drwxr-xr-x  4 sympa sympa   45 10 aug 21:43 outgoing/
drwxr-x---  2 sympa sympa   10 21 aug  2014 subscribe/
drwxr-xr-x  2 sympa sympa 4096 12 aug 10:25 task/
drwxr-xr-x  2 sympa sympa 4096 12 aug 10:24 tmp/
drwxr-x---  2 sympa sympa   10 21 aug  2014 topic/
drwxr-x---  3 sympa sympa   25  9 sep  2016 viewmail/

Also, there don't seem to be any lockfiles in ~sympa on our testserver,
so possibly I'm looking in the wrong place. /run/lock doesn't contain
any sympa locks either.

Best,

gerard

On 11-08-2021 22:05, Stefan Hornburg (Racke) wrote:
> My first step would be to check permissions on the spool directories.
> They should be writeable by the Sympa user.
> 
> Regards
> Racke
> 
> On August 11, 2021 9:39:38 PM GMT+02:00, Gerard Ranke
> <address@concealed> wrote:
> 
>     Dear list-users,
> 
>     After I got 6.2.64 working on a testserver, I decided to take the plunge
>     and try and upgrade our old v6.1.22 sympa to the latest stable version.
>     I followed all the instructions in the administration manual, and the
>     upgrade itself seemed to go well enough, but when I start the new sympa,
>     the task_manager keeps complaining like this:
> 
>     2021-08-11T21:20:10.602455+02:00 mail task_manager[29230]: message
>     repeated 5 times: [ err main::#148 > Sympa::Spindle::spin#78 >
>     Sympa::Spool::next#124 > Sympa::Spool::Task::_load#57 >
>     Sympa::Spool::Task::_create_all_tasks#93 > Sympa::List::get_lists#4562 >
>     Sympa::List::new#179 > Sympa::List::load#697 Could not create new lock]
> 
>     I attached part of the sympa logfile that shows this. Current status is
>     that sympa is up, but all our lists are down... I have no idea why the
>     task_manager can't create locks, nor where to look for those, nor can I
>     find anything related on our testserver. Is there anybody who can help
>     me with this? I'm happy to supply configfiles, but there seems to be
>     rather a lot of those, and I don't know what would be relevant.
>     Best regards, and many thanks in advance!
> 
>     Gerard
> 
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

Attachment: OpenPGP_signature
Description: OpenPGP digital signature