Hi guys, I have a rather old installation of Alfresco
and I noticed that the backup is way too bigger than I think it's supposed to be. If I measure \\alf\alfresco it's about 90GB but if I check out the contentsore directory it's twice that size. The trashcan cleaner is configured
trashcan-cleaner.cron=0 30 * * * ?
trashcan-cleaner.keepPeriod=P1D
trashcan-cleaner.deleteBatchCount=1000
system.content.deleted.cronExpression=0 0 23 * * ?
system.content.orphanProtectDays=2
but when I went to trash can in web interface I saw files from previous year and I couldn't find any entries about trash cleaner in alfresco.log or share.log. Is it supposed to be in another log file? Is it not supported by my alfresco version at all (should be supported starting with 5.2)?
As far as I know the contentStoreCleaner which moves items deleted from trash can to contentstore.deleted is run at 4 am by default, it there a way to reschedule it? The backup takes ages and not always ready by this time.
Hope this helps:
https://github.com/keensoft/alfresco-deleted-content-store-cleaner
You don't need to use this addon, but all the processes related with document removal are described in the readme file.
Thanks for reply, unfortunately it doesn't help to understand why trashcan cleaner is not working. Contentstore.deleted is not really a problem since it's not included in a backup.
It will be helpful to get some logs configured and observe what's going on. Try configuring below logs :
log4j.logger.org.alfresco.trashcan=DEBUG log4j.logger.org.alfresco.repo.transaction.RetryingTransactionHelper=DEBUG log4j.logger.org.alfresco.service.cmr.repository=DEBUG log4j.logger.org.alfresco.schedule=DEBUG
Use this config in your log4j.properties file. It will write all the above logs to a separate file so it doesn't mixup other things which will be helpful for you to debug.
#Scheduled jobs logs log4j.logger.org.alfresco.trashcan=DEBUG,ScheduledJobs log4j.logger.org.alfresco.repo.transaction.RetryingTransactionHelper=DEBUG,ScheduledJobs log4j.logger.org.alfresco.service.cmr.repository=DEBUG,ScheduledJobs log4j.logger.org.alfresco.schedule=DEBUG,ScheduledJobs ###### ScheduledJobs File appender definition ####### log4j.appender.ScheduledJobs=org.apache.log4j.DailyRollingFileAppender log4j.appender.ScheduledJobs.File=/usr/local/tomcat/logs/ScheduledJobsLog.log log4j.appender.ScheduledJobs.Append=true log4j.appender.ScheduledJobs.DatePattern='.'yyyy-MM-dd log4j.appender.ScheduledJobs.layout=org.apache.log4j.PatternLayout log4j.appender.ScheduledJobs.layout.ConversionPattern=%d{yyyy-MM-dd} %d{ABSOLUTE} %-5p [%c] [%t] %m%n
Try running trash can cleaner job via admin console and see what you get.
Where can I find log4j.properties file and where the log4j log will be located?
How to run trash can cleaner job via admin console?
And one more question if I may what does contentstore folder consists of? I thought it's only sites data, but it's 3 times larger than my sites folder. I have cleaned up trash can manually and I can see those gigabites gone but still sites folder is about 40GB and contentstore 130GB, how so?
@statira wrote:
Where can I find log4j.properties file and where the log4j log will be located?
How to run trash can cleaner job via admin console?
Custom logs can be placed within custom modules as well as here: $ALF_HOME/tomcat/shared/classes/alfresco/extension/dev-log4j.properties or $ALF_HOME/tomcat/shared/classes/alfresco/extension/custom-log4j.properties
You can add suggested configs in any of the above files.
Have a look at this documentation: https://docs.alfresco.com/5.1/concepts/dev-extensions-modules-module-log4j.html
Seems you are using community version, so you can not trigger jobs from admin console. You will not see options. However, you can install this add-on which has several helpful tools including option to run jobs on demand when its really needed.
https://github.com/OrderOfTheBee/ootbee-support-tools
And one more question if I may what does contentstore folder consists of?
Contentstore is not only for site data, it is for the repository.
You should get idea of lifecycle of a node, read this post: https://blog.dbi-services.com/understand-the-lifecycle-of-alfresco-nodes/
Go through this documentation for more details on repository architecture and content stores:
https://docs.alfresco.com/5.1/concepts/alfresco-arch-about.html
https://docs.alfresco.com/5.1/concepts/cs-overview.html
https://docs.alfresco.com/5.1/concepts/cs-manage.html
I've set up logging it has
org.alfresco.filesys.repo.FilesystemTransactionAdvice$PropagatingException: org.alfresco.jlan.server.filesys.IOControlNotImplementedException: Custom IO control request not implemented
org.alfresco.repo.security.permissions.AccessDeniedException: 11090003 Access Denied. You do not have the appropriate permissions to perform this operation.
What kind of permissions does it mean?
org.alfresco.filesys.repo.FilesystemTransactionAdvice$PropagatingException: java.io.FileNotFoundException: \Sites\sales\documentLibrary\Документы по пресейлам\Desktop.ini
and
org.alfresco.filesys.repo.FilesystemTransactionAdvice$PropagatingException: java.io.FileNotFoundException: \Sites\sales\documentLibrary\Документы по пресейлам\AutoRun.inf
for several sites
org.springframework.extensions.webscripts.WebScriptException: 11090001 Wrapped Exception (with status template): 11090026 Failed to execute script 'classpath*:alfresco/templates/webscripts/org/alfresco/repo$pository/thumbnail/thumbnail.get.js': 11090025 11090024 Transformation failed to obey timeout limit
and more.
With partial logs, can't say anything for sure. Please clear the log:
/usr/local/tomcat/logs/ScheduledJobsLog.log
And re-generate the log and share the file here.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.