Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Solution Pack objects not installed #84

Closed
McFateM opened this issue Dec 18, 2017 · 9 comments
Closed

Solution Pack objects not installed #84

McFateM opened this issue Dec 18, 2017 · 9 comments

Comments

@McFateM
Copy link
Member

McFateM commented Dec 18, 2017

I'm creating a new ISLE build on my MacBook using the instructions at https://islandora-collaboration-group.github.io/ISLE/1_system_process_overview/1_4_testing/alpha_quickstart/ and all appears to be OK until running the ./install_site.sh script. There I'm getting lots of errors, one for every content model I believe, like this one...

islandora_web_archive: Did not install any objects. Could not connect to the repository. Please check the settings on the Islandora configuration page and install the required objects manually on the Solution Pack admin page.   [error]

I'm not sure what might be wrong here, but I believe I've seen the effect of this before. In a previous build, not sure where anymore, we found that many metadata forms were not present, almost as though some of the solution pack objects had not been installed.

I will continue on with this build, but am wondering if we need to insert a step into the build process to ensure that the repository is working BEFORE the solution packs are installed? If others agree, how might we implement such a check?
@McFateM
Copy link
Member Author

McFateM commented Dec 18, 2017

Could this be our race condition in play? Since this was not the first time starting the containers I just did a 'docker-compose up -d' rather than starting them in the prescribed order.

@g7morris
Copy link
Member

@McFateM This feels like a race condition for sure. Having recently rebuilt and tested on Friday, I did not encounter this as I didn't use docker-compose up -d instead launching each container individually.

@g7morris
Copy link
Member

I don't know why this matters as most of the solution packs are installed later AFTER the containers spin up.

@McFateM
Copy link
Member Author

McFateM commented Dec 18, 2017 via email

@g7morris
Copy link
Member

@McFateM I'm not sure how to do that as an automated call as the script would need to poll tomcat and see if the webapp fedora is running? Perhaps some tomcat folks could advise here.

One can check http://fedora:8080/manager/html and restart the fedora service manually in case of this failure.

I can say from experience I"ve encountered random fedora service stops but not on ISLE (yet).

@McFateM
Copy link
Member Author

McFateM commented Dec 18, 2017 via email

@g7morris
Copy link
Member

@McFateM We can include it in the documentation for sure. Will revise this week.

@DiegoPino
Copy link

DiegoPino commented Dec 18, 2017 •
edited
Loading

Hi,

My 2cents

I have seen this issue with failed tuque connections/wrong authentication/XACML problems, but not on fresh ISLE deployments.

A simple way to check if Fedora is running (which won't mean always Islandora is able to actually connect to Fedora, there could be even drupal filter authentication issues that hinder the SP object´s to be deployed?) would be to run a bash script like

#/bin/bash
checkifalive_response=$(curl -sL -w "%{http_code}"   "http://fedora:8080/fedora" -o /dev/null --connect-timeout 3 --max-time 10)

if [ "$checkifalive_response" == "200" ] ;
then
   echo "continue"
else
   echo "KABOOM"
fi

To make sure islandora is connecting to fedora, i would prefer a simple PHP script that actually bootstraps Drupal/tuque and uses a real fedora user. Simply to code.

PS: Nothing here is something I invented, mostly copy and pasted from some random forums. I actually like the idea of services being checked instead of only being assumed running.

g7morris added a commit that referenced this issue Jan 24, 2018
@g7morris
Updated alpha_quickstart.md per Issue #84
a958fe3
@g7morris
Copy link
Member

Closing ticket as @McFateM 's original request to have plain wording advising the enduser to manually check if the fedora service is running has been added to the alphaquickstartguide.md with this commit Not merged to master yet

marksandford added a commit to ColgateUniversity/ISLE that referenced this issue May 20, 2019
@marksandford
Merge pull request Islandora-Collaboration-Group#84 from Islandora-Co…
abdcaa3 
…llaboration-Group/marksandford-patch-2

Cleaning up bad merge
g7morris added a commit to Born-Digital-US/ISLE that referenced this issue Oct 22, 2019
@g7morris
Updated alpha_quickstart.md per Issue Islandora-Collaboration-Group#84
7b83cbc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@g7morris @DiegoPino @McFateM