[Mailman-Users] Archive looping

Joseph Brennan brennan at columbia.edu
Tue Sep 1 16:27:18 CEST 2015

We have a list with a very large archive, over 137,000 messages in a month. 
It catches system alerts. This might just be a bad idea. Maybe we should 
archive by day. But it's been all right for many months up to now.

I'm looking for ideas on how to solve a problem with the archives.

Yesterday the archive got into a weird state that I could not break by a 
shutdown and fresh start. For each incoming message, it rewrites all of the 
old messages with one extra newline. This useless activity takes quite a 
while and has caused mail to accumulate in the in/ directory.

Inspection of a sample message in a backup from about 24 hours ago shows 
hundreds of newlines added to the message in that time. The newlines are 
always added at the same place, between this:---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <<A HREF="https://lists.columbia.edu [detail omitted] </A>>

and this:---


Below is a 'truss' (it's solaris!) showing the read and write for one 
message. It reads 8192 and 2187 bytes, and writes out the same file with 
8192 and 2188 bytes. (List name changed to 'listname')

fstat64(9, 0xFFBFEC40)				= 0
fstat64(9, 0xFFBFEC80)				= 0
fstat64(9, 0xFFBFEB28)				= 0
ioctl(9, TCGETA, 0xFFBFEC0C)			Err#25 ENOTTY
read(9, " < ! D O C T Y P E   H T".., 8192)	= 8192
read(9, "\n\n\n\n\n\n\n\n\n\n\n\n".., 8192)	= 2187
llseek(9, 0xFFFFFFFFFFFFFD8D, SEEK_CUR)		= 9752
close(9)					= 0
umask(02)					= 07
fstat64(9, 0xFFBFEC40)				= 0
umask(07)					= 02
0xFFBFE908) Err#2 ENOENT
0xFFBFE908) Err#2 ENOENT
0xFFBFE908) Err#2 ENOENT
0xFFBFE908) Err#2 ENOENT
fstat64(9, 0xFFBFECC8)				= 0
fstat64(9, 0xFFBFEB70)				= 0
ioctl(9, TCGETA, 0xFFBFEC54)			Err#25 ENOTTY
write(9, " < ! D O C T Y P E   H T".., 8192)	= 8192
write(9, "\n\n\n\n\n\n\n\n\n\n\n\n".., 2188)	= 2188
close(9)					= 0

Joseph Brennan
Columbia University Information Technology

More information about the Mailman-Users mailing list