Whats up with exim logs

BigWil

BigWil

Verified User
Joined
Aug 5, 2004
Messages
296
It looks like the exim install is writing to exim_mainlog but the DA install when trying to use the Log Viewer is looking for mainlog and not exim_mainlog.

Does anyone know how to correct this properly?

The mainlog, paniclog and rejectlog log files don't even exist so when trying to view the logs in DA all I get is "Unable to read log".


Big Wil
 
my logs are mainlog etc...

you could simply make a symlink to the other named files however.

what os/version of da/version of exim?
 
I tried the symlink first. However syslog is rotating the link with it thus the mainlog link becomes obsolete. Also because there is a mainlog it gets rotated also creating a real mess of things.

DA 1.23.3
Exim 4.42

I just commented out the newsyslog.conf entry for the mainlog, paniclog, and rejectlog. Maybe that was the problem that was making the mess.

Big Wil
 
Last edited:
heya, first you need to update your exim as that version has major vulnerabilities. (1.44 you should be running)

second, there is a newer da version out as well.

there is probably somewhere you need to change where the loggin dir is, i'm sure the da src does this but not sure.

have you contacted support yet?
 
I believe you mean upgrade to 4.44? Because 1.44 would certainly not be an upgrade. ;-)

Yah I just saw the DA version update available today. That is coming this evening. Would be nice to know if a build all will upgrade exim as well. I guess I will know in just a few hours.

Big Wil
 
sorry, 4.44 :)

no a build all will not do that, check the version updates forum there is an exim 4.44 thread there.
 
I looked for it I really did. Never saw that thread.

What I have already done is I created symlinks pointing to the true locations and turned off the rotation for the maillog, paniclog and rejectlog. It all seems to work fine now and the symlinks always point to the latest log file. Works great unless you know of some reason this shouldn't be done.

-rw------- 1 mail mail 606 Feb 7 00:20 exim_mainlog
-rw------- 1 mail mail 7924 Feb 7 00:00 exim_mainlog.0
-rw------- 1 mail mail 61 Feb 7 00:00 exim_paniclog
-rw------- 1 mail mail 238 Feb 7 00:00 exim_paniclog.0
-rw------- 1 mail mail 61 Feb 7 00:00 exim_rejectlog
-rw------- 1 mail mail 121 Feb 7 00:00 exim_rejectlog.0
lrwxr-xr-x 1 root mail 12 Feb 4 15:01 mainlog -> exim_mainlog
lrwxr-xr-x 1 root mail 13 Feb 4 15:01 paniclog -> exim_paniclog
lrwxr-xr-x 1 root mail 14 Feb 4 15:01 rejectlog -> exim_rejectlog

Big Wil
 
Last edited:
Will logrotation break the symlinks? If not, then there's no need to disable it. Thats the only drawback I can think of, of using symlinks instead of changing the logfile locations in DirectAdmin.
 
The symlinks were following the original log file and breaking the symlinks. Plus leaving a useless mainlog behind. Total chaos.

Since mainlog, rejectlog, paniclog didn't exist then having the rotation entries were pretty useless anyways. By turning them off now my symlinks point to the latest exim_mainlog, exim_rejectlog, and exim_paniclog the way they are supposed to.

Big Wil
 
You must log in or register to reply here.
Back
Top