<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Greg,<div class=""><br class=""></div><div class="">I think this is a different issue. I used to have this all the time, but since switching ovms_server_v2 to mongoose, I haven’t seen it. The features and parameters calls send a relatively large amount of data car->server. I think it is related to free RAM.</div><div class=""><br class=""></div><div class="">Regards, Mark.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 29 Jan 2018, at 2:55 AM, Greg D <<a href="mailto:gregd2350@gmail.com" class="">gregd2350@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Are the disconnects really the result of network drops? I recently "discovered" the Features and Parameters tabs in the V2 app (I'm still new at this) and notice that the server disconnects after some number of records have been sent. The server reconnects about 30 seconds later, but neither tab ever completes. Seems like there is an error along the way that kills the connection. 100% repeatable.<br class="">
<br class="">
Greg<br class="">
<br class=""><br class=""><div class="gmail_quote">On January 28, 2018 10:13:40 AM PST, Stephen Casner <<a href="mailto:casner@acm.org" class="">casner@acm.org</a>> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">I handled wifi shutdowns cleanly when I first implemented telnet and<br class="">ssh as their own tasks. Now that they are under Mongoose, it is out<br class="">of my control. The socket is owned by the Mongoose code.<br class=""><br class=""> -- Steve<br class=""><br class="">On Sun, 28 Jan 2018, Michael Balzer wrote:<br class=""><br class=""><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I've begun working on the webserver and noticed something that may<br class=""> be correlated to this: sockets don't get closed when losing the<br class=""> connection. The effect is visible on both web and telnet server (ssh<br class=""> not tested). To reproduce, switch the Wifi network with an open<br class=""> connection, the port will not be available until timeout.<br class=""><br class=""> Regards,<br class=""> Michael<br class=""></blockquote><hr class=""><br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class=""><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br class=""></pre></blockquote></div><br class="">
-- <br class="">
Sent from my Android device with K-9 Mail. Please excuse my brevity.</div>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>