Simple-monitor authentication problem, and worker DEADLINE exception

Hi
working with the simple-monitor docker-compose, its up on my laptop since yesterday .
yesterday everything worked fine , but this morning i get authentication problem from the simple-monitor container , also on the workers i get the famouse DEADLINE_EXCEEDED exception.

here is the monitor authentication issue exception

 TimeoutException: Authentication response did not come back in 60000 millis]
zeebe_monitor | 
zeebe_monitor | java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: Authentication response did not come back in 60000 millis
zeebe_monitor | 	at com.hazelcast.client.spi.impl.ClientInvocationFuture.resolve(ClientInvocationFuture.java:73) ~[hazelcast-client-3.11.1.jar!/:3.11.1]
zeebe_monitor | 	at com.hazelcast.spi.impl.AbstractInvocationFuture$1.run(AbstractInvocationFuture.java:250) ~[hazelcast-3.11.1.jar!/:3.11.1]
zeebe_monitor | 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_212]
zeebe_monitor | 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_212]
zeebe_monitor | 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_212]
zeebe_monitor | 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_212]
zeebe_monitor | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_212]
zeebe_monitor | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_212]
zeebe_monitor | 	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_212]
zeebe_monitor | 	at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64) [hazelcast-3.11.1.jar!/:3.11.1]
zeebe_monitor | 	at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80) [hazelcast-3.11.1.jar!/:3.11.1]
zeebe_monitor | Caused by: java.util.concurrent.TimeoutException: Authentication response did not come back in 60000 millis
zeebe_monitor | 	at com.hazelcast.client.connection.nio.ClientConnectionManagerImpl$TimeoutAuthenticationTask.run(ClientConnectionManagerImpl.java:619) ~[hazelcast-client-3.11.1.jar!/:3.11.1]
zeebe_monitor | 	... 9 common frames omitted

here is the deadline exception on the workers

io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: ClientCall was cancelled at or after deadline. [remote_addr=/127.0.0.1:26500]
	at io.grpc.Status.asRuntimeException(Status.java:533) ~[grpc-api-1.24.1.jar:1.24.1]
	at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:442) [grpc-stub-1.24.1.jar:1.24.1]
	at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39) [grpc-api-1.24.1.jar:1.24.1]
	at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23) [grpc-api-1.24.1.jar:1.24.1]
	at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40) [grpc-api-1.24.1.jar:1.24.1]
	at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:700) [grpc-core-1.24.1.jar:1.24.1]
	at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39) [grpc-api-1.24.1.jar:1.24.1]
	at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23) [grpc-api-1.24.1.jar:1.24.1]
	at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40) [grpc-api-1.24.1.jar:1.24.1]
	at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:399) [grpc-core-1.24.1.jar:1.24.1]
	at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:510) [grpc-core-1.24.1.jar:1.24.1]
	at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:66) [grpc-core-1.24.1.jar:1.24.1]
	at io.grpc.internal.ClientCallImpl$C

Looks like the broker has died.

Any tips to understand why it died ?

Sure, read the broker logs.