CND Property definition for hipposys:loglevel missing

Hello all,

I have a question regarding the CND. In my environments sometimes the property definition hipposys:loglevel disappears from the hipposys CND. When I next bootstrap an updater with a ‘hipposys:loglevel’ property, the CMS gives an exception during startup about the missing property definition hipposys:loglevel in the CND.

After I have removed this property from the bootstrap yaml files and deployed/restarted the CMS, I have to manually import the hipposys CND with the property definition of hipposys:loglevel to solve this.

My question is, how can this happen?

Thanks in advance,

Philippe.

11.09.2018 09:35:49 [localhost-startStop-1] ERROR [org.onehippo.cm.engine.ConfigurationServiceImpl.applyConfig():604] Failed to apply config
org.onehippo.cm.engine.ConfigurationRuntimeException: Failed to process property ‘/hippo:configuration/hippo:update/hippo:registry/RemoveElementIds/hipposys:loglevel’ defined in [myhippoproject/myhippoproject/myhippoproject-repository-data-application [config: configuration/update/registry/RemoveElementIds.yaml]]: no matching property definition found for {http://www.onehippo.org/jcr/hipposys/nt/1.0}loglevel
at org.onehippo.cm.engine.ConfigurationConfigService.updateProperty(ConfigurationConfigService.java:769) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWritePropertiesDelta(ConfigurationConfigService.java:474) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteNodeDelta(ConfigurationConfigService.java:330) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteChildNodesDelta(ConfigurationConfigService.java:561) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteNodeDelta(ConfigurationConfigService.java:333) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteChildNodesDelta(ConfigurationConfigService.java:561) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteNodeDelta(ConfigurationConfigService.java:333) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteChildNodesDelta(ConfigurationConfigService.java:561) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteNodeDelta(ConfigurationConfigService.java:333) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteChildNodesDelta(ConfigurationConfigService.java:561) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteNodeDelta(ConfigurationConfigService.java:333) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.computeAndWriteDelta(ConfigurationConfigService.java:228) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationServiceImpl.applyConfig(ConfigurationServiceImpl.java:589) [hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationServiceImpl.init(ConfigurationServiceImpl.java:204) [hippo-repository-engine-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationServiceImpl.start(ConfigurationServiceImpl.java:122) [hippo-repository-engine-5.5.0.jar:5.5.0]
at org.hippoecm.repository.LocalHippoRepository.initializeConfiguration(LocalHippoRepository.java:308) [hippo-repository-engine-5.5.0.jar:5.5.0]
at org.hippoecm.repository.LocalHippoRepository.initialize(LocalHippoRepository.java:292) [hippo-repository-engine-5.5.0.jar:5.5.0]
at org.hippoecm.repository.LocalHippoRepository.create(LocalHippoRepository.java:122) [hippo-repository-engine-5.5.0.jar:5.5.0]
at org.hippoecm.repository.LocalHippoRepository.create(LocalHippoRepository.java:112) [hippo-repository-engine-5.5.0.jar:5.5.0]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_181]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_181]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_181]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_181]
at org.hippoecm.repository.HippoRepositoryFactory.getHippoRepository(HippoRepositoryFactory.java:147) [hippo-repository-connector-5.5.0.jar:5.5.0]
at org.hippoecm.repository.RepositoryServlet.init(RepositoryServlet.java:184) [hippo-repository-servlets-5.5.0.jar:5.5.0]
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1227) [catalina.jar:8.0.45]
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1140) [catalina.jar:8.0.45]
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1027) [catalina.jar:8.0.45]
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5038) [catalina.jar:8.0.45]
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5348) [catalina.jar:8.0.45]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) [catalina.jar:8.0.45]
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753) [catalina.jar:8.0.45]
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729) [catalina.jar:8.0.45]
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717) [catalina.jar:8.0.45]
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:976) [catalina.jar:8.0.45]
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1853) [catalina.jar:8.0.45]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_181]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
Caused by: javax.jcr.nodetype.ConstraintViolationException: no matching property definition found for {http://www.onehippo.org/jcr/hipposys/nt/1.0}loglevel
at org.apache.jackrabbit.core.nodetype.EffectiveNodeType.getApplicablePropertyDef(EffectiveNodeType.java:782) ~[jackrabbit-core-2.16.2-h2.jar:2.16.2-h2]
at org.apache.jackrabbit.core.NodeImpl.getApplicablePropertyDefinition(NodeImpl.java:852) ~[jackrabbit-core-2.16.2-h2.jar:2.16.2-h2]
at org.apache.jackrabbit.core.NodeImpl.getOrCreateProperty(NodeImpl.java:400) ~[jackrabbit-core-2.16.2-h2.jar:2.16.2-h2]
at org.apache.jackrabbit.core.NodeImpl$SetPropertyOperation.perform(NodeImpl.java:2056) ~[jackrabbit-core-2.16.2-h2.jar:2.16.2-h2]
at org.apache.jackrabbit.core.NodeImpl$SetPropertyOperation.perform(NodeImpl.java:2002) ~[jackrabbit-core-2.16.2-h2.jar:2.16.2-h2]
at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216) ~[jackrabbit-core-2.16.2-h2.jar:2.16.2-h2]
at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:1924) ~[jackrabbit-core-2.16.2-h2.jar:2.16.2-h2]
at org.hippoecm.repository.decorating.NodeDecorator.setProperty(NodeDecorator.java:102) ~[hippo-repository-connector-5.5.0.jar:5.5.0]
at org.onehippo.cm.engine.ConfigurationConfigService.updateProperty(ConfigurationConfigService.java:762) ~[hippo-repository-engine-5.5.0.jar:5.5.0]
… 40 more

Hi,

Hmm strange case…
This property was introduced in 12.2 and you’re on 12.5 so what has been your upgrade path? When does the property disappear, after a restart maybe?

Perhaps the bootstrapping didn’t upgrade the cnd for some reason. It should take it from jar and re-register it in the repository. You may find some clue if you set lower (INFO, DEBUG) log level to package org.onehippo.cm.engine.

HTH
Jeroen

Hi Jeroen,

Thanks for your response. My upgrade path was as follows:
12.1.0 => 12.2.0 => 12.5.0
Although we already had this problems on 12.2.0.

At this moment I don’t know how to exactly reproduce it. I though it was when bootstrapping an updater with the loglevel property, but now that I’ve tried this a second time it works perfectly fine. I do have updated the loglevel of that package, when it happens again I hope to find a clue there.

Thanks, Philippe.