Yesterday I found another instance where I could not ssh to OVMS nor
ping it. This time I verified in my router status that the wifi
association with OVMS was "inactive" (down). The iPhone app said that
server-v2 was not hear for 108 minutes. This time I have a full log
file covering back to the previous day, which is attached.
I connected to OVMS with the serial console and the output from the
serial monitor is appended to the attached log file. The "wifi stat"
and "net stat" commands both indicated that the wifi connection was up
when all the external indications were to the contrary. Going back
108 minutes in the log file corresponds roughly to the first instance
of "job queue overflow detected". Perhaps the web server can act as
the canary in the coal mine? There is no indication that the wifi
driver signaled any problem at that time.
Diagnosing this problem is difficult because the loss of connectivity
occurs after a day or a few days of operation. I have not tried the
current esp-idf yet; I may do that, but I'm not sure how long that
would need to operate without loss to determine success.
-- Steve
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev