CA Service Management

 View Only
  • 1.  CA SDM 17.2 Error in Stdlog

    Posted Jul 23, 2020 11:01 AM
    Hello,

    We are using the CA SDM 17.2 with OS windows server 2012 R2.

    Getting the below errors in stdout log of SDM.

    07/23 09:09:07.02 "HostName"  pdm_d_mgr 13280 ERROR daemon_obj.c 1990 Daemon cawf_tomcat died: restarting
    07/23 09:36:26.10 "HostName" slump_nxd 580 ERROR list.c 2651 Process 0|proctor_NoVaLue is still unknown after 900 seconds; cancelling verification and discarding 8 messages


    Kinldy suggest and do the neeedful.

    Regards,
    Piyush Mer


  • 2.  RE: CA SDM 17.2 Error in Stdlog

    Posted Jul 24, 2020 01:58 AM
    Hi,
    Just an assumption: It seems that your system is not configured properly.
    I would start with a reconfigure.
    Regards
    ........Michael

    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------



  • 3.  RE: CA SDM 17.2 Error in Stdlog

    Posted Jul 24, 2020 03:24 AM
    We have recently upgraded it. In installation we didn't get the error.

    Kindly suggest and do the needful.


  • 4.  RE: CA SDM 17.2 Error in Stdlog

    Posted Jul 24, 2020 03:27 AM
    We have to rum pdm_configure… or  we have to setup it again...


  • 5.  RE: CA SDM 17.2 Error in Stdlog

    Posted Jul 24, 2020 04:08 AM
    I would try a pdm_configure first. lets see , if this helps already..
    Good luck.
    ....Michael

    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------



  • 6.  RE: CA SDM 17.2 Error in Stdlog

    Posted Jul 24, 2020 05:43 AM
    We have run the pdm_configure but still get the same error

    07/24 15:06:10.02 EMSAPP1        pdm_d_mgr            6700 ERROR        daemon_obj.c          1990 Daemon cawf_tomcat died: restarting''''



    Can you please tell us what actually  cawf_tomcat used for.  Can you please tell us it can affect the integration issue


  • 7.  RE: CA SDM 17.2 Error in Stdlog

    Posted Jul 24, 2020 06:13 AM
    I was more concentrating on the error message:

    07/23 09:36:26.10 "HostName" slump_nxd 580 ERROR list.c 2651 Process 0|proctor_NoVaLue is still unknown after 900 seconds; 

    Which pointed me into the pdm_configure direction. and which was the more serious and important  error for me.

    I can't tell you anything about the cawf tomcat, and what it is used for. Anyone?
    Anyway, the system tries to start this tomcat instance, if NX_CAWF_HOSTNAME is defined in your NX.env.
    I don't have this var in my NX.env , nor do I have the related NX_ROOT/bopcfg/www/CATALINA_BASE_WF directory.
    It might be related to an "old", separate workflow engine, which was replaced by Process Automation for some time. But this is just an assumption !


    Which actual version of SDM are we talking about? What other Service Management Applications do you have in place?
    And from which version did you upgrade?
    Regards
    ..........Michael


    ------------------------------
    Principal Services Consultant
    HCL Enterprise Studio
    Germany
    ------------------------------



  • 8.  RE: CA SDM 17.2 Error in Stdlog
    Best Answer

    Posted Jul 26, 2020 04:46 AM
    CAWF is used for CA Workflow and the following article may be of use:
    https://knowledge.broadcom.com/external/article/188033/nxenv-and-configproperties-after-update.html

    ------------------------------
    Joe
    ------------------------------