Can't steup hootenanny by vagrant on windows

[mapsearcher]

Hello everybody,

I followed the installation steps: https://github.com/ngageoint/hootenanny/blob/master/docs/user/VAGRANT.md But when I execute vagrant.exe up in a git bash, I always receive following error code:

. . . default: default: Updated: default: tomcat8.noarch 0:8.5.51-1.el7 default: default: Complete! default: ######## End tomcat8 installation ######## default: ### Installing node-export-server... The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

I am able to connect via ssh but after executing

vagrant ssh cd hoot source ./SetupEnv.sh

there is no hoot binary available that I could call.

Could you please help me with this?

Thank you!

[mattjdnv]

Hi, Looking at the VagrantProvisionCentOS7.sh script, the install might have died trying to install NodeJS. https://github.com/ngageoint/hootenanny/blob/22d686e0a89758f3c399b33ede3edd9d69153bd5/VagrantProvisionCentOS7.sh#L303

Since the install died, it didn't build the hoot binary. which is why you can'y run it.

You could try:

• ssh into the vagrant box
• Run the remaining commands from the VagrantProvisionCentOS7.sh script
• Run the 'VagrantBuild.sh' script
• Then 'sudo systemctl restart tomcat8'

[mapsearcher]

Thanks for the fast reply, I tried to do so but now I receive following error:

[vagrant@centos7-hoot hoot]$ ./VagrantBuild.sh HOOT_HOME: /home/vagrant/hoot "### Configuring Hoot... HOOT_HOME: /home/vagrant/hoot configure.ac:7: installing './missing' configure: error: cannot run /bin/sh ./config.sub

[mattjdnv]

Hmmmmm. I have not seen that error . Also, I have not tried building Hootenanny on windows. We mainly use Ubuntu or Centos7

Going for a bit of a google crawl came up with this: https://stackoverflow.com/questions/24168165/configure-error-cannot-run-bin-sh

I usually work on a Centos7 box. I have a Windows10 laptop but I can't put Vagrant on it - my IT folks won't allow it. I'll keep digging and see what I can find.

Are you wanting to just run Hootenanny or are you interested in building it from source/developing it?

[mapsearcher]

I just want to run it.

Sent from my iPhone

On 1. Sep 2020, at 19:18, Matt Jackson notifications@github.com wrote:



Hmmmmm. I have not seen that error . Also, I have not tried building Hootenanny on windows. We mainly use Ubuntu or Centos7

Going for a bit of a google crawl came up with this: https://stackoverflow.com/questions/24168165/configure-error-cannot-run-bin-sh

I usually work on a Centos7 box. I have a Windows10 laptop but I can't put Vagrant on it - my IT folks won't allow it. I'll keep digging and see what I can find.

Are you wanting to just run Hootenanny or are you interested in building it from source/developing it?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/ngageoint/hootenanny/issues/4223#issuecomment-685011309, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMIF5SAY4QKDHPC4L235443SDUUETANCNFSM4QRZ7ABQ.

If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.

[mattjdnv]

Have a look at the VagrantFile and provisioning script in branch 4225. It will get merged into the master branch after the pull request is reviewed. It installs Hootenanny from RPM's and skips the whole build from source part.

[mapsearcher]

Hi,

I checked out 4225 but I still get following error: Could you try to run the process yourself on a windows machine? On a ubuntu box it worked fine for me...

default: default: Verifying : libcurl-7.29.0-54.el7.x86_64 3/4 default: default: Verifying : curl-7.29.0-54.el7.x86_64 4/4 default: default: default: Updated: default: curl.x86_64 0:7.29.0-57.el7_8.1 default: default: Dependency Updated: default: libcurl.x86_64 0:7.29.0-57.el7_8.1 default: default: Complete! default: ### Add Hoot repo ### default: ### Add pgdg repo ### default: ### Installing hootenanny-core ### default: Loaded plugins: fastestmirror, versionlock default: Loading mirror speeds from cached hostfile default: base: mirror.eu.oneandone.net default: epel: mirror.imt-systems.com default: extras: mirror.netcologne.de default: updates: mirror.checkdomain.de default: Excluding 2 updates due to versionlock (use "yum versionlock status" to show them) default: No package hootenanny-core available. default: Error: Nothing to do default: ### Done ### default: /tmp/vagrant-shell: line 49: hoot: command not found The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

Thx.

Br mapsearcher

[mattjdnv]

@mapsearcher I found the problem. I didn't have the right repo set which is why the install failed. When it ran cleanly on my development box I assumed that the script was correct. The fixes have been merged into the master branch.

[d3netxer]

which is the right repo to be set @mattjdnv?

[d3netxer]

as an update, the reason I had the same error was because symbolic links did not work with vagrant on Windows, and symbolic links were being created when the npm install command was run. The same issue appeared here: https://github.com/ngageoint/hootenanny/issues/3527