There are probably two possible solutions to this problem:

1. globusrun could check the error that gets returned from acquire_cred
and print out something more informative.

2. The error message:

"Can't read credential's private key from PEM"

might be changed to something more informative.  I think it would
probably have to check the openssl errors and generate an error message
based on that.  Maybe both are necessary.

BTW,  The (null) error strings in the OpenSSL error lines should be
fixed in CVS.

On Tue, 2003-06-10 at 13:14, bugzilla-daemon@mcs.anl.gov wrote:
> http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=989
> 
>            Summary: Error message I get when 'grid-proxy-init' is all that's
>                     needed
>            Product: GSI
>            Version: unspecified
>           Platform: All
>         OS/Version: All
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: gssapi_gsi
>         AssignedTo: meder@mcs.anl.gov
>         ReportedBy: karonis@mcs.anl.gov
>                 CC: slang@mcs.anl.gov,welch@mcs.anl.gov
> 
> 
> Charles Bacon recently installed Globus 2.4.0 on an ANL cluster.  I tried
> to use its 'globusrun' to submit a job to the gatekeeper running on the
> same cluster.  My first attempt failed and after I did a 'grid-proxy-init'
> my second attempt succeeded.  
> 
> Typing 'grid-proxy-init' was just a lucky guess on my part.  The error message
> that I got on my failed first attempt was this:
> 
> ------------------------------------
> gram_init failure:
> GSS Major Status: General failure
> GSS Minor Status Error Chain:
> 
> acquire_cred.c:125: gss_acquire_cred: Error with GSI credential
> globus_i_gsi_gss_utils.c:1289: globus_i_gsi_gss_cred_read: Error with gss 
> credential handle
> globus_gsi_credential.c:359: globus_gsi_cred_read: Error reading user 
> credential
> globus_gsi_credential.c:1092: globus_gsi_cred_read_key: Error reading user 
> credential: Can't read credential's private key from PEM
> OpenSSL Error: pem_lib.c:434: in library: (null), function (null): (null)
> OpenSSL Error: pem_lib.c:666: in library: (null), function (null): (null)
> ------------------------------------
> 
> I've been told that these error messages are the result of our
> "new and improved" error reporting system.  I must confess that all
> that info was not really helpful (i.e., directed me to the solution
> which was to simply do a 'grid-proxy-init').
> 
> Isn't there a better way?
> 
> 
> 
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
> 

Commited changes to globusrun and globusrun-ws to report reasonable messages
for the cases of no proxy found and proxy expired.