Subject: The mailing list for listmasters using Sympa
List archive
- From: Olivier Salaün <address@concealed>
- To: Riccardo Veraldi <address@concealed>
- Cc: sympa-users <address@concealed>
- Subject: [sympa-users] Re: from 5.2.4 to 5.3.2
- Date: Tue, 07 Aug 2007 10:52:55 +0200
No, you should not get these warnings, unless another sympa process is updating the members cache for this list at the same time.
If the problems are related to the upgrade process, you can try 1) stopping all sympa processes (including the httpd server) , 2) remove all the include_admin_user.lock files 3) restart all sympa processe
Riccardo Veraldi a écrit :
after moving to a new sympa installation migrating from 5.2.4 to 5 .3.2
I have plenty of these warnings on sympa.log
this is normal ?
Aug 7 10:02:08 lists wwsympa[2153]: Lock::_lock_file() Waiting for read lock on /home/sympa/expl/utenti-to/include_admin_user.lock
Aug 7 10:02:09 lists wwsympa[2146]: Lock::_lock_file() Waiting for read lock on /home/sympa/expl/utenti-to/include_admin_user.lock
Aug 7 10:02:10 lists wwsympa[2156]: Lock::_lock_file() Waiting for read lock on /home/sympa/expl/utenti-to/include_admin_user.lock
Aug 7 10:02:13 lists wwsympa[2133]: Lock::_lock_file() Waiting for read lock on /home/sympa/expl/utenti-to/include_admin_user.lock
-
[sympa-users] from 5.2.4 to 5.3.2,
Riccardo Veraldi, 08/07/2007
- [sympa-users] Re: from 5.2.4 to 5.3.2, Olivier Salaün, 08/07/2007
Archive powered by MHonArc 2.6.19+.