ODK Aggregate stopped working

Support
5

Thanks for the heads up, @danbjoseph and thanks a lot @Alexander for your very useful hints that helped me finally find a solution and get Aggregate up and running again. I´ll look into upgrading to Central as soon as possible.

The problem was that after the internal ip change, MySQL was set to bind to that IP - and I was able to solve it by re-running the Aggreate installation as you suggested.

For others that may need to do someting similar with an old ODK Aggreate server - this is what I did:

  1. Determine the version of the defunct ODK Aggregate installation. This was possible by GREPping the tomcat log files for "Version:".

  2. On GitHub, find the correct ODK Aggregate version and download the Windows installer.

  3. Run the installer and get a new .war file that I called ROOT.war

  4. Stop tomcat

  5. Delete the old .war file and the directory called ROOT in the webapps directory.

  6. Restart tomcat

  7. Log into Aggregate with the admin user and the new standard password, which is 'aggregate'.

  8. Create new password for admin user.

(Actually step 3-6 was done a nmber of times until I got it right....)

Finally ODK Aggregate works as expected again.

Thanks a lot for all help!

3 Likes