The mailing list for listmasters using Sympa

[Miles Fidelman <address@concealed>]

Well, after installing the latest DBD:mysql, and thinking that bulk.pl 
was no longer dying, I discover that yes, indeed it still is:

server1:/var/log# /etc/init.d/sympa status
Status of Sympa subsystem:
Status file for subsystem found.
sympa (pid 31024) is active...
bulk died, pid file remains.
archived (pid 31047) is active...
bounced (pid 31050) is active...
task_manager (pid 31052) is active...

What's weird is this:
server1:/var/log# pgrep bulk.pl
31035

and it clearly is the one started by init:
server1:/var/log# pstree
init─┬─amavisd-new─┬─amavisd-new
│ └─amavisd-new───dccproc
├─apache2─┬─11*[apache2]
│ └─apache2───wwsympa.fcgi
├─archived.pl
├─bounced.pl
├─bulk.pl
<snip>

Just for the heck of this, I tried (note the last line):
server1:/var/log# /home/sympa/bin/bulk.pl --debug
Configuration file read, log level set using options : 2
List::send_notify_to_listmaster() 
List::send_notify_to_listmaster(sympa_died,lists.neighborhood.net )
List::send_global_file() List::send_global_file(listmaster_notification, 
address@concealed, lists.neighborhood.net)
List::get_user_db() List::get_user_db(address@concealed)
tools::decrypt_password() tools::decrypt_password 
(ba13285e60de8a24d42f974e1d55947b)
Use of uninitialized value $_[2] in sprintf at 
/usr/lib/perl5/Sys/Syslog.pm line 365.
mail::mail_file() 
mail::mail_file(/home/sympa/default/mail_tt2/listmaster_notification.tt2, address@concealed, 
)
Language::PushLang() Language::PushLang(en_US)
Language::SetLang() Language::SetLang(en_US)
Language::SetLang() Language::SetLang(en_US)
Language::PopLang()
Use of uninitialized value $_[0] in sprintf at 
/usr/lib/perl5/Sys/Syslog.pm line 365.
Language::SetLang() Language::SetLang()
Could not lock /home/sympa/bulk.pid, process is probably already running 
: Illegal seek

and I see this in syslog:
May 21 09:51:03 server1 bulk[9094]: Process 9094 didn't send any message 
since 600 seconds, exiting.
May 21 09:51:03 server1 bulk[9094]: bulk.pl exited normally due to signal

even weirder:
server1:/var/log# ls /home/sympa/*.pid
/home/sympa/archived.pid /home/sympa/bulk.pid /home/sympa/task_manager.pid
/home/sympa/bounced.pid /home/sympa/sympa.pid
server1:/var/log# more /home/sympa/bulk.pid
31035

i.e., the .pid file is there AND it indicates the pid of a running copy 
of bulk.pl

and when I run the test from /etc/init.d/sympa status (ps -A | grep "$pid)
server1:/var/log# ps -A|grep 31035
31035 pts/0 00:00:05 bulk.pl

So, this leaves me wondering: what the heck is going on????

Miles



--
In theory, there is no difference between theory and practice.
In<fnord>  practice, there is.   .... Yogi Berra