StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POUnix Domain Socket Code Fails on Embedded Device
primarykey
Id
20332780
data
AcceptedAnswerId
20333124
AnswerCount
1
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-12-02T16:16:29.980
FavoriteCount
1
LastActivityDate
2013-12-02T16:43:30.810
LastEditDate
LastEditorUserId
0
OwnerUserId
1747088
ParentId
0
PostTypeId
1
Score
0
ViewCount
780
LastEditorDisplayName
text
Body
I've added a Unix domain socket to a project I'm working on. The socket has a simple function, it simply broadcasts data that the code extracts from another device, the idea is that other applications will be able to read this data from the socket. I've written a simple server code, and when I run the code on my laptop, using a Ubuntu 10.04 VM, it works perfectly well. However, when I copy the code over onto the embedded device I'm using the code fails, when my application tries to write to the socket the code exits. In <code>/var/log/messages</code> I see the following messages: <pre><code>Dec 2 15:12:17 box local1.info my-app[17338]: Socket Opened Dec 2 15:12:17 box local1.err my-app[17338]: Socket Failed Dec 2 15:12:17 box local1.err my-app[17338]: Protocol wrong type for socket Dec 2 15:12:38 box local1.info ./server[17178]: accept failed: Invalid argument </code></pre> Here is the server code: <pre><code>#include <stdio.h> #include <sys/un.h> #include <sys/socket.h> #include <sys/types.h> #include <errno.h> #include<syslog.h> #define SV_SOCK_PATH "/tmp/rtig.sock" //path to be used by socket #define BUF_SIZE 256 //Max length of string listened to #define BACKLOG 5 int main(int argc, char *argv[]){ struct sockaddr_un addr; int sfd, cfd; //File Descriptors for the server and the client ssize_t numRead; //Length of the string read from the client. u_int8_t buf[BUF_SIZE]; //String that reads messages char plain[BUF_SIZE]; //Plain string for writing to the log memset(plain, 0, sizeof plain); //blank out plain string openlog(argv[0], LOG_CONS | LOG_PID | LOG_NDELAY, LOG_LOCAL1); //Write the messages to the syslog //---Declare socket-------------------------------------- sfd = socket(AF_UNIX, SOCK_STREAM, 0); if(sfd!=0){ syslog(LOG_INFO, "socket success"); } else{ syslog(LOG_INFO, "socket unsuccessful"); } //--Test to see if there's already a socket at SV_SOCK_PATH, and remove it if there is. if (remove(SV_SOCK_PATH) == -1 && errno !=ENOENT){ syslog(LOG_INFO, "error removing socket"); } //----------------------------------------------------------- //--blank out the socket address, then write the information to it memset(&addr, 0, sizeof(struct sockaddr_un)); addr.sun_family = AF_UNIX; strncpy(addr.sun_path, SV_SOCK_PATH, sizeof(addr.sun_path)-1); //ensure path is null terminated //----Bind the socket to the address------------------------------------- if (bind(sfd, (struct sockaddr *) &addr, sizeof(struct sockaddr_un))!=0){ syslog(LOG_INFO, "bind unsuccessful"); } else{ syslog(LOG_INFO, "bind successful"); } //------------------------------------------------------------------------ //-----Listen on the socket----------------------------------------------- if (listen(sfd, BACKLOG) != 0){ syslog(LOG_INFO, "listen failed"); } else{ syslog(LOG_INFO, "listen succeeded"); } //------------------------------------------------------------------------- //--------Accept messages on the socket------------------------------------ socklen_t csize; while(1){ cfd = accept(sfd, (struct sockaddr *)&addr,&csize); if (cfd < 0) { syslog(LOG_INFO, "accept failed: %s", strerror(errno)); } while ( (numRead=read(cfd, buf, BUF_SIZE)) > 0 ){ dump_packet(buf, numRead); } } //------------------------------------------------------------------------- //---code never gets here but this is how to close the log and the socket-- closelog(); close(cfd); } </code></pre> And here's a simple version of the client that connects to this server from my app: <pre><code>#include <sys/types.h> #include <sys/socket.h> #include <sys/un.h> #define SV_SOCK_PATH "/tmp/rtig.sock" //path to be used by socket #define BACKLOG 5 int isDaemon = 1; void etmlog(int level, char *message) { isDaemon == 1 ? syslog(level, message) : printf(message); } int main(){ struct sockaddr_un addr; unsigned int sockfd; ssize_t numRead; if ((sockfd = socket(AF_UNIX, SOCK_STREAM, 0)) > 0) { etmlog(LOG_INFO, "Socket Opened\n"); } else { etmlog(LOG_ERR, "Socket Failed:\n"); etmlog(LOG_ERR, strerror(errno)); exit(-1); } memset(&addr, 0, sizeof(struct sockaddr_un)); addr.sun_family = AF_UNIX; strncpy(addr.sun_path, SV_SOCK_PATH, sizeof(addr.sun_path) - 1); // -1 ensures null terminated string if (connect (sockfd, (struct sockaddr *)&addr, sizeof(struct sockaddr_un)) == -1) { etmlog(LOG_ERR, "Socket Failed\n"); etmlog(LOG_ERR, strerror(errno)); exit(1); } else { etmlog(LOG_INFO, "Socket Connection Successful\n"); } while (1){ // some data is read into buf up here if (write(sockfd, buf, rdlen) < 0) { etmlog(LOG_ERR, "Write to Socket Failed:"); etmlog(LOG_ERR, strerror(errno)); } } close(sockfd); return 0; } </code></pre> I appreciate that I've just posted a lot of code to read through, but I'd be very grateful if someone could give me a few pointers on this. 
Tags
<c><sockets><unix><unix-socket>
Title
Unix Domain Socket Code Fails on Embedded Device
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJames
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POUnix Domain Socket Code Fails on Embedded Device
 UserUserId
 USJames
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.