# After Launching Cluster Using v1.4.0, Proxysql Never Becomes Available **URL:** \ **Category:** Percona Operator for MySQL\ **Created:** [May 14, 2020, 12:08am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623 "2020-05-14T00:08:11Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![lots0logs](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lots0logs/32/1318_2.png) [@lots0logs](https://forums.percona.com/u/lots0logs)\ **Post date:** [May 14, 2020, 12:08am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623/1 "2020-05-14T00:08:11Z")
I created an issue on your tracker [here](https://jira.percona.com/browse/K8SPXC-278) but have yet to get any response. I’m really stuck on this and would appreciate any guidance that might help me resolve the problem. The pxc-monit container in the proxysql pod on each node never becomes available.  The logs for the container on each node look like this: ```auto 2020/05/07 20:16:15 Failed to execute /usr/bin/add_pxc_nodes.sh: + main + echo 'Running /usr/bin/add_pxc_nodes.sh' Running /usr/bin/add_pxc_nodes.sh + read -ra first_host + '[' -z db-cluster-1-pxc-0.db-cluster-1-pxc.pxc.svc.cluster.local ']' ++ echo db-cluster-1-pxc-0.db-cluster-1-pxc.pxc.svc.cluster.local ++ cut -d . -f 2- + service=db-cluster-1-pxc.pxc.svc.cluster.local + sleep 15s + wait_for_mysql db-cluster-1-pxc.pxc.svc.cluster.local + local h=db-cluster-1-pxc.pxc.svc.cluster.local + echo 'Waiting for host db-cluster-1-pxc.pxc.svc.cluster.local to be online...' Waiting for host db-cluster-1-pxc.pxc.svc.cluster.local to be online... ++ mysql_root_exec db-cluster-1-pxc.pxc.svc.cluster.local 'select 1' ++ local server=db-cluster-1-pxc.pxc.svc.cluster.local ++ local 'query=select 1' ++ MYSQL_PWD=1KO5UIduAdcQscyt ++ timeout 600 mysql -h db-cluster-1-pxc.pxc.svc.cluster.local -uroot -s -NB -e 'select 1' + '[' 1 '!=' 1 ']' + wait_for_proxy + local h=127.0.0.1 + echo 'Waiting for host 127.0.0.1 to be online...' Waiting for host 127.0.0.1 to be online... ++ proxysql_admin_exec 127.0.0.1 'select 1' ++ local server=127.0.0.1 ++ local 'query=select 1' ++ MYSQL_PWD=3BhMOqF5A521fy2Y ++ timeout 600 mysql -h 127.0.0.1 -P6032 -u proxyadmin -s -NB -e 'select 1' + '[' 1 '!=' 1 ']' + SSL_ARG= ++ proxysql_admin_exec 127.0.0.1 'SELECT variable_value FROM global_variables WHERE variable_name="mysql-have_ssl"' ++ local server=127.0.0.1 ++ local 'query=SELECT variable_value FROM global_variables WHERE variable_name="mysql-have_ssl"' ++ MYSQL_PWD=3BhMOqF5A521fy2Y ++ timeout 600 mysql -h 127.0.0.1 -P6032 -u proxyadmin -s -NB -e 'SELECT variable_value FROM global_variables WHERE variable_name="mysql-have_ssl"' + '[' true = true ']' + SSL_ARG=--use-ssl=yes + proxysql-admin --config-file=/etc/proxysql-admin.cnf --cluster-hostname=db-cluster-1-pxc-0.db-cluster-1-pxc.pxc.svc.cluster.local --enable --update-cluster --remove-all-servers --disable-updates --force --debug --use-ssl=yes debug (line:2771) : Loading /etc/proxysql-admin.cnf debug: ProxySQL datadir: /var/lib/proxysql debug (line:712) : exec_sql : proxyadmin@localhost:6032 ==> SELECT 1 mysql: [ERROR] Could not open required defaults file: /dev/stdin mysql: [ERROR] Fatal error in defaults handling. Program aborted! debug: --> query failed 1 ERROR (line:713) : ProxySQL connection check failed. -- Could not connect to ProxySQL at localhost:6032 Smart Checklist ``` ---
**Author:** ![pschwaller](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pschwaller/32/980_2.png) [@pschwaller](https://forums.percona.com/u/pschwaller)\ **Post date:** [May 15, 2020, 7:13am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623/2 "2020-05-15T07:13:18Z")
Your Jira issue is in our queue.  Sorry we haven’t gotten to it yet.  It should be soon. ---
**Author:** ![lots0logs](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lots0logs/32/1318_2.png) [@lots0logs](https://forums.percona.com/u/lots0logs)\ **Post date:** [May 16, 2020, 2:15am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623/3 "2020-05-16T02:15:40Z")
![](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/d/de85d70c13ecb487220ed13ab6e6c3b34e623a44.gif "Image: https://media.giphy.com/media/3orieTfp1MeFLiBQR2/giphy.gif") ---
**Author:** ![lots0logs](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lots0logs/32/1318_2.png) [@lots0logs](https://forums.percona.com/u/lots0logs)\ **Post date:** [May 16, 2020, 2:15am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623/4 "2020-05-16T02:15:40Z")
At this point I have to ask, has anyone successfully installed a working cluster using v.1.4.0 of the K8s Operator?  ---
**Author:** ![Ivan\_Pylypenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_pylypenko/32/2452_2.png) [@Ivan\_Pylypenko](https://forums.percona.com/u/Ivan_Pylypenko)\ **Post date:** [May 21, 2020, 2:09am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623/5 "2020-05-21T02:09:13Z")
Yes, me) Just followed the standard procedure listed in docs with GKE platform. ---
**Author:** ![lots0logs](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lots0logs/32/1318_2.png) [@lots0logs](https://forums.percona.com/u/lots0logs)\ **Post date:** [May 22, 2020, 12:17am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623/6 "2020-05-22T00:17:09Z")
I was able to identify a fix. See the jira ticket linked in my first post for details. ---
**Author:** ![lots0logs](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lots0logs/32/1318_2.png) [@lots0logs](https://forums.percona.com/u/lots0logs)\ **Post date:** [May 22, 2020, 12:17am UTC](https://forums.percona.com/t/after-launching-cluster-using-v1-4-0-proxysql-never-becomes-available/7623/7 "2020-05-22T00:17:49Z")
I was able to identify a fix. See the jira ticket linked in my first post for details.