Skip to Content.
Sympa Menu

en - Re: [sympa-users] help! - upgrade problems - archived problem - maybe fixed - more

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Miles Fidelman <address@concealed>
  • To: Miles Fidelman <address@concealed>
  • Cc: address@concealed, Olivier Salaün - CRU <address@concealed>
  • Subject: Re: [sympa-users] help! - upgrade problems - archived problem - maybe fixed - more
  • Date: Fri, 01 Sep 2006 14:11:18 -0400

Miles Fidelman wrote:
Miles Fidelman wrote:
Miles Fidelman wrote:
Olivier Salaün - CRU wrote:

4. tried a /home/sympa/bin/sympa.pl - and it seemed to start, so then stopped it and did a /home/rc3.d/sympa start and everything seemed to start, but archived stops immediately (which it's been doing lately - I expect something is locked or corrupted - ANY SUGGESTIONS?)
Check your log files or try to restart it.
Unfortunately, I've done this - both under Sympa 3.4.4.3 and under the newly upgraded 5.2.1 install.

Even at debug level 4, archived starts, then almost immediately stops - leaving no messages in the log.

Any thoughts on where to look for locks, corruption, diagnostic ideas, ....?

Made some progress on this. Tried running archived.pl -d, getting the following output before it exits:

[sympa@xel008 bin]$ ./archived.pl -d
queue : /home/sympa/spool/outgoing
Modification of a read-only value attempted at /usr/local/lib/perl5/5.8.4/i686-linux/Sys/Syslog.pm line 312, <REMOVE> line 1.

Looks like archived is making a call into Syslog.pm with data that causes Syslog.pm to fail in an unclean manner.

Miles
did some web searching, found out that syslog.pm doesn't like things that have a "%" in them

found a .remove. files in /home/sympa/spool/outgoing/ containing this:
address@concealed

removed the file, restarted archived.d and it sure seems to be doing a lot of work - probably catching up on a lot of stuff - the next question is whether it's also converting archives - we'll see

meanwhile: do you know if this problem goes away with later versions of Syslog.pm, or is this something that Sympa should screen for?

looks like the message was actually deleted, but logging failed:
looks like a message id containing a % can screw up archived.pl
deleted/23:Message-ID: <address@concealed>

Miles




Archive powered by MHonArc 2.6.19+.

Top of Page