FAQ
Hi,

I noticed the following messages in mailman error log every time when a
list is accessed, for example:

/usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13813
Feb 09 09:49:38 2006 (13810) Failed before cPickle:
/usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13810
Feb 09 09:50:38 2006 (13813) Failed before cPickle:

It doesn't seem to be harmful, because all operations seem normal.
The permission for the list is:

drwxrwsr-x 2 mailman mailman 4096 Feb 9 09:49 email-team/

and under email-team:

-rw-rw-r-- 1 www-data mailman 24 Jan 21 08:55 request.pck
-rw-rw---- 1 mailman mailman 12595 Feb 9 09:49 digest.mbox
-rw-rw---- 1 mailman mailman 6184 Feb 9 09:49 config.pck.last
-rw-rw---- 1 mailman mailman 6184 Feb 9 09:49 config.pck

What does the error mean? Should I worry?

Thanks!

Susan

Search Discussions

  • Mark Sapiro at Feb 11, 2006 at 9:52 pm

    Susan Feng wrote:
    I noticed the following messages in mailman error log every time when a
    list is accessed, for example:

    /usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13813
    Feb 09 09:49:38 2006 (13810) Failed before cPickle:
    /usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13810
    Feb 09 09:50:38 2006 (13813) Failed before cPickle:

    It doesn't seem to be harmful, because all operations seem normal.
    The permission for the list is:

    drwxrwsr-x 2 mailman mailman 4096 Feb 9 09:49 email-team/

    and under email-team:

    -rw-rw-r-- 1 www-data mailman 24 Jan 21 08:55 request.pck
    -rw-rw---- 1 mailman mailman 12595 Feb 9 09:49 digest.mbox
    -rw-rw---- 1 mailman mailman 6184 Feb 9 09:49 config.pck.last
    -rw-rw---- 1 mailman mailman 6184 Feb 9 09:49 config.pck

    What does the error mean? Should I worry?

    I don't know what the error means. I couldn't find the message anywhere
    in Mailman 2.1.7 or in Python 2.4.

    I might be somewhat concerned since the above shows your list's
    config.pck last updated at 09:49 and there was one of these messages
    at 9:50:38, so what was happening then.

    I'm also, curious about why the PIDs in the file names don't match the
    PID of the process doing the logging, at least not in every case. Or
    maybe they do. Maybe you have shown us the end of entry 1, all of
    entry 2 and the start of entry 3.

    Basically, here's what happens when a list is saved (__save() in
    MailList.py). There are three file names:

    fname = config.pck
    fname_last = config.pck.last and
    fname_tmp = config.pck.tmp.<hostname>.<PID> which in your case becomes
    fname_tmp = config.pck.tmp.mailman.Stanford.EDU.ppppp where ppppp is
    the PID of the process doing the save.

    The save consists of
    1. open fname_tmp
    2. call cPickle to pickle and dump the list to fname_tmp
    3. if IOError write to the error log a message that begins
    "Failed config.pck write, retaining old state." and remove
    fname_tmp.
    else
    4. remove fname_last
    5. link fname to fname_last
    6. rename fname_tmp fname

    So apparently, your list is being saved successfully at least some of
    the time, but I would try to find where those messages are coming from.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Mark Sapiro at Feb 12, 2006 at 3:24 am

    Susan Feng wrote:
    I noticed the following messages in mailman error log every time when a
    list is accessed, for example:

    /usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13813
    Feb 09 09:49:38 2006 (13810) Failed before cPickle:
    /usr/local/mailman/lists/email-team/config.pck.tmp.mailman.Stanford.EDU.13810
    Feb 09 09:50:38 2006 (13813) Failed before cPickle:

    The more I look at this, the more it looks like a 'debugging' entry
    that someone may have added in the definition of __save() in your
    version of Mailman/MailList.py. Even if that is the case, that still
    leaves the questions "what is the exact circumstance the causes it?"
    and "who put it there and why?".

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Xueshan Feng at Feb 16, 2006 at 6:22 am

    On Feb 11, 2006, at 7:24 PM, Mark Sapiro wrote:

    Susan Feng wrote:
    I noticed the following messages in mailman error log every time
    when a
    list is accessed, for example:

    /usr/local/mailman/lists/email-team/
    config.pck.tmp.mailman.Stanford.EDU.13813
    Feb 09 09:49:38 2006 (13810) Failed before cPickle:
    /usr/local/mailman/lists/email-team/
    config.pck.tmp.mailman.Stanford.EDU.13810
    Feb 09 09:50:38 2006 (13813) Failed before cPickle:

    The more I look at this, the more it looks like a 'debugging' entry
    that someone may have added in the definition of __save() in your
    version of Mailman/MailList.py. Even if that is the case, that still
    leaves the questions "what is the exact circumstance the causes it?"
    and "who put it there and why?".
    Ah, the culprit is me. I put a line of debugging in the "try:" block
    some months ago when I added Stanford Webauth code to mailman.
    That line of debugging was called every time when __save is called. It
    appears useless now, but I could not remember why I put it there in
    first place.

    I removed that line, all look good. I felt better.

    Thanks a lot!

    Susan
    --

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedFeb 9, '06 at 5:58p
activeFeb 16, '06 at 6:22a
posts4
users2
websitelist.org

2 users in discussion

Xueshan Feng: 2 posts Mark Sapiro: 2 posts

People

Translate

site design / logo © 2022 Grokbase