Skip to content
This repository has been archived by the owner on Oct 18, 2023. It is now read-only.

Pods do not start on deploy #60

Open
ganchandrasekaran opened this issue Dec 1, 2020 · 1 comment
Open

Pods do not start on deploy #60

ganchandrasekaran opened this issue Dec 1, 2020 · 1 comment

Comments

@ganchandrasekaran
Copy link

ganchandrasekaran commented Dec 1, 2020

I simply deployed the helm chart with:
cronjob:
enabled: false

Deployment: On OpenShift
The pods do not start, it simply goes to "Completed" state.

[root@bastion nesh]# kubectl get po -n test2
db-proxy-proxysql-cluste-0 0/1 Completed 1 17s

[root@bastion nesh]# kubectl logs -n test2 db-proxy-proxysql-cluste-0
2020-12-01 09:14:12 [INFO] Using config file /etc/proxysql.cnf
Renaming database file /var/lib/proxysql/proxysql.db
2020-12-01 09:14:12 [INFO] ProxySQL version 1.4.14-28-g0f6701c5
2020-12-01 09:14:12 [INFO] Detected OS: Linux db-proxy-proxysql-cluste-0 4.18.0-147.8.1.el8_1.x86_64 #1 SMP Wed Feb 26 03:08:15 UTC 2020 x86_64
Standard ProxySQL Cluster rev. 0.4.0906 -- ProxySQL_Cluster.cpp -- Fri Jan 25 16:04:59 2019
2020-12-01 09:14:12 sqlite3db.cpp:45:open(): [ERROR] SQLITE CRITICAL error: Unable to open /var/lib/proxysql/proxysql_stats.db. Shutting down.

@ganchandrasekaran
Copy link
Author

However, running the following command on the cluster fixed the issue:
[root@bastion nesh]# oc adm policy add-scc-to-group anyuid system:serviceaccounts:test2

But, instead it is good to follow the container creation best practices: https://docs.openshift.com/container-platform/4.2/openshift_images/create-images.html

Thanks..

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant