cristianCesanaIvolution opened a new issue, #15593:
URL: https://github.com/apache/dolphinscheduler/issues/15593

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   I deployed the last version of DolphinScheduler 3.2.1 through docker-compose 
procedure described here: 
https://dolphinscheduler.apache.org/en-us/docs/3.2.1/guide/start/docker#using-docker-compose-to-start-server
   
   Running the monitor I can see that no master node exists
   
![image](https://github.com/apache/dolphinscheduler/assets/146731324/9b8c316d-98f6-47ee-87eb-9d3a17614d88)
   
   Tring to run a workflow or task I get the error "master does not exists" (as 
expected)
   
![image](https://github.com/apache/dolphinscheduler/assets/146731324/a8feab2a-f073-4cc3-bc6f-b42fdc4f8e21)
   
   Looking at the logs contained in master container folder I can see this
   
![image](https://github.com/apache/dolphinscheduler/assets/146731324/37e08765-9ed2-4b3f-a95e-da15a223fe69)
   
   Any idea of what is causing the master instance to not start correctly?
   
   
   
   ### What you expected to happen
   
   Worker instance is properly started and visible for dolphinscheduler-api 
container and tasks are executed correctly
   
   
   ### How to reproduce
   
   Deploy with docker-compose as described in: 
https://dolphinscheduler.apache.org/en-us/docs/3.2.1/guide/start/docker#using-docker-compose-to-start-server
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.2.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to