This section explains the messages output or displayed by during command execution.
Description
Hadoop is already started.
Description
Hadoop is already stopped.
Description
The Hadoop process (JobTracker) is starting.
Description
The Hadoop process (JobTracker) is not starting.
Description
The Hadoop process shown in $PROCESS failed to start.
Action method
The required communications (port) may have been shut by a firewall. Refer to "A.3 Port List", permit connections for ports used by Interstage Big Data Processing Server, then retry the command.
The SSH daemon is not running or SSH communications may have failed. Review the SSH settings, then re-execute the command.
Communications between the primary and secondary master servers may not have been set so that SSH is possible without a password. Create a public key for both the primary and secondary master servers so that SSH communication is possible without a password, then retry the command.
If none of the above applies, refer to the log (/var/opt/FJSVbdpp/log/bdpp_hadoop.log), take the actions corresponding to the Apache Hadoop error content and Apache Hadoop-related logs, then retry the command.
Description
The Hadoop process shown in $PROCESS failed to stop.
Action method
Refer to the log ("/var/opt/FJSVbdpp/log/bdpp_hadoop.log"), check the Apache Hadoop error content and Apache Hadoop related log, take the appropriate action then re-execute the command.
Description
The cloning server definition file (clone.conf) does not exist.
Action method
Specify a directory where a cloning server definition file (clone.conf) does exist. If a cloning server definition file (clone.conf) does not yet exist, create one.
Description
The slave server for collecting cloning images could not be registered.
Action method
Check that there are no errors in the content of the cloning server definition file (clone.conf).
Description
The server information could not be obtained.
Action method
Check the bdpp_addserver command execution result, then re-execute the command.
Description
Required parameters are not specified.
Action method
Check the usage method of the command.
Description
The slave server for collecting cloning images could not be removed.
Action method
Refer to the log ("/var/opt/FJSVbdpp/log/bdpp_ROR.log") and syslog, take the action advised after the message prefix "FJSVrcx:" then re-execute the command.
Description
The cloning image could not be collected.
Action method
The required communications (port) may have been shut by a firewall. Refer to "A.3 Port List", permit connections for ports used by Interstage Big Data Processing Server, then retry the command.
In the system BIOS settings of the slave server, it is possible that booting from the network interface used by the admin LAN has not been set as first in the boot order. Check the system BIOS settings of the slave server, set booting from the network interface used by the admin LAN is first in the boot order, then retry the command.
If none of the above applies, refer to the log (/var/opt/FJSVbdpp/log/bdpp_ROR.log") and the syslog, take the actions for messages with the prefix "FJSVrcx:" then retry the command.
Note
If there is an error in clone.conf definitions (MAC address, etc.) or cloning image collection fails due to a timeout, the network interface of the slave server that performed the cloning image collection may have changed to "DHCP" due to the cloning process, and not changed back.
If this is the case, log into the slave server and manually restore the settings of the network interface. Next, reset by doing "4.6.1 Network Repliation and Hadoop Unsetup" and "4.2.3 Executing Network Repliation and Hadoop Setup" again.
Description
The cloning image information could not be obtained.
Action method
Check the bdpp_getimage command execution result, then re-execute the command.
Description
The cloning image could not be removed.
Action method
Refer to the log ("/var/opt/FJSVbdpp/log/bdpp_ROR.log") and syslog, take the action advised after the message prefix "FJSVrcx:" then re-execute the command.
Description
The cloning image could not be deployed.
Action method
The required communications (port) may have been shut by a firewall. Refer to "A.3 Port List", permit connections for ports used by Interstage Big Data Processing Server, then retry the command.
In the system BIOS settings of the slave server, it is possible that booting from the network interface used by the admin LAN has not been set as first in the boot order. Check the system BIOS settings of the slave server, set booting from the network interface used by the admin LAN is the first in the boot order, then retry the command.
If the message "FJSVnrmp:ERROR:64780:invalid file format(file=ipaddr.conf, detail=line X)" is output to the log ("/var/opt/FJSVbdpp/log/bdpp_ROR.log") (X is the line number in ipaddr.conf), the definition for the slave server whose cloning image is to be collected is not in the ipaddr.conf file.
Include the definition for the slave server whose cloning image is to be collected in the ipaddr.conf file, redo "4.9.1.1.2 Registering the Network Parameter Automatic Configuration Feature", then recollect the cloning image and distribute it.
If none of the above apply, refer to the log (/var/opt/FJSVbdpp/log/bdpp_ROR.log") and the syslog, take the actions for messages with the prefix "FJSVrcx:" then retry the command.
Description
Failed to register FJSVrcx.conf or ipaddr.conf to the slave server.
Action method
The required communications (port) may have been shut by a firewall. Refer to "A.3 Port List", permit connections for ports used by Interstage Big Data Processing Server, then retry the command.
The FJSVrcx.conf or ipaddr.conf file may not exist or the specified path may be incorrect.
Create the file if FJSVrcx.conf or ipaddr.conf does not exist, or correct the path, then retry the command.
If none of the above apply, refer to the log ("/var/opt/FJSVbdpp/log/bdpp_ROR.log") and the syslog, take the actions for messages with the prefix "FJSVrcx:" then retry the command.
Description
The cloning image storage directory could not be changed.
Action method
Refer to the log ("/var/opt/FJSVbdpp/log/bdpp_ROR.log") and syslog, take the action advised after the message prefix "FJSVrcx:" then re-execute the command.
Description
The command processing completed normally.
Description
The user attempting execution does not have administrator privilege.
Action method
Execute again with system administrator privilege.
