Hi.
I'm facing a weird problem.
Apparently, without any reason, my ser decide to work every other time. Is
very precise, run now, I restart stops, I restar it works and so on.
Enabling debug I can see the following sequence on a request.
mg_set_option        listening_port [58080]
accept_conn          0x69aed0 72 (nil) (nil)
ns_read_from_socket  0x69aed0 32 <- 131 bytes
on_recv_data         0x5e5ab0 131 0 32
[I] 06 10:53:27 (src/src/rest.c/handler:653) /apiv1/tags/all
close_local_endpoint 0x5e5ab0 3 1 32
on_recv_data         0x5e5ab0 0 0 32
ns_write_to_socket   0x69aed0 32 -> 5345 bytes
ns_read_from_socket  0x69aed0 32 <- 0 bytes
ns_close_conn        0x69aed0 48
mg_ev_handler        0x5e5ab0 0x69aed0 0 closing
close_local_endpoint 0x5e5ab0 0 0 48
ns_server_free       0x537cc0

The next time I run I just get the first line printed.
And got this back from the WGET command. Three tries, the first works, the
second time no.

Have someone experimented this kind of behavior?

Thanks in advance.

Mac-Book:~ carlos$ wget http://ce50.local:58080/apiv1/tags/all

--2014-09-06 10:53:27--  http://ce50.local:58080/apiv1/tags/all

Resolving ce50.local... 192.168.0.27, 2a01:e35:2e13:bc0:21e:c0ff:fe87:5aef

Connecting to ce50.local|192.168.0.27|:58080... connected.

HTTP request sent, awaiting response... 200 OK

Length: 5272 (5.1K) [application/json]

Saving to: 'all.16'


100%[=======================================================================================>]
5,272       --.-K/s   in 0s


2014-09-06 10:53:27 (152 MB/s) - 'all.16' saved [5272/5272]


Mac-Book:~ carlos$ wget http://ce50.local:58080/apiv1/tags/all

--2014-09-06 10:54:39--  http://ce50.local:58080/apiv1/tags/all

Resolving ce50.local... 192.168.0.27, 2a01:e35:2e13:bc0:21e:c0ff:fe87:5aef

Connecting to ce50.local|192.168.0.27|:58080... connected.

HTTP request sent, awaiting response... Read error (Connection reset by
peer) in headers.

Retrying.


--2014-09-06 10:54:44--  (try: 2)  http://ce50.local:58080/apiv1/tags/all

Connecting to ce50.local|192.168.0.27|:58080... failed: Connection refused.

Connecting to ce50.local|2a01:e35:2e13:bc0:21e:c0ff:fe87:5aef|:58080...
failed: Connection refused.

Resolving ce50.local... 192.168.0.27, 2a01:e35:2e13:bc0:21e:c0ff:fe87:5aef

Connecting to ce50.local|192.168.0.27|:58080... failed: Connection refused.

Connecting to ce50.local|2a01:e35:2e13:bc0:21e:c0ff:fe87:5aef|:58080...
failed: Connection refused.

Mac-Book:~ carlos$ telnet ce50.local 58080

Trying 192.168.0.27...

telnet: connect to address 192.168.0.27: Connection refused

Trying 2a01:e35:2e13:bc0:21e:c0ff:fe87:5aef...

telnet: connect to address 2a01:e35:2e13:bc0:21e:c0ff:fe87:5aef: Connection
refused

telnet: Unable to connect to remote host

Mac-Book:~ carlos$







On Fri, Jun 27, 2014 at 5:23 PM, Carlos Tangerino <
[email protected]> wrote:

> Embedded shall be.
> Many thanks
> Carlos
>
>
> On Fri, Jun 27, 2014 at 5:02 PM, Sergey Lyubka <[email protected]> wrote:
>
>> mongoose.c has net_skeleton files embedded inside, there is no need to
>> combine them.
>> If you want to use net skeleton API, just #include "net_skeleton.h" in
>> your code.
>>
>> However if you still want to disable embedded net skeleton code and
>> compile it separately, add -DNOEMBED_NET_SKELETON to your compilation flags.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "mongoose-users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/mongoose-users/KmWjIMHhGoc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/mongoose-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"mongoose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mongoose-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to