DevOps SRE Blog

I freshly installed k8s cluster. But when I tried to start cluster, cluster nodes were not coming up. While debugging the issue, noticed following Controller manager error in journalctl. kube-controller-manager.service: Main process exited, code=killed, status=11/SEGV Analysis: Somehow I suspected that it was due to partial download of k8s binaries as I was using slow mobile internet connection. It was confirmed when I compared the size of binaries. Solution: Re-downloaded the binaries freshly, Hurray !!!

Today I have developed a SOA composite that exposes REST service. It takes the input payload and does little transformation and inserts data into EBS database. When tried to deploy composite from em console, it was taking lot of time and eventually timing out after 20 mins.  Following is the error message from console: Redeploying on /Domain_soa_domain/soa_domain/soa_cluster … Redeploying on “/Domain_soa_domain/soa_domain/soa_cluster” failed! There was an error deploying/undeploying composite on soa_server1: Timed out waiting for operation to complete.. Following error message was also seen in server diagnostic logs: [2020-05-14T11:59:38.623+02:00] [soa_server1] [ERROR] [SOA-21537] [oracle.integration.platform.blocks.deploy.servlet] [tid: [STUCK].ExecuteThread: ’12’ for queue: ‘weblogic.kernel.Default (self-tuning)’] [userId: abcd] [ecid: fc57ea65-187d-47db-9331-e8a09e3ded00-0005e3eb,0:1:1] [APP: soa-infra] [partition-name: DOMAIN] [tenant-...