Solved

Reconnection causes SIGPIPE signal

Posted on 2006-11-21
4
845 Views
Last Modified: 2012-05-05
I have an infinite for loop where a client app is consistently requesting data from a server, using the GNU C socket library.  (It's all happening locally though.  I'm using my localhost as a server, since this is just a test program.)

The basic routine is:

initialize client socket

for (;;) {
     connect to server
     send request
     recv data
}

The data is received fine, and everything works normally when the above is done ONCE.  But if I do this in a loop, I get SIGPIPE signals after two iterations.  This causes the program to terminate.  I can pass MSG_NOSIGNAL to the send() function, but this just generates various broken pipe error messages.  The client continues to receive data normally, but the SIGPIPE messages keep happening.  

I know that a SIGPIPE means that I'm writing to a socket, but nothing is reading from it.  But this doesn't make sense, because the server clearly is reading from it, since I'm successfully getting the data.  Does anyone know what might be happening here?  

0
Comment
Question by:chsalvia
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 45

Accepted Solution

by:
Kent Olsen earned 250 total points
ID: 17987098

After the receive, close the connection.

Or test that an active connection doesn't exist before you issue the connect().


Kent
0
 
LVL 6

Expert Comment

by:_iskywalker_
ID: 17987127
yes, dont open too much connections, make the opning connection out from the intereaction
0
 
LVL 2

Assisted Solution

by:avsrivastava
avsrivastava earned 250 total points
ID: 17987170
One possibility is that the pipe buffer gets full before the client reads any data, which raises the SIGPIPE message.
You anyways read the data correctly because once the client reads the data, the server can read more.

Solution:
Don't send the MSG_NOSIGNAL, catch the SIGPIPE signal.
When you get the message, sleep for a random amount of time(could be predetermined as well).
When the program wakes, try to write again starting from the position where you left(the return value of write tells you till which byte you managed).


0
 
LVL 2

Expert Comment

by:avsrivastava
ID: 17987184
The pipe by default on linux kernel is 64k, so if the data you are writing is only bytes this would not be the problem though.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This is a short and sweet, but (hopefully) to the point article. There seems to be some fundamental misunderstanding about the function prototype for the "main" function in C and C++, more specifically what type this function should return. I see so…
Examines three attack vectors, specifically, the different types of malware used in malicious attacks, web application attacks, and finally, network based attacks.  Concludes by examining the means of securing and protecting critical systems and inf…
The goal of this video is to provide viewers with basic examples to understand recursion in the C programming language.
The goal of this video is to provide viewers with basic examples to understand and use switch statements in the C programming language.
Suggested Courses

635 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question