The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

Hi and sorry for this late answer,

Once the install is performed, the init script (called "sympa") is installed by default in "<your_system_config_dir>/rc.d/init.d". "<your_system_config_dir>" is "/etc" if you installed without the option "--enable-fsh". Otherwise, it is the default system config dir of your OS. Is is /etc in most of the Linux systems. What OS are you running? If your default config dir is different and you did not use the "enable-fsh" option, it is possible that the script, copied in "/etc/rc.d/init.d" will not be used.
If something went wrong, you can still find this script in the source, under the directory "<your_sympa_sources_dir>/src/etc/script/".

Regards,

David Verdin

Le 24/03/11 22:25, Scot Wilcoxon a écrit :

Looking for init script instructions...

http://www.sympa.org/manual/upgrading
"And that' it! This command will perform all the required DB changes (if
running MySQL) and will update the configuration files if required."
Apparently it missed a configuration file.

http://www.sympa.org/manual/installing-sympa#installing_sympa
Oh, that might be where it is!  Searching the page for "init" shows the
configure flag "--with-initdir=DIR".  Maybe the upgrade installation
config didn't detect the existing init script.

Hmm.  Makefile does have:
initdir = /etc/rc.d/init.d

Looking in /home/sympa, and in my sympa source directories, I'm not
finding a file with the init script in it.  None of the files with
"bulk.pl" seem to be the init script.


On Thu, 2011-03-24 at 15:07 -0500, Scot Wilcoxon wrote:

This is version 6, and I did upgrade recently.  I don't see a script
called "symba" in bin, and I didn't notice where in the install
instructions was a script update.

On Thu, 2011-03-24 at 12:25 -0700, Roger B.A. Klorese wrote:

What version is this?  If you upgraded from pre-6 to 6, you didn't 
 update the init script.

 On Thu, 24 Mar 2011 10:51:31 -0500, Scot Wilcoxon wrote:

I don't see a 'bulk' process.  It also isn't in /etc/init.d/sympa as 
a
daemon which should be started.

$ ps fax | grep -i sympa
12133 pts/0    S+     0:00              \_ grep -i sympa
 4914 ?        S      0:33  |   \_ /usr/bin/perl
-U /dev/fd/3//home/sympa/bin/wwsympa.fcgi
 4930 ?        S      0:19  |   \_ /usr/bin/perl
-U /dev/fd/3//home/sympa/bin/wwsympa.fcgi
13009 ?        S      0:18 /usr/bin/perl /home/sympa/bin/sympa.pl
13021 ?        S      0:02 /usr/bin/perl /home/sympa/bin/archived.pl
13036 ?        S      0:24 /usr/bin/perl 
/home/sympa/bin/task_manager.pl
13041 ?        S      0:01 /usr/bin/perl /home/sympa/bin/bounced.pl


On Wed, 2011-03-23 at 20:59 +0100, David Verdin wrote:

Hi,

Just a quick question: is your bulk.pl daemon running?

Regards,

David

Le 23/03/11 20:33, Scot Wilcoxon a écrit :

I don't remember previous_email in any configuration files.

The only scenari use of previous_email are:

./default/scenari/subscribe.owner:is_subscriber([listname],[previous_email]) 
smtp,smime,md5    -> do_it

./default/scenari/subscribe.auth_owner:is_subscriber([listname],[previous_email]) 
md5,smime -> do_it

The logs also don't say that anything failed due to that.  There 

are

many more log entries, but I don't see any keywords which indicate 

a

problem.

Isn't there a "Sympa Status" page which shows the status of what 

is

currently happening, or what recently happened?  Going to each
individual list to see if something is waiting to be moderated is
awkward when there are dozens of lists.  Seeing that something is 

stuck

in a queue seems to be even more awkward to accomplish...but I 

haven't

been able to find anything reporting that something tried or 

failed to

reach a queue.

I think this is the end of the log entries for the attempt to 

send:

Mar 23 13:30:53 dev wwsympa[4914]: debug2 Scenario::new()
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Scenario::new()
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Scenario::verify()
(is_subscriber([listname],[sender]))
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Scenario::verify()
(is_editor([listname],[sender]))
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Scenario::verify()
(is_owner([listname],[sender]))
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Scenario::verify() 

(true())

Mar 23 13:30:53 dev wwsympa[4914]: debug SympaSession::store()
Mar 23 13:30:53 dev wwsympa[4914]: debug SympaSession::renew()
id_session=(60874436625054)
Mar 23 13:30:53 dev wwsympa[4914]: debug 

SympaSession::get_random()

SympaSession::random
Mar 23 13:30:53 dev wwsympa[4914]: debug 

SympaSession::set_cookie()

Session::set_cookie(localhost,session,secure= 0)
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Language::SetLang()
Language::SetLang(en_US)
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Language::SetLang()
Language::SetLang(us)
Mar 23 13:30:53 dev wwsympa[4914]: debug Language::PushLang()
Language::PushLang(en_US)
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Language::SetLang()
Language::SetLang(en_US)
Mar 23 13:30:53 dev wwsympa[4914]: debug Language::PopLang()
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Language::SetLang()
Language::SetLang(en_US)
Mar 23 13:30:53 dev wwsympa[4914]: debug2 Language::SetLang()
Language::SetLang(en_US)
Mar 23 13:30:55 dev task_manager[27447]: debug2 mail::reaper() 

Reaper

unwaited pids :  Open = 0
Mar 23 13:30:55 dev task_manager[27447]: debug2 

List::init_list_cache()

List::init_list_cache()
Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1300924492.ACTION.purge_session_table._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1300924493.ACTION.purge_one_time_ticket_table._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1300924554.ACTION.purge_tables._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1300972529.ACTION.purge_logs_table._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1300972664.ACTION.expire_bounce._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1300972728.ACTION.eval_bouncers._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1301056420.ACTION.process_bouncers._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1302179433.ACTION.purge_user_table._global)

Mar 23 13:30:55 dev task_manager[27447]: debug2 Task::new()

Task::new(/home/sympa/spool/task/1302179500.ACTION.purge_orphan_bounces._global)

On Wed, 2011-03-23 at 14:55 -0400, Dan Pritts wrote:

this looks odd:

Mar 23 13:15:07 dev wwsympa[4914]: debug Scenario::verify() 

undefine

variable context [previous_email] in rule
is_subscriber([listname],[previous_email])

I see previous_email in a couple of the default "subscribe" 

scenari.  If you've used

it in a send scenario, I suspect that's your problem.

On Mar 23, 2011, at 2:37 PM, Scot Wilcoxon wrote:

Nothing is being sent by Sympa.  How do I get logging which 

reports what

is failing?  I'm running with debug level 2, and there are a 

lot of log

entries created, but none of them seem to be saying that there 

is a

failure.

Postfix log shows no messages coming out.  (Postfix 

configuration and

aliases are defined)  Postfix does deliver messages to Sympa, 

and the

incoming message does appear in the list's archive.

I checked the queue permissions, as suggested in the FAQ "All 

messages

are lost".  User sympa has permissions to queue directories, 

and the

queue program is setuid sympa.

When I use wws to send a text message to a list, I see the 

message

appear in the Archive, I see log entries about the number of
subscribers, but I don't see log entries about messages being 

emailed.

I also don't see anything to be moderated, so the message is 

not

awaiting moderation.

Is there a summary page that shows all queued moderations and 

other

actions?  Maybe I'm just not seeing something which is causing 

a global

blockage or slowdown.  I'm only aware of how to check the 

status of

individual lists, and I haven't found a summary of everything 

happening

in the Sympa installation.

Maybe log entries like this are supposed to mean something, 

but I'm not

seeing any words like "warning", "error", or "failure", so I 

don't know

if anything like this looks unusual:
Mar 23 13:15:07 dev wwsympa[4914]: debug2 Scenario::verify() 

(true())

Mar 23 13:15:07 dev wwsympa[4914]: debug 

List::check_list_authz()

List::check_list_authz subscribe,md5
Mar 23 13:15:07 dev wwsympa[4914]: debug 

Scenario::request_action()

List::request_action subscribe,md5,newsletters.bizmeasure.com
Mar 23 13:15:07 dev wwsympa[4914]: debug2 Scenario::new()
Mar 23 13:15:07 dev wwsympa[4914]: debug2 Scenario::new()
Mar 23 13:15:07 dev wwsympa[4914]: debug2 Scenario::verify()
(is_subscriber([listname],[previous_email]))
Mar 23 13:15:07 dev wwsympa[4914]: debug Scenario::verify() 

undefine

variable context [previous_email] in rule
is_subscriber([listname],[previous_email])
Mar 23 13:15:07 dev wwsympa[4914]: debug2 Scenario::verify() 

(true())

Mar 23 13:15:07 dev wwsympa[4914]: debug 

List::check_list_authz()

List::check_list_authz web_archive.access,md5
Mar 23 13:15:07 dev wwsympa[4914]: debug 

Scenario::request_action()

List::request_action 

web_archive.access,md5,newsletters.bizmeasure.com

Mar 23 13:15:07 dev wwsympa[4914]: debug2 Scenario::new()
Mar 23 13:15:07 dev wwsympa[4914]: debug2 Scenario::new()

danno
--
Dan Pritts, Sr. Systems Engineer
Internet2
office: +1-734-352-4953 | mobile: +1-734-834-7224

--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the
mails.
So if you want your bug reports or feature requests for Sympa to be
processed, please post them to the Sympa tracker

--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the mails.
So if you want your bug reports or feature requests for Sympa to be processed, please post them to the Sympa tracker

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature