scm-ui.2013-10-10.log file in temp folder keeps growing in size more than 30 GB

[Migration User]

scm-ui.2013-10-10.log file in temp folder keeps growing in size more than 30 GB.Why does it grow ?how to avoid this to prevent the disk space.it keeps growing and not able to delete the file .

Everytime i need to restart the server to get auto deleted of this file in temp folder.

Can anyone help me why this file is getting generated in temp folder?

 

 

[Migration User]

Hi,

What version of the SEPM do you have currently?  Do you have debug logging enabled? If so, that will explain why these log files are massive

http://www.symantec.com/docs/TECH102413

[Chetan Savade]

Hi,

Thank you for posting in Symantec community.

I would be glad to answer your query.

Limit the size of scm-ui.log and scm-ui.err. It's configurable in the conf.properties file. 

Test the logging for scm-ui.log and scm-ui.err. Default size is set to 500000000 bytes (~500MB). Configurable in conf.properties file: example: scm.console.log.logsize=100000 {for ~100K bytes}

Restart the SEPM services after making above suggested changes.

 

[Migration User]

SEPM version 12.1.3001.165

How to check the debug logging is enabled or not?

 

[Chetan Savade]

You will have to manually add those entry in the conf.properties file.

Location of conf.properties: C:\Program Files (x86) or installed drive\Symantec\Symantec Endpoint Protection Manager\tomcat\etc

[Migration User]

I found this on the path which yo have mentioned.

scm.shutdown.port=8765
scm.companysize=0
scm.console.log=true
scm.email.package.lifetime.days=45
scm.externallog.retrycount=30

 

This are the settings in the conf.properties file.

Suppose if i keep 500 MB, will it not generate log after 500 MB??

If suppose i change it to 5000000000 bytes what will be the impact?

but the log file is generated  in the c:\users\appdata\local\temp .

please advise.

 

[Chetan Savade]

Hi,

You can set the limit to grow the log size, contents on the file should be erased and the new logs will be written once it reached to defined limit.

After restarting SEPM service close the SEPM console as well.

After making changes monitor the status.

 

[Migration User]

Chetan,

 

What is the best practice???

 

And what  symantec recommeds??

[Migration User]

That tech article I linked shows you how to enable debug logging, change it to =WARNING

[Migration User]

Hi

Have you configured database maintainence

Regards

 

[Migration User]

Sorry i have no idea on this (DB maintenance.)

 

where to configure the DB maintenance in DB server or in SEPM server.

 

We use SQL 2008 R2 DB server.It is a dedicated DB server for SEPM.

 

We are not using the in-build Database.

 

[Chetan Savade]

Hi,

I believe default size is set to 500000000 bytes (~500MB) & it's hard coded in the background because I don't see any tab where you can configure these settings.

If you facing a problem you can configure it in conf.properties.

I would sugget to make it 550 or 600 MB and monitor the status.

 

[Chetan Savade]

Hi,

Is there any update on this issue?

[Migration User]

Hi Chetan,

 

That is kept under observation.So for there is no issue.

 

Thanks a lot .

 

Regards,

Ravishankar

[Chetan Savade]

Hi Ravishankar,

If issue reoccurred then need to upgrade to the latest release of SEP i.e. SEP 12.1 RU4.

According to SEP 12.1 RU4 fix notes, it's a known issue.

Log file size grows to be very large

Fix ID: 3162820

Symptom: Log messages continue to write to scm-ui.log, even after the user logs out of the console. As a result, the log file grows very large.

Solution: Limited the size of scm-ui.log and scm-ui.err, which are configurable in the conf.properties file. Modified the method of logging System.out, System.err and other console logging

 

Reference: New fixes and features in Symantec Endpoint Protection 12.1.4

 

http://www.symantec.com/docs/TECH211972

 

&

 

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.

[Chetan Savade]

Hi,

Is there any update?

OR

If issue has resolved, don't forget to mark your thread as 'SOLVED' with the answer that best helps you.

[Migration User]

Dear Chetan Cavade,

i'm facing this problem too, should i add scm.console.log.logsize=100000 (based on your advice above) to conf.properties manually ?

Where exactly should i put it on ?

is free to put anywhere or how ?

I used scm.server.version=12.1.3001.165

Regards,

[Chetan Savade]

Hi,

It seems you are using SEP 12.1 RU3 version (12.1.3001.165), Upgrade to the latest version can be a possible solution.

[Migration User]

Dear Chetan,

Could you like to give me guide to updgrade Symantec Version ?

 

 

Regards,

[Chetan Savade]

Hi,

Download the latest version SEP 12.1 RU4 MP1a from here.

Refer this article to follow articles to know Best practice & System requirements prior to upgrade.

http://www.symantec.com/docs/TECH211821

http://www.symantec.com/docs/TECH163829

 

[Migration User]

Hi thanks, 

i'll try it later.. i'll keep update if problem have solved