Error Reading Failed To Read Token Broken Pipe
- myproxy-logon returns poor error message when server crashes Summary: myproxy-logon returns poor error message when server crashes Status: NEW Product: MyProxy Component: MyProxy Version: 4.2.0 Platform: All All Importance: P3 enhancement TargetMilestone: --- Assigned To: Jim Basney URL: Keywords: Dependson: Blocks: Show dependency tree /graph Reported: 2009-03-18 14:44 by Von Welch Modified: 2009-03-18 14:44 (History) Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description From Von Welch 2009-03-18 14:44:34 The following output is from myproxy-logon when the server segfaulted. The error message is the same regardless whether the password was correct or not. % myproxy-logon Enter MyProxy pass phrase: Failed to receive credentials. Error reading: failed to read token Broken pipe I suggest an error message of the form: % myproxy-logon Enter MyProxy pass phrase: Error communicating with MyProxy server. This usually indicates an fault with the server or a networking error of some sort. Error details: Error reading: failed to read token Broken pipe Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next No search results available Actions: Home | New | Search | | Reports | NewAccount | Help | LogIn [Privacy statements]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Fri, Mar 13, 2015 at 07:17:04AM +0100, stefano piano wrote: > same issue in Trieste, do we need to refresh myproxy ? Same issue all over the sites, http://alimonitor.cern.ch/siteinfo/issues.jsp?level=7&showall=&name= Don't see anything related on https://cern.service-now.com/service-portal/ssb.do?area=IT As Massimo says, the problem is https://bugzilla.mcs.anl.gov/globus/show_bug.cgi?id=6699 really with px403.cern.ch and it doesn't looks as the network-related one: session establishes fine, but after this myproxy-info just hangs: {{{ MyProxy v5.9 Jul 2012 PAM SASL KRB5 LDAP VOMS OCSP Socket bound to port 20000. Attempting to connect to 128.142.201.166:7512 Successfully connected to https://mailman.ct.infn.it/pipermail/grid-prod/2015-March/020020.html myproxy.cern.ch:7512 using trusted certificates directory /etc/grid-security/certificates Using Proxy file (/var/lib/vobox/alice/proxy_repository/+2fC+3dRU+2fO+3dRDIG+2fOU+3dusers+2fOU+3dspbu+2eru+2fCN+3dAndrey+20Zarochentsev+2fCN+3dproxy-voms+20alice+3a+2falice+2fRole+3dlcgadmi) server name: /DC=ch/DC=cern/OU=computers/CN=px403.cern.ch checking that server name is acceptable... server name matches "myproxy at px403.cern.ch" authenticated server name is acceptable [... waits here for a couple of minutes ...] Error reading: failed to read token Broken pipe }}} Probably service is stuck due to some problems with file system, memory or alike. -- Eygene Ryabinkin, National Research Centre "Kurchatov Institute" Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. Previous message: [grid-prod] Problems with a myproxy-server ? Next message: [grid-prod] Problems with a myproxy-server ? Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the grid-prod mailing list
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://stackoverflow.com/questions/4584904/what-causes-the-broken-pipe-error Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What causes the Broken Pipe Error? up vote 42 down vote favorite 12 error reading I know that broken pipe error is thrown when the socket on the peer side is closed. But, in my test I have noted that an immediate 'send' call on this side when the peer side is closed doesn't always lead to a broken pipe error. E.g.: After closing the socket on peer side (I have tried clean closing by calling close and also abnormal closing by killing the peer), error reading failed if I try to send 40 bytes, then I don't get a broken pipe, but, if I try to send 40000 bytes then it immediately gives broken pipe error. What exactly causes broken pipe and can it's behavior be predicted? c broken-pipe share|improve this question edited Jun 9 at 7:53 Robert Siemer 7,09433455 asked Jan 3 '11 at 13:39 Jay 10.6k1551106 add a comment| 3 Answers 3 active oldest votes up vote 32 down vote accepted It can take time for the network close to be observed - the total time is nominally about 2 minutes (yes, minutes!) after a close before the packets destined for the port are all assumed to be dead. The error condition is detected at some point. With a small write, you are inside the MTU of the system, so the message is queued for sending. With a big write, you are bigger than the MTU and the system spots the problem quicker. If you ignore the SIGPIPE signal, then the functions will return EPIPE error on a broken pipe - at some point when the broken-ness of the connection is detected. share|improve this answer answered Jan 3 '11 at 16:55 Jonathan Leffler 439k62509823 3 @varevarao: I don't think that