[Ovmsdev] Strange DNS lookup issue with current build

[Mark Webb-Johnson]

Nice find. That explains a lot of auto-recovered DNS issues over the past few months.

Regards, Mark.


> On 16 Jun 2018, at 4:30 PM, Michael Balzer <dexter at expeedo.de> wrote:
> 
> Got it:
> https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/a4a70b59eb5038a9c374f0b70e4b8d13e9103ea4 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/a4a70b59eb5038a9c374f0b70e4b8d13e9103ea4>
> 
> This may have been responsible for some other DNS issues in the past.
> 
> Regards,
> Michael
> 
> 
> Am 15.06.2018 um 23:52 schrieb Michael Balzer:
>> Answering my own question: yes, the bug has been introduced with commit c1f96e71dd51c44f9aeff9cf5940982b939a8b24, the SPIMEM rework.
>> 
>> Very strange…
>> 
>> 
>> Am 15.06.2018 um 23:35 schrieb Michael Balzer:
>>> …manifesting in "ota status" and web firmware page not being able to show the latest version & info.
>>> 
>>> It seems the error always comes on the web page.
>>> 
>>> On "ota status" it normally only comes once, then successive "ota status" calls work. Loading the web page seems to restart the cycle.
>>> 
>>> I (695311) webserver: HTTP GET /cfg/firmware
>>> W (695361) net: DNS lookup on ovms.dexters-web.de failed err=200
>>> D (695471) webserver: Serve /cfg/firmware: 9940 bytes used, 4171640 free
>>> OVMS# ota status 
>>> Running partition: ota_1
>>> Boot partition:    ota_1
>>> Firmware:          3.1.006-44-gd3fcb8b-dirty/ota_1/edge (build idf ovms-3.1.006-2-g1a1a544a Jun 13 2018 23:28:20)
>>> W (698871) net: DNS lookup on ovms.dexters-web.de failed err=200
>>> OVMS# ota status 
>>> Running partition: ota_1
>>> Boot partition:    ota_1
>>> Firmware:          3.1.006-44-gd3fcb8b-dirty/ota_1/edge (build idf ovms-3.1.006-2-g1a1a544a Jun 13 2018 23:28:20)
>>> Server Available:  3.1.006-45-gd8220ef (is newer)
>>> 
>>> OTA bleeding edge developer build Wed Jun 13 23:54:42 CEST 2018
>>> See ovms3.log for details
>>> 
>>> d8220ef - Web UI: simplified time zone region selection (vehicle config)
>>> d3fcb8b esp32can: Try draining rx fifo in main ESP32CAN_rxframe function
>>> 
>>> This is brand new, has been working flawlessly before. Mark, can this be caused by the aggressive SPIMEM rework?
>>> 
>>> Regards,
>>> Michael
>>> 
>>> -- 
>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>>> 
>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
>> 
>> -- 
>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
>> 
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
> 
> -- 
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180616/bb022f33/attachment.htm>