-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: High
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.3
-
Component/s: voltha-onos
-
Labels:
-
Story Points:3
-
Epic Link:
With latest version of `kind-voltha` and enabled Karaf logging (kafka_logging) in the helm chart the following exception is thrown at startup, preventing any logging for being displayed via log:tail or log:display. I've seen the issue happening in the ONF Berlin POD and in kind voltha. Issue was confirmed also by Hardik Windlass
I've worked around the issue by putting
kafka_logging:
enabled: false
in `minimal-values.yaml`
Exception
Mar 09, 2020 2:59:50 PM org.apache.karaf.main.Main$KarafLockCallback lockAcquired
INFO: Lock acquired. Setting startlevel to 100
org.ops4j.pax.logging.pax-logging-api [log4j2] ERROR : Log4J2 configuration problem: Failed to construct kafka producer Ignored FQCN: org.apache.logging.log4j.spi.AbstractLogger
org.apache.kafka.common.KafkaException: Failed to construct kafka producer
at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:456)
at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:303)
at org.apache.logging.log4j.core.appender.mom.kafka.DefaultKafkaProducerFactory.newKafkaProducer(DefaultKafkaProducerFactory.java:40)
at org.apache.logging.log4j.core.appender.mom.kafka.KafkaManager.startup(KafkaManager.java:136)
at org.apache.logging.log4j.core.appender.mom.kafka.KafkaAppender.start(KafkaAppender.java:169)
at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:618)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:295)
at org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl.configureLog4J2(PaxLoggingServiceImpl.java:425)
at org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl.updated(PaxLoggingServiceImpl.java:277)
at org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl$1ManagedPaxLoggingService.updated(PaxLoggingServiceImpl.java:585)
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)
at org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1405)
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.apache.kafka.common.config.ConfigException: No resolvable bootstrap urls given in bootstrap.servers
at org.apache.kafka.clients.ClientUtils.parseAndValidateAddresses(ClientUtils.java:66)
at org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:405)
... 17 more
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.esotericsoftware.kryo.util.UnsafeUtil (jar:bundle://113.0:0/!/) to constructor java.nio.DirectByteBuffer(long,int,java.lang.Object)
WARNING: Please consider reporting this to the maintainers of com.esotericsoftware.kryo.util.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
org.ops4j.pax.logging.pax-logging-api [log4j2] ERROR : Log4J2 configuration problem: Failed to construct kafka producer Ignored FQCN: org.apache.logging.log4j.spi.AbstractLogger