The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Cron Daemon email from Mailman after upgrade, IOError: [Errno 20] Not a directory

Discussion in 'E-mail Discussions' started by Bdzzld, Nov 9, 2010.

  1. Bdzzld

    Bdzzld Well-Known Member

    Joined:
    Apr 3, 2004
    Messages:
    363
    Likes Received:
    2
    Trophy Points:
    168
    Hi,

    After this night's upgrade to cPanel 11.28 I keep on receiving the following message every hour on one of the servers :

    Code:
    From: root@servername.domainname.xx (Cron Daemon)
To: postmaster@servername.domainname.xx
Subject: Cron <mailman@servername> /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests 


Traceback (most recent call last):
  File "/usr/local/cpanel/3rdparty/mailman/cron/senddigests", line 106, in ?
    main()
  File "/usr/local/cpanel/3rdparty/mailman/cron/senddigests", line 84, in main
    mlist = MailList.MailList(listname, lock=0)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 130, in __init__
    self.Load()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 689, in Load
    self.CheckVersion(dict)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 731, in CheckVersion
    self.InitVars()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 421, in InitVars
    baseclass.InitVars(self)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/Archiver/Archiver.py", line 112, in InitVars
    fp = open(indexfile)
IOError: [Errno 20] Not a directory: '/usr/local/cpanel/3rdparty/mailman/archives/private/newsletter_userdomain.com/index.html'
    Mailman is not running and has not been running on any of our servers, including this one.

    Any one know how to solve this?

    Thanks.
     
    #1 Bdzzld, Nov 9, 2010
  2. cPanelJared

    cPanelJared Technical Analyst
    Staff Member

    Joined:
    Feb 25, 2010
    Messages:
    1,841
    Likes Received:
    19
    Trophy Points:
    143
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    This is the output of a cron job. The cron jobs related to Mailman are stored in /var/spool/cron/mailman:

    Code:
    # cat /var/spool/cron/mailman 
MAILTO=postmaster
# At 8AM every day, mail reminders to admins as to pending requests.
# They are less likely to ignore these reminders if they're mailed
# early in the morning, but of course, this is local time... ;)
0 8 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/checkdbs
#
# At 9AM, send notifications to disabled members that are due to be
# reminded to re-enable their accounts.
0 9 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/disabled
#
# Noon, mail digests for lists that do periodic as well as threshhold delivery.
0 12 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/senddigests
#
# 5 AM on the first of each month, mail out password reminders.
0 5 1 * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/mailpasswds
#
# Every 5 mins, try to gate news to mail.  You can comment this one out
# if you don't want to allow gating, or don't have any going on right now,
# or want to exclusively use a callback strategy instead of polling.
#0,5,10,15,20,25,30,35,40,45,50,55 * * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/gate_news
#
# At 3:27am every night, regenerate the gzip'd archive file.  Only
# turn this on if the internal archiver is used and
# GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py
27 3 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/nightly_gzip
#
# At 4:30AM daily, cull old entries from the 'bad' and 'shunt' queues.
30 4 * * * /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/cull_bad_shunt
    You can either edit the cron job and save the changes, after which cron will automatically detect the changes:

    Code:
    # crontab -e -u mailman
    Or you can move the /var/spool/cron/mailman file to another location, and restart cron:

    Code:
    # mv /var/spool/cron/mailman /root
# /etc/rc.d/init.d/crond restart
     
    #2 cPanelJared, Nov 9, 2010
  3. morefood2001

    morefood2001 Active Member

    Joined:
    Mar 18, 2008
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    51
    I'm not getting them hourly, but I've also noticed the same problem. It seems like something happened to mailman. I submitted a ticket (1011946) and they're looking into it.
     
    #3 morefood2001, Nov 9, 2010
  4. handsonhosting

    handsonhosting Well-Known Member

    Joined:
    Feb 17, 2002
    Messages:
    151
    Likes Received:
    0
    Trophy Points:
    316
    Location:
    Omaha, NE
    cPanel Access Level:
    Root Administrator
    Had the same issue happen here for us on a number of newly updated servers :(

    Keep us posted on what you find out.
     
    #4 handsonhosting, Nov 10, 2010
  5. Bdzzld

    Bdzzld Well-Known Member

    Joined:
    Apr 3, 2004
    Messages:
    363
    Likes Received:
    2
    Trophy Points:
    168
    Hi morefood2001 & handsonhosting,

    (Sort of) Glad to hear the issue is not only happening on our server.
    Did you also have Mailman disabled on those servers as well?

    Thanks.
     
    #5 Bdzzld, Nov 10, 2010
  6. Bdzzld

    Bdzzld Well-Known Member

    Joined:
    Apr 3, 2004
    Messages:
    363
    Likes Received:
    2
    Trophy Points:
    168
    Update:
    Tonight the servers were updated to the newest Release version of cPanel and afterwards we've received a similar e-mail from the following crons :

    • /usr/local/cpanel/3rdparty/mailman/cron/checkdbs
    • /usr/local/cpanel/3rdparty/mailman/cron/disabled

    I've added a "#"-sign to all rules in the Mailman cronjob as it's not used any way. Can I assume that's safe?

    Thanks.
     
    #6 Bdzzld, Nov 10, 2010
  7. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    15,450
    Likes Received:
    285
    Trophy Points:
    433
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    As mentioned above, you can move the entire cron file out of it's location if you like.
     
    #7 Infopro, Nov 10, 2010
  8. morefood2001

    morefood2001 Active Member

    Joined:
    Mar 18, 2008
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    51
    The files for mailman were updated and became corrupted during the update in my case. CPanel's staff removed the corrupted information and re-created the directories and the problems went away.
     
    #8 morefood2001, Nov 10, 2010
  9. Bdzzld

    Bdzzld Well-Known Member

    Joined:
    Apr 3, 2004
    Messages:
    363
    Likes Received:
    2
    Trophy Points:
    168
    Original cronjob overwrites own cronjob!

    This morning (CET) we received the same e-mail again :
    Code:
    From: root@servername.serverdomain.xxx (Cron Daemon)
To: postmaster@servername.serverdomain.xxx
Subject: Cron <mailman@servername> /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/checkdbs 


Traceback (most recent call last):
  File "/usr/local/cpanel/3rdparty/mailman/cron/checkdbs", line 203, in ?
    main()
  File "/usr/local/cpanel/3rdparty/mailman/cron/checkdbs", line 86, in main
    mlist = MailList.MailList(name)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 128, in __init__
    self.Lock()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 165, in Lock
    self.Load()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 689, in Load
    self.CheckVersion(dict)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 731, in CheckVersion
    self.InitVars()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 421, in InitVars
    baseclass.InitVars(self)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/Archiver/Archiver.py", line 112, in InitVars
    fp = open(indexfile)
IOError: [Errno 20] Not a directory: '/usr/local/cpanel/3rdparty/mailman/archives/private/newsletter_userdom.XXX/index.html'
    Although all entries in the Mailman cronjob were edited two days ago by adding a preceeding "#" to each line, the original cronjob was back again.
    Very very annoying!! :mad:
     
    #9 Bdzzld, Nov 12, 2010
  10. Bdzzld

    Bdzzld Well-Known Member

    Joined:
    Apr 3, 2004
    Messages:
    363
    Likes Received:
    2
    Trophy Points:
    168
    And once again this morning :
    Code:
    From: root@servername.serverdomain.xxx (Cron Daemon)
To: postmaster@servername.serverdomain.xxx
Subject: Cron <mailman@servername> /usr/local/cpanel/3rdparty/bin/python -S /usr/local/cpanel/3rdparty/mailman/cron/checkdbs 


Traceback (most recent call last):
  File "/usr/local/cpanel/3rdparty/mailman/cron/checkdbs", line 203, in ?
    main()
  File "/usr/local/cpanel/3rdparty/mailman/cron/checkdbs", line 86, in main
    mlist = MailList.MailList(name)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 128, in __init__
    self.Lock()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 165, in Lock
    self.Load()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 689, in Load
    self.CheckVersion(dict)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 731, in CheckVersion
    self.InitVars()
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 421, in InitVars
    baseclass.InitVars(self)
  File "/usr/local/cpanel/3rdparty/mailman/Mailman/Archiver/Archiver.py", line 112, in InitVars
    fp = open(indexfile)
IOError: [Errno 20] Not a directory: '/usr/local/cpanel/3rdparty/mailman/archives/private/newsletter_userdomain.xxx/index.html'
    It appears each time the Release version is updated the Mailman cron gets overwritten and coughs up the same error message once again.
    This probably means the Mailman installation has been corrupted as well as with user morefood2001. Should I create a truoble ticket?
     
    #10 Bdzzld, Nov 13, 2010
  11. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    15,450
    Likes Received:
    285
    Trophy Points:
    433
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    You could, and link them to this thread.
     
    #11 Infopro, Nov 13, 2010
  12. PDW

    PDW Well-Known Member

    Joined:
    Dec 29, 2003
    Messages:
    119
    Likes Received:
    0
    Trophy Points:
    166
    Just recently we started getting an error from mailman for domains that have been removed from the server - so they arent there anymore. Any suggestions on how to clear up this error

    Code:
    Traceback (most recent call last):
 File "/usr/local/cpanel/3rdparty/mailman/cron/disabled", line 224, in ?
   main()
 File "/usr/local/cpanel/3rdparty/mailman/cron/disabled", line 150, in main
   mlist = MailList.MailList(listname)
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 128, in __init__
   self.Lock()
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 165, in Lock
   self.Load()
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 689, in Load
   self.CheckVersion(dict)
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 731, in CheckVersion
   self.InitVars()
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 421, in InitVars
   baseclass.InitVars(self)
 File "/usr/local/cpanel/3rdparty/mailman/Mailman/Archiver/Archiver.py", line 112, in InitVars
   fp = open(indexfile)
     
    #12 PDW, Dec 4, 2010
  13. bspiller

    bspiller Member

    Joined:
    Jun 4, 2008
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    51
    Location:
    Burnington, WI
    cPanel Access Level:
    Root Administrator
    BuMp, should we send in a support ticket. Would it be faster..
     
    #13 bspiller, Dec 6, 2010
  14. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    8
    Trophy Points:
    168
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    Please submit a support ticket so that we can directly inspect the issue and surrounding circumstances. I have not yet seen other reports of this issue at the present time; by submitting a ticket this will allow for a more thorough and in-depth direct investigation to properly diagnose and identify the problem.

    When available, please post your support ticket ID number. Thanks! :)
     
    #14 cPanelDon, Dec 6, 2010
  15. bspiller

    bspiller Member

    Joined:
    Jun 4, 2008
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    51
    Location:
    Burnington, WI
    cPanel Access Level:
    Root Administrator
    Thanks, I sent in a support ticket a few moments ago.
     
    #15 bspiller, Dec 6, 2010
  16. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    8
    Trophy Points:
    168
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    Friendly Moderator Note

    I have merged two related discussions into a single thread that I believe pertain to the same issue surrounding Mailman. I also revised the topic in attempt to more accurately describe the common symptom that has been reported.

    As always, the best method of receiving support for this issue is to submit a support request. If I am able to confirm specific details of a viable resolution I will share applicable steps or corrective measures in this thread.
     
    #16 cPanelDon, Dec 6, 2010
  17. cPanelDon

    cPanelDon cPanel Quality Assurance Analyst
    Staff Member

    Joined:
    Nov 5, 2008
    Messages:
    2,557
    Likes Received:
    8
    Trophy Points:
    168
    Location:
    Houston, Texas, U.S.A.
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    Thank you for the ticket submission; I confirm it is received. If anyone else experiences the same difficulty please submit a support request so that we can gather more details during investigation. Thank you! :)
     
    #17 cPanelDon, Dec 6, 2010
(You must log in or sign up to post here.)
Loading...
Similar Threads - Cron Daemon email
  1. Ender Bonnet

    Problems with cron daemon module

    Ender Bonnet, Oct 21, 2015, in forum: General Discussion
    Replies:
    1
    Views:
    356
    cPanelMichael
    Oct 22, 2015
  2. internetbug256

    some cPanel update added jailshell to my crontabs

    internetbug256, Jun 27, 2017 at 12:39 PM, in forum: General Discussion
    Replies:
    8
    Views:
    67
    cPanelMichael
    Jun 28, 2017 at 12:31 PM
  3. Axitech

    User cron jobs not being logged

    Axitech, Jun 21, 2017, in forum: General Discussion
    Replies:
    3
    Views:
    45
    cPanelMichael
    Jun 21, 2017
  4. vacancy

    Autossl renew check cron time

    vacancy, Jun 13, 2017, in forum: General Discussion
    Replies:
    1
    Views:
    50
    cPanelMichael
    Jun 13, 2017
  5. linux4me2

    SOLVED Cron Emails Are Treated As Spam By Gmail

    linux4me2, Jun 10, 2017, in forum: E-mail Discussions
    Replies:
    9
    Views:
    102
    linux4me2
    Jun 14, 2017

Share This Page