Table of Contents
Please refer to the MyProxy User's Guide on the MyProxy web site.
Please refer to the MyProxy Reference Manual for documentation of the MyProxy command-line tools.
For a list of common errors in GT, see Error Codes.
Table 3.1. MyProxy Errors
|Error Code||Definition||Possible Solutions|
This error appears as a mutual authentication failure or a server authentication failure, and the error message should list two names: the expected name of the MyProxy server and the actual authenticated name.
By default, the MyProxy clients expect the MyProxy server to be running with a host certificate that matches the target hostname. This error can occur when running the MyProxy server under a non-host certificate or if the server is running on a machine with multiple hostnames.The MyProxy clients authenticate the identity of the MyProxy server to avoid sending passphrases and credentials to rogue servers.
If the expected name contains an IP address, your system is unable to do a reverse lookup on that address to get the canonical hostname of the server, indicating either a problem with that machine's DNS record or a problem with the resolver on your system.
If the server name shown in the error message is acceptable, set the |
|This error indicates that the myproxy-server port (default: 7512) is in use by another process, probably another myproxy-server instance. You cannot run multiple instances of the myproxy-server on the same network port.||
If you want to run multiple instances of the myproxy-server on a machine, you can specify different ports with the |
|This error indicates that the grid-proxy-init command failed when myproxy-init attempted to run it, which implies a problem with the underlying Globus installation.||
grid-proxy-init -debug -verifyfor more information.
|An error from the myproxy-server saying you are "not authorized" to complete an operation typically indicates that the
||See Configuring MyProxy for more information.|
An error saying "Unable to verify remote side's credentials,"
"Couldn't verify the remote certificate," or "alert bad certificate"
often indicates that the client or server's certificate is signed by
an untrusted Certification Authority (CA). The client must have a CA
certificate and signing policy file installed in
||See Configuring Certificates for more information.|
For additional information, see the MyProxy Troubleshooting Page at NCSA.
Table of Contents