You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Were the processes that you had to explicitly kill long running? Or they just ran for a short period of time?
From the ports these processes corresponded to zookeeper and kafka. A certain CLI instance controls only the processes that manages itself.
To troubleshoot more, try next time running confluent current to access the directory where CLI stores all its descriptors. If the metadata there do not match the running instances CLI won't be able to stop the running processes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Confluent CP 4.0 installed on CentoOS 7.2
After installation started
confluent start schema-reigstry
Played with producers and consumers
confluent stop
confluent destroy
Tried restarting
confluent schema-registry
Got, Error starting zookeeper
confluent log zookeeper indicates that java coundnt bind to port 2181 because it's already in use.
Had to kill the 2 java processes holding on to 2181 and 9092.
The text was updated successfully, but these errors were encountered: