Hi Dave, We have extended out disk and increase the RAM. I think it's no longer disk or memory space. postgres is located on separate server and hosts databases for other instances on 2.28 with which analytics are perfectly running. I have removed existing war file and redeploy a fresh new as suggested . I am still exploring if there are not other jobs interfering ! I have stopped scheduler analytics job but there re still other builtin ones in 2.29 like resource file, credentials still active as it set on demo? do i have stop these also?
Regards, *Adolphe Kamugunga* *MIS Technical Advisor* Mobile: +250 788 740 578 Email:kaa...@gmail.com Skype: ka.adolphe RWANDA On 1 August 2018 at 10:04, David Huser <dhu...@baosystems.com> wrote: > Hi Adolphe, > > Can you confirm the points raised earlier by Hannan, Jason and Gerald? > > - free disk space has been increased > - disabled external sources triggering analytics (cronjob, apps, ...)? > - monitored startup logs? > > If yes, you can try to clear analytic tables, then do a manual triggering > of analytics every day > <https://jira.dhis2.org/browse/DHIS2-4214?focusedCommentId=17829&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17829> > . > > Regards, > David > > > On Tue, Jul 31, 2018 at 6:55 PM Kamugunga Adolphe <kaa...@gmail.com> > wrote: > >> Dear Dave, >> >> I tried your workaround but analytics run once successfully and compile >> aggregate values of my weekly reports only, the dashboard with cases based >> data(program indicators) don't have values. The strange situation is that >> from Event Reports app, i list/display events reported before upgrade only >> and when i change the period to "This month" no values displayed. >> >> I run again the analytics but it failed with similar message. If someone >> has another alternative to fix this plz let me know! I am completely stack? >> The instance is updated with the today build version Version:2.29Build >> revision:153207cBuild date:2018-07-31 06:50Jasper reports version:6.3.1 >> >> >> Down here is the error message content: >> >> >> >> >> Job 'inMemoryAnalyticsJob' failed >> >> System title:Integrated Disease Surveillance >> Base URL: >> Time: 2018-07-31T16:04:01.496+02:00 >> Message: StatementCallback; uncategorized SQLException for SQL [drop >> table analytics]; SQL state [2BP01]; error code [0]; ERROR: cannot drop >> table analytics because other objects depend on it >> Detail: table analytics_2004 depends on table analytics >> table analytics_2005 depends on table analytics >> table analytics_2007 depends on table analytics >> table analytics_2008 depends on table analytics >> table analytics_2009 depends on table analytics >> table analytics_2010 depends on table analytics >> table analytics_2011 depends on table analytics >> table analytics_2012 depends on table analytics >> table analytics_2013 depends on table analytics >> table analytics_2014 depends on table analytics >> table analytics_2015 depends on table analytics >> Hint: Use DROP ... CASCADE to drop the dependent objects too.; nested >> exception is org.postgresql.util.PSQLException: ERROR: cannot drop table >> analytics because other objects depend on it >> Detail: table analytics_2004 depends on table analytics >> table analytics_2005 depends on table analytics >> table analytics_2007 depends on table analytics >> table analytics_2008 depends on table analytics >> table analytics_2009 depends on table analytics >> table analytics_2010 depends on table analytics >> table analytics_2011 depends on table analytics >> table analytics_2012 depends on table analytics >> table analytics_2013 depends on table analytics >> table analytics_2014 depends on table analytics >> table analytics_2015 depends on table analytics >> Hint: Use DROP ... CASCADE to drop the dependent objects too. >> >> Cause: org.postgresql.util.PSQLException: ERROR: cannot drop table >> analytics because other objects depend on it >> Detail: table analytics_2004 depends on table analytics >> table analytics_2005 depends on table analytics >> table analytics_2007 depends on table analytics >> table analytics_2008 depends on table analytics >> table analytics_2009 depends on table analytics >> table analytics_2010 depends on table analytics >> table analytics_2011 depends on table analytics >> table analytics_2012 depends on table analytics >> table analytics_2013 depends on table analytics >> table analytics_2014 depends on table analytics >> table analytics_2015 depends on table analytics >> Hint: Use DROP ... CASCADE to drop the dependent objects too. >> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse( >> QueryExecutorImpl.java:2422) >> at org.postgresql.core.v3.QueryExecutorImpl.processResults( >> QueryExecutorImpl.java:2167) >> at org.postgresql.core.v3.QueryExecutorImpl.execute( >> QueryExecutorImpl.java:306) >> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441) >> at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365) >> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307) >> at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293) >> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270) >> at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:266) >> at com.mchange.v2.c3p0.impl.NewProxyStatement.execute( >> NewProxyStatement.java:75) >> at org.springframework.jdbc.core.JdbcTemplate$1ExecuteStatementCallback. >> doInStatement(JdbcTemplate.java:436) >> at org.springframework.jdbc.core.JdbcTemplate.execute( >> JdbcTemplate.java:408) >> at org.springframework.jdbc.core.JdbcTemplate.execute( >> JdbcTemplate.java:445) >> at org.hisp.dhis.analytics.table.AbstractJdbcTableManager. >> executeSilently(AbstractJdbcTableManager.java:341) >> at org.hisp.dhis.analytics.table.AbstractJdbcTableManager.swapTable( >> AbstractJdbcTableManager.java:508) >> at org.hisp.dhis.analytics.table.AbstractJdbcTableManager.swapTable( >> AbstractJdbcTableManager.java:178) >> at sun.reflect.GeneratedMethodAccessor2130.invoke(Unknown Source) >> at sun.reflect.DelegatingMethodAccessorImpl.invoke( >> DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:498) >> at org.springframework.aop.support.AopUtils. >> invokeJoinpointUsingReflection(AopUtils.java:333) >> at org.springframework.aop.framework.JdkDynamicAopProxy. >> invoke(JdkDynamicAopProxy.java:207) >> at com.sun.proxy.$Proxy142.swapTable(Unknown Source) >> at org.hisp.dhis.analytics.table.DefaultAnalyticsTableService. >> lambda$swapTables$5(DefaultAnalyticsTableService.java:373) >> at java.util.ArrayList.forEach(ArrayList.java:1249) >> at org.hisp.dhis.analytics.table.DefaultAnalyticsTableService.swapTables( >> DefaultAnalyticsTableService.java:373) >> at org.hisp.dhis.analytics.table.DefaultAnalyticsTableService.update( >> DefaultAnalyticsTableService.java:171) >> at org.hisp.dhis.analytics.table.DefaultAnalyticsTableGenerator >> .generateTables(DefaultAnalyticsTableGenerator.java:115) >> at org.hisp.dhis.analytics.table.scheduling.AnalyticsTableJob. >> execute(AnalyticsTableJob.java:70) >> at org.hisp.dhis.scheduling.DefaultJobInstance.executeJob( >> DefaultJobInstance.java:145) >> at org.hisp.dhis.scheduling.DefaultJobInstance.execute( >> DefaultJobInstance.java:59) >> at org.hisp.dhis.scheduling.DefaultSchedulingManager.lambda$ >> internalExecuteJobConfiguration$2(DefaultSchedulingManager.java:237) >> at java.util.concurrent.Executors$RunnableAdapter. >> call(Executors.java:511) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at org.springframework.scheduling.support.DelegatingErrorHandlingRunnabl >> e.run(DelegatingErrorHandlingRunnable.java:54) >> at java.util.concurrent.Executors$RunnableAdapter. >> call(Executors.java:511) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at java.util.concurrent.ScheduledThreadPoolExecutor$ >> ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) >> at java.util.concurrent.ScheduledThreadPoolExecutor$ >> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) >> at java.util.concurrent.ThreadPoolExecutor.runWorker( >> ThreadPoolExecutor.java:1142) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run( >> ThreadPoolExecutor.java:617) >> at java.lang.Thread.run(Thread.java:745) >> >> >> >> *Adolphe Kamugunga* >> *MIS Technical Advisor* >> Mobile: +250 788 740 578 >> Email:kaa...@gmail.com >> Skype: ka.adolphe >> RWANDA >> >> >> On 5 July 2018 at 15:38, David Huser <dhu...@baosystems.com> wrote: >> >>> Is it possible that the Reports app to run analytics does something >>> different to what the Scheduler does, not dropping / creating the same >>> tables? We added a JIRA issue <https://jira.dhis2.org/browse/DHIS2-4214> >>> describing this - Scheduler cannot complete analytics generation once >>> Reports has created analytics beforehand. >>> >>> A workaround for now is so far is to clear analytics via Data Admin > >>> Maintenance then using the Scheduler only to run - manually or scheduled. >>> >>> Regards, >>> David >>> >>> On Wed, Jul 4, 2018 at 6:28 PM gerald thomas <gerald17...@gmail.com> >>> wrote: >>> >>>> Dear Jason, >>>> That is true but the errors are still generating into the various >>>> analytics tables. That is why I wanted him to check those tables and if >>>> there are data in them he should delete them. >>>> >>>> On Wed, 4 Jul 2018 at 15:53, Jason Pickering < >>>> jason.p.picker...@gmail.com> wrote: >>>> >>>>> Hi Adolphe, >>>>> >>>>> The error points to lack of disk space. Check that as well. >>>>> >>>>> Regards, >>>>> Jason >>>>> >>>>> On Wed, Jul 4, 2018, 10:55 gerald thomas <gerald17...@gmail.com> >>>>> wrote: >>>>> >>>>>> Dear Kamugunga, >>>>>> I think they are still in the completedatasetregistration. Please run >>>>>> the query below so that we can know the quantity. >>>>>> We will have to delete them here and at the analytics tables again. >>>>>> >>>>>> dhis-# SELECT p.startdate, count(dv.datasetid) as recno from >>>>>> completedatasetregistration dv INNER JOIN period p on >>>>>> p.periodid=dv.periodid group by p.startdate order by p.startdate; >>>>>> >>>>>> >>>>>> On Wed, 4 Jul 2018 at 14:43, Kamugunga Adolphe <kaa...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Thomas and Dan for sharing your experience, >>>>>>> However i have dropped the analytics table and analytics_temp >>>>>>> tables. and deploy my the recent war file. Then i run the analytics >>>>>>> successfully. Afterward i started receiven the same massage as by >>>>>>> attachment. >>>>>>> >>>>>>> I am suspecting jobs that are by default created in the new feature >>>>>>> of "Scheduler" Can any one explain reasons of having these? And please >>>>>>> share more hints on how to deal with this problem. >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Adolphe Kamugunga* >>>>>>> *MIS Technical Advisor* >>>>>>> Mobile: +250 788 740 578 >>>>>>> Email:kaa...@gmail.com >>>>>>> Skype: ka.adolphe >>>>>>> RWANDA >>>>>>> >>>>>>> >>>>>>> On 3 July 2018 at 23:56, gerald thomas <gerald17...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Dear Kamugunga, >>>>>>>> I think you need to shutdown instance; remove your current war file >>>>>>>> folder e.g ROOT or dhis which depends on the name of your war file. >>>>>>>> Switch to your Postgres database and manually delete all those >>>>>>>> analytics tables. Then you restart instance and monitor log at startup >>>>>>>> and >>>>>>>> when running analytics again. >>>>>>>> >>>>>>>> >>>>>>>> On Tue, 3 Jul 2018 at 16:57, Kamugunga Adolphe <kaa...@gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I have upgraded my 2.28 instance to 2.29 version,7c81fba >>>>>>>>> Build date: 2018-06-28 06:46 . I have run the upgrade scripts >>>>>>>>> before as instructed in guide. My server runs ubuntu 14.04 and >>>>>>>>> postgresql >>>>>>>>> 9.5.5. >>>>>>>>> >>>>>>>>> However since then, my analytics is not running, i am receiving >>>>>>>>> number of system emails with subject " Job 'Credentials expiry alert' >>>>>>>>> failed; Job 'inMemoryAnalyticsJob' failed;Analytics table process >>>>>>>>> failed " >>>>>>>>> >>>>>>>>> Attached are some screenshots of the message. I tried to clear >>>>>>>>> analytics tables and run analytics again but its not improving. >>>>>>>>> >>>>>>>>> The online 2.29 demo also has the same message bu with different >>>>>>>>> contents. >>>>>>>>> >>>>>>>>> Please share the hints on how i can dealt with these. As my system >>>>>>>>> has to sent out notification messages when thresholds are reached. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Adolphe Kamugunga* >>>>>>>>> *MIS Technical Advisor* >>>>>>>>> Mobile: +250 788 740 578; >>>>>>>>> Email:kaa...@gmail.com >>>>>>>>> Skype: ka.adolphe >>>>>>>>> RWANDA >>>>>>>>> >>>>>>>>> >>>>>>>>> On 1 July 2018 at 01:04, gerald thomas <gerald17...@gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Djibril, >>>>>>>>>> Why not try to install java 8 manually? >>>>>>>>>> >>>>>>>>>> Follow these steps: >>>>>>>>>> >>>>>>>>>> https://tecadmin.net/install-oracle-java-8-ubuntu-via-ppa/ >>>>>>>>>> >>>>>>>>>> On Sat, 30 Jun 2018 at 22:26, DJIBRIL Hakim <djib.ha...@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> I am setting up dhis2 instance on ubuntu 16.04 with dhis2-tools. >>>>>>>>>>> When I am running this instance and choose to view log with >>>>>>>>>>> dhis2-logtail, I got this error >>>>>>>>>>> *usr/share/tomcat7/bin/catalina.sh: 1: eval: >>>>>>>>>>> /usr/lib/jvm/java-8-oracle/jre/bin/java: not found* >>>>>>>>>>> >>>>>>>>>>> What can I do to fix it ? >>>>>>>>>>> Best >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Mailing list: https://launchpad.net/~dhis2-users >>>>>>>>>>> Post to : dhis2-us...@lists.launchpad.net >>>>>>>>>>> Unsubscribe : https://launchpad.net/~dhis2-users >>>>>>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Gerald >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Mailing list: https://launchpad.net/~dhis2-users >>>>>>>>>> Post to : dhis2-us...@lists.launchpad.net >>>>>>>>>> Unsubscribe : https://launchpad.net/~dhis2-users >>>>>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>>>>> >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Mailing list: https://launchpad.net/~dhis2-users >>>>>>>>> Post to : dhis2-us...@lists.launchpad.net >>>>>>>>> Unsubscribe : https://launchpad.net/~dhis2-users >>>>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> >>>>>>>> Gerald >>>>>>>> >>>>>>> >>>>>>> -- >>>>>> Regards, >>>>>> >>>>>> Gerald >>>>>> >>>>> _______________________________________________ >>>>>> Mailing list: https://launchpad.net/~dhis2-devs >>>>>> Post to : dhis2-devs@lists.launchpad.net >>>>>> Unsubscribe : https://launchpad.net/~dhis2-devs >>>>>> More help : https://help.launchpad.net/ListHelp >>>>>> >>>>> -- >>>> Regards, >>>> >>>> Gerald >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~dhis2-devs >>>> Post to : dhis2-devs@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~dhis2-devs >>>> More help : https://help.launchpad.net/ListHelp >>>> >>> >>> >>> -- >>> >>> >>> *David Huser* >>> DHIS2 Support Specialist >>> dhu...@baosystems.com | https://baosystems.com | 2900 K Street, Suite >>> 507, Washington D.C. 20007 >>> >> >> > > -- > > > *David Huser* > DHIS2 Support Specialist > dhu...@baosystems.com | https://baosystems.com | 2900 K Street, Suite > 507, Washington D.C. 20007 >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
