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.

spamd failed

Discussion in 'General Discussion' started by billdagou, Apr 14, 2008.

  1. billdagou

    billdagou Member

    Joined:
    Apr 7, 2008
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    I always get the spamd failure warning every 10 minutes.

    I ran /scripts/installspam, and configured SpamAssassin in Exim Configuration Editor. And also, I enabled it in Tweak Settings. But seems all above doesn't work.

    When running /etc/init.d/exim restart, I always get the following error message.
    Shutting down exim: [ OK ]
    Shutting down antirelayd: [ OK ]
    Shutting down spamd: [FAILED]
    Starting exim: [ OK ]
    Starting exim-smtps: [ OK ]
    Starting antirelayd: [ OK ]

    Can someone help? Any advice would be appreciated.
     
  2. MBHWizards

    MBHWizards Registered

    Joined:
    Aug 23, 2007
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    I Second That Commotion

    No response ehh ....

    I also have the same issue running CENTOS 5 WHM 11.15.0 cPanel 11.18.3-C23466. This failure has been going on for about a week. A temporay solution had been to upgrade to EDGE. However, no one likes to remain on the EDGE too long.

    NOTE: Last week when this issue began both spamd and antirelayd were failing. Today after upgrading (downgrading) to Current only spamd has failed ..

    Anything ??? Anyone ??? HELO!
     
  3. pglock

    pglock Member

    Joined:
    Jun 14, 2007
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    UK
    It doesn't help, but...

    I'm seeing the same behaviour. clamd and spamd are repeatedly failing....
     
  4. steve-sydney

    steve-sydney Registered

    Joined:
    Mar 31, 2006
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Ive got the same thing, im getting told its because my loopback is set to 127.0.0.2
     
  5. MBHWizards

    MBHWizards Registered

    Joined:
    Aug 23, 2007
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Still No REAL resolution ...

    I opened a trouble ticket and Jesse has been working on it for the past several days. He rebuilt exim and updated to Release. That worked for exactly two days. Then after last night's update the problem resurfaced. This time he re-installed some perl mods and that appeared to correct spamd. However now tailwatchd is failing ..

    tailwatchd failed @ Tue Apr 22 02:05:57 2008. A restart was attempted automagically.
    tailwatchd failed @ Tue Apr 22 02:14:22 2008. A restart was attempted automagically.
    tailwatchd failed @ Tue Apr 22 02:22:48 2008. A restart was attempted automagically.
    tailwatchd failed @ Tue Apr 22 02:31:13 2008. A restart was attempted automagically.

    Has ANY body come up with a solutin to this annoying issue?
     
  6. Henrik

    Henrik Member

    Joined:
    Feb 1, 2008
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Sweden
    Hello,



    I am only having problems with antirelayd.

    Code:
    /etc/init.d/exim restart
    Shutting down clamd:                                       [  OK  ]
    Shutting down exim:                                        [  OK  ]
    Shutting down antirelayd:                                  [FAILED]
    Shutting down spamd:                                       [  OK  ]
    Starting clamd:                                            [  OK  ]
    Starting exim:                                             [  OK  ]
    Starting exim-smtps:                                       [  OK  ]
    Starting antirelayd:                                       [  OK  ]
    
    Everything comes up and is shown inside service-status in WHM. With antirelayd, this value isn't even visible within WHM's service status page.

    "ps aux |grep anti" gives out nothing.

    I am running WHM 11.20.0 cPanel 11.22.2-C23870, and the tree is CURRENT. (CENTOS Enterprise 5 i686 on standard - WHM X v3.1.0)


    What to do here?
     
  7. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Antirelayd is handled by the Tailwatch daemon, hence grepping for anti in the process table won't output anything:

    Code:
    root@mundane [~]# ps ax | grep -i anti
    29226 pts/0    R+     0:00 grep -i anti
    root@mundane [~]# ps ax | grep -i tail
     9288 ?        Ss     0:00 tailwatchd
    29228 pts/0    S+     0:00 grep -i tail
    
    However:
    Code:
    root@mundane [~]# /usr/local/cpanel/libexec/tailwatchd --status
    tailwatchd is enabled
    Running, PID 9288
      Driver (Active: 0) Cpanel::TailWatch::Antirelayd
      Driver (Active: 1) Cpanel::TailWatch::cPBandwd
      Driver (Active: 1) Cpanel::TailWatch::Eximstats
    
    That means on this machine, Antirelayd is disabled. THis can be changed by using the Service Manager within WHM. We will look into making the status information available within Service Status, or another relevant page in WHM.

    For MBHWizards and others who have opened tickets with us, what is your ticket number?
     
  8. MBHWizards

    MBHWizards Registered

    Joined:
    Aug 23, 2007
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    This appears to have resolved the issues ... for now

    We've updated this box to:
    WHM 11.15.0 cPanel 11.18.4-C23809
    CENTOS Enterprise 5 i686 on standard - WHM X v3.1.0

    And this is the trouble ticket response and solution steps:


    Subject: Re: [cPanel tickets ID# 246640] Waiting for your response

    Hello,

    For the tailwatchd, it is not in the latest Current, so I had to remove the tailwatchd file from /etc/chkservd.d directory to stop the checks for it.

    As for spamassassin, it is several things. One was due to 2 lines entry in /etc/mail/spamassassin/local.cf which is causing issues. Secondly, it was looking for some perl modules which did not exist, so I had to do complete uninstall of spamassassin from perl and then do fresh install to replace it.

    Once that was done, I observed there is no errors being generated in the logs for spamassassin.
    --
    Russell Rademacher
    cPanel
    Technical Analyst 2​
     
    #8 MBHWizards, May 1, 2008
    Last edited: May 1, 2008
  9. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Correct, at time of writing, which was April 25, according to the ticket. Tailwatch has since entered Current, but not Release or Stable. We'll double check the latest Stable and Release builds to determine whether problems still exist with clamd and antirelayd.
     
  10. Henrik

    Henrik Member

    Joined:
    Feb 1, 2008
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Sweden
    Hello Kenneth,


    I went inside the service manager inside WHM, however I can not see "Antirelayd" inside of there. It is as a driver with tailwatchd, but not as a stand-alone service.

    Is it "enabled" when the driver inside tailwatchd is enabled?
     
  11. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    That is correct. Once the driver for tailwatchd is enabled, Antirelayd is enabled.
     
  12. Henrik

    Henrik Member

    Joined:
    Feb 1, 2008
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Sweden
    Cheers for replying here and in the support-ticket, Kenneth! :)
     
  13. d_t

    d_t Well-Known Member

    Joined:
    Sep 20, 2003
    Messages:
    243
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Bucharest
    The error message received by Henrik still appear.
    I think you should update /etc/init.d/exim (and remove antirelayd)

    Question: where can I restart tailwatchd because it does not appear in init.d ?
     
  14. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,461
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    /usr/local/cpanel/libexec/tailwatchd


    Execute the above with the --help flag to see the options available.
     
Loading...

Share This Page