Hi @jwulf, i have configured zeebe in my local Linux machine. One day back it is working fine.Yesterday onwards i am facing this issue.I am able to access simple monitor but unable to deploy bpmn file,while starting broker getting above error.
Hi @jwulf ,
i was deployed nearly 40 bpmn files. but in bpmn/ folder only 3 bpmn files are there.
Could you please tell me where the deployed bpmn files will be stored is it inside bpmn/ folder or any inmemory database.
If it is inmemory database, how to find those bpmn files.
ohh , then in production if we want to check transaction details how to do it.
How can we analyse the issue without accessing zeebe transaction db.
Please guide me, what is the best approach to over come above issues.
In camunda we can use any database and check the tables, but in zeebe how to check.
As Josh mention, in Zeebe all the internal information is pushed out with the exporters. if something happens inside a broker you will get that into an external source depending on which exporters you have configured. Notice that this is not Camunda BPM anymore, completely new design and purpose, so similar problems will have completely different solutions.
The error that you are getting to restart a container is related to mount paths and directories that might be erased, and that is usually the reason why you need a container orchestrator to deal with containers and their associated resources. Maintaining containers alive is a full time job.