Top
PRIMECLUSTER  Web-Based Admin ViewOperation Guide
FUJITSU Software
Appendix B Troubleshooting > B.1 Corrective action
PreviousNext

B.1 Corrective action

This section explains the actions to be taken in the event of a Web-Based Admin View failure.

Be sure to check "Symptom 1" before working on each problem.

Symptom No

Content of Symptom

Symptom 1

The Web-Based Admin View screen cannot be started. Even though it was started, the screen is not displayed properly, or a dialog message from 0001-0005 appears.

Symptom 2

The screen is not switched when clicking the confirmation button for 0003 or 0007 dialog message. The browser is hung up when attempting to reconnect to the management server that was previously connected.

Symptom 3

The message "FJSVwvbs: OutOfMemoryError" may be output to the Java console screen of the management server or monitoring node.

Symptom 4

When the browser accesses the management server, dialog message 0005 is displayed, and the Web-Based Admin View screen and dialog message are not displayed.

Symptom 5

When the IP address of the LAN was changed, the operation of Web-Based Admin View was disabled.

Symptom 6

With the operation management view, the monitoring node cannot be displayed in the node list for each product.

Symptom 7

The screen is not switched when clicking the confirmation button of dialog message.

Symptom 8

It takes a few minutes to show the Web-Based Admin View screen. Even the menu is displayed, the client gets hung up, or the dialog message 0001 appears.

Symptom 9

When a Java Plug-in is used for the client browser, garbage data are jumbled up or the screen display is distorted after accessing the Web-Based Admin View screen or operation management view of each product.

Symptom 10

The message "FJSVwvbs: webview.cnf abnormal" or "Node process abnormal end" is output when starting up or restarting Web-Based Admin view, or starting up a node.

Symptom 11

The message "WARNING: unrelated 'httpip' property." is output when the Web-Based Admin View is started or restarted.

Symptom 12

The manual title is not displayed by manual reference operation after the manual package is installed, or the manual title remains after the package is deleted.

Symptom 13

The dialog message 0023 is displayed when starting the operation management product from the Web-Based Admin View screen.

Symptom 14

The start button of the operation management product gets out of the Web-Based Admin View screen.

Symptom 15

The 0003 or 0007 dialog message may not appear when the management server is disconnected.

Symptom 16

The 0006 dialog message is displayed, and the Web-Based Admin View screen is not displayed when accessing to the management server from the browser.

Symptom 17

The server is unable to login with the user ID and password, and the 0016 dialog message is output.

Symptom 18

"PRIMECLUSTER Global File Services Configuration and Administration Guide" is not displayed in the manual menu.

Symptom 19

The cluster node is not displayed, or an access error occurs when the operation management screen is activated for the first time after Web-Based Admin View installation.

Symptom 20

When reading the URL of Java Plug-in by using Internet Explorer, the message "Welcome to Web-Based Admin View" is not displayed or the dialog of "Security Warning" (If the Java Plug-in should be installed and executed) is displayed in the Web browser.

Symptom 21

The japanese character turns into garbage or is not displayed on a screen.

Symptom 22

The message of 0032 dialog message is displayed in the Web browser when you refer the manual or help.

Symptom 23

Web-Based Admin View or each operation management view (such as GDS operation management view and GFS operation management view) on Web-Based Admin View becomes unusable in process of the operation, or the connection to the management server is cut in process of the operation.

Symptom 24

During the displaying of each operation management view (such as GDS operation management view and GFS operation management view), if the hardware of the client machine is reset or the network of the client machine is cut, you will become to not able to login Web-Based Admin View after it is recovered.

Symptom 25

Monitored nodes might not be displayed on a list of nodes for each product after the network disconnection between the management servers and monitored nodes is recovered.

GFS: Global File Services
GDS: Global Disk Services

Symptom 1: The Web-Based Admin View screen cannot be started. Even though it was started, the screen is not displayed properly, or a dialog message from 0001-0005 appears.

No

Corrective action

1

Check the following:

  • If the designated URL is correct.

  • If the host name is correctly specified.

  • If the environment supports Java Plug-in. (Refer to "3.1.3 Web environment")

  • If the browser type and version are the recommended ones.

  • If the slew mode is selected for NTP settings.

2

Refer to "7.2.1 http port number" and confirm the http port number that is currently set up.

3

Check whether Web-Based Admin View is started on the management server.

Execute the ps(1) command to check whether the following process is started correctly.

[When the monitoring node acts as the management server]

wvAgent /opt/FJSVwvbs
wvAgent /opt/FJSVwvbs
/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>
<java_home>/bin/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs
-mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp
com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs
<java_home>:Environment variable of Web-based Admin View.

[When the monitoring node does not act as the management server]

wvAgent /opt/FJSVwvbs

wvAgent /opt/FJSVwvbs

/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>

If even one process is not running, take actions as described in the following action 9 to 11.

4

The browser might be hung up depending on the client OS or the browser version.

In such a case, restart the browser and retry accessing the management server.

5

Refer to the installation guide for the product and make sure all the required packages are correctly installed.

6

Change NTP settings so that time will be synchronized slowly by the slew mode.

7

Check the proxy setting of the browser not using a proxy server. For the proxy setting, refer to "Proxy setting" in "3.1.3.1 Preparing the Web browser".

Both the host name and corresponding IP address must be set not using a proxy server.

8

Check mip, httpip, and the IP address or the host name for the management server in all the nodes.

  • IP address or host name for identifying own host

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip
    local:mip <IP address or Host name>

  • IP address used for the client

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip
    local:httpip <IP address>

  • IP address of the primary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server
    sys:primary-server <IP address>

  • IP address of the secondary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server
    sys:secondary-server <IP address>

If these parameters are not set up correctly, set correct addresses. Refer to "7.1 Network address", or "7.3 Management server", and "7.5 Multi-network between server and client by classified use".

9

Check if the Java environment is specified by Web-Based Admin.

[How to check the defined Java environment]

# /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home

local:java_home /opt/SMAW/SMAWcj2re/jre


If the Java environment is different from the one Web-Based Admin specified, perform the following setting:

  1. Stop Web-Based Admin View
    Refer to "6.1 Stop" to stop Web-Based Admin View.

  2. Modify the Java environment
    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam java_home /opt/SMAW/SMAWcj2re/jre

  3. Restart Web-Based Admin View
    Refer to "6.2 Restart" to restart Web-Based Admin View.

10

Check if the specified port number has not already been used. Refer to "7.2 Network service port number".

11

Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes.

The following is an example of the webview.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/webview.cnf]

usr:out-time:0
usr:c-tlog-debug:off
usr:look-and-feel:Metal
sys:_serialID:<IP address or Host name>@XXXX.XX.XX XX:XX:XX.XXX
sys:http-home:
sys:s-tlog-debug:on
sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar
sys:health-time:10
sys:keep-time:10
sys:tophtml-suffix:html
sys:httpdif:hme0
sys:n-tlog-debug:on
sys:s-llog-vol:100
sys:n-tlog-vol:200
sys:s-tlog-vol:200
sys:acsif:hme0
sys:s-olog-vol:100
sys:s-elog-vol:100
sys:rmi-cmdread-timer:900
sys:n-pending-events:100
sys:retry-time:30
sys:cluster-lib-path:
sys:cluster-path:
sys:s-llog-num:2
sys:n-tlog-num:5
sys:s-tlog-num:5
sys:group-addr:<IP address>
sys:s-olog-num:5
sys:s-elog-num:2
sys:rmi-cmdwait-timer:900
sys:server-ha:off
sys:secondary-server:<IP address>
sys:primary-server:<IP address>
sys:s-java-option:-Xmx128m

The following is an example of the wvlocal.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf]

local:classpath:
local:cluster-path:
local:cluster-lib-path:
local:mip:<IP address or Host name>
local:httpip:<IP address>
local:server-election:on
local:java_home:/opt/SMAW/SMAWcj2re/jre
local:s-log-path:/var/opt/FJSVwvbs/logs/server
local:n-log-path:/var/opt/FJSVwvbs/logs/node

If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi).

If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset

the node specific parameter on all the management servers and monitoring nodes.

Set up the Network address that is used for Web-Based Admin View on the node. Refer to "7.1 Network address".

  1. Set up the IP addresses of the primary management server and the secondary server. Refer to "7.3 Management server".

  2. Set up the IP address of the open network for clients when the node acts as a management server. Refer to "7.5 Multi-network between server and client by classified use".

  3. Set up the group address. Refer to the method used for command-based setup in "7.4 Secondary management server automatic migration".

  4. Restart Web-Based Admin View. Refer to "6.2 Restart".

Symptom 2: The screen is not switched when clicking the confirmation button for 0003 or 0007 dialog message.  The browser is hung up when attempting to reconnect to the management server that was previously connected.

No

Corrective action

1

Enter the URL of the connected management server in the URL field of the browser and switch the screen manually, or restart the browser, and then retry accessing the server.

Symptom 3: The message "FJSVwvbs: OutOfMemoryError" may be output to the Java console screen of the management server or monitoring node.

No

Corrective action

1

Restart Web-Based Admin View on the management server or monitoring node on which the message appeared. Shut down/restart the client Web browser and then reaccess.

See

For restarting Web-Based Admin View, refer to "6.2 Restart".

2

  1. Stop Web-Based Admin View.

    See

    Refer to "6.1 Stop".

  2. Change a heap size.

    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam s-java-option -Xmx<heap-size>m
    <heap-size>: Heap size. The initial value is 128Mbyte.
    For example,When changing a heap size to 256Mbyte.
    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam s-java-option -Xmx256m
    Restart Web-Based Admin View.

    See

    Refer to "6.2 Restart".

Symptom 4: When the browser accesses the management server, dialog message 0005 is displayed, and the Web-Based Admin View screen and dialog message are not displayed.

No

Corrective action

1

If a name is specified as the host name of the management server in the URL field of the browser, designate the IP address used for the client of the management server. If the authentication dialog box is displayed then, the client DNS settings may be incorrect. In that case, follow the procedure shown below:

The default value of httpip set to the IP address, which is assigned to the displayed node name as a result of executing "uname -n."

If it does not appear, go to Corrective Action 3.

  • If Windows Vista(R) is installed in the client

    Select [View status] of Local area connection from [Control Panel]-[View network status and tasks]. Then, [Properties] is displayed.

    If [User Account Control] dialog box is displayed, click [Continue].

    From the list on the [Networking] tab, select [Internet protocol Version 4 (TCP/IPv4)] and then display [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.

  • If Windows(R) 7 is installed in the client

    View by: Category
    Select [Local Area Connection] from [Control Panel]-[View network status and tasks]. Then, [Properties] is displayed.

    From the list on the [Networking] tab, select [Internet protocol Version 4 (TCP/IPv4)] and then display [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.
    View by: Large icons or Small icons
    Select [Local Area Connection] from [Control Panel]-[Network and Sharing Center]. Then, [Properties] is displayed.

    From the list on the [Networking] tab, select [Internet protocol Version 4 (TCP/IPv4)] and then display [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.

  • If Windows(R) other than 7 is installed in the client

    View by: Category
    Select [Control Panel]-[View network status and tasks], click the <network name> displayed in "Connections" from "View your active networks". Then, click [Properties] from the "General" tab. Select [Internet Protocol Version 4 (TCP/IPv4)] from the list on the "Networking" tab and then click [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.
    View by: Large icons or Small icons
    Select [Control Panel]-[Network and Sharing Center], click the <network name> displayed in "Connections" from "View your active networks". Then, click [Properties] from the "General" tab. Select [Internet Protocol Version 4 (TCP/IPv4)] from the list on the "Networking" tab and then click [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.

2

Confirm whether a combination of the host name (local host name) displayed as a result of executing "uname -n" and the IP address is registered either in the "/etc/inet/hosts" file or DNS. If not, you need to register either in the /etc/inet/hosts file or in DNS for host name to be mapped to the IP address.

3

Check whether Web-Based Admin View is started on the management server.

Execute the ps(1) command to check whether the following process is started correctly.

[When the monitoring node acts as the management server]

wvAgent /opt/FJSVwvbs
wvAgent /opt/FJSVwvbs
/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>
<java_home>/bin/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs
-mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp
com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs
<java_home>:Environment variable of Web-based Admin View.

[When the monitoring node does not act as the management server]

wvAgent /opt/FJSVwvbs
wvAgent /opt/FJSVwvbs
/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>

If even one process is not running, take actions as described in the following action 7 to 9.

4

Check mip, httpip, and the IP address or the host name for the management server in all the nodes.

  • IP address or host name for identifying own host

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip
    local:mip <IP address or Host name>

  • IP address used for the client

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip
    local:httpip <IP address>

  • IP address of the primary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server
    sys:primary-server <IP address>

  • IP address of the secondary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server
    sys:secondary-server <IP address>

If these parameters are not set up correctly, set correct addresses. Refer to "7.1 Network address", or "7.3 Management server", and "7.5 Multi-network between server and client by classified use".

5

  1. Edit and access the following file on the management server:

    File: /etc/opt/FJSVwvbs/etc/WebView.html
    Record: < PARAM NAME=Port VALUE="????" >

  2. Execute the following command:

    # /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c

    If the VALUE in 2 is ????, the same as that in 1, go to Corrective action 6.
    If the VALUE in 2 is nor the same as that in 1, change the RMI port number of fjwv_c, according to "7.2.2 RMI port number".
    # /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c=<RMI port number>
    The initial value is 9399 in Solaris and 9799 in Linux.

After changing the port number, be sure to restart Web-Based Admin View. Refer to "6.2 Restart".

6

Edit the following file in the management server and retry accessing the management server:

File: /etc/opt/FJSVwvbs/etc/WebView.html
File: /etc/opt/FJSVwvbs/etc/Plugin.html
Record: < PARAM NAME=Initial_wait VALUE="??">
Specify 60 or more in "??".

After editing a file, be sure to restart Web-Based Admin View. Refer to "6.2 Restart".

7

Check if the Java environment is specified by Web-Based Admin.

[How to check the defined Java environment]

# /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home

local:java_home /opt/SMAW/SMAWcj2re/jre


If the Java environment is different from the one Web-Based Admin specified, perform the following setting:

  1. Stop Web-Based Admin View
    Refer to "6.1 Stop" to stop Web-Based Admin View.

  2. Modify the Java environment
    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam java_home /opt/SMAW/SMAWcj2re/jre

  3. Restart Web-Based Admin View
    Refer to "6.2 Restart" to restart Web-Based Admin View.

8

Check if the specified port number has not already been used. Refer to "7.2 Network service port number".

9

Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes.

The following is an example of the webview.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/webview.cnf]

usr:out-time:0
usr:c-tlog-debug:off
usr:look-and-feel:Metal
sys:_serialID:<IP address or Host name>@XXXX.XX.XX XX:XX:XX.XXX
sys:http-home:
sys:s-tlog-debug:on
sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar
sys:health-time:10
sys:keep-time:10
sys:tophtml-suffix:html
sys:httpdif:hme0
sys:n-tlog-debug:on
sys:s-llog-vol:100
sys:n-tlog-vol:200
sys:s-tlog-vol:200
sys:acsif:hme0
sys:s-olog-vol:100
sys:s-elog-vol:100
sys:rmi-cmdread-timer:900
sys:n-pending-events:100
sys:retry-time:30
sys:cluster-lib-path:
sys:cluster-path:
sys:s-llog-num:2
sys:n-tlog-num:5
sys:s-tlog-num:5
sys:group-addr:<IP address>
sys:s-olog-num:5
sys:s-elog-num:2
sys:rmi-cmdwait-timer:900
sys:server-ha:off
sys:secondary-server:<IP address>
sys:primary-server:<IP address>
sys:s-java-option:-Xmx128m

The following is an example of the wvlocal.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf]

local:classpath:
local:cluster-path:
local:cluster-lib-path:
local:mip:<IP address or Host name>
local:httpip:<IP address>
local:server-election:on
local:java_home:/opt/SMAW/SMAWcj2re/jre
local:s-log-path:/var/opt/FJSVwvbs/logs/server
local:n-log-path:/var/opt/FJSVwvbs/logs/node

If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi).

If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset

the node specific parameter on all the management servers and monitoring nodes.

  1. Set up the Network address that is used for Web-Based Admin View on the node. Refer to "7.1 Network address ".

  2. Set up the IP addresses of the primary management server and the secondary server. Refer to "7.3 Management server".

  3. Set up the IP address of the open network for clients when the node acts as a management server. Refer to "7.5 Multi-network between server and client by classified use".

  4. Set up the group address. Refer to the method used for command-based setup in "7.4 Secondary management server automatic migration".

  5. Restart Web-Based Admin View. Refer to "6.2 Restart".

Symptom 5: When the IP address of the LAN was changed, the operation of Web-Based Admin View was disabled.

No

Corrective action

1

Change the network address used for Web-Based Admin View in accordance with "7.1 Network address". Then, reset the IP address available to management server setup and the clients, Refer to "7.3 Management server" and "7.5 Multi-network between server and client by classified use".

Symptom 6: With the operation management view, the monitoring node cannot be displayed in the node list for each product.

No

Corrective action

1

Follow the Corrective Action of Symptom 5, and then, restart Web-Based View in accordance with "6.2 Restart".

Symptom 7: The screen is not switched when clicking the confirmation button of dialog message.

No

Corrective action

1

When the picture on the right of the Web-Based Admin View screen is red, the hidden message dialog behind other windows might appear by clicking it. In order to recognize such a hidden dialog, show the picture on the display at all time.

Symptom 8: It takes a few minutes to show the Web-Based Admin View screen.  Even the menu is displayed, the client gets hung up, or the dialog message 0001 appears.

No

Corrective action

1

Set up longer time than the existing [Connection monitoring time between client and server] in the system environment.

2

If a name is specified as the host name of the management server in the URL field of the browser, designate the IP address used for the client of the management server. If the authentication dialog box is displayed then, the client DNS settings may be incorrect. In that case, follow the procedure shown below:

The default value of httpip set to the IP address, which is assigned to the displayed node name as a result of executing "uname -n."

If it does not appear, go to Corrective Action 4.

  • If Windows Vista(R) is installed in the client

    Select [View status] of Local area connection from [Control Panel]-[View network status and tasks]. Then, [Properties] is displayed.

    If [User Account Control] dialog box is displayed, click [Continue].

    From the list on the [Networking] tab, select [Internet protocol Version 4 (TCP/IPv4)] and then display [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.

  • If Windows(R) 7 is installed in the client

    View by: Category
    Select [Local Area Connection] from [Control Panel]-[View network status and tasks]. Then, [Properties] is displayed.

    From the list on the [Networking] tab, select [Internet protocol Version 4 (TCP/IPv4)] and then display [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.
    View by: Large icons or Small icons
    Select [Local Area Connection] from [Control Panel]-[Network and Sharing Center]. Then, [Properties] is displayed.

    From the list on the [Networking] tab, select [Internet protocol Version 4 (TCP/IPv4)] and then display [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.

  • If Windows(R) other than 7 is installed in the client

    View by: Category
    Select [Control Panel]-[View network status and tasks], click the <network name> displayed in "Connections" from "View your active networks". Then, click [Properties] from the "General" tab. Select [Internet Protocol Version 4 (TCP/IPv4)] from the list on the "Networking" tab and then click [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.
    View by: Large icons or Small icons
    Select [Control Panel]-[Network and Sharing Center], click the <network name> displayed in "Connections" from "View your active networks". Then, click [Properties] from the "General" tab. Select [Internet Protocol Version 4 (TCP/IPv4)] from the list on the "Networking" tab and then click [Properties]. If either [Obtain DNS server address automatically] or [Use the following DNS server addresses:] is selected, check if the name is configured in the DNS and mapped to an IP address by the designated DNS server. If neither is selected, go to Corrective Action 3.

3

Confirm whether a combination of the host name (local host name) displayed as a result of executing "uname -n" and the IP address is registered either in the "/etc/inet/hosts" file or DNS. If not, you need to register either in the /etc/inet/hosts file or in DNS for host name to be mapped to the IP address.

4

Check whether Web-Based Admin View is started on the management server.

Execute the ps(1) command to check whether the following process is started correctly.

[When the monitoring node acts as the management server]

wvAgent /opt/FJSVwvbs
wvAgent /opt/FJSVwvbs
/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>
<java_home>/bin/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs
-mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp
com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs
<java_home>:Environment variable of Web-based Admin View.

[When the monitoring node does not act as the management server]

wvAgent /opt/FJSVwvbs
wvAgent /opt/FJSVwvbs
/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>

If even one process is not running, take actions as described in the following action 8 to 10.

5

Check mip, httpip, and the IP address or the host name for the management server in all the nodes.

  • IP address or host name for identifying own host

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip
    local:mip <IP address or Host name>

  • IP address used for the client

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip
    local:httpip <IP address>

  • IP address of the primary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server
    sys:primary-server <IP address>

  • IP address of the secondary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server
    sys:secondary-server <IP address>

If these parameters are not set up correctly, set correct addresses. Refer to "7.1 Network address", or "7.3 Management server", and "7.5 Multi-network between server and client by classified use".

6

  1. Edit and access the following file on the management server:

    File: /etc/opt/FJSVwvbs/etc/WebView.html

    Record: < PARAM NAME=Port VALUE="????" >

  2. Execute the following command:

# /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c

If the VALUE in 2 is ????, the same as that in 1, go to Corrective action 7.
If the VALUE in 2 is nor the same as that in 1, change the RMI port number of fjwv_c, according to "7.2.2 RMI port number".
# /etc/opt/FJSVwvbs/etc/bin/wvSetport fjwv_c=<RMI port number>
The initial value is 9399 in Solaris and 9799 in Linux.

After changing the port number, be sure to restart Web-Based Admin View. Refer to "6.2 Restart".

7

Edit the following file in the management server and retry accessing the management server:

File: /etc/opt/FJSVwvbs/etc/WebView.html
File: /etc/opt/FJSVwvbs/etc/Plugin.html
Record: < PARAM NAME=Initial_wait VALUE="??">
Specify 60 or more in "??".

After editing a file, be sure to restart Web-Based Admin View. Refer to "6.2 Restart".

8

Check if the Java environment is specified by Web-Based Admin.

[How to check the defined Java environment]

# /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home

local:java_home /opt/SMAW/SMAWcj2re/jre


If the Java environment is different from the one Web-Based Admin specified, perform the following setting:

  1. Stop Web-Based Admin View
    Refer to "6.1 Stop" to stop Web-Based Admin View.

  2. Modify the Java environment
    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam java_home /opt/SMAW/SMAWcj2re/jre

  3. Restart Web-Based Admin View
    Refer to "6.2 Restart" to restart Web-Based Admin View.

9

Check if the specified port number has not already been used. Refer to "7.2 Network service port number".

10

Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes.

The following is an example of the webview.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/webview.cnf]

usr:out-time:0
usr:c-tlog-debug:off
usr:look-and-feel:Metal
sys:_serialID:<IP address or Host name>@XXXX.XX.XX XX:XX:XX.XXX
sys:http-home:
sys:s-tlog-debug:on
sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar
sys:health-time:10
sys:keep-time:10
sys:tophtml-suffix:html
sys:httpdif:hme0
sys:n-tlog-debug:on
sys:s-llog-vol:100
sys:n-tlog-vol:200
sys:s-tlog-vol:200
sys:acsif:hme0
sys:s-olog-vol:100
sys:s-elog-vol:100
sys:rmi-cmdread-timer:900
sys:n-pending-events:100
sys:retry-time:30
sys:cluster-lib-path:
sys:cluster-path:
sys:s-llog-num:2
sys:n-tlog-num:5
sys:s-tlog-num:5
sys:group-addr:<IP address>
sys:s-olog-num:5
sys:s-elog-num:2
sys:rmi-cmdwait-timer:900
sys:server-ha:off
sys:secondary-server:<IP address>
sys:primary-server:<IP address>
sys:s-java-option:-Xmx128m

The following is an example of the wvlocal.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf]

local:classpath:
local:cluster-path:
local:cluster-lib-path:
local:mip:<IP address or Host name>
local:httpip:<IP address>
local:server-election:on
local:java_home:/opt/SMAW/SMAWcj2re/jre
local:s-log-path:/var/opt/FJSVwvbs/logs/server
local:n-log-path:/var/opt/FJSVwvbs/logs/node

If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi).

If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset

the node specific parameter on all the management servers and monitoring nodes.

  1. Set up the Network address that is used for Web-Based Admin View on the node. Refer to "7.1 Network address".

  2. Set up the IP addresses of the primary management server and the secondary server. Refer to "7.3 Management server".

  3. Set up the IP address of the open network for clients when the node acts as a management server. Refer to "7.5 Multi-network between server and client by classified use".

  4. Set up the group address. Refer to the method used for command-based setup in "7.4 Secondary management server automatic migration".

  5. Restart Web-Based Admin View. Refer to "6.2 Restart".

Symptom 9: When a Java Plug-in is used for the client browser, garbage data are jumbled up or the screen display is distorted after accessing the Web-Based Admin View screen or operation management view of each product.

No

Corrective action

1

The graphics hardware of the client might be failed. Modify the operation method (see below) or update the graphics driver. If the problem is not solved, contact your local Customer Support.

[For Windows Vista(R)]

  1. Select [Start]-[Control Panel]-[Adjust screen resolution]-[Advanced Setting]- [Troubleshoot] - [Change setting].

  2. If [User Account Control] dialog box is displayed, click [Continue].

  3. Change the settings of the hardware accelerator.

[For Windows(R) 7]

View by: Category

  1. Select [Start]-[Control Panel]-[Adjust screen resolution]-[Advanced Setting]-[Troubleshoot]-[Change setting].

  2. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

  3. Change the settings of the hardware accelerator.

View by: Large icons or Small icons

  1. Select [Start]-[Control Panel]-[Display]-[Adjust screen resolution]-[Advanced Setting]-[Troubleshoot]-[Change setting].

  2. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.

  3. Change the settings of the hardware accelerator.

Note

  • If the problem is not solved even after the performance is lowered to a next level, check the display as turning down the level one by one.

  • The modification of operation method might affect the overall client's graphic displays. When Web-Based Admin View is not used, undo any setup modifications.

Symptom 10: The message "FJSVwvbs: webview.cnf abnormal" or "Node process abnormal end" is output when starting up or restarting Web-Based Admin view, or starting up a node.

No

Corrective action

1

Check if the Java environment is specified by Web-Based Admin.

[How to check the defined Java environment]

# /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home

local:java_home /opt/SMAW/SMAWcj2re/jre


If the Java environment is different from the one Web-Based Admin specified, perform the following setting:

  1. Stop Web-Based Admin View
    Refer to "6.1 Stop" to stop Web-Based Admin View.

  2. Modify the Java environment
    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam java_home /opt/SMAW/SMAWcj2re/jre

  3. Restart Web-Based Admin View
    Refer to "6.2 Restart" to restart Web-Based Admin View.

2

Check mip, httpip, and the IP address or the host name for the management server in all the nodes.

  • IP address or host name for identifying own host

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip
    local:mip <IP address or Host name>

  • IP address used for the client

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip
    local:httpip <IP address>

  • IP address of the primary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server
    sys:primary-server <IP address>

  • IP address of the secondary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-serve
    sys:secondary-server <IP address>

If these parameters are not set up correctly, set correct addresses. Refer to "7.1 Network address", or "7.3 Management server", and "7.5 Multi-network between server and client by classified use".

3

Check if the specified port number has not already been used. Refer to "7.2 Network service port number".

4

Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes.

The following is an example of the webview.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/webview.cnf]

usr:out-time:0
usr:c-tlog-debug:off
usr:look-and-feel:Metal
sys:_serialID:<IP address or Host name>@XXXX.XX.XX XX:XX:XX.XXX
sys:http-home:
sys:s-tlog-debug:on
sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar
sys:health-time:10
sys:keep-time:10
sys:tophtml-suffix:html
sys:httpdif:hme0
sys:n-tlog-debug:on
sys:s-llog-vol:100
sys:n-tlog-vol:200
sys:s-tlog-vol:200
sys:acsif:hme0
sys:s-olog-vol:100
sys:s-elog-vol:100
sys:rmi-cmdread-timer:900
sys:n-pending-events:100
sys:retry-time:30
sys:cluster-lib-path:
sys:cluster-path:
sys:s-llog-num:2
sys:n-tlog-num:5
sys:s-tlog-num:5
sys:group-addr:<IP address>
sys:s-olog-num:5
sys:s-elog-num:2
sys:rmi-cmdwait-timer:900
sys:server-ha:off
sys:secondary-server:<IP address>
sys:primary-server:<IP address>
sys:s-java-option:-Xmx128m

The following is an example of the wvlocal.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf]

local:classpath:
local:cluster-path:
local:cluster-lib-path:
local:mip:<IP address or Host name>
local:httpip:<IP address>
local:server-election:on
local:java_home:/opt/SMAW/SMAWcj2re/jre
local:s-log-path:/var/opt/FJSVwvbs/logs/server
local:n-log-path:/var/opt/FJSVwvbs/logs/node

If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi).

If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset

the node specific parameter on all the management servers and monitoring nodes.

  1. Set up the Network address that is used for Web-Based Admin View on the node. Refer to "7.1 Network address".

  2. Set up the IP addresses of the primary management server and the secondary server. Refer to "7.3 Management server".

  3. Set up the IP address of the open network for clients when the node acts as a management server. Refer to "7.5 Multi-network between server and client by classified use".

  4. Set up the group address. Refer to the method used for command-based setup in "7.4 Secondary management server automatic migration".

  5. Restart Web-Based Admin View. Refer to "6.2 Restart".

Symptom 11: The message  "WARNING: unrelated 'httpip' property." is output when the  Web-Based Admin View is started or restarted.

No

Corrective action

1

Confirm if the IP address of the open network is correctly set up in the management server. Refer to "7.5 Multi-network between server and client by classified use".

Symptom 12: The manual title is not displayed by manual reference operation after the manual package is installed, or the manual title remains after the package is deleted.

No

Corrective action

1

The installation or deletion of the manual contents while Web-Based Admin View is active will not take effect. You need to restart to make it valid. Refer to "6.2 Restart". Restart the Web-Based Admin View, and then retry accessing from the client.

Symptom 13: The dialog message 0023 is displayed when starting the operation management product from the Web-Based Admin View screen.

No

Corrective action

1

Since the access method may vary depending on the operation management product, recheck by referring to the manual of operation management products.

In case of the concurrent use of operation management products with different access methods, refer to "3.3.4 Concurrent use of operation management products with different access methods".

Symptom 14: The start button of the operation management product gets out of the Web-Based Admin View screen.

No

Corrective action

1

If the incorrect access method is applied to start an optional operation management product, the system might show the 0022 dialog message, and then automatically re-access by a correct access method. In such a case, the Web-Based Admin View screen that was displayed by the first incorrect method is exited.

If you need to display this first Web-Based Admin View screen again, start the Web browser and access on the screen.

For details refer to "Concurrent use of operation management products with different access methods".

Symptom 15: The 0003 or 0007 dialog message may not appear when the management server is disconnected.

No

Corrective action

1

Restart the browser and retry accessing the management server

Symptom 16: The 0006 dialog message is displayed, and the Web-Based Admin View screen is not displayed when accessing to the management server from the browser.

No

Corrective action

1

Check whether Web-Based Admin View is started on the management server.

Execute the ps(1) command to check whether the following process is started correctly.

[When the monitoring node acts as the management server]

wvAgent /opt/FJSVwvbs
wvAgent /opt/FJSVwvbs
/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>
<java_home>/bin/java -Dwebview.htdocs=/etc/opt/FJSVwvcnf/htdocs/FJSVwvbs
-mx128m -Djava.security.policy=/opt/FJSVwvbs/etc/.policyAp
com.fujitsu.webview.base.server.ServerMain /opt/FJSVwvbs
<java_home>:Environment variable of Web-based Admin View.

[When the monitoring node does not act as the management server]

wvAgent /opt/FJSVwvbs
wvAgent /opt/FJSVwvbs
/opt/FJSVwvcnf/bin/wvcnfd -b <IP address or Host name> -p <Port number>

If even one process is not running, take actions as described in the following action 3 to 5.

2

Check mip, httpip, and the IP address or the host name for the management server in all the nodes.

  • IP address or host name for identifying own host

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam mip
    local:mip <IP address or Host name>

  • IP address used for the client

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam httpip
    local:httpip <IP address>

  • IP address of the primary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam primary-server
    sys:primary-server <IP address>

  • IP address of the secondary management server

    # /etc/opt/FJSVwvbs/etc/bin/wvGetparam secondary-server
    sys:secondary-server <IP address>

If these parameters are not set up correctly, set correct addresses. Refer to "7.1 Network address", or "7.3 Management server", and "7.5 Multi-network between server and client by classified use".

3

Check if the Java environment is specified by Web-Based Admin.

[How to check the defined Java environment]

# /etc/opt/FJSVwvbs/etc/bin/wvGetparam java_home

local:java_home /opt/SMAW/SMAWcj2re/jre


If the Java environment is different from the one Web-Based Admin specified, perform the following setting:

  1. Stop Web-Based Admin View
    Refer to "6.1 Stop" to stop Web-Based Admin View.

  2. Modify the Java environment
    # /etc/opt/FJSVwvbs/etc/bin/wvSetparam java_home /opt/SMAW/SMAWcj2re/jre

  3. Restart Web-Based Admin View
    Refer to "6.2 Restart" to restart Web-Based Admin View.

4

Check if the specified port number has not already been used. Refer to "7.2 Network service port number".

5

Check whether the definition file (/etc/opt/FJSVwvbs/etc/webview.cnf or /etc/opt/FJSVwvbs/etc/wvlocal.cnf) of Web-Based Admin View is set up correctly on all the management servers or monitoring nodes.

The following is an example of the webview.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/webview.cnf]

usr:out-time:0
usr:c-tlog-debug:off
usr:look-and-feel:Metal
sys:_serialID:<IP address or Host name>@XXXX.XX.XX XX:XX:XX.XXX
sys:http-home:
sys:s-tlog-debug:on
sys:classpath:/opt/FJSVwvbs/etc/jars/swingall.jar
sys:health-time:10
sys:keep-time:10
sys:tophtml-suffix:html
sys:httpdif:hme0
sys:n-tlog-debug:on
sys:s-llog-vol:100
sys:n-tlog-vol:200
sys:s-tlog-vol:200
sys:acsif:hme0
sys:s-olog-vol:100
sys:s-elog-vol:100
sys:rmi-cmdread-timer:900
sys:n-pending-events:100
sys:retry-time:30
sys:cluster-lib-path:
sys:cluster-path:
sys:s-llog-num:2
sys:n-tlog-num:5
sys:s-tlog-num:5
sys:group-addr:<IP address>
sys:s-olog-num:5
sys:s-elog-num:2
sys:rmi-cmdwait-timer:900
sys:server-ha:off
sys:secondary-server:<IP address>
sys:primary-server:<IP address>
sys:s-java-option:-Xmx128m

The following is an example of the wvlocal.cnf file:

[Example of /etc/opt/FJSVwvbs/etc/wvlocal.cnf]

local:classpath:
local:cluster-path:
local:cluster-lib-path:
local:mip:<IP address or Host name>
local:httpip:<IP address>
local:server-election:on
local:java_home:/opt/SMAW/SMAWcj2re/jre
local:s-log-path:/var/opt/FJSVwvbs/logs/server
local:n-log-path:/var/opt/FJSVwvbs/logs/node

If the webview.cnf or wvlocal.cnf file is not in this format, recreate the above file by using an editor (eg. vi).

If the "webview.cnf or wvlocal.cnf" file is created as shown above, take the following steps to reset the node specific parameter on all the management servers and monitoring nodes.

  1. Set up the Network address that is used for Web-Based Admin View on the node. Refer to "7.1 Network address".

  2. Set up the IP addresses of the primary management server and the secondary server. Refer to "7.3 Management server".

  3. Set up the IP address of the open network for clients when the node acts as a management server. Refer to "7.5 Multi-network between server and client by classified use".

  4. Set up the group address. Refer to the method used for command-based setup in "7.4 Secondary management server automatic migration".

  5. Restart Web-Based Admin View. Refer to "6.2 Restart".

6

Through Firewall and NAT, a client may accesses each node on which PRIMECLUSTER is installed.

From a client, do not access each node on which PRIMECLUSTER is installed through Firewall and NAT.

Symptom 17: The server is unable to login with the user ID and password, and the 0016 dialog message is output.

No

Corrective action

1

Check if the user ID and password provided are correctly registered.

2

If no password is assigned for the user ID, set the password.

3

If you continue to login, follow the corrective action 4 below.

4

If the problem is not improved, reconnect from a client after restarting the management server of Web-Based Admin View. Refer to "6.2 Restart".

Symptom 18: "PRIMECLUSTER Global File Services Configuration and Administration Guide" is not displayed in the manual menu.

No

Corrective action

1

The English and Japanese versions of "PRIMECLUSTER Global File Services Configuration and Administration Guide" cannot be displayed at the same time.

Reinstall the manual package of GFS. Refer to "3.3.3 Common menu functions".

GFS: Global File Services

Symptom 19 : The cluster node is not displayed, or an access error occurs when the operation management screen is activated for the first time after Web-Based Admin View installation.

No

Corrective action

1

Take the following steps to check if the setup for primary and secondary management server is properly done. For your reference, you can see "4.3.3 Primary management server", "4.3.4 Secondary management server".

  1. Check the provided [Secondary] information in the upper right of the Web-Based Admin View screen.

  2. Take proper actions according to the information.

    • In case of non-display

      Check if there's any failure or damage in the secondary management server.

      • If any, locate the cause of the node failure and take corrective actions.

      • If not, set up the primary and secondary management server. Refer to "7.3 Management server".

    • In case of displaying "Down"

      Check if there's any failure or damage in the nodes and if the package is correctly installed for each product. If any, take corrective actions.

Symptom 20 : When reading the URL of Java Plug-in by using Internet Explorer, the message "Welcome to Web-Based Admin View" is not displayed or the dialog of "Security Warning" (If the Java Plug-in should be installed and executed) is displayed in the Web browser.

No

Corrective action

1

Verify the following:

  • If the Java Plug-in is installed.

  • If the supported version is updated.

If there is any problem, install Java Plug-in according to "Setting up Java Plug-in" in "3.1.3.2 Required for the Web browser environment".

Note that the dialogue box appears when clicking the icon on "Click here to get the plugin", so select [Cancel].

Symptom 21 : The japanese character turns into garbage or is not displayed on a screen.

No

Corrective action

1

The client might be used where Japanese environment is not set up. Check the environment, and then use the client with proper environment. For details about the recommended display language on your environment, refer to "4.3.1 Display setup".

Symptom 22 : The dialog message of  0032  is displayed in the Web browser when you refer the manual or help.

No

Corrective action

1

Change the settings of the Web browser according to "3.1.3.1 Preparing the Web browser".

Symptom 23 : Web-Based Admin View or each operation management view (such as GDS operation management view and GFS operation management view) on Web-Based Admin View becomes unusable in process of the operation, or the connection to the management server is cut in process of the operation.

No

Corrective action

1

Check whether the port number which uses in Web-Based Admin View overlaps with one in other products.

Check the port numbers which use in Web-Based Admin View.

[Example of checking the port number setting in Solaris]

# /etc/opt/FJSVwvbs/etc/bin/wvSetport

fjwv-h=8081
fjwv_s=9398
fjwv_n=9397
fjwv_c=9399
fjwv_g=9396

[Example of checking the port number setting in Linux]

# /etc/opt/FJSVwvbs/etc/bin/wvSetport

fjwv-h=8081
fjwv_s=9798
fjwv_n=9797
fjwv_c=9799
fjwv_g=9796

If the above port numbers are repeatedly used by other products, refer to "7.2 Network service port number" to change them.

Symptom 24 : During the displaying of each operation management view (such as GDS operation management view or GFS operation management view), if the hardware of the client machine is reset or the network of the client machine is cut, you will become to not able to login Web-Based Admin View after it is recovered.

No

Corrective action

1

Restart Web-Based Admin View. Refer to "6.2 Restart".

Symptom 25 : Monitored nodes might not be displayed on a list of nodes for each product after the network disconnection between the management servers and monitored nodes is recovered.

No

Corrective action

1

Restart Web-Based Admin View. Refer to "6.2 Restart".

PreviousNext
Copyright FUJITSU LIMITED 2006-2018