This section explains the messages output or displayed 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 "Appendix D Port List", permit connections for ports used by Interstage Big Data Processing Server, then re-execute the command.
The SSH daemon is not running or SSH communications may have failed. Review the SSH settings, then re-execute the command.
The settings may not permit SSH communications on master servers without a password. Create a public key for both the primary and secondary master servers, and configure settings to enable the servers to communicate without a password both separately and mutually. Then, re-execute 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 re-execute 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 logs, 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 the cloning server definition file clone.conf does exist. If the cloning server definition file clone.conf does not yet exist, create one.
Description
The slave server for creating clone 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 creating clone images could not be removed.
Action method
Refer to the log (/var/opt/FJSVbdpp/log/bdpp_ROR.log) and the syslog, take the action advised after the message prefix "FJSVrcx:", then re-execute the command.
Description
The clone image could not be created.
Action method
The required communications (port) may have been shut by a firewall. Refer to "Appendix D Port List", permit connections for ports used by Interstage Big Data Processing Server, then re-execute 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 as first in the boot order, then re-execute 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 re-execute the command.
Note
If there is an error in clone.conf definitions (such as MAC address) or clone image creation fails due to a timeout, the network interface of the slave server that performed the clone image creation may have changed to "DHCP" due to the cloning process, and not changed back.
If this is the case, log in to the slave server and manually restore the settings of the network interface. Next, reset by performing "7.2.1 Removing the Network Replication Setup" and "6.2.3 Network Replication and Hadoop Setup" again.
Description
The clone image information could not be obtained.
Action method
Check the bdpp_getimage command execution result, then re-execute the command.
Description
The clone image could not be removed.
Action method
Refer to the log (/var/opt/FJSVbdpp/log/bdpp_ROR.log) and the syslog, take the action advised after the message prefix "FJSVrcx:", then re-execute the command.
Description
The clone image could not be deployed.
Action method
The required communications (port) may have been shut by a firewall. Refer to "Appendix D Port List", permit connections for ports used by Interstage Big Data Processing Server, then re-execute 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 as first in the boot order, then re-execute 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 clone image is to be created is not in ipaddr.conf.
Include the definition for the slave server whose clone image is to be created in ipaddr.conf, again perform "6.3.1.3 Registering the Network Parameter and iSCSI Name Automatic Configuration Feature", then recreate the clone image and distribute it.
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 re-execute 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 "Appendix D Port List", permit connections for ports used by Interstage Big Data Processing Server, then re-execute 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 re-execute 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 re-execute the command.
Description
The clone image storage directory could not be changed.
Action method
Refer to the log (/var/opt/FJSVbdpp/log/bdpp_ROR.log) and the syslog, take the action advised after the message prefix "FJSVrcx:", then re-execute the command.
Description
The command processing completed normally.
Supplementary note:
When cloning, this is also output to the system log on slave servers where the clone image is distributed (or slave servers at the clone destination in a virtual environment).
Description
Failed to set the iSCSI initiator name.
Action method
Check if the settings can be found for the server name specified in the setup files clone.conf, ipaddr.conf, and initiator.conf when cloning.
If the settings cannot be found, review the setup files and then re-execute the bdpp_prepareserver command for the slave server whose clone image will be created (or the slave server at the clone source in a virtual environment).
Supplementary note:
This message is output to the system log on slave servers where the clone image is distributed (or slave servers at the clone destination in a virtual environment).
Description
The command cannot be executed, because there is an error in the argument or the option specified in the command.
Action method
Check the reference for each command, and then re-execute the command after confirming how it is used.
Description
The command cannot be executed, because Hadoop or an associated command is running.
Action method
If $PROCESS is "Hadoop"
Use the bdpp_stop command to stop Hadoop, and then re-execute the command.
If $PROCESS is any of the following commands:
bdpp_addserver
bdpp_backup
bdpp_changeimagedir
bdpp_changeslaves
bdpp_deployimage
bdpp_getimage
bdpp_lanctl
bdpp_prepareserver
bdpp_removeimage
bdpp_removeserver
bdpp_restore
bdpp_start
Refer to the output information. When the associated commands have finished executing, re-execute the command.
Description
Processing failed, because a problem occurred during command execution. A message about the cause of the error will be output to the log (to the file under /var/opt/FJSVbdpp/log).
Action method
Typical messages and actions:
If the message "No enough space." is output, the command has failed because of insufficient disk space at the specified backup destination or on the server to be restored.
Refer to "Chapter 14 Backup and Restore", secure the required space, and then re-execute the command.
If the message "$BACKUP_PATH: Already exits." (where $BACKUP_PATH is the backup destination directory specified in the command) is output to the log, the backup has failed because the backup storage directory in the specified directory (FJSVbdpp-backup) or a file with the same name already exists. Delete the directory or specify a different directory as required, and re-execute the command.
If the message "Backup files are not found." is output to the log, the restore could not be executed because the backup files were not found in the specified directory. Specify the correct directory that stores the backup files, and then re-execute the command.
Other messages:
Refer to the log, remove the cause of the error, and then re-execute the command.
Description
The user attempting execution does not have root permissions.
Action method
Re-execute using root permissions.
