RHEL6 - Tomcat deploy fails with context path error.

[ozomozo]

I managed to run the InstallHoot-CentOS-RHEL.sh script and had to tweak it to skip the Tomcat install as i already have Tomcat installed. I didnt see any errors and i can see the hootenanny-0.2.17 application in my Tomcat admin window but it cannot get deployed. I manually invoked the Start deploy button when i get this error: FAIL - Application at context path /hootenanny-services-0.2.17 could not be started. I examined the Catalina logs and it looks like the docbase at /usr/local/hoot/ingest/processed does not exist. Any thoughts ?

[dizzykc]

You can create the ingest/processed directories manually and give it 777 permissions.

"mkdir -p /usr/local/hoot/ingest/processed" "chmod 777 -R /usr/local/ingest/"

Run these two commands and that should take care of your issue.

[ozomozo]

Thanks mv but i already did that and restarted it but i get this WARNING Setting property 'docbase' to '/usr/local/hoot/ingest/processed' did not find a matching property. and then SEVERE: Context [/hootenanny-services-0.2.17] startup failed due to previous errors. My guess is a required jar may not be loading correctly.

[bwitham]

Looks like this is the related line in the script:

if ! grep -i --quiet 'ingest/processed' /etc/tomcat6/server.xml; then echo "Adding Tomcat context path for tile images" sudo sed -i.bak "s@<\/Host>@ <Context docBase=\"\/usr\/local\/hoot\/ingest\/processed\" path=\"\/static\" \/>\n &@" /etc/tomcat6/server.xml fi

Is it having problems editing /etc/tomcat6/server.xml possibly?

[brianhatchl]

@ozomozo Yeah, there's a line in the install script https://github.com/ngageoint/hootenanny/blob/master/scripts/InstallHoot-CentOS-RHEL.sh#L465-L469 that are modify the tomcat config for this path. Because you already have tomcat installed, it may have it's config files in a different location.

[ozomozo]

I manually edited the config file and added: Context allowLinking="true" docbase="/usr/local/hoot/ingest/processed" path="/static" because ultimately its what the script does. Im running Tomcat 7 though which may be the source of all my problems ?!! Also thx for all the quick responses !! [Uploading install-out.txt…]()

[dizzykc]

tomcat7 exists in /var/lib/tomcat/... whereas tomcat6 lives in /var/lib/tomcat6/

If there is an environment var called "TOMCAT6_HOME=/var/lib/tomcat6", you can modify it to say "TOMCAT6_HOME=/var/lib/tomcat" and that would propagate to all the other instances. Another option is to use Tomcat6.

[bwitham]

That should work. That script installs Tomcat 6, but you should be able to make it work with 7.

[ozomozo]

Guys ... i think i have bigger problems than Tomcat. First off i deleted my Tomcat 7 install completely and did 'yum clean all'. I tried to yum install tomcat6 tomcat6-webapps etc. It seems to install it correctly but i cant start the service up. Its a 'unrecognized service" error.

So i went back to executing the original script and ive attached the command line output redirect log as well as errors on the command line itself. I can see that some packages are not getting installed (GEOS) for example. Could this be a more fundamental permissions issue. I log in as myself and 'sudo su' to root. I have root privileges at that point on my VM. Any suggestions are welcome though the logs are pretty large and tedious and i dont blame you guys if you are busy ... out10.txt install.txt

Thanks much Oz

[bwitham]

@ozomozo A couple of questions first: Is running on centos/rhel necessary for you? The Hootenanny Ubuntu instructions are much easier to follow and less complicated than the ones for centos, which are right now are still kind of experimental. We may be close to being able to share an RPM based install with you for centos, which would make things easier, but I don't think its ready yet.

If you need to run on centos, is starting from a clean environment and running the install script a possibility?...may get rid of some of the Tomcat conflicts you're seeing right away.

As far as working from your current environment, the output in out10(1).txt looks ok to me. I didn't see any issues with it.. It looks like hoot installed correctly. However, if you're unable to start tomcat then that's obviously the first thing to focus on correcting. Seeing "unrecognized service" makes me think that the service name you're trying to start tomcat with is incorrect. Either that or there are still remnants of the tomcat 7 install around causing a conflict between the two. Hoot expects the tomcat service name to be "tomcat6", so check to see if that's what you have, launch the service, thenverify you can hit http://localhost:8080.

[ozomozo]

@bwithan Thanks for looking at the output. I figured it was experimental but i wanted to give it a shot. Unfortunately im tied to RHEL6 for now. I even attempted the Vagrant VM path and didnt succeed. Despite this i think you are right ... i should be able to deploy Tomcat independently and then comment out the Tomcat install bit (like i did earlier with Tomcat7) and retry it. Hoot seems to install correctly. When i tried this with Tomcat7 i still had deploy/missing-jars issues. I will try to start with a clean Tomcat6 install and then re-install Hoot based on this.

My goal ultimately is to use Hootenanny (and its extensive conflation algorithms) with our Oracle database which contains proprietary data. Is that even a possibility at this point ?

[bwitham]

@ozomozo Ok, sounds good. If the RPM install becomes available I'll let you know. Until then, keep using the script to install.

Hoot doesn't have the capability to interact with data in Oracle afaik, but if you can get your data converted to one of the supported formats...shape, osm, file geodb, postgres, etc. as an intermediate step, then you'll be good to go.

[ozomozo]

@bwitham I already have a mechanism built in that queries and generates GeoJSON and shapefiles. I was able to import them into both ESRI and MapBox. The idea here is to use our Oracle data and sort of leverage the extensive Hoot conflation algorithms at its source. Regardless, even if we can simply push our shapefiles into Hoot i would consider that a success as i can use your client based software i presume for analysis and display. I may have to read more into it but i kinda got bogged down with implementation.

So i reinstalled Tomcat7 and moved the hoot-services.war file into the webapps directory manually. As expected Tomcat explodes the war on startup and creates a dir and i can see Hoot in the Manager App. However when i try 'start' the app i get errors (compressed for brevity). Ex:

FINE: Sending application start events Feb 03, 2016 9:30:12 AM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class hoot.services.HootServletContext javax.ws.rs.WebApplicationException at hoot.services.utils.ResourceErrorHandler.handleError(ResourceErrorHandler.java:49) at hoot.services.controllers.ogr.TranslatorResource.startTranslationService(TranslatorResource.java:240) at hoot.services.HootServletContext.contextInitialized(HootServletContext.java:42) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5077) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5591) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) .........

Feb 03, 2016 9:30:12 AM org.apache.catalina.core.StandardContext filterStop FINE: Stopping filters Feb 03, 2016 9:30:12 AM org.apache.catalina.core.StandardContext listenerStop SEVERE: Exception sending context destroyed event to listener instance of class hoot.services.HootServletContext java.lang.NullPointerException at hoot.services.HootServletContext.contextDestroyed(HootServletContext.java:51) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5124) at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5786) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:232) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:160) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) ....... Feb 03, 2016 9:30:12 AM org.apache.catalina.core.StandardContext listenerStart FINE: Sending application start events

[bwitham]

@ozomozo The idea for your approach on how to integrate with hoot sounds good.

Regarding the error output...not quite enough to go on there...not sure what's causing that null pointer exception. If possible, let's change the logging configuration file in hoot-services under tomcat, so we can get some more info. File is at: hoot-services/WEB-INF/class/log4j.xml (path approximate).

Change this:

`

` to this: ` ` (we can knock it down again to "debug" if needed later). restart tomat and then send me the log output again. thanks.

[ozomozo]

@bwitham Ive attached the logs after the above step. localhost.2016-02-03.info.txt catalina.2016-02-03.txt

[bwitham]

This one is unrelated to the exception:

WARNING: [SetContextPropertiesRule]{Context} Setting property 'docbase' to '/usr/local/hoot/ingest/processed' did not find a matching property.

But can you verify that /usr/local/hoot/ingest/processed exists? If not, create it. If it does, post that tomcat file with that docBase property in it.

For the exception it looks like the nodejs service which performs on the fly tag translations is not starting up, but the error occurring as a result didn't get logged for some reason. @jchoi1267 Looking at the last localhost output posted, do you have any idea why the translation service wouldn't be starting? Could it be a port issue?

@ozomozo In the hoot-services.conf file under the hoot-services tomcat dir, there are the settings "translationServerPort" and "P2PServerPort". Verify the ports configured there aren't possibly already in use by some other process and that they aren't being prevented from being opened by a firewall, etc. thanks.

[ozomozo]

@bwitham I verified the ports and they are different. Since the Context issue is a WARNING im guessing we can ignore it but i do have the ingest/processed dir created already.

If i recollect correctly i did have errors with node.js but i think it got fixed. I could rerun the Install with FUO translations turned on if thats needed.

[bwitham]

@ozomozo Did you check to see if those two ports aren't being used by some other non Hootenanny process (some combination of netstat or lsof should do the trick for that)? If so, the port numbers can be changed in the configuration file to something not already in use.

Also, are you running a firewall locally? If so, use iptables to make sure the two ports can be connected to through the firewall (example with the tomcat port is shown in the script). thanks.

[ozomozo]

@bwitham I actually changed the ports just in case and also made sure the ipTables persisted. We definitely have severe local firewall issues and im not too familiar with networks but i can take a look at that. In the meanwhile this is slightly modded install script to accomodate a couple of small tweaks for non-functioning rpm downloads.

InstallHoot-CentOS-RHEL.sh.txt out-12.txt

[bwitham]

@ozomozo Ok, you're still seeing the problem with the translation server when connecting to the Hootenanny UI? I'll try to round up someone more knowledgeable in that area tomorrow.

[brianhatchl]

@ozomozo Can you shutdown tomcat and try to start the node translation server manually?

sudo service tomcat6 stop
cd /pathto/hoot
source SetupEnv.sh
cd scripts
node TranslationServer.js

There is no logging on startup, but doing ps -ef | grep node should show several node processes for TranslationServer.js

vagrant@vagrant-ubuntu-trusty-64:~$ ps -ef | grep node
vagrant   3108  2763  0 14:30 pts/1    00:00:00 node TranslationServer.js
vagrant   3110  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3111  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3112  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3113  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3114  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3115  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3116  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3117  3108  0 14:30 pts/1    00:00:00 /usr/bin/nodejs /home/vagrant/hoot/scripts/TranslationServer.js
vagrant   3215  3180  0 14:35 pts/3    00:00:00 grep --color=auto node

To test the server is up and running do curl http://localhost:8233/capabilities (8233 is the default port in the TranslationServer.js file, but gets set to 8094 by tomcat). The result should be:

{"TDSv40":{"isvailable":"true"},"TDSv61":{"isvailable":"true"}}

[ozomozo]

@brianhatchl There is definitely an issue with node translation. To begin with it doesnt recognize 'node' command. Its possible it did not install correctly and didnt log it either. Si it fails at this command "node TranslationServer.js" with a "node: command not found" message. Also i looked at the script and i cant find "/usr/local/lib/node_modules" directory either on my VM. Im executing the script as 'root'. I log in as myself and su to root.

[ozomozo]

@brianhatchl Ok i discovered several inconsistencies on my VM. The 'npm' command didnt work. So i tried to install node and its dependencies from http://tecadmin.net/setup-node-js-on-centos-rhel-6-with-example/#. Turns out i can download that tar file directly from the browser (http) but wget returns a 404 error. I tried 'curl -R -O' option and same issue. Anyways i managed to manually downlaod it and install it. I need to figure out how to configure it so it recognizes 'npm' etc.

[brianhatchl]

npm (node package manager) is another package (separate from nodejs) that should have been installed by the shell script.

[dizzykc]

npm, nodejs, and nodejs-devel are installed in the beginning of the script from the yum repo.

[ozomozo]

I ran thos install individually and was able to run the node cmd, but executing "node TranslationServer.js" results in this error: [root@red-rhel6 scripts]# node TranslationServer.js

module.js:340 throw err; ^ Error: Cannot find module 'undefined/lib/HootJs' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object. (/root/hootenanny-0.2.17/scripts/TranslationServer.js:15:8) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10)

[bwitham]

@ozomozo 'source $HOOT_HOME/SetupEnv.sh' and then rerun the node command

[ozomozo]

@bwitham I now get a slightly modified error. Im guessing the path is wrong ... it should be '/root/hootenanny-0.2.17/scripts/TranslationServer.js' ?

module.js:340 throw err; ^ Error: Cannot find module '/root/hootenanny-0.2.17/TranslationServer.js' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Function.Module.runMain (module.js:497:10) at startup (node.js:119:16) at node.js:929:3

[brianhatchl]

actually, it's HOOT_HOME that's not yet defined. SetupEnv.sh will do that (among other things).

cd /pathto/hoot
source SetupEnv.sh
cd scripts
node TranslationServer.js

[brianhatchl]

you need to be in the hoot/scripts directory to run node TranslationServer.js

[ozomozo]

You guys have been great !!

[ozomozo]

@brianhatchl @bwitham Now this: node TranslationServer.js

module.js:340 throw err; ^ Error: Cannot find module '/root/hootenanny-0.2.17/lib/HootJs' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object. (/root/hootenanny-0.2.17/scripts/TranslationServer.js:15:8) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10)

[brianhatchl]

does the file /root/hootenanny-0.2.17/lib/HootJs.node exist?

[ozomozo]

I was just gonna edit my prev post. The lib dir doesnt exist (/root/hootenanny-0.2.17/lib)

[brianhatchl]

Hmm, I'm skeptical that the build succeeded then. Here's an ls of my HOOT_HOME dir:

aclocal.m4        hoot-js               output.osm
AUTHORS           hoot-main             patches
autom4te.cache    hoot-rnd              patches.txt
bin               hoot-services         plugins
ChangeLog         hoot-test             plugins-local
ChangeLog.md      hoot-translate        pom.xml
conf              hoot-ui               pretty-pipes
config.guess      HOOT_VERSION_FILE     README
config.h          HOOT_VERSION_GEN      README.md
config.h.in       ingest                RebuildServices
config.h.in~      INSTALL               renderdb-export-server
config.log        install-sh            report
config.status     lib                   rules
config.sub        libtool               scripts
configure         LICENSE               SetupEnv.sh
configure.ac      LicenseTemplate.txt   stamp-h1
Configure.pri     LocalConfig.pri       stub
Configure.pri.in  LocalConfig.pri.orig  tbs
COPYING           ltmain.sh             templates
customscript      m4                    test-files
data              Makefile              test-output
depcomp           Makefile.am           tgs
distribution      Makefile.in           tmp
docs              Makefile.inc          translations
fouo              Makefile.inc.in       translations-local
GPLv3             Makefile.old          upload
hoot-cmd          Makefile.qmake        Vagrantfile
hoot-core         missing               Vagrant.marker
hoot-core-test    NEWS                  VAGRANT.md
Hootenanny.pro    node-mapnik-server    VagrantProvision.sh
hoot-hadoop       npm-debug.log         valgrind.supp

How does yours compare?

[ozomozo]

Here you go. I think you are right.

-rw-rw-r--. 1 tom.daley 1000 344041 Jul 22 2015 aclocal.m4 -rw-rw-r--. 1 root root 33 Jul 22 2015 AUTHORS -rw-rw-r--. 1 root root 0 Jul 22 2015 ChangeLog drwxrwxr-x. 5 root root 4096 Jul 22 2015 conf -rwxrwxr-x. 1 root root 44826 Jul 22 2015 config.guess -rw-rw-r--. 1 tom.daley 1000 5733 Jul 22 2015 config.h.in -rwxr-xr-x. 1 tomcat tomcat 25992 Jan 27 13:47 config.log -rwxrwxr-x. 1 root root 35454 Jul 22 2015 config.sub -rwxrwxr-x. 1 tom.daley 1000 659647 Jul 22 2015 configure -rw-rw-r--. 1 root root 4812 Jul 22 2015 configure.ac -rw-rw-r--. 1 root root 997 Jul 22 2015 Configure.pri.in -rw-rw-r--. 1 root root 12 Jul 22 2015 COPYING -rwxrwxr-x. 1 root root 20334 Jul 22 2015 depcomp drwxrwxr-x. 3 root root 4096 Jul 22 2015 distribution drwxrwxr-x. 8 tom.daley 1000 4096 Jul 22 2015 docs -rw-rw-r--. 1 root root 70293 Jul 22 2015 GPLv3 drwxrwxr-x. 3 root root 4096 Jul 22 2015 hoot-cmd drwxrwxr-x. 3 tom.daley 1000 4096 Jul 22 2015 hoot-core drwxrwxr-x. 3 root root 4096 Jul 22 2015 hoot-core-test -rw-rw-r--. 1 root root 360 Jul 22 2015 Hootenanny.pro drwxrwxr-x. 3 root root 4096 Jul 22 2015 hoot-hadoop drwxrwxr-x. 3 root root 4096 Jul 22 2015 hoot-js -rw-rw-r--. 1 root root 70293 Jul 22 2015 hoot-main drwxrwxr-x. 3 root root 4096 Jul 22 2015 hoot-rnd drwxrwxr-x. 3 root root 4096 Jul 22 2015 hoot-services drwxrwxr-x. 3 root root 4096 Jul 22 2015 hoot-test drwxrwxr-x. 6 root root 4096 Jul 22 2015 hoot-translate drwxrwxr-x. 10 root root 4096 Jul 15 2015 hoot-ui -rwxrwxr-x. 1 root root 1638 Jul 22 2015 HOOT_VERSION_GEN -rw-rw-r--. 1 root root 48 Jul 22 2015 INSTALL -rw-rw-r--. 1 root root 8621 Jul 22 2015 INSTALL-CentOS6.5-PG9.1.txt -rw-rw-r--. 1 root root 507 Jul 22 2015 INSTALL-CentOS6.5-PG9.1.txt.rej -rw-rw-r--. 1 root root 0 Jul 22 2015 install-sh -rw-rw-r--. 1 root root 35142 Jul 22 2015 LICENSE -rw-rw-r--. 1 root root 1044 Jul 22 2015 LicenseTemplate.txt drwxrwxr-x. 3 root root 4096 Jul 22 2015 local -rw-rw-r--. 1 root root 256 Jul 22 2015 LocalConfig.pri.orig -rw-rw-r--. 1 root root 283680 Jul 22 2015 ltmain.sh drwxrwxr-x. 2 root root 4096 Jul 22 2015 m4 -rw-rw-r--. 1 root root 2906 Jul 22 2015 Makefile.am -rw-rw-r--. 1 tom.daley 1000 28605 Jul 22 2015 Makefile.in -rw-rw-r--. 1 root root 30 Jul 22 2015 Makefile.inc.in -rw-rw-r--. 1 root root 12394 Jul 22 2015 Makefile.old -rw-rw-r--. 1 root root 531 Jul 22 2015 Makefile.old.rej -rwxrwxr-x. 1 root root 10346 Jul 22 2015 missing -rw-rw-r--. 1 root root 25 Jul 22 2015 NEWS -rw-rw-r--. 1 root root 391 Jul 22 2015 patches.txt drwxrwxr-x. 3 tom.daley 1000 4096 Jul 22 2015 plugins -rw-rw-r--. 1 root root 4517 Jul 22 2015 pom.xml drwxrwxr-x. 5 root root 4096 Jul 22 2015 pretty-pipes -rw-rw-r--. 1 root root 14 Jul 22 2015 README -rw-rw-r--. 1 root root 4155 Jul 22 2015 README.md -rwxrwxr-x. 1 root root 531 Jul 22 2015 RebuildServices drwxrwxr-x. 3 root root 4096 Jul 22 2015 report drwxrwxr-x. 4 root root 4096 Jul 22 2015 rules drwxrwxr-x. 2 root root 4096 Jul 22 2015 scripts -rwxrwxr-x. 1 root root 123 Jul 22 2015 SetupEnv.sh drwxrwxr-x. 2 root root 4096 Jul 22 2015 stub drwxrwxr-x. 3 root root 4096 Jul 22 2015 tbs drwxrwxr-x. 3 root root 4096 Jul 22 2015 templates lrwxrwxrwx. 1 root root 36 Feb 3 16:04 test-files -> ./hoot-core-test/src/test/resources/ drwxrwxr-x. 3 root root 4096 Jul 22 2015 tgs drwxrwxr-x. 2 root root 4096 Jul 22 2015 translations -rw-rw-r--. 1 root root 3522 Jul 22 2015 Vagrantfile -rw-rw-r--. 1 root root 702 Jul 22 2015 Vagrantfile.rej -rw-rw-r--. 1 root root 2125 Jul 22 2015 VAGRANT.md -rw-rw-r--. 1 root root 1946 Jul 22 2015 VAGRANT.md.rej -rw-rw-r--. 1 root root 8477 Jul 22 2015 VagrantProvision.sh -rw-rw-r--. 1 root root 123440 Jul 22 2015 valgrind.supp -rw-rw-r--. 1 tom.daley 1000 7 Jul 22 2015 version

[brianhatchl]

Can you try running:

aclocal && autoconf && autoheader && automake && ./configure -q --with-rnd --with-services
make clean
make

[ozomozo]

aclocal && autoconf && autoheader && automake && ./configure -q --with-tnd --with-services configure.ac:4: error: Autoconf version 2.65 or higher is required configure.ac:4: the top level autom4te: /usr/bin/m4 failed with exit status: 63 aclocal: autom4te failed with exit status: 63

'yum list autoconf' returns: autoconf.noarch 2.63-5.1.el6 'yum list automake' returns: automake.noarch 1.11.1-4.el6 aclocal and autoheader return 'no matching packages' msg.

[brianhatchl]

Autoconf version 2.65 or higher is required

I'm not running CentOS, but my autoconf version is:

vagrant@vagrant-ubuntu-trusty-64:~/hoot$ autoconf --version
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.

autoconf is something the install script should take care of. With your setup, are you running the InstallHoot-CentOS-RHEL.sh script?

[brianhatchl]

@mv003348 might have some better guidance as he's working our own CentOS deployment

[ozomozo]

Im running RHEL6 and dont have an option VM's are tightly controlled). 2.63 seems to be the latest and highest version on RHEL. This may be the issue thats breaking it.

And yes im running the InstallHoot-CentOS-RHEL.sh script.

[brianhatchl]

Definitely. I don't think anyone has tried to deploy Hoot on RHEL6, so it's unknown what and how much will break.

[bmarchant]

@ozomozo you might want to try to build the latest autoconf since we haven't deployed on RHEL6.

cd ~
wget http://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.gz
tar xzvf autoconf-2.69.tar.gz
cd autoconf-2.69/
./configure
make
make install

That should at least get you the right version of autoconf. We've got a CentOS 6 RPM but not a RHEL6 RPM.

[ozomozo]

@bmarchant @brianhatchl I was able to install the 2.69 version using the above commands. But i get the same errors. Its likely its not pcking up the new path for autoconf. correction I made a symbolic link that points to the new autorun directory. So now my autorun is upgraded.

[brianhatchl]

What does autoconf --version show? What about which autoconf?

[bmarchant]

@ozomozo removing v 2.63 is probably a good first step sudo yum remove autoconf

Then try repeating make install You may actually need to do that as root if you get a permission denied sudo make install

[ozomozo]

@brianhatchl @bmarchant

autoconf --version shows it as 2.69

which autoconf : /usr/bin/autoconf

I did a 'yum remove autoconf' to get rid of traces of 2.65 and it looks like it blew away aclocal.

[ozomozo]

@brianhatchl @bmarchant Removing autoconf removes aclocal and automake and autom4te. I tried to make copies and copy it back into /usr/bin along with the 2.69 version of autoconf but it looks messy. I ran this: aclocal && autoconf && autoheader && automake && ./configure -q --with-rnd --with-services

And the errors:

Can't locate Automake/Config.pm in @INC (@INC contains: /usr/share/automake-1.11 /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/bin/aclocal line 37. BEGIN failed--compilation aborted at /usr/bin/aclocal line 37.

[bmarchant]

The automake package contains aclocal sudo yum install automake

[ozomozo]

It also re-installs autoconf 2.63 unfortunately. Im not sure how i can split it.

[bmarchant]

Using something like the following when making autoconf 2.69 should give you some insight into what the install is doing: make SHELL='sh -x' install