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.

Exim Troubles

Discussion in 'General Discussion' started by madcow774, Aug 9, 2004.

  1. madcow774

    madcow774 Member

    Joined:
    Oct 23, 2002
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Hoping someone can help me out. running WHM 9.4.0 cPanel 9.4.1-C72 FreeBSD 4.9-RELEASE - WHM X v3.1.0
    I had a problem with exim not starting yesterday. I found the solution to my problem in this thread

    Now I am getting exim failure messages in my mailbox every 8-10 minutes. However, exim seems to be running? It shows up in the running processes list & mail seems to be working OK. If I restart exim, it starts OK, but the messages start coming again about 15 mins later & exim shows up as 'failed' in the Service Status area in WHM. Has been showing as failed since yesterday, so it's not that I am not waiting long enough for the service status page to refresh. But like I said, exim seems to be running.

    I looked in the exim mainlog & it is loaded with the following message:
    2004-08-09 14:32:13 socket bind() to port 465 for address (any IPv6) failed: Address already in use: daemon abandoned
    2004-08-09 14:40:35 socket bind() to port 465 for address (any IPv6) failed: Address already in use: daemon abandoned
    2004-08-09 14:48:56 socket bind() to port 465 for address (any IPv6) failed: Address already in use: daemon abandoned
    2004-08-09 14:57:17 socket bind() to port 465 for address (any IPv6) failed: Address already in use: daemon abandoned
    2004-08-09 15:05:42 socket bind() to port 465 for address (any IPv6) failed: Address already in use: daemon abandoned
    2004-08-09 14:23:53 socket bind() to port 465 for address (any IPv6) failed: Address already in use: daemon abandoned

    I found a reference to this message in another thread, where it was suggested i run:
    netstat -lpn | grep 465
    Then kill any processes on that port. But running that command results in this message:
    netstat: n: unknown or uninstrumented protocol

    Any help would be much appreciated. Thanks.
     
    #1 madcow774, Aug 9, 2004
    Last edited: Aug 9, 2004
  2. thelinophile

    thelinophile Registered

    Joined:
    Aug 7, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Check it

    Hello,
    THis happens when socket executes the bind() call to bind the specific port for specific daemon ...but the port which it trying to bind is already in use..
    try this :
    /etc/init.d/exim status
    /etc/init.d/spamd status

    And post it here so let me check it !!
     
  3. madcow774

    madcow774 Member

    Joined:
    Oct 23, 2002
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    I'm running BSD. So that command does not work.

    mcn07# /etc/init.d/exim status
    /etc/init.d/exim: Command not found.
     
  4. thelinophile

    thelinophile Registered

    Joined:
    Aug 7, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Oh !! I forgot that!!

    Hello,
    I ignored that u were on bsd...
    So do the same:
    /etc/init.d/exim start
    /etc/init.d/spamd start
    I just want to check if both are locked or only exim is locked ...
    What it show?
     
  5. madcow774

    madcow774 Member

    Joined:
    Oct 23, 2002
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    OK, forgive the stupidity on my part. BSD is new to me.

    The command you posted does not work, but I ran:
    mcn07# /etc/rc.d/init.d/exim start

    & I get:
    exim exim.: Can't open /etc/rc.d/init.d/functions: No such file or directory
    Could not create INET socket: Address already in use IO::Socket::INET: Address already in use


    BTW, really appreciate you helping me out...
     
  6. madcow774

    madcow774 Member

    Joined:
    Oct 23, 2002
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    I opened a ticket with Cpanel & they fixed my problem. :)
    I figured I would post what they wrote me in case someone else with the same problem runs across this post. So here goes:

    -----------------------------------------
    Try running
    "/scripts/installcpbsdpkg"
    "cd /usr/local/cpanel/bsdconf/exim"
    "sh install"
    This usually corrects issues with exim on FreeBSD such as this.

    As for the netstat command, try "sockstat -4 | grep 465" instead of the (linux) netstat command in the future.
    -----------------------------------------
     
Loading...

Share This Page