search

pegasystems / pega-helm-charts

Orchestrate a Pega Platform™ deployment by using Docker, Kubernetes, and Helm to take advantage of Pega Platform Cloud Choice flexibility.
https://community.pega.com/knowledgebase/articles/cloud-choice
Apache License 2.0
123 stars 194 forks source link

container "pega-web-tomcat" in pod "pega-web-xxxx" is waiting to start: PodInitializing #153

Closed rohit-eaisystems closed 4 years ago

rohit-eaisystems commented 4 years ago

my pega.yaml helm installation doesn't go past this.

image

when I do kubectl get pods -n mypega I get: NAME READY STATUS RESTARTS AGE pega-batch-5fc4df6db-mzb8b 0/1 Init:0/1 0 5m32s pega-search-0 0/1 CrashLoopBackOff 5 5m32s pega-stream-0 0/1 Init:0/1 0 5m32s pega-web-6c459cfc74-9r2r8 0/1 Init:0/1 0 5m32s

Also My Azure gateway shows this when I deploy image

Not sure what is wrong here?

rohit-eaisystems commented 4 years ago

I found the issue, image

Even though I have passed the jdbc url on pega yaml file.

dcasavant commented 4 years ago

Can you share your pega yaml file? Please redact any sensitive information such as passwords.

rohit-eaisystems commented 4 years ago

Can you share your pega yaml file? Please redact any sensitive information such as passwords.

Thanks a lot for your reply. I am attaching my pega.yaml file below.

pega.yaml.txt

dcasavant commented 4 years ago

@rohit-eaisystems it does look like your pega.yaml file is properly configured. Are you able to confirm that the environment variable is making its way into the container? It should have generated into a configmap first, so you should be able to find it there. If you need additional debugging assistance, please reach out to Pega Global Client Support.

rohit-eaisystems commented 4 years ago

@rohit-eaisystems it does look like your pega.yaml file is properly configured. Are you able to confirm that the environment variable is making its way into the container? It should have generated into a configmap first, so you should be able to find it there. If you need additional debugging assistance, please reach out to Pega Global Client Support.

@dcasavant I checked the pega-environment-config in Config Maps . I went to portal which was created using "az aks browse --resource-group --name " to check that.

In that there is a valid value in JDBC_URL which I had passed from pega.yaml file in jdbc: url: So I am able to find that too, yet for pega-search-0 pod it shows

| _ \ _ _ | \ | | __ | |) / \/ ` |/ ` | | | | |/ _ \ / | |/ / _ \ '| | / / (| | (| | | || | () | (| < _/ |
|| _|_, |_,| |_/ \/ __||\_||
|/ v2.1.0

JDBC_URL must be specified.

rohit-eaisystems commented 4 years ago

@dcasavant

@rohit-eaisystems it does look like your pega.yaml file is properly configured. Are you able to confirm that the environment variable is making its way into the container? It should have generated into a configmap first, so you should be able to find it there. If you need additional debugging assistance, please reach out to Pega Global Client Support.

The issue was with the images, so it ran after I used a fresh one.

Right now facing issues with readiness and live probe which is causing pods to restart after sometime.

dcasavant commented 4 years ago

@rohit-eaisystems There is a different image for the search Pods. If you are seeing "Pega Docker" in the log at startup, you are pointed at the wrong one. Try using the pegasystems/search docker image for that container instead.

rohit-eaisystems commented 4 years ago

@rohit-eaisystems There is a different image for the search Pods. If you are seeing "Pega Docker" in the log at startup, you are pointed at the wrong one. Try using the pegasystems/search docker image for that container instead.

Thanks for the help @dcasavant , I used the above images now I am getting stuck when the pods start. image

pega.yaml.txt

rohit-eaisystems commented 4 years ago

I get below in logs from pega-web-tomcat.

{"app":"","stack":"","@timestamp":"2020-06-22T13:17:27.171Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.pegarules.web.servlet.WebAppLifeCycleListener","message":"System Start Date: Mon Jun 22 13:17:26 GMT 2020","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:17:28.003Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.pegarules.web.servlet.WebAppLifeCycleListener","message":"PegaRULES Web Tier 8.4.1","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:17:28.003Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.pegarules.web.servlet.WebAppLifeCycleListener","message":"PRPC-8.4.1-359: 2020-04-04 09.31 EDT","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:17:28.003Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.pegarules.web.servlet.WebAppLifeCycleListener","message":"prpc-platform.git (125297a798a5bd1b0045c0abec772ae9268be871)","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:17:28.003Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.pegarules.web.servlet.WebAppLifeCycleListener","message":"Now starting the PegaRULES Web Tier...","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:17:31.241Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.pegarules.priv.context.web.WebEnvironment","message":"Web tier using local JNDI context\nfactory = org.apache.naming.java.javaURLContextFactory\n url = \n path = java:","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:17:31.241Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.pegarules.priv.context.JNDIEnvironment","message":"Web-tier default Engine bean name is EngineBMT","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:18:10.189Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.platform.modules.internal.ModulesBridgeImpl","message":"Initializing engine modules.","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:19:03.554Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.platform.environment.nodeclassification.internal.NodeClassificationImpl","message":"Node is started without applicableNodeTypes. Hence applicableNodeTypes will be the default list: [Search, WebUser, BIX, BackgroundProcessing, Custom1, Custom2, Custom3, Custom4, Custom5, DDS, ADM, Batch, RealTime, RTDG, Stream]","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:19:03.645Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.platform.environment.nodeclassification.internal.NodeClassificationImpl","message":"NodeTypes considered on current node = [Stream, BackgroundProcessing, WebUser, Search] , for given -DNodeType = [ Stream,BackgroundProcessing,WebUser,Search ]","userid":"","pegathread":""} Located PegaRULES configuration: file:/usr/local/tomcat/webapps/prweb/WEB-INF/classes/prconfig.xml {"app":"","stack":"","@timestamp":"2020-06-22T13:19:06.368Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.platform.environment.configuration.internal.sources.CommandLineConfigurationSource","message":"Using command line setting: pega-integrationengine\/enablerequestorpools=false","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:19:06.731Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"com.pega.platform.environment.configuration.internal.DefaultConfigurationSource","message":"prconfig.xml merged with prconfig entries in Data-Admin-System-Settings","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:19:09.431Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"DataGrid-Provider","message":"Datagrid module is using undefined datagrid provider","userid":"","pegathread":""} {"app":"","stack":"","@timestamp":"2020-06-22T13:19:09.618Z","source_host":"pega-minikube-0","level":"INFO","thread_name":"main","@version":1,"tenantid":"","logger_name":"DataGrid-Provider","message":"Datagrid module overridden to use hazelcast datagrid provider","userid":"","pegathread":""}

And I get

Normal Created 5m31s kubelet, aks-agentpool-20230462-1 Created container pega-web-tomcat Normal Started 5m30s kubelet, aks-agentpool-20230462-1 Started container pega-web-tomcat Warning Unhealthy 3s kubelet, aks-agentpool-20230462-1 Liveness probe failed: Get http://10.0.0.39:8080/prweb/PRRestService/monitor/pingService/ping: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

When I do kubectl describe pod pega-minikube -n mypega

Pod gets restarted.

rohit-eaisystems commented 4 years ago

Another log of startup attached. logs-from-pega-web-tomcat-in-pega-minikube-0.txt

cdancy commented 4 years ago

@rohit-eaisystems how far away is the database? Looks like you've got a fair amount of "database performance" related alert logs showing up.

rohit-eaisystems commented 4 years ago

@rohit-eaisystems how far away is the database? Looks like you've got a fair amount of "database performance" related alert logs showing up.

@cdancy both are in the same region in azure.

rohit-eaisystems commented 4 years ago

Able to successfully deploy and install pega on AKS