Community Discussions and Support
Server drive suddenly filling up

I only have logging on as I was trying to find out why certain emails were not being received.

Now that's sorted logging will be turned off.

<p>I only have logging on as I was trying to find out why certain emails were not being received.</p><p>Now that's sorted logging will be turned off. </p>

Have Mercury/32 running on a Windows Server 2002 Service Pack 2; been working for a couple of years no issues.

 Suddenly today, drive space has been filling up to the point of having  1GB left.

 Log files look ok, but there are hundreds of TCxxxx.MS files, from 8000KB to 45,000 KB in size.  Any ideas? 

 

<P>Have Mercury/32 running on a Windows Server 2002 Service Pack 2; been working for a couple of years no issues.</P> <P> Suddenly today, drive space has been filling up to the point of having  1GB left.</P> <P> Log files look ok, but there are hundreds of TCxxxx.MS files, from 8000KB to 45,000 KB in size.  Any ideas?  </P> <P mce_keep="true"> </P>

I haven't changed anything, I don't even know where to enable it.

I haven't changed anything, I don't even know where to enable it.

Configuration -> MercuryS -> General Tab - Logging

May be worth checking the other modules. 

<p>Configuration -> MercuryS -> General Tab - Logging</p><p>May be worth checking the other modules. </p>

Loggin 'ON' but it is only 20kb,  but there are hundreds of the TCPxxxx.MS files just for today

Loggin 'ON' but it is only 20kb,  but there are hundreds of the TCPxxxx.MS files just for today

I have session logging enabled for MercuryS..
Currently there are over 10,000 files equalling about 200MB

All the files are named TCP****.MS

I'm not sure if other modules create similar named files. 

<p>I have session logging enabled for MercuryS.. Currently there are over 10,000 files equalling about 200MB</p><p>All the files are named TCP****.MS</p><p>I'm not sure if other modules create similar named files. </p>

Turn off session logging and delete the TCP*.MS files.  Session logging is creating a complete record of every mail message passing through MercuryS and it can fill up the disk space in a hurry.  Session logging should only be turned on when troubleshooting your system.

 

<p>Turn off session logging and delete the TCP*.MS files.  Session logging is creating a complete record of every mail message passing through MercuryS and it can fill up the disk space in a hurry.  Session logging should only be turned on when troubleshooting your system.</p><p> </p>

Will do...thanks.  Guess I better find a manual, this was passed on by the previous admin who said, "Just check it every week or so..."

Will do...thanks.  Guess I better find a manual, this was passed on by the previous admin who said, "Just check it every week or so..."

[quote user="tomt"]

I have session logging enabled for MercuryS..
Currently there are over 10,000 files equalling about 200MB

All the files are named TCP****.MS

I'm not sure if other modules create similar named files. 

[/quote]

Excerpt from the Mercury help file:

Session logging is supported by MercuryS, MercuryP, MercuryH, MercuryC, MercuryE, MercuryI, and MercuryD. When session logging is turned on in a module, it will create one file per connection in a directory you specify. The file will contain a complete transcript of the data sent between the module and the remote machine to which it is connected. Session logging files are given numerically ascending filenames in the general form TCPxxxx.yy, where xxxx is a serial number and yy is an extension representing the module that created the log file. The extensions generated by the various modules are as follows:

TCP*.MS  Generated by the SMTP server, MercuryS
TCP*.MC  Generated by the SMTP client, MercuryC
TCP*.ME  Generated by the full delivery SMTP client, MercuryE
TCP*.MH  Generated by the PH server, MercuryH
TCP*.MP  Generated by the POP3 server, MercuryP
TCP*.MD  Generated by the POP3 client, MercuryD
TCP*.MI   Generated by the IMAP4 server, MercuryI


Sven

[quote user="tomt"]<P>I have session logging enabled for MercuryS.. Currently there are over 10,000 files equalling about 200MB</P><P>All the files are named TCP****.MS</P><P>I'm not sure if other modules create similar named files. </P>[/quote] Excerpt from the Mercury help file: Session logging is supported by MercuryS, MercuryP, MercuryH, MercuryC, MercuryE, MercuryI, and MercuryD. When session logging is turned on in a module, it will create one file per connection in a directory you specify. The file will contain a complete transcript of the data sent between the module and the remote machine to which it is connected. Session logging files are given numerically ascending filenames in the general form TCPxxxx.yy, where xxxx is a serial number and yy is an extension representing the module that created the log file. The extensions generated by the various modules are as follows: TCP*.MS  Generated by the SMTP server, MercuryS TCP*.MC  Generated by the SMTP client, MercuryC TCP*.ME  Generated by the full delivery SMTP client, MercuryE TCP*.MH  Generated by the PH server, MercuryH TCP*.MP  Generated by the POP3 server, MercuryP TCP*.MD  Generated by the POP3 client, MercuryD TCP*.MI   Generated by the IMAP4 server, MercuryI Sven
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 ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft