search

fcrepo-exts / fcrepo-vagrant

Fedora 4 Vagrant Virtual Machine
26 stars 22 forks source link

Enable karaf features to install with fcrepo-camel-toolbox:4.6.0 #55

Closed awoods closed 8 years ago

awoods commented 8 years ago

This PR enables the karaf features to install, but there still appears to be an AuthZ issue with fcrepo-serialization and fcrepo-audit.

whikloj commented 8 years ago

I can't figure out what the authHost value is supposed to be set to...

acoburn commented 8 years ago

You can leave authHost blank. Or you can set it to localhost

whikloj commented 8 years ago

@awoods I had to add feature:install fcrepo-ldpath to get Solr to work too, did you want to add that to your PR or should I open a PR against your PR?

awoods commented 8 years ago

A PR against my PR would be great... although I am surprised you would need fcrepo-ldpath since fcrepo-transform is still being used... and I was getting installation errors in karaf with fcrepo-ldpath. Anyways, are you seeing AuthZ errors in your karaf.log?

whikloj commented 8 years ago

Much tweaking and destroy/building. I am getting AuthZ errors, but I was able to resolve them by restarting the vagrant machine. Not sure what that is doing. I'll make a PR against this one and you might be able to see the problem.

awoods commented 8 years ago

Great... looking forward to the PR!

whikloj commented 8 years ago

I will note, though probably unrelated when the indexing is working I still get this error in the karaf.log

2016-08-31 02:18:26,154 | WARN  | Consumer[fedora] | EndpointMessageListener          | 65 - org.apache.camel.camel-core - 2.17.1 | Execution of JMS message listener failed. Caused by: [org.apache.camel.RuntimeCamelException - java.io.IOException: No baseURL header available!]
org.apache.camel.RuntimeCamelException: java.io.IOException: No baseURL header available!
awoods commented 8 years ago

Thanks for the PR, @whikloj. I am not seeing any relief after pulling down your PR and:

vagrant destroy
vagrant up # serialization, solr, nor fuseki working
vagrant provision # same as above

I also see an unending supply of the following error in my karaf.log:

2016-08-31 03:17:41,872 | ERROR | Consumer[fixity] | faultJmsMessageListenerContainer | 91 - org.apache.servicemix.bundles.spring-jms - 4.1.7.RELEASE_2 | Could not refresh JMS Connection for destination 'fixity' - retrying using attempting to add new Connection to the pool

Let's investigate more in the morning.

whikloj commented 8 years ago

Huh, I just tried to push a karaf-service restart to my branch, but I didn't realize you had merged already. What I was doing was

vagrant destroy
vagrant up
vagrant ssh
sudo shutdown -r now

But I'm guessing a vagrant halt and vagrant up would work too.

whikloj commented 8 years ago

Here is a diff of my branch to yours with the change I tried to push

whikloj commented 8 years ago

Add the line as a PR on your PR. https://github.com/awoods/fcrepo4-vagrant/pull/2

awoods commented 8 years ago

Shall we squash/merge and re-tag the 4.6.0 vagrant release?