Huge S3 - NOT FOUND ERROR Logs while all content looks in share

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Active Member

Huge S3 - NOT FOUND ERROR Logs while all content looks in share

My community 5.2 with some customizations is running on linux 18 on DO server. contentstore is S3 bucket. Now an error S3 NOT FOUND is getting generated continuously in my logs. While DMS looks working fine with all the content. But these logs generates continuouly and very huge.

ERROR [extensions.webscripts.AbstractRuntime] [http-bio-8443-exec-39] Exception from executeScript: Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: 120F8AF3DD0438B7; S3 Extended Request ID: hNGT+vGLtYaKcDCMGpeWeHZNnJlbo9ZuE/lIKgjWmcShg6VLY1jZVXWdXRn9IQQta4Ku7JQo7C8=)
com.amazonaws.services.s3.model.AmazonS3Exception: Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: 120F8AF3DD0438B7; S3 Extended Request ID: hNGT+vGLtYaKcDCMGpeWeHZNnJlbo9ZuE/lIKgjWmcShg6VLY1jZVXWdXRn9IQQta4Ku7JQo7C8=), S3 Extended Request ID: hNGT+vGLtYaKcDCMGpeWeHZNnJlbo9ZuE/lIKgjWmcShg6VLY1jZVXWdXRn9IQQta4Ku7JQo7C8=

at org.alfresco.solr.client.SOLRAPIClient.getTextContent(SOLRAPIClient.java:1118)
at org.alfresco.solr.SolrInformationServer.addContentPropertyToDocUsingAlfrescoRepository(SolrInformationServer.java:2783)...

Can someone please help me? Thanks.

2 Replies
Highlighted
Community Manager
Community Manager

Re: Huge S3 - NOT FOUND ERROR Logs while all content looks in share

Are you using your own connector for S3 or the Alfresco S3 connector?

Highlighted
Active Member

Re: Huge S3 - NOT FOUND ERROR Logs while all content looks in share

Thanks jljwoznica for your reply. We are using alfresco S3 connector https://github.com/Redpill-Linpro/alfresco-s3-adapter for this. And this is working fine in some alfresco instances but in other instances it continusly giving above error in tomcat catalina. While DMS is up and running with all the contents in all DMSs.

While we also have migrated some DMSs from one server to other. And this error is not all migrated ones.

 

-Sumit