Skip to Content.
Sympa Menu

devel - Re: [sympa-dev] wwsympa failure after an upgrade to perl 5.10

Subject: Developers of Sympa

List archive

Chronological Thread  
  • From: Olivier Salaün <address@concealed>
  • To: Guillaume Rousse <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-dev] wwsympa failure after an upgrade to perl 5.10
  • Date: Mon, 14 Apr 2008 14:19:09 +0200

Hi Guillaume,

We'll perform some tests with Perl 5.10 ourselves. Could you please submit an "official" bug report in our tracking system : https://sourcesup.cru.fr/tracker/?group_id=23

In the meanwhile I recommend you downgrade to perl 5.8.

Guillaume Rousse a écrit :
Hello.

I just updated a server from mdv 2008.0 to mdv 2008.1, and the sympa web
interface doesn't work anymore. Settings logs to maximum level, it seems
to wait forever to never released locks:
Apr 14 12:33:57 chatelet wwsympa[20420]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/seminars/include_admin_user.lock
Apr 14 12:33:59 chatelet wwsympa[20383]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/test/include_admin_user.lock
Apr 14 12:34:08 chatelet wwsympa[20420]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/seminars/include_admin_user.lock
Apr 14 12:34:10 chatelet wwsympa[20403]: Lock::_lock_file() Waiting for
read lock on /var/lib/sympa/expl/test/include_admin_user.lock
Apr 14 12:34:23 chatelet wwsympa[20383]: Lock::_lock_file() Waiting for
read lock on /var/lib/sympa/expl/test/include_admin_user.lock
Apr 14 12:34:23 chatelet wwsympa[20403]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/test/include_admin_user.lock
Apr 14 12:34:33 chatelet wwsympa[20403]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/test/include_admin_user.lock
Apr 14 12:34:36 chatelet wwsympa[20412]: Lock::_lock_file() Waiting for
read lock on /var/lib/sympa/expl/ssreflect/include_admin_user.lock
Apr 14 12:34:58 chatelet wwsympa[20378]: Lock::_lock_file() Waiting for
read lock on /var/lib/sympa/expl/testlist/include_admin_user.lock
Apr 14 12:34:59 chatelet wwsympa[20378]: Lock::_lock_file() Removing
lock file /var/lib/sympa/expl/testlist/include_admin_user.lock
Apr 14 12:35:12 chatelet wwsympa[20412]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/test/include_admin_user.lock
Apr 14 12:35:12 chatelet wwsympa[20378]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/testlist/include_admin_user.lock
Apr 14 12:35:22 chatelet wwsympa[20381]: Lock::_lock_file() Waiting for
read lock on /var/lib/sympa/expl/testlist/include_admin_user.lock
Apr 14 12:35:27 chatelet wwsympa[20378]: Lock::_lock_file() Waiting for
write lock on /var/lib/sympa/expl/testlist/include_admin_user.lock
Apr 14 12:35:28 chatelet wwsympa[20414]: Lock::_lock_file() Waiting for
read lock on /var/lib/sympa/expl/test/include_admin_user.lock
...

Stopping all sympa processes and removing those lock files doesn't help,
they still seem to grow indefinitly:
[root@chatelet sympa]# find /var/lib/sympa/ -name *.lock | xargs wc -l
0 /var/lib/sympa/expl/all/config.lock
30 /var/lib/sympa/expl/all/stats.lock
1 /var/lib/sympa/expl/all/include_admin_user.lock
1 /var/lib/sympa/expl/all/include.lock
0 /var/lib/sympa/expl/sec/config.lock
22 /var/lib/sympa/expl/sec/stats.lock
39 /var/lib/sympa/expl/sec/include_admin_user.lock
0 /var/lib/sympa/expl/testlist/config.lock
21 /var/lib/sympa/expl/testlist/stats.lock
33 /var/lib/sympa/expl/testlist/include_admin_user.lock
0 /var/lib/sympa/expl/retest/config.lock
23 /var/lib/sympa/expl/retest/stats.lock
38 /var/lib/sympa/expl/retest/include_admin_user.lock
0 /var/lib/sympa/expl/test/config.lock
21 /var/lib/sympa/expl/test/stats.lock
35 /var/lib/sympa/expl/test/include_admin_user.lock
0 /var/lib/sympa/expl/seminars/config.lock
22 /var/lib/sympa/expl/seminars/stats.lock
44 /var/lib/sympa/expl/seminars/include_admin_user.lock
0 /var/lib/sympa/expl/ssreflect/config.lock
37 /var/lib/sympa/expl/ssreflect/include_admin_user.lock
22 /var/lib/sympa/expl/ssreflect/stats.lock

The sympa version before and after the upgrade is the same (5.3.4), but
perl version changed from 5.8 to 5.10.

Trying to run wwsympa.fcgi by hand raise the following warnings, due to
the redefinition of system constants imported just before (evil, a bug
report should probably get open there):

Prototype mismatch: sub Lock::LOCK_SH () vs none at
/usr/share/sympa/lib/Lock.pm line 38.
Constant subroutine LOCK_SH redefined at /usr/share/sympa/lib/Lock.pm
line 38.
Prototype mismatch: sub Lock::LOCK_EX () vs none at
/usr/share/sympa/lib/Lock.pm line 39.
Constant subroutine LOCK_EX redefined at /usr/share/sympa/lib/Lock.pm
line 39.
Prototype mismatch: sub Lock::LOCK_NB () vs none at
/usr/share/sympa/lib/Lock.pm line 40.
Constant subroutine LOCK_NB redefined at /usr/share/sympa/lib/Lock.pm
line 40.

But commenting them doesn't help. wwwsympa.fcgi launched either by root
or apache user just hangs forever. I couldn't use the debugger,
apparently due to mismatch with -U option in script shellbang, nor
strace due to a failure to change gid (BTW, how a perl script with
setgid bit invoked by apached is supposed to work without invoking
setuipdperl ?).

I also tried running with or without fast CGI, same result. Any hints
welcome.





Archive powered by MHonArc 2.6.19+.

Top of Page