0 votes

Hi,

We're seeing the following error while trying to save some recipes (and this seems blocking for saving or running recipes).

java.lang.Exception
    at com.dataiku.dip.transactions.TransactionDebugInfo.<init>(TransactionDebugInfo.java:8)
    at com.dataiku.dip.transactions.impl.MinimalRWTransactionImpl.<init>(MinimalRWTransactionImpl.java:60)
    at com.dataiku.dip.transactions.TransactionProvider.beginWrite(TransactionProvider.java:257)
    at com.dataiku.dip.server.services.BackendTransactionService.beginWriteAsLoggedInUser(BackendTransactionService.java:54)
    at com.dataiku.dip.server.services.BackendTransactionService.beginWriteAsLoggedInUser(BackendTransactionService.java:73)
    at com.dataiku.dip.server.datasets.DatasetsCRUDController.deleteMulti(DatasetsCRUDController.java:260)
    at com.dataiku.dip.server.datasets.DatasetsCRUDController$$FastClassBySpringCGLIB$$978fceb2.invoke(<generated>)
    at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
    at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:700)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
    at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
    at com.dataiku.dip.server.controllers.CallTracingAspect.doCall(CallTracingAspect.java:80)
    at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)


Seems to be linked to a corruption in our recipes db.

DSS version == 3.1.4

Could you help us with this issue?

Thanks!

 

asked by Leopold Boudard

1 Answer

0 votes
Hi,

Please open a support ticket at [email protected] and attach a diagnosis of the instance (Administration > Maintenance > Diagnostic tool). If this page is unavailable, please run from the DSS datadir: ./bin/dssadmin run-diagnosis -c -s -f -l diag.zip and send us the diag.zip file

If the resulting file is too big, you can use a file transfer service like WeTransfer to get it to us.

After sending the diag, you can restart DSS which should fix the issue
answered by
595 questions
605 answers
440 comments
327 users