Camel/Karaf indexing errors when FEDORA_AUDIT=false

[bbpennel]

While trying to turn down some of the extra settings in the VM, I've run across an issue where it appears that setting FEDORA_AUDIT to false here triggers an error in the karaf logs every time I create an object, which seems to be having a measurable impact on server performance (although oddly I am still getting a lot of triples in fuseki). I've tested with an unmodified fcrepo-vagrant instance and one with this property set to false, and the error below only occurs with it set to false.

$ curl -is -X PUT 127.0.0.1:8080/fcrepo/rest/object

And then in /opt/karaf/data/log/karaf.log I see:

2016-02-04 19:50:17,166 | WARN  | Consumer[fedora] | EndpointMessageListener          | 62 - org.apache.camel.camel-core - 2.15.1 | Execution of JMS message listener failed. Caused by: [org.apache.camel.R
untimeCamelException - org.fcrepo.camel.FcrepoOperationFailedException: HTTP operation failed invoking http://localhost:8080/fcrepo/rest/object/fcr:transform/default with statusCode: 400 and message: Bad 
Request]
org.apache.camel.RuntimeCamelException: org.fcrepo.camel.FcrepoOperationFailedException: HTTP operation failed invoking http://localhost:8080/fcrepo/rest/object/fcr:transform/default with statusCode: 400 
and message: Bad Request
        at org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1619)[62:org.apache.camel.camel-core:2.15.1]
        at org.apache.camel.component.jms.EndpointMessageListener$EndpointMessageListenerAsyncCallback.done(EndpointMessageListener.java:186)[64:org.apache.camel.camel-jms:2.15.1]
        at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:107)[64:org.apache.camel.camel-jms:2.15.1]
        at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:569)[90:org.apache.servicemix.bundles.spring-jms:3.2.14.RELEASE_1]
...
Caused by: org.fcrepo.camel.FcrepoOperationFailedException: HTTP operation failed invoking http://localhost:8080/fcrepo/rest/object/fcr:transform/default with statusCode: 400 and message: Bad Request
        at org.fcrepo.camel.FcrepoClient.head(FcrepoClient.java:97)[94:org.fcrepo.camel.fcrepo-camel:4.4.0]
        at org.fcrepo.camel.FcrepoProducer.getMetadataUri(FcrepoProducer.java:154)[94:org.fcrepo.camel.fcrepo-camel:4.4.0]
        at org.fcrepo.camel.FcrepoProducer.doRequest(FcrepoProducer.java:137)[94:org.fcrepo.camel.fcrepo-camel:4.4.0]
        at org.fcrepo.camel.FcrepoProducer.process(FcrepoProducer.java:95)[94:org.fcrepo.camel.fcrepo-camel:4.4.0]
        at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[62:org.apache.camel.camel-core:2.15.1]
...

A second set of issues I'm seeing relate to permissions problems with the karaf client, with the files below and with getting the lock.

vagrant@fedora4:~$ /opt/karaf/bin/karaf
Unable to update instance pid: /opt/apache-karaf-4.0.1/instances/instance.properties (Permission denied)
/opt/apache-karaf-4.0.1/data/log/karaf.log (Permission denied)
Unable to update instance pid: /opt/apache-karaf-4.0.1/instances/instance.properties (Permission denied)

I am running the vm on a physical machine running mac os 10.10.5, with vagrant 1.8.1 and fcrepo-vagrant at 1f4568d. I have run the VM on this machine successfully in the past, although I can't recall if I tried to use the karaf client prior to updating to a fcrepo 4.5 versions