AutoSys Workload Automation

 View Only
  • 1.  Not able to register WCC with EEM

    Posted May 19, 2020 06:43 AM
    Hello All,

    I was not getting event drop down options in wcc quick view tab. I tried to add wcc user in event policy but still it was not showing. As per article given by Broadcom, i unregistered my WCC from EIAM URL and trying to register again.  
    I am experiencing below error while registering WCC with EEM. I have restarted EEM service as well as wcc service but still getting error. Also wcc id and pw is correct. Please help here.

    Note: Autosys scheduler, WCC and EEM are on same server.

    [root@svcas0067 bin]# ./wcc_config.sh -u ejmcommander -p ejmcommander --displayeem
    Logging in as 'ejmcommander' - FAILED
    IAM not available.

    Error in wcc log file:

    INFO | jvm 1 | 2020/05/19 16:24:41 | 79470 | @rest < status-check-1> [] WARN #EEMStatusCheck # Cannot ping the EEM backend ...
    INFO | jvm 1 | 2020/05/19 16:24:54 | 79483 | @rest < status-check-1> [] WARN #EEMStatusCheck # Cannot ping the EEM backend ...
    INFO | jvm 1 | 2020/05/19 16:25:02 | 79490 | @asi <ForkJoinPool-1304-worker-1> [] ERROR #CAMResponseLoader # Failed request with : https://server_name:9443/AEWS/machine?version=2&filter=updateStamp%3E1589833947000%7CcreateStamp%3E1589833947000 , java.io.FileNotFoundException: /opt/CA/WorkloadAutomationAE/wcc/tomcat/webapps/asi/WEB-INF/lib/asm-5.0.4.jar (Too many open files)

    Thanks,
    Sunish M.


  • 2.  RE: Not able to register WCC with EEM
    Best Answer

    Posted May 20, 2020 03:46 AM
    Hi Sunish, 

    That java.io.FileNotFoundException: ....(Too many open files) in log seems to suggest that the user owning the WCC process is hitting the max open files limit (ulimit nofile)
    Try bumping it up and see if these errors go away. 

    $ ulimit -a
    core file size (blocks, -c) 0
    data seg size (kbytes, -d) unlimited
    scheduling priority (-e) 0
    file size (blocks, -f) unlimited
    pending signals (-i) 144965
    max locked memory (kbytes, -l) 64
    max memory size (kbytes, -m) unlimited
    open files (-n) 1024
    pipe size (512 bytes, -p) 8
    POSIX message queues (bytes, -q) 819200
    real-time priority (-r) 0
    stack size (kbytes, -s) 10240
    cpu time (seconds, -t) unlimited
    max user processes (-u) 1024
    virtual memory (kbytes, -v) unlimited
    file locks (-x) unlimited

    See if you are able to connect to the EEM server using the safex command line.

    1. Create a XML file like so:
    $ cat ~/safex_wcc.xml
    <?xml version='1.0' encoding='UTF-8' standalone='no'?>
    <Safex>
    <Attach label="WCC0004"/>
    <Detach/>
    </Safex>

    $ /opt/CA/WorkloadCC/safex/safex -h <EEM_hostname> -u EiamAdmin -p <EiamAdmin_Password> -f ~/safex_wcc.xml
    Setting Translation file:safex.tr
    Setting back end to "<EEM_hostname>"

    Setting locale to "en_us"

    OK:Successfully Authenticated
    OK: action[Attach] with ApplicationInstance label[WCC0004]
    OK: action[Detach] from ApplicationInstance label[WCC0004]
    OK:Total objects Added 0
    OK:Total objects Modified 0
    OK:Total objects Removed 0
    OK:Total objects Skipped 0
    OK:Total objects Exported 0


    Thanks,
    Chandru Venkataraman