MaxScale Pod CrashLoopBackOff - Service Name Conflict

25 views
Skip to first unread message

Bharath Achar

unread,
Oct 5, 2024, 11:24:11 PM10/5/24
to MariaDB MaxScale
I've posted an issue GitHub, maxscale pod is failing with below:

kubectl -n kaizen logs maxscale

Starting... MaxScale PID = 18 'check system' not defined in control file, failed to add automatic configuration (service name maxscale is used already) -- please add 'check system <name>' manually maxscale:2: Service name conflict, maxscale already defined '/var/log/monit.log'

Reply all
Reply to author
Forward
0 new messages