No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

File server trail different lead to fail to set up emergency resource

Publication Date:  2012-10-08 Views:  37 Downloads:  0
Issue Description
Version:
Emergency command Emergency CC R001C01LCNZ01
Networking:
Server E6000(with NX110), standard networking mode, ECC COMMON and ECS are VCS two-node cluster mode
Board name E2-S1 E2-S2 E2-S3 E2-S4 E2-S5 E2-S6
service module Mportal、ISSWeb、RCCR、GISApp Mportal、ISSWeb、RCCR、GISApp IDM、RMC、ISSApp、IAS IDM、RMC、ISSApp、IAS ECS ECS
deployment two-node two-node two-node two-node two-node two-node

When we need to set up emergency resource and log in ECC COMMON by admin, choose “emergency resource management” in “configuration management”, click “create module” is informed “create module success”, then add new emergency resource, but is informed the error“module is not exist, please contact admin”
Alarm Information
None
Handling Process
1,Login interface is Mportal module, check ISSWEB status is OK, check ISSWEB module and tomcat log, they are all OK
2,The module is created by ISSWEB and save to the path iss.filesys.path that the ISSWeb configuration file webServerConfig.properties, check iss.filesys.path=/home/ecc/fs and find the module file
3,When we create emergency resource it still inform the error“module is not exist, please contact admin”, this process is not search by ISSWEB and open the module file, it need to send to ISSAPP to process but ISSAPP failed to find out it
4,Check ISSAPP configuration file appServerConfig.properties,and find iss.filesys.path=/home/ecc/fileserver is different from ISSWEB. The different share path lead ISSAPP can not find the module that ISSWEB created in /home/ecc/fileserver, this is the error
5,Amend ISSWEB and ISAPP has the same iss.filesys.path, and remount the path menu to make they has the same share path on the file server
6,Restart the tomcat of ISSWEB and ISSAPP, the problem is resolved
Root Cause
The module is located in ISSWEB’s path iss.filesys.path=/home/ecc/fs. This path is created when install ECS the ISSWEB configure the file server path. The module is created by ISSWEB but used by ISSAPP, if ISSAPP can not call this path then it will inform the error“module is not exist, please contact admin”
Suggestions
We need to know each process is execute by which module, the created module and emergency resource are executed by different module, so if the resource pass and share is not free between each step they may make some fault.

END