# Some logging timestamps of kafka libraries are in the future

**URL:** https://forum.confluent.io/t/some-logging-timestamps-of-kafka-libraries-are-in-the-future/5236
**Category:** Kafka Streams
**Created:** [8 June 2022 09:52 UTC](https://forum.confluent.io/t/some-logging-timestamps-of-kafka-libraries-are-in-the-future/5236 "2022-06-08T09:52:54Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![suikast42](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/suikast42/32/1957_2.png) [@suikast42](https://forum.confluent.io/u/suikast42)
#### Post date: [8 June 2022 09:52 UTC](https://forum.confluent.io/t/some-logging-timestamps-of-kafka-libraries-are-in-the-future/5236/1 "2022-06-08T09:52:54Z")

</div>

I have strange situation here.

I kafka-connect, kafka, zookeeper etc installed with docker and based on confluent platform 7.1.1

The local setup on the VMWare VM based on Ubuntu 22.04 and Docker 20.10.10 and compose v 2.1.1 works like a charm.

I migrate the VM to esxi 6.7 format and move it to production.

So far so good. It works pretty well I would say. But there is a strange sitiutation here.

On the production sytsem the threads of these loggers logs entries in the future 6 -7 minutes :

1. org.apache.kafka.streams.kstream.internals.KStreamWindowAggregate
2. org.apache.kafka.clients.consumer.internals.ConsumerCoordinator
3. org.apache.kafka.clients.NetworkClient

Has someone any explanation ?

 ![image](https://us1.discourse-cdn.com/flex019/uploads/confluentcommunity/original/2X/1/164f1163ef6407df43c044ca2ec46c256cdf519f.png)