dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #33304
Re: Moving to 2.16
Hi Tim,
You may want to look here for the necessary upgrade script.
http://www.dhis2.org/download/resources/sql/rename-patient-to-trackedentity.sql
Regards,
Jason
On Oct 7, 2014 7:41 PM, "Timothy Harding" <hardingt@xxxxxxxxx> wrote:
> Hello Developer's Group
>
> I'm now working on migrating from 2.14 to 2.16 in our test environment and
> the startup for tomcat is hanging on step 7. I've included some relevant
> snippets of logs below and have attached the full logs:
>
> - stdout.txt = Standard out during importing the DHIS2 2.14 database,
> running the upgrade script, and starting tomcat)
> - catalina.out = The tomcat log for the latest attempt to start up 2.16
>
> My Notes:
> I can boot up 2.14 with the database dump without problem
> I can boot up 2.16 with a *blank* database without problem (it creates
> the live environment i.e. admin:district)
> The problem occurs when I try to boot up 2.16 with the 2.14 database
> (after I've run the 2.15 upgrade script found here:
> http://www.dhis2.org/download/resources/sql/rename-patient-to-trackedentity.sql
> )
> It hangs at step 7 of 14 * INFO 2014-10-08 09:45:03,291 Executing
> startup routine [7 of 14, runlevel 4]: TrackedEntityTableAlteror
> (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
> The system, for having such meager hardware, is really snappy with both
> the live version of 2.16, and our full production mirror of 2.14.
> The com.hazelcast.util.HealthMonitor continues to function even after
> the initialization process hangs at step 7 of 14 (as you can see in
> catalina.out) Oct 08, 2014 10:36:58 AM com.hazelcast.util.HealthMonitor
>
> Both Java and Postgres are using no cpu cycles after the hang, so it
> doesn't *feel* like it is churning away at something:
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 1413 dhis 20 0 1895572 570840 16532 S 1.0 44.7 1:48.39 java
> 906 postgres 20 0 523944 30260 28868 S 0.0 2.4 0:00.47
> postgres
> 908 postgres 20 0 524704 77648 75724 S 0.0 6.1 0:01.04
> postgres
> 909 postgres 20 0 524140 4304 2904 S 0.0 0.3 0:00.16
> postgres
> 910 postgres 20 0 524140 14056 12656 S 0.0 1.1 0:00.50
> postgres
> 911 postgres 20 0 524980 3068 1096 S 0.0 0.2 0:00.11
> postgres
> 912 postgres 20 0 103712 1984 352 S 0.0 0.2 0:00.71
> postgres
> 1432 postgres 20 0 526508 7656 4524 S 0.0 0.6 0:00.00
> postgres
> 1433 postgres 20 0 529308 14604 8948 S 0.0 1.1 0:00.22
> postgres
> 1434 postgres 20 0 536664 46672 32832 S 0.0 3.7 0:08.00
> postgres
> 1904 postgres 20 0 525372 5652 3204 S 0.0 0.4 0:00.00
> postgres
> 1906 postgres 20 0 525256 4860 2548 S 0.0 0.4 0:00.00
> postgres
> 1907 postgres 20 0 525256 4856 2540 S 0.0 0.4 0:00.00
> postgres
> 2114 postgres 20 0 525372 5600 3192 S 0.0 0.4 0:00.00
> postgres
> (there are a lot of postgres processes it seems like)
>
> I saw some errors on startup but the notes for 2.16 says to expect a few
> the first time. I also saw some errors when I ran the import and 2.15
> upgrade script.
> Database import (grep for errors)
> ERROR: must be owner of extension plpgsql
>
> Upgrade script (grep for errors)
> ERROR: table "patientaggregatereportmembers" does not exist
> ERROR: table "patienttabularreportmembers" does not exist
> ERROR: table "patientregistrationform_attributes" does not exist
> ERROR: table "patientregistrationform_fixedattributes" does not exist
> ERROR: table "patientregistrationform_identifiertypes" does not exist
> ERROR: table "patientregistrationform_attributes" does not exist
> ERROR: table "patientmobilesetting" does not exist
>
> Any ideas? Is there an upgrade script I've forgotten to run or maybe a
> setting I've missed?
>
> Timothy Harding
> PeaceCorps Volunteer
> Republic of Vanuatu
> hardingt@xxxxxxxxx
> +678 5955137
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References