Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Conﬁguring a System

Using Distributed Systems Administration Utilities

Chapter 3244

— pdsh@<local hostname>: gethostbyname(“<target

hostname>”) failed

Reason: When the hostname is unknown.

— pdsh@<local hostname>: <target hostname>: connect:

Connection refused

Reason: The target system is unreachable. The r services might

be disabled for this system.

— pdsh@<local hostname>: <target hostname>: connect:

timed out

Reason: The hostname exists (e.g. the ip address lookup

succeeded) but the system is not up or not reachable.

— rresvport: bind: Permission denied pdsh@<local

hostname>: <local hostname>: rcmd: socket: Permission

denied

Reason: An unprivileged user is attempting to use the remote

shell transport. See the Security Notes section for details on

allowing unprivileged users to use pdsh with the remote shell

transport.

— <target hostname>: remshd: Login incorrect.

remote

Reason: The user’s $HOME/.rhosts on the remote system is not

allowing access.

• Target node error messages:

— <target hostname>: sh: <command name>: not found

Reason: The command does not exist on the target node. Note

that the remote shell invoked by pdsh has only a minimal path.

The user’s login scripts are not executed on the remote nodes.

Make sure to specify commands using full paths.