Skip to Content.
Sympa Menu

en - Re: [sympa-users] sympa errors after update to 6.2.64

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: David Carter <address@concealed>
  • To: Gerard Ranke <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-users] sympa errors after update to 6.2.64
  • Date: Thu, 12 Aug 2021 10:07:25 +0100

On 12/08/2021 09:29, Gerard Ranke (via sympa-users Mailing List) wrote:

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

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]

Sympa::List::load() [line 697 in Sympa 6.2.64] is attempting to lock the config file on a specific list using:

## Get a shared lock on config file first
my $lock_fh =
Sympa::LockedFile->new($self->{'dir'} . '/config', 5, '<');
unless ($lock_fh) {
$log->syslog('err', 'Could not create new lock');
return undef;
}

in my case that would be:

-rw-r----- 1 sympa sympa 620 Aug 11 08:15 /var/lib/sympa/list_data/test-dpc22/config

Sympa::LockedFile() uses File::NFSLock(), so this creates a file named "config.lock" using a hitching post algorithm (see File::NFSLock(3)).

Consequently user sympa needs write access on the parent directory.

In my case:

drwxr-x--- 4 sympa sympa 4096 Aug 11 08:16 /var/lib/sympa/list_data/test-dpc22

Hope that helps.

--
David Carter Email: address@concealed
University of Cambridge, Phone: (01223) 334502
Information Services,
7 J J Thomson Avenue,
Cambridge UK. CB3 0RB



Archive powered by MHonArc 2.6.19+.

Top of Page