Hello!
After playing around with the VM installation of ODK Aggregate, I have been
trying to configure it on a physical machine that is running Ubuntu 14.04
with Tomcat 8.
I tried downloading and installing the Aggregate 1.4.13 .run file (multiple
times after verifying the file size/checksum etc.). Each time, the system
would give me "*cannot execute binary file: Exec format error". *
I tried downloading the 1.4.12 .run file and it installs just fine. But
then, since I am running tomcat 8, I am unable to figure out how to make it
work since the install page distinctly says that Aggregate 1.4.12 will not
work with Tomcat 8 without the following modification. I am getting the
error "You do not have permission for this action. Error: Invalid request"
when accessing the application.
From a user:
My ODK Aggregate file is installed as
/var/lib/tomcat8/webapps/ODKAggregate.war
The following content needed to be placed in the file
webapps/ODKAggregate/META-INF/context.xml (this is within the expanded
content of the war file, once the Tomcat 8 server has exploded it).
The problem is, there is no context.xml file in my webapps/ODKAggregate/META-INF/ folder. Even if I create one and put only the line saying "", it does not help.
Has anyone actually tried (or can try) installing the Aggregate 1.4.13 on a x64 machine that is running tomcat 8?
Or a somewhat detailed explanation of what to do with the context.xml file would be very helpful too.
I've been able to install ODK 1.4.13 (x64, sha256:
cbff6e5eb0b9dad0c50b1faa73cfdbe1b52cf3285568a421b5e640aa1859d6dd) on
Ubuntu 16 from the command line.
In the past when I've run older versions of Aggregate on Tomcat 8,
adding the context.xml file has worked great. I usually add it inside
the WAR, but it should also work by adding the file directly to the
exploded WAR and setting the appropriate permissions. Maybe then
remove the WAR so it can't overwrite the exploded folder and reboot.
Start from your logs and see if there are any hints there about what,
if anything, is wrong.
Yaw
···
On Sun, Feb 19, 2017 at 8:45 PM, Gaurav Kumar wrote:
> Hello!
> After playing around with the VM installation of ODK Aggregate, I have been
> trying to configure it on a physical machine that is running Ubuntu 14.04
> with Tomcat 8.
>
> I tried downloading and installing the Aggregate 1.4.13 .run file (multiple
> times after verifying the file size/checksum etc.). Each time, the system
> would give me "cannot execute binary file: Exec format error".
>
> I tried downloading the 1.4.12 .run file and it installs just fine. But
> then, since I am running tomcat 8, I am unable to figure out how to make it
> work since the install page distinctly says that Aggregate 1.4.12 will not
> work with Tomcat 8 without the following modification. I am getting the
> error "You do not have permission for this action. Error: Invalid request"
> when accessing the application.
>
>> From a user:
>> My ODK Aggregate file is installed as
>> /var/lib/tomcat8/webapps/ODKAggregate.war
>> The following content needed to be placed in the file
>> webapps/ODKAggregate/META-INF/context.xml (this is within the expanded
>> content of the war file, once the Tomcat 8 server has exploded it).
>>
>
>
> The problem is, there is no context.xml file in my
> webapps/ODKAggregate/META-INF/ folder. Even if I create one and put only the
> line saying "", it does not help.
>
>
> Has anyone actually tried (or can try) installing the Aggregate 1.4.13 on a
> x64 machine that is running tomcat 8?
>
>
> Or a somewhat detailed explanation of what to do with the context.xml file
> would be very helpful too.
>
>
> Cheers!
>
> Gaurav
>
>
>
> --
> --
> 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.
I must admit my stupidity. I had been trying out Aggregate on a virtualbox
that was x64 machine. I completely forgot that the production machine
(physical server) that I intended to deploy the final version of Aggregate
was a 32 bit machine. It did not click despite multiple helpful pages
pointed out that "*cannot execute binary file: Exec format error" *was an
error that happened only when you run a 64 bit .run file on a 32 bit
machine.
I was able to deploy Aggregate successfully using the 32 bit installer.
Cheers!
Gaurav
···
On Tuesday, February 21, 2017 at 7:11:35 AM UTC+5:30, Yaw Anokwa wrote:
>
> Hi Gaurav,
>
> I've been able to install ODK 1.4.13 (x64, sha256:
> cbff6e5eb0b9dad0c50b1faa73cfdbe1b52cf3285568a421b5e640aa1859d6dd) on
> Ubuntu 16 from the command line.
>
> The command I used was: ./ODK-Aggregate-v1.4.13.run --mode unattended
> --parent_installdir /tmp --platform mysql --tomcat_http_port 80
> --tomcat_https_port 443 --raw_hostname 0.0.0.0 --database_port 3306
> --database_hostname 127.0.0.1 --jdbc_username db_user --jdbc_password
> db_pass --jdbc_database odk_prod --instance_display_name 0.0.0.0
> --username admin --app_id '' --master_slave_app_id ''
> --jdbc_sqlserver_url '' --jdbc_gae_mysql_instance_name ''
> --jdbc_gae_mysql_password ''"
>
> If you want to try this yourself, I have a Vagrant/ansible setup at
> https://github.com/nafundi/odk-aggregate-vagrant.
>
> In the past when I've run older versions of Aggregate on Tomcat 8,
> adding the context.xml file has worked great. I usually add it inside
> the WAR, but it should also work by adding the file directly to the
> exploded WAR and setting the appropriate permissions. Maybe then
> remove the WAR so it can't overwrite the exploded folder and reboot.
>
> Start from your logs and see if there are any hints there about what,
> if anything, is wrong.
>
> Yaw
>
> On Sun, Feb 19, 2017 at 8:45 PM, Gaurav Kumar <gaura...@gmail.com > wrote:
> > Hello!
> > After playing around with the VM installation of ODK Aggregate, I have
> been
> > trying to configure it on a physical machine that is running Ubuntu
> 14.04
> > with Tomcat 8.
> >
> > I tried downloading and installing the Aggregate 1.4.13 .run file
> (multiple
> > times after verifying the file size/checksum etc.). Each time, the
> system
> > would give me "cannot execute binary file: Exec format error".
> >
> > I tried downloading the 1.4.12 .run file and it installs just fine. But
> > then, since I am running tomcat 8, I am unable to figure out how to make
> it
> > work since the install page distinctly says that Aggregate 1.4.12 will
> not
> > work with Tomcat 8 without the following modification. I am getting the
> > error "You do not have permission for this action. Error: Invalid
> request"
> > when accessing the application.
> >
> >> From a user:
> >> My ODK Aggregate file is installed as
> >> /var/lib/tomcat8/webapps/ODKAggregate.war
> >> The following content needed to be placed in the file
> >> webapps/ODKAggregate/META-INF/context.xml (this is within the expanded
> >> content of the war file, once the Tomcat 8 server has exploded it).
> >>
> >
> >
> > The problem is, there is no context.xml file in my
> > webapps/ODKAggregate/META-INF/ folder. Even if I create one and put only
> the
> > line saying "", it does not help.
> >
> >
> > Has anyone actually tried (or can try) installing the Aggregate 1.4.13
> on a
> > x64 machine that is running tomcat 8?
> >
> >
> > Or a somewhat detailed explanation of what to do with the context.xml
> file
> > would be very helpful too.
> >
> >
> > Cheers!
> >
> > Gaurav
> >
> >
> >
> > --
> > --
> > Post: opend...@googlegroups.com
> > Unsubscribe: opendatakit...@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...@googlegroups.com .
> > For more options, visit https://groups.google.com/d/optout.
>