I have setup Camunda 8.6.6 in Windows10, and I can access Operate and Tasklist. However, when I try to connect a simple Spring Boot project using spring-boot-starter-camunda-sdk, I’m getting below error in ZeebeDeploymentAnnotationProcessor
Caused by: io.grpc.StatusRuntimeException : UNAVAILABLE: Expected to execute command on partition 1, but either it does not exist or the gateway is not yet aware of it.
I had a look into the camunda.log file, and I can see below exception though I can access Operate and Tasklist.
io.camunda.zeebe.util.actor- Uncaught exceptionin ‘Startup’ in phase ‘STARTED’. Continuing ith next job. java.lang.UnsatisfiedLinkError: ‘int org.rocksdb.RocksDB.version()’
I’m not sure if the latter rocksdb error has anything to do with the former grpc connection error while deploying the bpmn file I have mentioned with @Deployment annotation.
FYI, I’m simply using camunda.client.mode=self-managed property, and falling back with the other default properties.
Hi @Sankar - that’s not expected. I would recommend trying a clean start: shutdown the running instances, remove the downloaded artifacts, and start C8 Run again. Zeebe uses RocksDB for temporary local storage and if Zeebe can’t connect to RocksDB, it can’t start.
Hi @nathan.loding
I have tried a clean install, it didn’t work either. Infact I could not deploy the bpmn from Camunda modeler, so definitely zeebe is not running because of RocksDB as you said.
And the issue I’m mentioning here is happening in my office Windows 10 machine sitting inside proxy firewall. Is there any dependencies to make rocksdb run in Windows 10?
However, the same installation worked instantly in my personal macOS, where I deployed a simple process and completed it.
@Sankar - that’s very strange. The proxy shouldn’t matter, I don’t think, but it’s possible other security configurations on the workstation might be causing an issue. It’s hard to say what that might be though. Are you running it as an admin?
I’ll share this with the engineering team and see if they have any additional thoughts.
@nathan.loding - Yes, Running it as admin. I would like to remind you again that I can access and login Operate and Tasklist, and elasticsearch is also running fine, it’s only zeebe I could not connect from my simple spring boot application and Camunda modeler.
Hi @Sankar - yes, it is normal for some applications to start while others might fail. In this case, Operate and Tasklist don’t have a direct dependency on a running Zeebe instance (they pull their data from Elastic once it has been exported). Your Spring application and Modeler are trying to directly communicate with Zeebe, and Zeebe isn’t running, so that is why they fail.
However, it is still a very strange error, and this isn’t one that our engineering team has encountered yet. We opened a GitHub issue for this also (here) but there’s no additional info yet.
Hi @nathan.loding
I think I cannot share the log from my office machine in the public forum for security reasons. Probably, I will raise an Enterprise support ticket.
@Sankar - that’s fair! I don’t think the log file contains anything confidential, but better safe than sorry. If you do open a support ticket, be sure to reference this thread and the GitHub issue I linked also - that will help the support team get up to speed as quickly as possible.