Solved

IAM pod is in state CrashLoopBackOff

  • 1 April 2024
  • 2 replies
  • 45 views
C
Rank
Badge +7

IAM pod is in state CrashLoopBackOff for new installation
ifsapp-iam-77698f8bf9-rqtsl       1/2     CrashLoopBackOff
 
IP ranges defined are as below 
ManagementServerIP: 10.1.1.14
PodCidrRange: 192.168.0.0/16
LocalNetworkIpRange: 10.1.1.0/24
Linuxhost":  10.1.1.15
DB HOST=10.1.0.11

ifscloud-values.yaml and main_config.json attached
iam.log and iam pod describe also attached.

.\main.ps1 CHANGE-POD-IP-RANGE also executed. But still error is the same.

No communication issue between MT and DB servers

root@vm-prd1-ifscloud-mt-xxxxxx-uks:/home/xxxAdmin# ping 10.1.0.11
PING 10.1.0.11 (10.1.0.11) 56(84) bytes of data.
64 bytes from 10.1.0.11: icmp_seq=1 ttl=128 time=8.07 ms

 

DB init is in completed state.

ifs-db-init-zz8vc   0/1     Completed

 

What could be the issue here?
This is 23R1 SU5

Thanks,

icon

Best answer by Ben Monroe 2 April 2024, 03:18

View original
4 Attachments

2 replies

B
Rank
Userlevel 5
Badge +12

Hi Mayura,

Please try to check the past logs (-p). They may have further details

kubectl logs -p deployment/ifsapp-iam -c ifsapp-iam -n <ifs namespace>

Also please check the events:

kubectl get events -n <ifs namespace>

Best regards -- Ben

C
Rank
Badge +7

Hi Ben,

Thank you very much.

Only “kubectl logs -p deployment/ifsapp-iam -c ifsapp-iam -n <ifs namespace>” shows the error. Not in iam log file.

It's due to the password for ifsiamsys.

Best Regards,

Mayura

Reply


Terms & ConditionsCookie settings