You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I start boot node with 21.1.5 first time, there is an warning about logging. The config.toml file was moved from a running node. Is it problem? How to fix this warning?
2021-05-21 01:47:37.631+08:00 | main | INFO | LogBloomCacheMetadata | Lookup cache metadata file in data directory: /home/besu_network/node1/data/caches
2021-05-21 01:47:37,637 pool-8-thread-1 WARN org.apache.logging.log4j.spi.AbstractLogger caught java.lang.IllegalArgumentException logging MessageFormatMessage: Using the APIs optimized for: {} java.lang.IllegalArgumentException: can't parse argument number:
at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1454)
at java.base/java.text.MessageFormat.applyPattern(MessageFormat.java:492)
at java.base/java.text.MessageFormat.(MessageFormat.java:391)
at org.apache.logging.log4j.message.MessageFormatMessage.formatMessage(MessageFormatMessage.java:115)
at org.apache.logging.log4j.message.MessageFormatMessage.getFormattedMessage(MessageFormatMessage.java:87)
at org.apache.logging.log4j.core.async.InternalAsyncUtil.makeMessageImmutable(InternalAsyncUtil.java:41)
at org.apache.logging.log4j.core.impl.MutableLogEvent.setMessage(MutableLogEvent.java:217)
at org.apache.logging.log4j.core.impl.ReusableLogEventFactory.createEvent(ReusableLogEventFactory.java:100)
at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:408)
at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:63)
at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:153)
at org.apache.logging.log4j.spi.ExtendedLoggerWrapper.logMessage(ExtendedLoggerWrapper.java:222)
at org.apache.logging.log4j.spi.AbstractLogger.log(AbstractLogger.java:2110)
at org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2198)
at org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2152)
at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2135)
at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2028)
at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1899)
at org.apache.logging.log4j.spi.AbstractLogger.log(AbstractLogger.java:1778)
at org.apache.logging.log4j.jul.ApiLogger.log(ApiLogger.java:132)
at io.opentelemetry.sdk.internal.JavaVersionSpecific.(JavaVersionSpecific.java:44)
at io.opentelemetry.sdk.internal.SystemClock.now(SystemClock.java:30)
at io.opentelemetry.sdk.internal.MonotonicClock.create(MonotonicClock.java:40)
at io.opentelemetry.sdk.trace.SdkSpanBuilder.getClock(SdkSpanBuilder.java:251)
atoulme
changed the title
Warnning about logging with 21.1.5 on Ubuntu 20.04
Warning from the OpenTelemetry instrumentation at startup time
May 21, 2021
Description
When I start boot node with 21.1.5 first time, there is an warning about logging. The config.toml file was moved from a running node. Is it problem? How to fix this warning?
2021-05-21 01:47:37.631+08:00 | main | INFO | LogBloomCacheMetadata | Lookup cache metadata file in data directory: /home/besu_network/node1/data/caches
2021-05-21 01:47:37,637 pool-8-thread-1 WARN org.apache.logging.log4j.spi.AbstractLogger caught java.lang.IllegalArgumentException logging MessageFormatMessage: Using the APIs optimized for: {} java.lang.IllegalArgumentException: can't parse argument number:
at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1454)
at java.base/java.text.MessageFormat.applyPattern(MessageFormat.java:492)
at java.base/java.text.MessageFormat.(MessageFormat.java:391)
at org.apache.logging.log4j.message.MessageFormatMessage.formatMessage(MessageFormatMessage.java:115)
at org.apache.logging.log4j.message.MessageFormatMessage.getFormattedMessage(MessageFormatMessage.java:87)
at org.apache.logging.log4j.core.async.InternalAsyncUtil.makeMessageImmutable(InternalAsyncUtil.java:41)
at org.apache.logging.log4j.core.impl.MutableLogEvent.setMessage(MutableLogEvent.java:217)
at org.apache.logging.log4j.core.impl.ReusableLogEventFactory.createEvent(ReusableLogEventFactory.java:100)
at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:408)
at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:63)
at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:153)
at org.apache.logging.log4j.spi.ExtendedLoggerWrapper.logMessage(ExtendedLoggerWrapper.java:222)
at org.apache.logging.log4j.spi.AbstractLogger.log(AbstractLogger.java:2110)
at org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2198)
at org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2152)
at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2135)
at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2028)
at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1899)
at org.apache.logging.log4j.spi.AbstractLogger.log(AbstractLogger.java:1778)
at org.apache.logging.log4j.jul.ApiLogger.log(ApiLogger.java:132)
at io.opentelemetry.sdk.internal.JavaVersionSpecific.(JavaVersionSpecific.java:44)
at io.opentelemetry.sdk.internal.SystemClock.now(SystemClock.java:30)
at io.opentelemetry.sdk.internal.MonotonicClock.create(MonotonicClock.java:40)
at io.opentelemetry.sdk.trace.SdkSpanBuilder.getClock(SdkSpanBuilder.java:251)
Versions (Add all that apply)
vmware -v
]docker version
]Additional Information
The text was updated successfully, but these errors were encountered: