Hello,
I'm using Karaf 2.2.9 and Cellar 2.2.4 on two nodes (node 2 is remote).
Group configuration is set to allow feature, config and bundle sync:
default.config.whitelist.inbound=*
default.config.whitelist.outbound=*
default.config.blacklist.inbound=org.apache.karaf.cellar.groups, \
org.apache.karaf.cellar.node, \
org.apache.karaf.management, \
org.apache.karaf.shell, \
org.ops4j.pax.logging
default.config.blacklist.outbound=org.apache.karaf.cellar.groups, \
org.apache.karaf.cellar.node, \
org.apache.karaf.management, \
org.apache.karaf.shell, \
org.ops4j.pax.logging
default.config.sync=true
default.features.whitelist.inbound=*
default.features.whitelist.outbound=*
default.features.blacklist.inbound=cellar
default.features.blacklist.outbound=cellar
default.features.sync=true
default.features.repositories.sync=true
default.bundle.whitelist.inbound = *
default.bundle.whitelist.outbound = *
default.bundle.sync = true
default.obr.urls.sync=true
default.obr.bundles.sync=true
When I try to start 2 nodes, one of them doesn’t correctly start the
org.apache.karaf.cellar.bundle bundle. Bundle is marked as ACTIVE but the
blueprint section marks it as in Failure:
[ 50] [Active ] [Created ] [ 31] hazelcast (1.9.4.8)
Fragments: 52
[ 51] [Active ] [Created ] [ 32] Apache Karaf :: Cellar ::
Core
(2.2.4)
[ 52] [Resolved ] [ ] [ 33] Apache Karaf :: Cellar ::
Hazelcast (2.2.4)
Hosts: 50
[ 53] [Active ] [Created ] [ 40] Apache Karaf :: Cellar ::
Config (2.2.4)
[ 54] [Active ] [Created ] [ 40] Apache Karaf :: Cellar ::
Features (2.2.4)
[ 55] [Active ] [Failure ] [ 40] Apache Karaf :: Cellar ::
Bundle (2.2.4)
[ 56] [Active ] [Created ] [ 40] Apache Karaf :: Cellar ::
DOSGi
(2.2.4)
[ 57] [Active ] [Created ] [ 40] Apache Karaf :: Cellar ::
Utils
(2.2.4)
[ 58] [Active ] [Created ] [ 40] Apache Karaf :: Cellar ::
Shell
(2.2.4)
[ 59] [Active ] [Created ] [ 40] Apache Karaf :: Cellar ::
Management (2.2.4)
Log service reported the following error:
Unable to start blueprint container for bundle
org.apache.karaf.cellar.bundle
Result of this problem is that the bundle sync no longer works and some
console commands are not present on the affected node.
I discovered that the mentioned bundle is always correctly initialized on
the node that is started first. On the second one it always stays in the
Grace period for some time and then drops to Failure.
Yesterday everything synced perfectly (features, bundles, configurations) on
a fresh karaf+cellar installation. Once karaf nodes were shutdown (over
night) these problems arose.
Browsing through similar error messages I found that others encountered
problems with starting the …cellar.features bundle, and that the fix had
been made to the Cellar 2.2.4 and 3.0.0 branch. Could this problem also be
fixed with the cellar bundle start level tweaks? Is there something wrong
with my cellar configuration listed above (both nodes have the same)?
Any help would be appreciated,
-D
--
View this message in context:
http://karaf.922171.n3.nabble.com/Cellar-bundle-blueprint-faliure-tp4025940.html
Sent from the Karaf - User mailing list archive at Nabble.com.
