Local Aggregate redirect fails

Greetings: I am attempting to upgrade a local Aggregate server in Malawi
from an earlier version to 1.4.5, but I cannot get it to redirect to the
Forms page. First, I used Briefcase to download all surveys on the server
to archive them as csv and media files, so that Aggregate could resume
uncluttered with past surveys . Then, I reinstalled Tomcat and MySQL with
the latest versions, and deleted and recreated the MySQL database. Everything
worked as expected, up to the point where Aggregate redirects to the
Aggregate.html page. At first, nothing happened at all – Aggregate simply
froze at the initial page. I redid the Aggregate installation, this time
double-checking each step against my setup notes and the ODK instruction
page. I deleted the old war file from Tomcat webapps (causing Tomcat to
delete the ODKAggregate folder) and substituted the new war file (after
which Tomcat recreated the ODKAggregate folder). Now, the ODK icon in the
upper left of the screen appears, but it begins to flash on and off and the
rest of the page does not load. I’ve attached the catalina log file, which
includes the two attempts. Other Tomcat log files created on that date
(commons-daemon and host-manager) do not seem to contain any possibly
relevant information.

I would like to get the server working again before I return from Malawi
to the USA on April 24, since getting surveys off late-model Androids is
not an easy task otherwise. Any help and guidance would be greatly
appreciated. Thanks in advance. Hayden

catalina.2015-04-12.log (7.71 KB)

There is usually a tomcat6-stdout log that will contain much more logging
information.

The most likely causes:

(1) if you are using MySQL, you forgot to download and install the MySQL
Connector/J into the lib directory of Tomcat6 (and restart Tomcat6).

(2) you entered an incorrect hostname when running the ODK Aggregate
installer. Look at the URL that the browser is trying to access when it
hangs or returns a 404 (you may need to hit a back button in the browser to
access that URL). Is it what you expect? The more detailed log file will
identify the hostname the server is using; if you have access to those logs
(tomcat6-stdout...), search for "INFO: Hostname" e.g.,

INFO: Hostname: xxxxxxx.cs.washington.edu

(3) you did not run the create_db_and_user.sql script, or it ran and didn't
create the the database and user correctly. Use MySQL workbench to confirm
that the database and user are present. If possible, try connecting as
that user (from the webserver machine) to confirm that you can access the
database from that machine.

(4) It is also probable that the latest version of ODK Aggregate (1.4.5)
now requires that you have a Java 1.7 runtime environment. If you were
using Java 6 or earlier, be sure your system has been updated to use Java
7. Do not install Java 8, as we have not tested with that, and other
users have reported problems using it.

Finally, if none of those fix the issue, it sounds like you may have
modified your Tomcat and/or not followed the installation sequence
described here https://opendatakit.org/use/aggregate/tomcat-install/ .

Without a detailed tomcat6-stdout log, it will be impossible to debug the
problem and/or where your alterations are impacting the install. I would
recommend trying an fresh install on a different computer to see what
changes you've made to your Tomcat installation that are disabling the
production of the tomcat6-stdout log, and undo them. In general, you
should always have this detailed log being produced, but should configure
Tomcat to delete older log files (e.g., those older than 30 days). This
will enable you to examine recent history for failures.

··· On Tue, Apr 14, 2015 at 3:59 AM, Hayden Boyd wrote:

Greetings: I am attempting to upgrade a local Aggregate server in Malawi
from an earlier version to 1.4.5, but I cannot get it to redirect to the
Forms page. First, I used Briefcase to download all surveys on the
server to archive them as csv and media files, so that Aggregate could
resume uncluttered with past surveys . Then, I reinstalled Tomcat and
MySQL with the latest versions, and deleted and recreated the MySQL
database. Everything worked as expected, up to the point where Aggregate
redirects to the Aggregate.html page. At first, nothing happened at all
– Aggregate simply froze at the initial page. I redid the Aggregate
installation, this time double-checking each step against my setup notes
and the ODK instruction page. I deleted the old war file from Tomcat
webapps (causing Tomcat to delete the ODKAggregate folder) and substituted
the new war file (after which Tomcat recreated the ODKAggregate folder). Now,
the ODK icon in the upper left of the screen appears, but it begins to
flash on and off and the rest of the page does not load. I’ve attached
the catalina log file, which includes the two attempts. Other Tomcat log
files created on that date (commons-daemon and host-manager) do not seem to
contain any possibly relevant information.

I would like to get the server working again before I return from Malawi
to the USA on April 24, since getting surveys off late-model Androids is
not an easy task otherwise. Any help and guidance would be greatly
appreciated. Thanks in advance. Hayden

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Thanks, Mitch. Everything on your list checked out, except that the
stdout.log contained only one line, not useful for debugging. Uninstalling
and reinstalling everything gave the same result: everything seemed ok, but
Aggregate would not redirect to the forms page. It turns out that the
culprit was the Google Chrome browser (version 42.0.2311.90 m), When I
downloaded and substituted Firefox, everything worked as expected.

Your warning about updating from jre7 was timely. I was about to allow the
update to proceed just as soon as I got Aggregate working again. Disabling
the automatic update in the Java control panel, as directed by the Java
website, does not work, because the JCP does not save your changes. Java
says it is a bug that they are working on, and meanwhile they provide a
workaround at https://www.java.com/en/download/help/javacpl.xml. The page
applies to jre6, but the procedure also worked for me with jre7.

All the best, Hayden

··· On Tue, Apr 14, 2015 at 6:35 PM, Mitch Sundt wrote:

There is usually a tomcat6-stdout log that will contain much more logging
information.

The most likely causes:

(1) if you are using MySQL, you forgot to download and install the MySQL
Connector/J into the lib directory of Tomcat6 (and restart Tomcat6).

(2) you entered an incorrect hostname when running the ODK Aggregate
installer. Look at the URL that the browser is trying to access when it
hangs or returns a 404 (you may need to hit a back button in the browser to
access that URL). Is it what you expect? The more detailed log file will
identify the hostname the server is using; if you have access to those logs
(tomcat6-stdout...), search for "INFO: Hostname" e.g.,

INFO: Hostname: xxxxxxx.cs.washington.edu

(3) you did not run the create_db_and_user.sql script, or it ran and
didn't create the the database and user correctly. Use MySQL workbench to
confirm that the database and user are present. If possible, try
connecting as that user (from the webserver machine) to confirm that you
can access the database from that machine.

(4) It is also probable that the latest version of ODK Aggregate (1.4.5)
now requires that you have a Java 1.7 runtime environment. If you were
using Java 6 or earlier, be sure your system has been updated to use Java
7. Do not install Java 8, as we have not tested with that, and other
users have reported problems using it.

Finally, if none of those fix the issue, it sounds like you may have
modified your Tomcat and/or not followed the installation sequence
described here https://opendatakit.org/use/aggregate/tomcat-install/ .

Without a detailed tomcat6-stdout log, it will be impossible to debug the
problem and/or where your alterations are impacting the install. I would
recommend trying an fresh install on a different computer to see what
changes you've made to your Tomcat installation that are disabling the
production of the tomcat6-stdout log, and undo them. In general, you
should always have this detailed log being produced, but should configure
Tomcat to delete older log files (e.g., those older than 30 days). This
will enable you to examine recent history for failures.

On Tue, Apr 14, 2015 at 3:59 AM, Hayden Boyd haydenboyd507@gmail.com wrote:

Greetings: I am attempting to upgrade a local Aggregate server in Malawi
from an earlier version to 1.4.5, but I cannot get it to redirect to the
Forms page. First, I used Briefcase to download all surveys on the
server to archive them as csv and media files, so that Aggregate could
resume uncluttered with past surveys . Then, I reinstalled Tomcat and
MySQL with the latest versions, and deleted and recreated the MySQL
database. Everything worked as expected, up to the point where
Aggregate redirects to the Aggregate.html page. At first, nothing
happened at all – Aggregate simply froze at the initial page. I redid
the Aggregate installation, this time double-checking each step against my
setup notes and the ODK instruction page. I deleted the old war file
from Tomcat webapps (causing Tomcat to delete the ODKAggregate folder) and
substituted the new war file (after which Tomcat recreated the ODKAggregate
folder). Now, the ODK icon in the upper left of the screen appears, but
it begins to flash on and off and the rest of the page does not load. I’ve
attached the catalina log file, which includes the two attempts. Other
Tomcat log files created on that date (commons-daemon and host-manager) do
not seem to contain any possibly relevant information.

I would like to get the server working again before I return from Malawi
to the USA on April 24, since getting surveys off late-model Androids is
not an easy task otherwise. Any help and guidance would be greatly
appreciated. Thanks in advance. Hayden

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Odd. I regularly use Chrome, and haven't seen this behavior.

It might be an extension or plugin. If you run it in Incognito mode, that
usually does not activate any extensions, and it should work.

··· On Sun, Apr 19, 2015 at 11:30 AM, Hayden Boyd wrote:

Thanks, Mitch. Everything on your list checked out, except that the
stdout.log contained only one line, not useful for debugging. Uninstalling
and reinstalling everything gave the same result: everything seemed ok, but
Aggregate would not redirect to the forms page. It turns out that the
culprit was the Google Chrome browser (version 42.0.2311.90 m), When I
downloaded and substituted Firefox, everything worked as expected.

Your warning about updating from jre7 was timely. I was about to allow the
update to proceed just as soon as I got Aggregate working again. Disabling
the automatic update in the Java control panel, as directed by the Java
website, does not work, because the JCP does not save your changes. Java
says it is a bug that they are working on, and meanwhile they provide a
workaround at https://www.java.com/en/download/help/javacpl.xml. The
page applies to jre6, but the procedure also worked for me with jre7.

All the best, Hayden

On Tue, Apr 14, 2015 at 6:35 PM, Mitch Sundt mitchellsundt@gmail.com wrote:

There is usually a tomcat6-stdout log that will contain much more logging
information.

The most likely causes:

(1) if you are using MySQL, you forgot to download and install the MySQL
Connector/J into the lib directory of Tomcat6 (and restart Tomcat6).

(2) you entered an incorrect hostname when running the ODK Aggregate
installer. Look at the URL that the browser is trying to access when it
hangs or returns a 404 (you may need to hit a back button in the browser to
access that URL). Is it what you expect? The more detailed log file will
identify the hostname the server is using; if you have access to those logs
(tomcat6-stdout...), search for "INFO: Hostname" e.g.,

INFO: Hostname: xxxxxxx.cs.washington.edu

(3) you did not run the create_db_and_user.sql script, or it ran and
didn't create the the database and user correctly. Use MySQL workbench to
confirm that the database and user are present. If possible, try
connecting as that user (from the webserver machine) to confirm that you
can access the database from that machine.

(4) It is also probable that the latest version of ODK Aggregate (1.4.5)
now requires that you have a Java 1.7 runtime environment. If you were
using Java 6 or earlier, be sure your system has been updated to use Java
7. Do not install Java 8, as we have not tested with that, and other
users have reported problems using it.

Finally, if none of those fix the issue, it sounds like you may have
modified your Tomcat and/or not followed the installation sequence
described here https://opendatakit.org/use/aggregate/tomcat-install/ .

Without a detailed tomcat6-stdout log, it will be impossible to debug the
problem and/or where your alterations are impacting the install. I would
recommend trying an fresh install on a different computer to see what
changes you've made to your Tomcat installation that are disabling the
production of the tomcat6-stdout log, and undo them. In general, you
should always have this detailed log being produced, but should configure
Tomcat to delete older log files (e.g., those older than 30 days). This
will enable you to examine recent history for failures.

On Tue, Apr 14, 2015 at 3:59 AM, Hayden Boyd haydenboyd507@gmail.com wrote:

Greetings: I am attempting to upgrade a local Aggregate server in Malawi
from an earlier version to 1.4.5, but I cannot get it to redirect to the
Forms page. First, I used Briefcase to download all surveys on the
server to archive them as csv and media files, so that Aggregate could
resume uncluttered with past surveys . Then, I reinstalled Tomcat and
MySQL with the latest versions, and deleted and recreated the MySQL
database. Everything worked as expected, up to the point where
Aggregate redirects to the Aggregate.html page. At first, nothing
happened at all – Aggregate simply froze at the initial page. I redid
the Aggregate installation, this time double-checking each step against my
setup notes and the ODK instruction page. I deleted the old war file
from Tomcat webapps (causing Tomcat to delete the ODKAggregate folder) and
substituted the new war file (after which Tomcat recreated the ODKAggregate
folder). Now, the ODK icon in the upper left of the screen appears,
but it begins to flash on and off and the rest of the page does not load.
I’ve attached the catalina log file, which includes the two attempts. Other
Tomcat log files created on that date (commons-daemon and host-manager) do
not seem to contain any possibly relevant information.

I would like to get the server working again before I return from
Malawi to the USA on April 24, since getting surveys off late-model
Androids is not an easy task otherwise. Any help and guidance would be
greatly appreciated. Thanks in advance. Hayden

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google
Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com