UIM 20.3 - Primary hub wasp won't start - mcs_ws is not valid

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Our Wasp on the primary hub has failed to start so Admin console is not working.

Log shows error complaining 'Failed to start component ... D:\program files (x86)\Nimsoft\probes\service\wasp\webapps\mcs_ws is no valid.

 Caused by: java.lang.IllegalArgumentException: The main resource set specified [C:\Program Files\Nimsoft\probes\service\wasp\webapps\mcs_ws] is not valid

 

Environment

Release : 20.3

Component : UIM - UMP_ADMINCONSOLE2

Cause

Possible webapp corruption 

 

Resolution

To workaround and resolve this issue remove the webapp mcs-ws

This Webapp MCS RESTful Web Services (broadcom.com) provides rest capabilities to the MCS.

 

 

1. Deactivate the affected wasp on the primary hub

2. Use Raw configure to delete the entire webeapp section. (Webapp > mcs-ws) and delete section

 

The entire section should be removed from the wasp.cfg:

Example:

 

  <mcs-ws>
        reloadable = true
        cross_context = true
        <log>
            <com.nimsoft.selfservice.v2.utility>
                loglevel = 5
            </com.nimsoft.selfservice.v2.utility>
            <com.nimsoft.selfservice.v2.database.mapper>
                loglevel = 5
            </com.nimsoft.selfservice.v2.database.mapper>
            <com.nimsoft.selfservice.v2.database>
                loglevel = 5
            </com.nimsoft.selfservice.v2.database>
            <com.nimsoft.selfservice.v2.controller>
                loglevel = 5
            </com.nimsoft.selfservice.v2.controller>
            <com.nimsoft.selfservice.v2.deployer>
                loglevel = 5
            </com.nimsoft.selfservice.v2.deployer>
            <com.nimsoft.selfservice.v2.model>
                loglevel = 5
            </com.nimsoft.selfservice.v2.model>
            <com.nimsoft.selfservice.v2.database.util>
                loglevel = 5
            </com.nimsoft.selfservice.v2.database.util>
        </log>
        load_on_startup = true
        unpack_war = true
        path = /mcsws
        doc_base = mcs_ws
        <mcs>
            device_id_fields = name,origin
        </mcs>
    </mcs-ws>

 

3. Start wasp. 

 

See if wasp starts. 

If wasp starts deploy the lates version of mon_config_service_ws to the same primary hub wasp and the webapp will be reinstalled and not it should work fine.