Closed rohit-eaisystems closed 4 years ago
I found the issue,
Even though I have passed the jdbc url on pega yaml file.
Can you share your pega yaml file? Please redact any sensitive information such as passwords.
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.
@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 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
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.
@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.
@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 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.
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 =
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.
Another log of startup attached. logs-from-pega-web-tomcat-in-pega-minikube-0.txt
@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 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.
Able to successfully deploy and install pega on AKS
my pega.yaml helm installation doesn't go past this.
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](https://user-images.githubusercontent.com/51824077/84933481-9580a900-b0f3-11ea-860f-0099bdb2af3b.png)
Not sure what is wrong here?