Forum: DCCP-TP

Forums->DCCP-TP->Can't open socket: No such file or directory

ckoliver	Can't open socket: No such file or directory
	Hi all, i'm havina a (maybe trivial) problem: when I dispatch the discard-server process (and discard_client), after dispatching the dccp-tp process, I got the error message "Can't open socket: No such file or directory", generated when the server and client try to open the socket. Someone could aid me? Thanks in advance, Cristian
	on: Wed 03 of Jun, 2009 [18:54 UTC] reads: 2508

Posted messages Style Plain Threaded Headers Only Sort Newest first Oldest first Find author message ckoliver Re: Can't open socket: No such file or directory on: Wed 03 of Jun, 2009 [18:55 UTC] > Hi all, > i'm having a (maybe trivial) problem: when I dispatch the discard-server process (and discard_client), after dispatching the dccp-tp process, I got the error message "Can't open socket: No such file or directory", generated when the server and client try to open the socket. Someone could aid me? > Thanks in advance, > Cristian author message trphelan Re: Can't open socket: No such file or directory on: Wed 03 of Jun, 2009 [19:12 UTC] Hi Christian, By "dispatch the discard-server process" I assume you mean kill it. When you kill it, that leaves the listening socket open. Then when you restart discard-server, you can't open a new one to listen on because the port is still in use. It'd be nice if the API was able to clean up sockets for processes that die, but that hasn't been implemented yet. Or discard-server could detect the kill and close the socket, but that hasn't been done yet either. For now, if you want to restart a server process you need to restart the protocol process too. Tom P. > Hi all, > i'm havina a (maybe trivial) problem: when I dispatch the discard-server process (and discard_client), after dispatching the dccp-tp process, I got the error message "Can't open socket: No such file or directory", generated when the server and client try to open the socket. Someone could aid me? > Thanks in advance, > Cristian author message ckoliver Re: Can't open socket: No such file or directory on: Fri 05 of Jun, 2009 [19:27 UTC] Hi Tom, sorry for annoying you, but I'm still having problems in running DCCP. I'm using two machines: 200.233.23.66 (griducs server) and 200.233.27.213 (napro-desktop client). I open four windows, two for each machine and follow the steps: 1) start dccp service at the server: ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ ./dccp-tp 2) start dccp service at the client: ckoliver@napro-desktop:~/dccp-tp-r0.10/ports/lprocess$ ./dccp-tp 3) start discard server at the server: ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ ./discard-server 4) start discard client at the client: ckoliver@napro-desktop:~/dccp-tp-r0.10/ports/lprocess$ ./discard-client -a 200.233.23.66 After step 4, I got the messages 1) ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ ./dccp-tp dccp-tp: -1210198336: main: dccp-tp running attached dccp-tp: -1218593904: sendPacket: bad encap 5, packet not sent dccp-tp: -1218593904: sendPacket: bad encap 5, packet not sent dccp-tp: -1218593904: sendPacket: bad encap 5, packet not sent dccp-tp: -1218593904: sendPacket: bad encap 5, packet not sent dccp-tp: -1218593904: sendPacket: bad encap 5, packet not sent dccp-tp: -1218593904: sendPacket: bad encap 5, packet not sent dccp-tp: -1218593904: sendPacket: bad encap 5, packet not sent 2) ckoliver@napro-desktop:~/dccp-tp-r0.10/ports/lprocess$ ./dccp-tp dccp-tp: -1210653008: main: dccp-tp running attached dccp-tp: -1210655856: dispatchTimer: new timer worker 0x80a7f80 dccp-tp: -1244226672: RequestTimeout: socket 0x80a85e4, server 0, request timeout dccp-tp: -1244226672: featureTimeout: negotiation timed out for sock 0x80a85e4, server 0 dccp-tp: -1244226672: RequestTimeout: socket 0x80a85e4, server 0, request timeout dccp-tp: -1244226672: RequestTimeout: socket 0x80a85e4, server 0, request timeout dccp-tp: -1244226672: featureTimeout: negotiation timed out for sock 0x80a85e4, server 0 dccp-tp: -1244226672: RequestTimeout: socket 0x80a85e4, server 0, request timeout dccp-tp: -1244226672: featureTimeout: negotiation timed out for sock 0x80a85e4, server 0 dccp-tp: -1244226672: RequestTimeout: socket 0x80a85e4, server 0, request timeout dccp-tp: -1244226672: featureTimeout: negotiation timed out for sock 0x80a85e4, server 0 dccp-tp: -1244226672: RequestTimeout: socket 0x80a85e4, server 0, request timeout dccp-tp: -1244226672: featureTimeout: negotiation timed out for sock 0x80a85e4, server 0 dccp-tp: -1244226672: RequestTimeout: socket 0x80a85e4, server 0, request timeout dccp-tp: -1235833968: dctpiCloseConnection: closing 0x80a85e4, server 0 dccp-tp: -1235833968: dctpiDestroySock: destroying sock 0x80a85e4, server 0 3) ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ ./discard-server dctp-dcard-server17679: discard-server running attached 4) ckoliver@napro-desktop:~/dccp-tp-r0.10/ports/lprocess$ ./discard-client -a 200.233.23.66 dctp-dcard-client5065: discard-client running attached dctp-dcard-client5065: Connecting to 200.233.23.66... dctp-dcard-client5065: Can't connect: Connection refused ckoliver@napro-desktop:~/dccp-tp-r0.10/ports/lprocess$ e. g., the client can't stablish a connection to the server. Do you know why? Again, thanks in advance, Cristian > Hi all, > i'm havina a (maybe trivial) problem: when I dispatch the discard-server process (and discard_client), after dispatching the dccp-tp process, I got the error message "Can't open socket: No such file or directory", generated when the server and client try to open the socket. Someone could aid me? > Thanks in advance, > Cristian author message trphelan Re: Can't open socket: No such file or directory on: Fri 05 of Jun, 2009 [21:02 UTC] Hi Cristian, Could you try it on one server? So three windows on one computer, one instance each of dccp-tp, discard-server and discard-client (in that order). Tom P. author message ckoliver Re: Re: Can't open socket: No such file or directory on: Fri 05 of Jun, 2009 [22:12 UTC] > Hi Cristian, > > Could you try it on one server? So three windows on one computer, one instance each of dccp-tp, discard-server and discard-client (in that order). > > Tom P. Well, unfortunately, I got the same problem... Take a look: WINDOW DCCP SERVER (started firstly) ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ ./dccp-tp dccp-tp: -1209817408: main: dccp-tp running attached dccp-tp: -1218212976: sendPacket: bad encap 5, packet not sent dccp-tp: -1209820272: dispatchTimer: new timer worker 0x80a8060 dccp-tp: -1251783792: RequestTimeout: socket 0x80a961c, server 0, request timeout dccp-tp: -1218212976: sendPacket: bad encap 5, packet not sent dccp-tp: -1251783792: featureTimeout: negotiation timed out for sock 0x80a961c, server 0 dccp-tp: -1251783792: RequestTimeout: socket 0x80a961c, server 0, request timeout dccp-tp: -1218212976: sendPacket: bad encap 5, packet not sent dccp-tp: -1251783792: RequestTimeout: socket 0x80a961c, server 0, request timeout dccp-tp: -1218212976: sendPacket: bad encap 5, packet not sent dccp-tp: -1251783792: featureTimeout: negotiation timed out for sock 0x80a961c, server 0 dccp-tp: -1251783792: RequestTimeout: socket 0x80a961c, server 0, request timeout dccp-tp: -1218212976: sendPacket: bad encap 5, packet not sent dccp-tp: -1251783792: featureTimeout: negotiation timed out for sock 0x80a961c, server 0 dccp-tp: -1251783792: RequestTimeout: socket 0x80a961c, server 0, request timeout dccp-tp: -1218212976: sendPacket: bad encap 5, packet not sent dccp-tp: -1251783792: featureTimeout: negotiation timed out for sock 0x80a961c, server 0 dccp-tp: -1251783792: RequestTimeout: socket 0x80a961c, server 0, request timeout dccp-tp: -1218212976: sendPacket: bad encap 5, packet not sent dccp-tp: -1251783792: featureTimeout: negotiation timed out for sock 0x80a961c, server 0 dccp-tp: -1251783792: RequestTimeout: socket 0x80a961c, server 0, request timeout dccp-tp: -1243391088: dctpiCloseConnection: closing 0x80a961c, server 0 dccp-tp: -1243391088: dctpiDestroySock: destroying sock 0x80a961c, server 0 WINDOW DISCARD SERVER (started secondly) ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ ./discard-server dctp-dcard-server13821: discard-server running attached WINDOW DISCARD CLIENT ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ ./discard-client dctp-dcard-client13881: discard-client running attached dctp-dcard-client13881: Connecting to 127.0.0.1... dctp-dcard-client13881: Can't connect: Connection refused ckoliver@griducs:~/dccp-tp-r0.10/ports/lprocess$ Cheers, Cristian author message trphelan Re: Can't open socket: No such file or directory on: Fri 05 of Jun, 2009 [22:22 UTC] Hi Cristian, Please try the version of dccp-tp at http://www.phelan-4.com/dccp-tp/dccp-tp-debug.tgz — there are fixes for several bugs in the lprocess support code there that I haven't had time to package up in a new release. Tom P. author message ckoliver Re: Can't open socket: No such file or directory on: Mon 08 of Jun, 2009 [19:25 UTC] Hi Tom, new release worked! Thank you very much! Cheers, Cristian author message trphelan Re: Can't open socket: No such file or directory on: Tue 09 of Jun, 2009 [11:36 UTC] Hi Cristian, Great! I guess I'll have to release that code soon :-). Tom P.

Show posts: All posts Last hour Last 24 hours Last 48 hours