I've reviewed the info on under Using the Application, however when select the Log In button as suggested in (4) below the page times out on and gives me a Problem loading page: The connection was reset warning.
I'm unable to change the super-user password and to set up users since I cannot access the Site Admin tab.
Any help would be greatly appreciated.
Thank you,
Che
If the Site Admin tab is not visible, click the Log In link in the upper right corner of the screen to be presented with the Log onto Aggregate screen. Beginning with ODK Aggregate 1.4.4, the super-user account (the account with full access to the server) is an ODK Aggregate-specific account and not a Google e-mail account. Choose the Sign in with Aggregate password button and enter the super-user username you specified within the installer. The initial password for this account is aggregate When signing in with this method, if you do not enter the password correctly, you may need to close all your browser windows and quit your browser before you can try again.
If you have not yet changed your super-user password to something other than aggregate, the server will display This server and its data are not secure! Please change the super-user's password! at the top of the web page. Please visit the Permissions sub-tab under the Site Admin tab to change this user's password.
I've reviewed the info on under Using the Application, however when select the Log In button as suggested in (4) below the page times out on and gives me a Problem loading page: The connection was reset warning.
I'm unable to change the super-user password and to set up users since I cannot access the Site Admin tab.
Any help would be greatly appreciated.
Thank you,
Che
If the Site Admin tab is not visible, click the Log In link in the upper right corner of the screen to be presented with the Log onto Aggregate screen. Beginning with ODK Aggregate 1.4.4, the super-user account (the account with full access to the server) is an ODK Aggregate-specific account and not a Google e-mail account. Choose the Sign in with Aggregate password button and enter the super-user username you specified within the installer. The initial password for this account is aggregate When signing in with this method, if you do not enter the password correctly, you may need to close all your browser windows and quit your browser before you can try again.
If you have not yet changed your super-user password to something other than aggregate, the server will display This server and its data are not secure! Please change the super-user's password! at the top of the web page. Please visit the Permissions sub-tab under the Site Admin tab to change this user's password.
Very strange. If it was a caching issue, the separate browser would
have worked. Are you on a particularly bad connection? Can you see any
of the other Aggregate pages at all? If you have no data in the
server, you could try re-installing over your existing install.
Yaw
···
--
Need ODK consultants? https://nafundi.com provides form design, server
setup, in-field training, and software development for ODK.
The interconnection is good. I can see other pages: Form Management (Forms
List, Published Data, Submission Admin, Manually Upload Submission Data)
and Submissions (Filter Submissions, Exported Submissions) all seem to
work. I did manually upload some data, though not having used ODK Aggregate
before I'm not sure I I should be able to upload multiple media images - if
this should work, then something is wrong there.
This has been set up through Amazon's Web Services. I first tried using the
Windows ODK Aggregate Installer to create the .war file and the
create_db_and_user.sql file. I uploaded these to the proper folders on the
AWS server, but could not access the website. I tried this several times
with no luck. Next I loaded a new AWS instance and used the linux installer
for ODK Aggregate - this time I'm able to load the ODK Agreggate pages but
the login problem described in the first post is preventing me from moving
forward.
As always, we recommend you first use AppEngine so that you understand the
basic mechanics of ODK Aggregate and what all the pages should look like,
how to log into the server, etc.
When setting up your own server, first set it up without an SSL
certificate, and get that working. Then fight through configuring it to use
an SSL certificate, (re-running the ODK Aggregate installer to specify that
you have one). Unless you are familiar with setting up your own webserver
with an SSL certificate, do not attempt to immediately configure and use
SSL.
The reset could be the result of a misconfigured SSL cert or bad
hostname/port. It could also be the result of an incorrect system time.
When setting up your own server, look in the all the log files for the
server to see if there are any errors. i.e., the Tomcat logs.
Note that you need to run the create_db_and_user.sql file on the database
to create the needed tables before the server will allow you to log in.
Also, for cloud deployments, if you have a separate database server, there
is probably a configuration setting on the hosting service admin screens or
on both the webserver and database server that governs whether they can
communicate (e.g., something like a firewall setting). After you to
install the database client software on your webserver, and run it and
verify that you can connect to your database server.
···
On Mon, Oct 26, 2015 at 9:58 AM, Che Geiser wrote:
Hi Yaw,
The interconnection is good. I can see other pages: Form Management (Forms
List, Published Data, Submission Admin, Manually Upload Submission Data)
and Submissions (Filter Submissions, Exported Submissions) all seem to
work. I did manually upload some data, though not having used ODK Aggregate
before I'm not sure I I should be able to upload multiple media images - if
this should work, then something is wrong there.
This has been set up through Amazon's Web Services. I first tried using
the Windows ODK Aggregate Installer to create the .war file and the
create_db_and_user.sql file. I uploaded these to the proper folders on the
AWS server, but could not access the website. I tried this several times
with no luck. Next I loaded a new AWS instance and used the linux installer
for ODK Aggregate - this time I'm able to load the ODK Agreggate pages but
the login problem described in the first post is preventing me from moving
forward.
I tried the App Engine first but it seems that Google has changed the
procedure or terminology and I was not able to figure out how to set this
up on the App Engine.
I have set up web servers and MySQL databases before so felt that the AWS
solution made sense. I did not use an SSL certificate per the
recommendations I read on the ODK website.
For the system time, the default was UTC - which appears to be what ODK
Aggregate is set to by default from a Google search. I have created an AWS
Instance (totally fresh build) several times. I've used the Windows ODK
Aggregate Installer as well as the Linux Installer. It doesn't matter what
path I take - I get the pages to load, except the relogin page that would
give me the Site Admin access.
As this is just a test implementation on my part would it be helpful if I
provided the ip address so you can go to the site. I could create AWS
account access as well if you think there may be some sort of bug in v1.4.7
that is causing this and you want to do any troubleshooting.
As this is just a test implementation on my part would it be helpful if I
provided the ip address so you can go to the site. I could create AWS
account access as well if you think there may be some sort of bug in v1.4.7
that is causing this and you want to do any troubleshooting.
If you are having a hard time getting to the login screen, right-click on
the Log in link, and choose Open in new Tab. You should then get a login
box. See attached image.
As this is just a test implementation on my part would it be helpful if I
provided the ip address so you can go to the site. I could create AWS
account access as well if you think there may be some sort of bug in
v1.4.7
that is causing this and you want to do any troubleshooting.
Also, when running on AWS, if you are using the Elastic IP functionality,
you should run the installer and specify that IP address (or the DNS name
associated with that IP address).
When you associate that with an AWS instance, the public IP address of the
instance goes away and is invalid.
And when you stop an AWS instance, you may need to re-associate the Elastic
IP with that instance.
It very much sounds like the IP address and port that were supplied during
the installer is not matching the IP address and port that the AWS instance
and Tomcat server are reachable at.
···
On Tue, Oct 27, 2015 at 9:55 AM, Mitch Sundt wrote:
If you are having a hard time getting to the login screen, right-click on
the Log in link, and choose Open in new Tab. You should then get a login
box. See attached image.
As this is just a test implementation on my part would it be helpful if
I
provided the ip address so you can go to the site. I could create AWS
account access as well if you think there may be some sort of bug in
v1.4.7
that is causing this and you want to do any troubleshooting.
I've tried right-click on the Log in link, and choose Open in new Tab in
Firefox, Chrome and IE. It opens a new tab but eventually goes to the
"connection was reset" screen and does not provide the login box. The AWS
elastic IP is working since I can get to the various pages previously
described.
To clarify, I created the AWS instance and associated the Elastic IP with
the instance. Then I ran the ODK Aggregate Installer and entered the
Elastic IP.
There was a spot in the ODK Aggregate Installer that defaulted to port 3306
and 127.0.0.1 - I left that as the default as I thought that was correct.
Is this possibly the source of the issue? Should I be entering the Elastic
IP and 8080 here as well?
Oct 27, 2015 6:35:09 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with JAR file [/usr/share/java/tomcat6/tomcat-coyote.jar],
exists: [false], canRead: [false]
Oct 27, 2015 6:35:09 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with JAR file [/usr/share/java/tomcat6/commons-dbcp.jar],
exists: [false], canRead: [false]
Oct 27, 2015 6:35:09 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with JAR file [/usr/share/java/tomcat6/jasper-el.jar],
exists: [false], canRead: [false]
Oct 27, 2015 6:35:09 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with JAR file
[/usr/share/java/tomcat6/annotations-api.jar], exists: [false], canRead:
[false]
Oct 27, 2015 6:35:09 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with JAR file [/usr/share/java/tomcat6/jasper-jdt.jar],
exists: [false], canRead: [false]
Oct 27, 2015 6:35:09 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with JAR file
[/usr/share/java/tomcat6/tomcat6-el-2.1-api-6.0.44.jar], exists: [false],
canRead: [false]
Oct 27, 2015 6:35:09 PM org.apache.catalina.startup.ClassLoaderFactory
validateFile
WARNING: Problem with JAR file [/usr/share/java/tomcat6/commons-pool.jar],
exists: [false], canRead: [false]
No idea what is broken, but you need to fix that before anything will work.
···
=========================
The installer asks for the server hostname and port, and for the database
hostname (127.0.0.1) and port (3306).
If the database is not running on the same machine, yes, you will need to
specify something different.
To clarify, I created the AWS instance and associated the Elastic IP with
the instance. Then I ran the ODK Aggregate Installer and entered the
Elastic IP.
There was a spot in the ODK Aggregate Installer that defaulted to port
3306 and 127.0.0.1 - I left that as the default as I thought that was
correct. Is this possibly the source of the issue? Should I be entering the
Elastic IP and 8080 here as well?
I've done a totally fresh t1.micro build on AWS. This time the tomcat logs
still show some problems:
log4j:WARN No appenders could be found for logger
(org.springframework.web.context.ContextLoader).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
But the reading I found seemed to indicate there may be an issue beyond
just your typical IT stuff in setting up the server and loading the proper
components. See here:
I followed the AWS installation guide very carefully. The one place I found
a problem here: "The installation will also create an ODKAggregate.war
file. Rename this to ROOT.war and upload it to the
/usr/share/tomcat6/webapps folder. If you receive a "Permission Denied"
error, you might need to execute "chmod 666" or something similar for the
webapps folder". I had to use chmod 777 on both webapps and lib folders in
order to drop the files in using WinSCP.
Any other ideas? I've tried the Google App Engine route but the directions
seem outdated to the terminology - I get lost near the beginning where the
directions say 'Create an empty project'. This option never appears and a
search for those terms does not help either.
I've checked which versions of MySQL and Java are installed: JRE 1.7.0_91
and MySQL 5.5.45 Community Server (GPL).
At this stage, I think we should take a step back because
troubleshooting AWS *nix builds over email is the path to madness!
Let's focus instead on the GAE install. On the Google dev console, you
should have a Select a project dropdown at the top right. Click that
to get Create a project. If you get stuck, use http://pasteboard.co to
send out a screenshot.
Yaw
···
--
Need ODK consultants? https://nafundi.com provides form design, server
setup, in-field training, and software development for ODK.
I've done a totally fresh t1.micro build on AWS. This time the tomcat logs
still show some problems:
log4j:WARN No appenders could be found for logger
(org.springframework.web.context.ContextLoader).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
I followed the AWS installation guide very carefully. The one place I found
a problem here: "The installation will also create an ODKAggregate.war file.
Rename this to ROOT.war and upload it to the /usr/share/tomcat6/webapps
folder. If you receive a "Permission Denied" error, you might need to
execute "chmod 666" or something similar for the webapps folder". I had to
use chmod 777 on both webapps and lib folders in order to drop the files in
using WinSCP.
Any other ideas? I've tried the Google App Engine route but the directions
seem outdated to the terminology - I get lost near the beginning where the
directions say 'Create an empty project'. This option never appears and a
search for those terms does not help either.
I've checked which versions of MySQL and Java are installed: JRE 1.7.0_91
and MySQL 5.5.45 Community Server (GPL).
Yes, at this point, either hire someone locally to help with the AWS
install or switch to AppEngine.
···
On Wed, Oct 28, 2015 at 6:08 PM, Yaw Anokwa wrote:
Hi Che,
At this stage, I think we should take a step back because
troubleshooting AWS *nix builds over email is the path to madness!
Let's focus instead on the GAE install. On the Google dev console, you
should have a Select a project dropdown at the top right. Click that
to get Create a project. If you get stuck, use http://pasteboard.co to
send out a screenshot.
Yaw
Need ODK consultants? https://nafundi.com provides form design, server
setup, in-field training, and software development for ODK.
I've done a totally fresh t1.micro build on AWS. This time the tomcat
logs
still show some problems:
log4j:WARN No appenders could be found for logger
(org.springframework.web.context.ContextLoader).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
But the reading I found seemed to indicate there may be an issue beyond
just
your typical IT stuff in setting up the server and loading the proper
components. See here:
I followed the AWS installation guide very carefully. The one place I
found
a problem here: "The installation will also create an ODKAggregate.war
file.
Rename this to ROOT.war and upload it to the /usr/share/tomcat6/webapps
folder. If you receive a "Permission Denied" error, you might need to
execute "chmod 666" or something similar for the webapps folder". I had
to
use chmod 777 on both webapps and lib folders in order to drop the files
in
using WinSCP.
Any other ideas? I've tried the Google App Engine route but the
directions
seem outdated to the terminology - I get lost near the beginning where
the
directions say 'Create an empty project'. This option never appears and a
search for those terms does not help either.
I've checked which versions of MySQL and Java are installed: JRE 1.7.0_91
and MySQL 5.5.45 Community Server (GPL).
I've gone back and set up the project in the Google Developers Console. I've run the ODK Aggregate windows installer. The installer seemed to run fine until the Upload ODK Aggregate to Google AppEngine upload failed and gave this:
Looking for java...
found java in PATH... C:\ProgramData\Oracle\Java\javapath\java.exe
Error occurred during initialization of VM
Could not reserve enough space for 1126400KB object heap
---- WEBSITE COMPLETE - BEGIN BACKEND ----
Error occurred during initialization of VM
Could not reserve enough space for 1126400KB object heap
---END-SCRIPT-SUCCESS---
I'm not sure what this means or how to deal with this.
I have also added Java exceptions using
file://address to the ODK Installer
file://address to the folder containing the ODK Installer
file://address to folder containing the uploadAggregateToAppEngine.ha file
http://####.appspot.com where ### is the app ID (project ID)
