Cpanel / Exim update deleted /etc/exim.conf

[FreedomNet]

We are currently running WHM 9.9.0 cPanel 9.9.1-S50
RedHat Enterprise 3 i686 - WHM X v3.1.0
Looking at WHM this morning the left column is formatted differently so I am assuming cPanel was auto updated last night. The issue is Exim now fails, can not send or recieve messages on ANY domains. Restarting Exim produces:
Oct 11 09:51:04 freedom exim: 2004-10-11 09:51:04 non-existent configuration file(s): /etc/exim.conf
Oct 11 09:51:04 freedom exim: exim startup failed
We run a very vanilla system and have never updated or modified the /etc/exim.conf. Does anyone know how / why the Cpanel update deleted this file and will it be a problem if we restore a copy from before the cpanel update?
THANKS!

[chirpy]

No idea why it broke, but you should be able to fix it with:

/scripts/buildeximconf

If that doesn't fix it, you can resinstall Exim with:

/scripts/exim4

[anand]

hmm strange i had the same problem on one box of mine. exim.conf was removed. I had to reinstall exim and get the conf back. Don;t remember seeing anything like this earlier.

[FreedomNet]

No idea why it broke, but you should be able to fix it with:

/scripts/buildeximconf

If that doesn't fix it, you can resinstall Exim with:

/scripts/exim4

Johnathan, thanks for the help. /scripts/buildeximconf allowed me to get Exim back up (Exim restarts clean through WHM), but thre are 2 other issues now. One is you can not send email (all domains recieve "please enter user name and password prompt" when trying to send via Outlook) and and email sent from an outside domain is lost (no message back to sender and the email does not end up in mail queues). After sending some more form off host email server to the failing Exim server, I was able to see smessages in the mail queue like:
60P Received: from mailnull by freedom.freedomnetworking.net with local (Exim 4.34)
id 1CH3IM-0005Jp-26
for plymouth@theramp.net; Mon, 11 Oct 2004 11:45:10 -0500
041 X-Failed-Recipients: ddemark@comcast.net
031 Auto-Submitted: auto-generated
073F From: Mail Delivery System <Mailer-Daemon@freedom.freedomnetworking.net>
025T To: plymouth@theramp.net
059 Subject: Mail delivery failed: returning message to sender
062I Message-Id: <E1CH3IM-0005Jp-26@freedom.freedomnetworking.net>
038 Date: Mon, 11 Oct 2004 11:45:10 -0500

Here is from a different message in the mail queue:
unrouteable mail domain "comcast.net"
(this should be a vaild email address to send email to).

It looks like exim is rejecting all email being sent to it. Would you recommend reinstalling Exim and if so well this screw up all the domain settings (like autoresponders, passwords, etc.)
THANK AGAIN!

[chirpy]

It looks like it has trashed your /etc/localdomains files too.

Upgrading exim should work, as anand said.

One last alternative before trying would be to run:

/scripts/mailperm
/scripts/fixvaliases

[FreedomNet]

It looks like it has trashed your /etc/localdomains files too.

Upgrading exim should work, as anand said.

One last alternative before trying would be to run:

/scripts/mailperm
/scripts/fixvaliases

Johnathan, I ended up having run /scripts/exim4 and that fixed things - thanks a milllion.

Also, I notiched you provide cPanel and general admin services for dedicated linux servers. I'll look into that as well as it looks like something we might want to take advantage of also.

Thanks again for taking the time and trouble to help!!!

Don

[Elikster]

Greetings,

I posted about that problem like a week ago when they came out with 4.43-0 version for the servers. It just simply ate the exim.conf when it did the automatic update during the nightly upcp run.

Now it seems others have started seeing this as well.

[nacs]

Rebuilding exim with /scripts/exim4 fixed the problem for me too.

This latest cpanel update has been an absolute mess though. This wasn't the only problem that came up. :\

[cpanelnick]

Make sure none of your exim files are chattr +i

rpm -ql exim (to get a list)

This is the number one reason why exim installs fail

[justhost]

This solution ( /scripts/exim4 ) worked for me temporarily last night but now this morning it is all down again. I have run this scripts again but this time it doesnt fix the problem.....

Is anyone still having this trouble?

[anand]

Make sure none of your exim files are chattr +i

rpm -ql exim (to get a list)

This is the number one reason why exim installs fail

Nick, i don't use chattr on any files still i faced this problem, anyways after reinstalling exim things came back to normal.

[anand]

This solution ( /scripts/exim4 ) worked for me temporarily last night but now this morning it is all down again. I have run this scripts again but this time it doesnt fix the problem.....

Is anyone still having this trouble?

Do this

/scripts/reseteximtodefaults
/scripts/exim4 --latest

This will reset your exim.conf to default and force install exim again.

Tail your /var/log/exim_mainlog to see if you find any errors.

P.S. And make sure as Nick said no chattr on any of the files, otherwise things can fail.

[justhost]

Do this

/scripts/reseteximtodefaults
/scripts/exim4 --latest

This will reset your exim.conf to default and force install exim again.

Tail your /var/log/exim_mainlog to see if you find any errors.

P.S. And make sure as Nick said no chattr on any of the files, otherwise things can fail.

Thanks anand. Can you please explain "Tail".

Also how do you check to see if no chattr on all of the files?

[justhost]

Rebuilding exim with /scripts/exim4 fixed the problem for me too.

This latest cpanel update has been an absolute mess though. This wasn't the only problem that came up. :\

What other problems have you seen nacs?

[anand]

Thanks anand. Can you please explain "Tail".

Also how do you check to see if no chattr on all of the files?

To be on safer side do this

chattr -i /etc/exim.conf

As for tail:

tail -f /var/log/exim_mainlog

This will show you the exim log, see if you can find any errors. To break from tail, press Ctrl+C.

You can send mails after executing the commands i mentioned earlier and see if you find any errors.

It could be some custom modification in exim.conf which caused the problems to you.