IDM stays at 0/2 after upgrading CDF to 2019.02 (readiness probe fail)

Hello,

After upgrading the CDF to version 2019.02,  when checking kube-status   it seems idm deployment is not being up.   

from kube-status output:

 

kubectl get deployments -n core    :  

idm 0/2 

 

kubectl get pods -n core:

kubectl describe pod idm-597756fd98-5bksp -n core :

...

..

Warning ....  .....               Readiness probe failed: HTTP probe failed with statuscode: 404

 

I can not login to both cdf administration and suite pages.

 

Any idea please?  

Thanks. 

Levent.

 

 

 

 

Parents
  • Hi Levent,

    For this issue, I would suggest getting more information from idm logs, you can run the command as follows:

    kubectl logs -f idm-xxxx -n core -c idm

    Thanks,

    Elva

  • hi,

    there is an error in that log.  it says one or more configuration file is not provided.  

     

    2019-06-11T09:04:30.623 0000 INFO [localhost-startStop-1] com.hp.sw.bto.ast.security.lwsso.conf.LWSSOConfigurationManager - com.hp.sw.bto.ast.security.lwsso.conf.LWSSOConfigurationManager was not initialized explicitly. Trying to initialize it implicitly from lwssofmconf.xml
    2019-06-11T09:04:31.712 0000 INFO [localhost-startStop-1] com.hp.sw.bto.ast.security.lwsso.utils.StringEncrypter - StringEncrypter [ isUseEncryption = false] : One or any of configuration files is not provided ...
    2019-06-11T09:04:31.819 0000 INFO [localhost-startStop-1] com.hp.sw.bto.ast.security.lwsso.conf.LWSSOConfigurationManager - Building of configuration completed in 1195 milliseconds.
    2019-06-11T09:04:31.846000000 0000 SEVERE org.apache.catalina.core.StandardContext startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
    2019-06-11T09:04:31.852000000 0000 SEVERE org.apache.catalina.core.StandardContext startInternal Context [/idm-service] startup failed due to previous errors

     

    ??? 

    Before running upgrade-l and upgrade-u  I hadn't modified install.properties file in upgrade folder.   Should I had made it? 

     

  • Can you attach the log file with this command:  kubectl logs idm-xxxx -n core -c idm > idm.log, i am not sure whether the error message you posted is the cause or not.

    Thanks,

    Elva

  • Hi, 

    ok.  I have attached that logs. I applied masking on private information like hostname, server name in the logs.  There are two pods in core namespace. Their logs are attached. 

    Thanks in advance.

    idmpod2.zip
Reply Children
No Data