1
SmarterLogs TEMP files don't go away!
Problem reported by Brian Lewis - 3/17/2016 at 9:16 AM
Resolved
We have a server that had over 600GB of 'temp' files in c:\smarterlogs\weblogs\##\temp for 3 different sites. 
After having the server take a week to delete them (millions of files) I stated SmarterStats (10.5.5751) back up and its started to create those files again and not delete them.
 
Any idea on what the issue might be?
 

4 Replies

Reply to Thread
0
Employee Replied
Employee Post
Hey Brian,
 
The purpose of the temp folder in a SmarterLogs folder is a holding location for files as they are manipulated by the SmarterStats service.  Once the service is finished with the files, the file should be removed.  In your case though it sounds as though the service might not have full permissions to the SmarterLogs location causing the files to be left behind.
 
You want to check and make sure the account that the SmarterStats Service runs under has read\write access to the SmarterLogs location. By default this is a "Local System" account, but if you modified the service to run under a different account, it too would need to have permissions accordingly.
 
Thanks
0
Brian Lewis Replied
That was checked already, service uses LOCAL SYSTEM, and 'SYSTEM' account has full control of the temp folders.
0
Brian Lewis Replied
Found the BUG - Yes this is a bug in 10.5

If SmarterStats has an import error - writing to the file below, it will cause itself to NOT delete TEMP files!!

Stopping service, deleting the 2015-09 folder, starting the service fixes everything

Import Error: 3/18/2016 6:51 AM - C:\SmarterLogs\WebLogs\5\2015-09\spdrsessionlengths.stat.new could not be written correctly
0
Brian Lewis Replied
Found the BUG - Yes this is a bug in 10.5
 
If SmarterStats has an import error - writing to the file below, it will cause itself to NOT delete TEMP files!!
 
Stopping service, deleting the 2015-09 folder, starting the service fixes everything

Import Error: 3/18/2016 6:51 AM - C:\SmarterLogs\WebLogs\5\2015-09\spdrsessionlengths.stat.new could not be written correctly

Reply to Thread