ISM web cann't login after changing ISM server hostname

Publication Date:  2013-01-06 Views:  235 Downloads:  0
Issue Description
According to ISM configuration part in SingleCLOUD solution document(GPI), ISM has been installed and the server OS hostname is linux. The web can login without problems. But after changing /etc/HOSTNAME and reboot or using command ‘hostname ***’, the web cann't login and the pop-up window prompt ‘Inner error’.
Alarm Information
When login to ISM web, the pop-up window will prompt ‘Inner error'.
Handling Process
a. stop ISM service.
Login to ISM and change directory to ‘installation directory//Runtime/bin’, carry on the command 'sh shutdownSystem.sh'. The output as blew:
System is shutting down. Please wait...

System is shut down successfully.

(User can use command 'ps -ef | grep java' to check whether the service is stopped or not)

b.change contents of file‘hosts’
Change directory to '/etc/', using ‘vi hosts’ to edit contents.Take the hostname 'abc'  and full name 'abc.site'for instance. Change the contents as below:

#
# hosts         This file describes a number of hostname-to-address
#               mappings for the TCP/IP subsystem.  It is mostly
#               used at boot time, when no name servers are running.
#               On small systems, this file can be used instead of a
#               "named" name server.
# Syntax:
#   
# IP-Address  Full-Qualified-Hostname  Short-Hostname
#

127.0.0.1       localhost

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts
127.0.0.1      abc.site abc


c. start ISM service
Change directory to ‘installation directory//Runtime/bin’, carry on the command 'sh startSystem.sh.

End
Root Cause
Because of the GPI of SingleCLOUD has some mistake. The content is only applicable when the ISM server name is 'linux'.
Suggestions
None

END