Managed Kubernetes
Latest
During Host Onboarding PF9CTL Check Node Fails
Problem
pf9ctl check node command shows below output.
# pf9ctl check-node
2021-04-28T10:56:54.3605Z INFO Loading config...Removal of existing CLI : PASSExisting Installation Check : PASSSudoCheck : PASSCPUCheck : PASSDiskCheck : PASSMemoryCheck : PASSPortCheck : FAILNode not ready. See /root/pf9/log/pf9ctl-20210428.log or use --verbose for logs
pf9ctl logs show below error during node onboarding.
{"level":"debug","ts":"2021-04-28T10:56:54.3358Z","caller":"debian/debian.go:58","msg":"Ports required but not available: [3306]"}...{"level":"debug","ts":"2021-04-28T10:56:54.3605Z","caller":"pmk/checkNode.go:108","msg":"Sending Segment Event: CheckNode: PortCheck"}.{"level":"debug","ts":"2021-04-28T10:56:54.3606Z","caller":"cmd/checkNode.go:81","msg":"Error in PortCheck : Following port(s) should not be in use: 3306"}.{"level":"debug","ts":"2021-04-28T10:56:54.3606Z","caller":"pmk/checkNode.go:101","msg":"Sending Segment Event: CheckNode: Existing Kubernetes Cluster Check"}
Environment
Platform9 Managed Kubernetes - v4.0 and Higher
PF9CTL
Cause
Port 3306 is currently in use on the node.
Resolution
Port 3306 should not be in use on the node that you are trying to onboard.
# netstat -tlna | grep ":3306"
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 1115/mysqld
Warning
If there are any ESTABLISHED connections to mysql, ensure the service may be safely stopped before proceeding.
Stop the mysqld process on the node.
# systemctl stop mysqld
Last updated on
Was this page helpful?
Frequently Asked Questions
Solutions
How Tos
Internal Only
Templates
Powered by
