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-26 failed

Discussion in 'General Discussion' started by hostseeker, Dec 17, 2002.

  1. hostseeker

    hostseeker Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    6
    This morning I manually upgraded via the link in WHM to the latest stable cpanel release (101).

    I have been running exim on port 26 via the &service manager& link for several months with no problems.

    After the upgrade exim on port 26 failed and I can't get it back up after restarting exim several times.

    The &service status& still shows exim-26 as failed.

    Any ideas?
     
  2. promak

    promak Well-Known Member

    Joined:
    Oct 6, 2001
    Messages:
    248
    Likes Received:
    0
    Trophy Points:
    16
    Yes this is a problem but now fix
    whm & upgrade to new cpanel then it will fix
     
  3. hostseeker

    hostseeker Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    6
    [quote:f3eed46a68][i:f3eed46a68]Originally posted by promak[/i:f3eed46a68]

    Yes this is a problem but now fix
    whm & upgrade to new cpanel then it will fix[/quote:f3eed46a68]

    Release 101 is the latest stable release for Linux and that's what I upgraded to this morning that caused the problem.

    See the release page at:
    http://layer2.cpanel.net/
     
  4. kensmith

    kensmith Member

    Joined:
    Dec 13, 2002
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    This is my first post, and I'm pretty new at WHM/Cpanel, so excuse any obvious errors. :)

    I had this problem also. After getting Cpanel 5.3.0-S101,
    only one instance of exim was running. I 'fixed' it by going to Service Manager, unchecking the 'exim on another port' option, saving it, then rechecking the option and saving it.

    I'm guessing that the restarting chksrvd would have done the same thing, but then I would have had to figure out how to do that.

    Hope this helps, -Ken-
     
  5. kensmith

    kensmith Member

    Joined:
    Dec 13, 2002
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    This is my first post, and I'm pretty new at WHM/Cpanel, so excuse any obvious errors. :)

    I had this problem also. After getting Cpanel 5.3.0-S101,
    only one instance of exim was running. I 'fixed' it by going to Service Manager, unchecking the 'exim on another port' option, saving it, then rechecking the option and saving it.

    I'm guessing that the restarting chksrvd would have done the same thing, but then I would have had to figure out how to do that.

    Hope this helps, -Ken-
     
  6. hostseeker

    hostseeker Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    85
    Likes Received:
    0
    Trophy Points:
    6
    Well I rebooted the server the &exim-26& is not even listed on the &service status& page anymore!

    So I don't know if it is just not working, or if it is not an option anymore or if Cpanel developers just decided not to show it's status.

    Go figure.
     
  7. JustinK

    JustinK Well-Known Member

    Joined:
    Sep 4, 2001
    Messages:
    251
    Likes Received:
    0
    Trophy Points:
    16
    We found out that it doesn't seem to restart itself properly when exim is restarted awhile back. You should be able to go into the service manager and just re-submit the info without having to uncheck, submit, check, submit to get it back up.
     
  8. kensmith

    kensmith Member

    Joined:
    Dec 13, 2002
    Messages:
    18
    Likes Received:
    0
    Trophy Points:
    1
    You are correct, JustinK. Just clicking save on the Service Manager page will restart it correctly. On the other hand, restarting exim under 'Restart Services' kills both copies, and only restarts the one on port 25.

    And of course, each automatic Cpanel update causes this problem to pop up, because it restarts exim afterwards.

    Should this be submitted somewhere as a bug report?
     
Loading...

Share This Page