| Scyld ClusterWare HPC: Reference Guide | ||
|---|---|---|
| << Previous | Next >> | |
bpctl [-h, --help ] [-v, --version ] [-f]
[-M, --master ] [-S num, --slave num ]
[-r dir, --chroot dir] [-s state, --state state ]
[-m mode, --mode mode]
[-u user, --user user] [-g group, --group group]
[-R, --reboot ] [-H, --halt] [-P, --pwroff]
[---cache-purge-fail] [---cache-purge]
[--reconnect master[:port [,local [:port]]]]]
This utility is part of the BProc package and is installed by default. It allows the root user to modify the state of the compute nodes. Compute nodes may be in one of eight states: down, boot, up, error, unavailable, reboot, halt, pwroff. The states are described as follows:
No communication with compute node, and prior node state is unknown.
Node has initialized communication and started but not completed the node_up script. This state is not commandable. It is status information only.
Node is communicating and has completed the node_up script without errors.
Node is communicating and encountered an error while running the node_up script.
Node is communicating and the cluster administrator has marked the node as unavailable to non-root users.
Node will do a software reboot. Node status will show reboot through start of machine shutdown until node_up script has begun.
Node has been commanded to halt. This command causes the node CPUs to execute the halt machine instruction. Once halted the node must be reset by external means to resume normal operations.
Node will power off. This command is valid for nodes that meet the ATX specification. This command requires BIOS support. Non-ATX machines may reboot on this command.
Normally the node will transition from down to boot to up, and will remain up until commanded otherwise. up is the operational state for user programs. User BProc commands will be rejected if the node is not up.
BProc supports a simplified user and group compute node access scheme. Before any action is taken on a node, BProc checks if the user or group match. If either is matched the user action is processed. Note, normal file permissions are still in affect on each node. BProc permissions simply allow users to execute a program on a node. Root bypasses the check and always has access.
User and group changes made with bpctl remain in effect until the node or the beowulf daemons are restarted. After a restart, the user and group information is read from the /etc/beowulf/config file. For persistent changes, you should edit the config file. Note that Beosetup has a convenient way to do this. The new file will take effect when you SIGHUP the daemons or reboot the nodes. With SIGHUP, running jobs will not be affected unless they start a new process and are denied node access based on the file changes.
Anytime the beowulf daemons are restarted, all nodes will be initialized to the down state. Any node history will be lost. When this occurs, previously communicating nodes will reboot and attempt to re-establish communication after a 30 second timeout.
The following options are available to bpctl:
Print the command usage message and exit. If -h is the first option, all other options will be ignored. If -h is not the first option, the other options will be parsed up to the -h option, but no action will be taken.
Print the command version number and exit. If -v is the first option, all other options will be ignored. If -v is not the first option, the other options will be parsed up to the -v option, but no action will be taken.
Fast mode. Whenever possible, do not wait for acknowledgment from compute nodes.
Specifies that the remaining options apply to the master node.
Specifies that the remaining options apply to the specified compute node. The num can range from 0 to the total number of nodes minus one.
Command the compute daemon to chroot to the indicated directory. After doing this, all processes started on a node via BProc will see the directory dir as their root directory. This command is only usable on compute nodes.
Set the node to the indicated state. Valid state values are down, up, error, unavailable, reboot, halt, or pwroff. Setting state to down causes the node to reboot due to a communications timeout after 30 seconds.
Set the permission bits for the indicated node. Not valid after -M.
Set the user id for the indicated node. Will reject invalid users. Numbers or strings may be used. A numeric user id will be converted to a name if the name is known. Not valid after -M.
Set the group id for the indicated node. Will reject invalid groups. Numbers or strings may be used. A numeric group id will be converted to a names if the name is known. Not valid after -M.
Reboot the indicated node.
Halt the indicated node.
Power off the indicated node.
Purge the library cache fail list.
Purge library cache.
Reconnect to the front-end.
This command will cause all nodes to reboot:
[root@cluster ~] # bpctl -S all -s reboot |
This command returns an error, because boot is not commandable:
[root@cluster ~] # bpctl -S 4 -s boot Non-commandable node state: boot |
The following sets the node 3 user to "foo", which must be a valid user:
[root@cluster ~] # bpctl -S 3 -u foo |
Upon successful completion, bpctl returns 0.
On failure, an error message is printed to stderr and bpctl returns 1.
| << Previous | Home | Next >> |
| beoserv | Up | bplib |