Error on tomcat catalina.ot

83 views
Skip to first unread message

mehdi.al...@gmail.com

unread,
Sep 15, 2020, 7:43:05 AM9/15/20
to Sentilo
Hi Dear Sentilo Team 
I installed an instance of Sentilo of 4 docker  containers.  First one for Redis, second one for mongodb, third one for apache tomcat and catalog and last one for running platform service.  
Every things  worked fine until today, when I was going to login in dashboard got the 
I checked the logs and I find out that on tomcat (catalina.out) there are some  errors like below

020-09-15 11:29:20,431 GMT [catalogScheduler-3] ERROR org.springframework.scheduling.support.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.org.sentilo.web.catalog.exception.CatalogException: ; nested exception is com.mongodb.MongoBulkWriteException: Bulk write operation error on server mongo_host:27017. Write errors: [BulkWriteError{index=0, code=11000, message='E11000 duplicate key error collection: sentilo.performance index: _id_ dup key: { : "1600169337062" }', details={ }}, BulkWriteError{index=1, code=11000, message='E11000 duplicate key error collection: sentilo.performance index: _id_ dup key: { : "1600169337062test" }', details={ }}]. 
at org.sentilo.web.catalog.aop.aspect.CatalogExceptionTranslationInterceptor.doTranslationAction(CatalogExceptionTranslationInterceptor.java:69) ~[classes/:na]
at sun.reflect.GeneratedMethodAccessor256.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_232]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_232]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:644) ~[spring-aop-5.0.8.RELEASE.jar:5.0.8.RELEASE]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:626) ~[spring-aop-5.0.8.RELEASE.jar:5.0.8.RELEASE]
at org.springframework.aop.aspectj.AspectJAfterThrowingAdvice.invoke(AspectJAfterThrowingAdvice.java:66) ~[spring-aop-5.0.8.RELEASE.jar:5.0.8.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185) ~[spring-aop-5.0.8.RELEASE.jar:5.0.8.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-5.0.8.RELEASE.jar:5.0.8.RELEASE] 


.....

know I reinstalled mongodb , cleared all data from mongodb 
also
I have already  cleared all KEYS from Redis, restart sentilo server restart apcahe tomcat but still I have got the error in catalina.out

please help me 
Regard 
Mehdi

Sentilo IO

unread,
Sep 17, 2020, 5:16:51 AM9/17/20
to Sentilo
Hi Mehdi,

This error occurs when the platform tries to save some internal metrics.  We think It's caused by a minor bug and not really a critical issue, the platform should work fine but we understand that it could be confuse.
As a temporary workaround, before starting the platform, you could delete from mongoDB the last two registers of the "performance" collection(seems to be a multi-tenant instance, timestamp 1600169337062).

Hope it helps...

Regards,
Sentilo Team.

mehdi.al...@gmail.com

unread,
Sep 21, 2020, 5:11:58 AM9/21/20
to Sentilo
Thank you for your response 
I will try your suggestion for error log and share the result 

but, I have another question which I mentioned in the previous question.  when I want to login into the platform, URL change to 
I checked the catalog logs in catalina.out and just  see this message when press login  button

2020-09-21 08:23:26,284 GMT [http-nio-8080-exec-9] INFO  org.sentilo.web.catalog.interceptor.RequestLoggingInterceptor - Incoming request [remote_addr=IPAddress;request=POST /sentilo-catalog-web/accessDenied]

Thank you again

Sentilo IO

unread,
Sep 23, 2020, 4:21:47 AM9/23/20
to Sentilo
Hi Mehdi,

I'm not sure about the issue, but just in case, are you using a multi-tenant instance ?
If you're using a multi-tenant instance you have to add the tenant at the end of the URL.
Example: /sentilo-catalog-web/<tenant>
The root context will only be accessible by the super-admin profile.

Please, let us know if this is the problem or if you found the solution by yourself ;)

Regards,
Sentilo Team
Reply all
Reply to author
Forward
Message has been deleted
Message has been deleted
0 new messages