Top
PRIMECLUSTER  Web-Based Admin ViewOperation Guide 4.6
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 dialog messages from 0001-0005 and 0076 appear.

Symptom 2

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

Symptom 3

A message such as "FJSVwvbs: OutOfMemoryError" may be output to the Java console screen of the management server, monitoring node or the Java execution log.

Symptom 4

When accessing the management server by starting the Java application (Web-Based Admin View screen), the dialog message 0005 is displayed, and the Web-Based Admin View screen and the dialog messages 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

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

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, and Web-Based Admin View is not started.

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 0003 or 0007 dialog message may not appear when the management server is disconnected.

Symptom 14

The 0006 dialog message is displayed, and the Web-Based Admin View screen is not displayed when accessing the management server by starting the Java application (Web-Based Admin View screen).

Symptom 15

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

Symptom 16

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

Symptom 17

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 18

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 19

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 20

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.

Symptom 21

The message "NoClassDefFoundErr" is displayed and the Web-Based Admin View screen is unable to launch.

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 dialog messages from 0001-0005 and 0076 appear.

No

Corrective action

1

Check the following:

If the connection information set for the shortcut is correct.

If the IP address is correctly specified.

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
-Xmx128m -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 OS might be hung up depending on the client OS version.

In such a case, restart the OS 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

Make sure that accessing is established not via a proxy server.

Also make sure that both the host name and the corresponding IP address of the accessing management server are set not via a proxy.

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 or host name used for the client

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

  • IP address or host name of the primary management server

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

  • IP address or host name of the secondary management server

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

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 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>@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/FJSVwvbs/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".

11

The communication between the client and the management server may be blocked by firewall.

When using firewalld, iptables, ip6tables, or nftables as a firewall on the management server, allow the communication on port numbers used by Web-Based Admin View.

For details on the port numbers used by Web-Based Admin View, see "7.2 Network service port number."

12

If PRIMECLUSTER is configured in a cloud environment, review the security group settings of each cloud.

Refer to "PRIMECLUSTER Installation and Administration Guide Cloud Services" for the security group settings of each cloud.

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

No

Corrective action

1

Refer to "3.1.3.2 Setting up Java application" and set the automatic connection to the management server to "no", and then restart the Web-Based Admin View screen to retry accessing the server.

Symptom 3: A message such as "FJSVwvbs: OutOfMemoryError" may be output to the Java console screen of the management server, monitoring node or the Java execution log.

No

Corrective action

1

Restart Web-Based Admin View on the management server or monitoring node on which the message appeared. Also restart the Web-Based Admin View screen on a client 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

  3. Restart Web-Based Admin View.

    See

    Refer to "6.2 Restart".

Symptom 4: When accessing the management server by starting the Java application (Web-Based Admin View screen), the dialog message 0005 is displayed, and the Web-Based Admin View screen and the dialog messages are not displayed.

No

Corrective action

1

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/hosts" file or DNS. If not, you need to register either in the "/etc/hosts" file or in DNS for host name to be mapped to the IP address.

2

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 -Xmx128m -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 6 and 7.

3

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".

4

  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 9799.

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

5

Edit the configuration file described in "3.1.3.2 Setting up Java application" (WVStartup.properties) to set the current value (default value is 60) or more for the parameter "initialwait".

By setting this parameter, the maximum waiting time to connect from a client to the server can be changed.

File location:

The installation folder in the home folder of a Windows login user

(Example:
C:\Users\[User name]\AppData\Local\Programs\PRIMECLUSTER Web-Based Admin View Startup\)

File name:

WVStartup.properties

Parameter:

initialwait

Function:

Maximum waiting time (second)

Settable values:

Values (default value: 60)

Setting example (in the WVStartup.properties):

initialwait = 120

6

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

7

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>@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/FJSVwvbs/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

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/hosts" file or DNS. If not, you need to register either in the "/etc/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
-Xmx128m -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 6 and 7.

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

Edit the configuration file described in "3.1.3.2 Setting up Java application" (WVStartup.properties) to set a value 60 or more for the parameter "initialwait".

By setting this parameter, the maximum waiting time to connect from a client to the server can be changed.

File location:

The installation folder in the home folder of a Windows login user

(Example:
C:\Users\[User name]\AppData\Local\Programs\PRIMECLUSTER Web-Based Admin View Startup\)

File name:

WVStartup.properties

Parameter:

initialwait

Function:

Maximum waiting time (second)

Settable values:

Values (default value: 60)

Setting example (in the WVStartup.properties):

initialwait = 120

6

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

7

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>@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/FJSVwvbs/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: 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 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, and Web-Based Admin View is not started.

No

Corrective action

1

Check mip, httpip, and the IP address or the host name for the management server in all 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."

2

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

3

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>@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/FJSVwvbs/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 0003 or 0007 dialog message may not appear when the management server is disconnected.

No

Corrective action

1

Restart the Web-Based Admin View screen and retry accessing the management server.

Symptom 14: The 0006 dialog message is displayed, and the Web-Based Admin View screen is not displayed when accessing the management server by starting the Java application (Web-Based Admin View screen).

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
-Xmx128m -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 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>@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/FJSVwvbs/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".

5

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 15: 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 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 16: "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 17: 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 18: 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]

# /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 19: 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 20: 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."

Symptom 21: The message "NoClassDefFoundErr" is displayed and the Web-Based Admin View screen is unable to launch.

No

Corrective action

1

The operation to uninstall IPv4 as stated below may be implemented on the client.

  • netsh interface ipv4 uninstall

If IPv4 was accidentally uninstalled, install it again.

  • netsh interface ipv4 install

PreviousNext
Copyright FUJITSU LIMITED 2019-2021