Community Discussions and Support
Cannot turn off session logging

> Since  yesterday I have actually (for whatever reason) managed to
> turn it off when I restarted the server once again. Nonetheless, I
> still have a problem. When I turn session logging on (because I need
> more information than I can find in the normal logs), the session
> log file immediately has some 40 MB and starts in May 2009. Do you
> know the reason for that?

Huh?  Are  you saying there is a 40 MByte *.MS created immediately when this is checked without anything going through MercuryS??

 Was the directory empty before you started session logging.

 

<p>> Since  yesterday I have actually (for whatever reason) managed to > turn it off when I restarted the server once again. Nonetheless, I > still have a problem. When I turn session logging on (because I need > more information than I can find in the normal logs), the session > log file immediately has some 40 MB and starts in May 2009. Do you > know the reason for that? Huh?  Are  you saying there is a 40 MByte *.MS created immediately when this is checked without anything going through MercuryS??</p><p> Was the directory empty before you started session logging.</p><p> </p>

Hi everybody,

I recently noticed that I apparently had left the session logging for my mercury32 STMP system on, and that it was writing huge (up to 500MB) session logs.  I decided to turn it off and disabled session logging both for MERCURYS and MERCURYE. Since then, no new files are being created in the c:\MERCURY\SESSION\MERCURYE directory, but the server continues to create huge log files in c:\MERCURY\SESSION\MERCURYS. I've restarted the mercury task and the whole machine, but it keeps on logging.

Can anybody help with that?

Cheers,
Stefan. 

<p>Hi everybody,</p><p>I recently noticed that I apparently had left the session logging for my mercury32 STMP system on, and that it was writing huge (up to 500MB) session logs.  I decided to turn it off and disabled session logging both for MERCURYS and MERCURYE. Since then, no new files are being created in the c:\MERCURY\SESSION\MERCURYE directory, but the server continues to create huge log files in c:\MERCURY\SESSION\MERCURYS. I've restarted the mercury task and the whole machine, but it keeps on logging.</p><p>Can anybody help with that?</p><p>Cheers, Stefan. </p>

> I recently noticed that I apparently had left the session logging for my mercury32 STMP system on, and that it was writing huge (up to
> 500MB) session logs.  I decided to turn it off and disabled session logging both for MERCURYS and MERCURYE. Since then, no new files are
> being created in the c:\MERCURY\SESSION\MERCURYE directory, but the server continues to create huge log files in
> c:\MERCURY\SESSION\MERCURYS. I've restarted the mercury task and the whole machine, but it keeps on logging.

This is probably the MercuryS log.  Have you tried making a daily, weekly or monthly log?  You can then delete the old logs when you no longer need them.


General logging is supported by MercuryS (the SMTP server), MercuryP (the POP3 server), MercuryC (the SMTP relay client), MercuryE (the full-delivery SMTP client), MercuryI (the IMAP4 server) and MercuryH (the PH Directory Services server). Each of these modules can be given a filename for a general log file: they will create this file as required and will write a single-line record describing each connection they process. Each module's general log file has a regular format that can be parsed by software tools to generate statistics and reporting. To turn general logging off, enter a blank filename. You can change the name of the general log file any time you wish in order to start a new log file. You must not attempt to use the same filename for the logging output of two different modules - this will result in improper behaviour and may result in Mercury crashing.

Special naming options for log files:  Mercury allows you to use certain special characters in the names you give for log files: these special characters are replaced by Mercury each time it needs to open the log file, allowing you to "build" a filename based on the time and date. This is particularly useful for making log files "roll over" periodically. The special characters you can use in log file names are:

    ~Y    The year, expressed as 2 digits
    ~M    The month, expressed as 2 digits

~D    The day of the month (1..31), expressed as 2 digits
    ~W    The week of the year, starting from 0.

Example: to create a logfile for each week of the year, you might enter a path like this:

    C:\MERCURY\LOGS\MERC~Y~W.LOG




> I recently noticed that I apparently had left the session logging for my mercury32 STMP system on, and that it was writing huge (up to > 500MB) session logs.  I decided to turn it off and disabled session logging both for MERCURYS and MERCURYE. Since then, no new files are > being created in the c:\MERCURY\SESSION\MERCURYE directory, but the server continues to create huge log files in > c:\MERCURY\SESSION\MERCURYS. I've restarted the mercury task and the whole machine, but it keeps on logging. This is probably the MercuryS log.  Have you tried making a daily, weekly or monthly log?  You can then delete the old logs when you no longer need them. General logging is supported by MercuryS (the SMTP server), MercuryP (the POP3 server), MercuryC (the SMTP relay client), MercuryE (the full-delivery SMTP client), MercuryI (the IMAP4 server) and MercuryH (the PH Directory Services server). Each of these modules can be given a filename for a general log file: they will create this file as required and will write a single-line record describing each connection they process. Each module's general log file has a regular format that can be parsed by software tools to generate statistics and reporting. To turn general logging off, enter a blank filename. You can change the name of the general log file any time you wish in order to start a new log file. You must not attempt to use the same filename for the logging output of two different modules - this will result in improper behaviour and may result in Mercury crashing. Special naming options for log files:  Mercury allows you to use certain special characters in the names you give for log files: these special characters are replaced by Mercury each time it needs to open the log file, allowing you to "build" a filename based on the time and date. This is particularly useful for making log files "roll over" periodically. The special characters you can use in log file names are:     ~Y    The year, expressed as 2 digits     ~M    The month, expressed as 2 digits ~D    The day of the month (1..31), expressed as 2 digits     ~W    The week of the year, starting from 0. Example: to create a logfile for each week of the year, you might enter a path like this:     C:\MERCURY\LOGS\MERC~Y~W.LOG

Hi Thomas!

Thanks for your help, yet it is really not the normal logging feature I'm talking about, but the session logging. The option for session logging (i.e. very detailed logging including data) can be found under Configuration-Mercury S SMTP Server, where there is a checkbox to turn it on.

Since  yesterday I have actually (for whatever reason) managed to turn it off when I restarted the server once again. Nonetheless, I still have a problem. When I turn session logging on (because I need more information than I can find in the normal logs), the session log file immediately has some 40 MB and starts in May 2009. Do you know the reason for that?

Cheers,
Stefan. 

<p>Hi Thomas!</p><p>Thanks for your help, yet it is really not the normal logging feature I'm talking about, but the session logging. The option for session logging (i.e. very detailed logging including data) can be found under Configuration-Mercury S SMTP Server, where there is a checkbox to turn it on.</p><p>Since  yesterday I have actually (for whatever reason) managed to turn it off when I restarted the server once again. Nonetheless, I still have a problem. When I turn session logging on (because I need more information than I can find in the normal logs), the session log file immediately has some 40 MB and starts in May 2009. Do you know the reason for that?</p><p>Cheers, Stefan. </p>

Did you delete the old logs before restarting Mercury?

I recall that they were still around after a restart unless you removed them by hand.

 

<P>Did you delete the old logs before restarting Mercury?</P> <P>I recall that they were still around after a restart unless you removed them by hand.</P> <P mce_keep="true"> </P>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft