INFO: [ 2442] 15:49:53.819 overlay_interface.c:654:overlay_interface_init() Allowing a maximum of 7 packets every 5ms
INFO: [ 2442] 15:49:53.819 keyring.c:1413:keyring_inmemory_identity() Created in-memory identity: 1326FBB259AE28052C66535471188A1F76A3EADB9DDDFD829431CC0C18C4CD5B
INFO: [ 2442] 15:50:07.702 [httpd/1] httpd.c:286:httpd_server_poll() HTTP SERVER, ACCEPT AF_INET:127.0.0.1:60777
INFO: [ 2442] 15:50:07.702 [httpd/1] httpd.c:59:httpd_dispatch() HTTP SERVER, GET /restful/net/peercount
ERROR:[ 2442] 15:50:12.703 [httpd/1] net_restful.c:155:restful_net_peercount() MDP Server error #1: 'Timeout waiting for reply to MDP packet (packet was successfully sent).'
ERROR:[ 2442] 15:50:12.703 [httpd/1] http_server.c:1930:http_request_receive() Internal failure parsing HTTP request: invalid result code -1
INFO: [ 2442] 15:50:12.703 performance_timing.c:80:fd_showstat() 5001ms (100.0%) in 1 calls (max 5001ms, avg 5001.0ms, +child avg 5001.0ms) : http_request_receive
INFO: [ 2442] 15:50:12.704 overlay_mdp.c:323:overlay_mdp_reply() SOCK: AF_UNIX:"/tmp/s/mdp.client.2442.00000001.socket\0\0"
ERROR:[ 2442] 15:50:12.704 overlay_mdp.c:326:overlay_mdp_reply() sendto(fd=3,len=22,addr=AF_UNIX:"/tmp/s/mdp.client.2442.00000001.socket\0\0"): No such file or directory [errno=2]
INFO: [ 2442] 15:50:12.704 overlay_mdp.c:329:overlay_mdp_reply() Closing dead MDP client 'AF_UNIX:"/tmp/s/mdp.client.2442.00000001.socket\0\0"'
You received this message because you are subscribed to the Google Groups "Serval Project Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsub...@googlegroups.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/serval-project-developers.
For more options, visit https://groups.google.com/d/optout.
Okay thanks for the clarification. The single threaded design makes it complicated. I forgot that we already learned that the hard way in our big evaluation in 2016 :)
Pulling all the small bits and pieces out of the serval internals without a clear internal API is too error prone for me and as Andrew is already on the task of implementing the routing API, we will just wait a bit longer and hope for a release "really soon[tm]". Even though I only found the documentation in route-rest-api not an implementation.
At the moment Andrew seem to be the one working on all the stuff we want (iOS library, route-rest-api etc) :D
On Monday, November 6, 2017 at 12:33:31 AM UTC+1, Jeremy Lakeman wrote:Your code is running within the server's single thread, so you blocked it from processing the incoming message.
Since your code is running within the server, you have access to all static state. So you could just copy / call / refactor the existing processing code;The API the server uses internally for MDP is a little different. If you want to send and receive packets between network peers, you need to write event driven code like this;
While waiting for network traffic, you can pause your HTTP processing and specify a failure timeout, eg;
And resume it again later;If you are planning on building some kind of restful routing table functions, Andrew has started writing down the design we've been discussing internally in the route-rest-api branch.
-- Andrew Bettison Senior Software Engineer and...@servalproject.org | Mobile +61 407185656 | Skype ajbettison