Colored output is lost with 25.7.0

[ibhagwan]

Steps to Reproduce

Run besu in the terminal or use besu with --color-enabled=true, output has no ansi coloring.

Expected behavior: [What you expect to happen]
Expect output to be colored as previously.

Versions (Add all that apply)

• Software version: [besu --version]: 25.7.0
• Java version: [java -version]: openjdk 21.0.7 2025-04-15
• OS Name & Version: [cat /etc/*release]: Void Linux
• Kernel Version: [uname -a]: 6.12.34

[ahamlat]

Hi @ibhagwan,
Thanks for spotting this issue. I could reproduce this issue on 25.7.0 whereas it works fine on 25.6.0.

[ahamlat]

I identified the commit responsible of the error 9c7fb88. This seems to be related to a classloading issue. cc @fab-10
I have a workaround if this feature is very important while continuing the investigation :
As in the code, we check the configuration from a log4j configuration file before applying the Java config, you can start you besu node by adding this a variable environment like this

LOG4J_CONFIGURATION_FILE=/opt/log4j/besu-log-config.xml besu ....

You don't need to specify --color-enabled=true
In /opt/log4j/besu-log-config.xml, add this configuration

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN" level="INFO" monitorInterval="5">

  <Properties>
    <Property name="root.log.level">INFO</Property>
  </Properties>

  <Appenders>
    <Console name="Console" target="SYSTEM_OUT">
      <PatternLayout alwaysWriteExceptions="false"
        pattern="%style{%d{yyyy-MM-dd HH:mm:ss.SSSZZZ}}{DIM} | %style{%t}{DIM} | %highlight{%-5level}{FATAL=red bold, ERROR=red bold, WARN=yellow, INFO=green, DEBUG=blue, TRACE=normal} |  %style{%c{1}}{DIM} |  %highlight{%msg%n%throwable}{FATAL=red bold, ERROR=red bold, WARN=yellow, INFO=green, DEBUG=blue, TRACE=white}"
      />
    </Console>
  </Appenders>

  <Loggers>
    <!-- Logger racine -->
    <Root level="${sys:root.log.level}">
      <AppenderRef ref="Console"/>
    </Root>

    <!-- log peering disconnects -->
    <Logger name="org.hyperledger.besu.ethereum.eth.manager.EthProtocolManager" level="INFO"/>

    <!-- turn down the noise -->
    <Logger name="org.apache.logging.log4j.status.StatusLogger" level="OFF"/>

    <Logger name="org.apache.tuweni.discovery.DNSTimerTask" level="INFO">
      <RegexFilter regex="Refreshing DNS records with .*" onMatch="DENY" onMismatch="NEUTRAL"/>
    </Logger>

    <Logger name="org.apache.tuweni.discovery.DNSResolver" level="INFO">
      <RegexFilter regex="DNS query error with .*" onMatch="DENY" onMismatch="NEUTRAL"/>
    </Logger>

    <Logger name="io.vertx.core.dns.DnsException" level="INFO">
      <RegexFilter regex="DNS query error occurred:.*" onMatch="DENY" onMismatch="NEUTRAL"/>
    </Logger>

    <Logger name="org.hyperledger.besu.ethereum.eth.transactions" level="INFO">
      <MarkerFilter marker="INVALID_TX_REMOVED" onMatch="DENY" onMismatch="NEUTRAL"/>
    </Logger>

    <Logger name="io.opentelemetry.extension.trace.propagation.B3PropagatorExtractorMultipleHeaders" level="INFO">
      <RegexFilter regex="Invalid TraceId in B3 header:.*" onMatch="DENY" onMismatch="NEUTRAL"/>
    </Logger>
  </Loggers>

</Configuration>

[ahamlat]

This is more powerful of course, as you can change the log of the output as you want. You can change the colors as well.

[ibhagwan]

This is more powerful of course, as you can change the log of the output as you want. You can change the colors as well.

Ty @ahamlat for the investigation and workaround 🙏

[jintukumardas]

Hi @macfarla @jframe , just wanted to confirm if this is available to pick up. I'd be happy to work on it.

[jframe]

Hi @jintukumardas, It's available to pick up. I'll assign it to you

[jintukumardas]

Hi @jframe, thanks for assigning it to me.

[jintukumardas]

Hi @jframe , I've made the changes. Please take a look whenever you get a chance and let me know if changes looks good.