[Ovmsdev] OVMS going comatose

Stephen Casner casner at acm.org
Sun Mar 28 10:31:57 HKT 2021

On Thu, 25 Mar 2021, Stephen Casner wrote:
> Since updating my in-car OVMS with a build from the master branch
> after my WolfSSL update I've experienced a couple of instances where
> connectivity from app was lost.  The first time I needed a quick
> resolution so I just reset OVMS.  It happened again during the night
> while charging, and this time I connected to the console to check
> conditions before resetting.  What I found was that the async console
> was not responding at all.  Since I have OVMS configured to drop into
> gdb on a crash, I should have seen something.  I've turned on logging
> to file to see if that sheds any light.

I had another apparent crash today, now with file logging enabled.
This occurred while on a drive, so away from the home wifi.  The last
log messages indicate that the crash happened when bringing up
networking via the modem connection:

2021-03-27 12:48:39.688 PDT I (176007218) netmanager: MODEM up (with WIFI client down): starting network with MODEM
2021-03-27 12:48:39.698 PDT I (176007228) time: Starting SNTP client
2021-03-27 12:48:39.708 PDT I (176007238) webserver: Launching Web Server
2021-03-27 12:48:39.708 PDT I (176007238) webserver: Binding to port 80 (http)
2021-03-27 12:48:39.708 PDT I (176007238) webserver: Binding to port 443 (https)
2021-03-27 12:48:39.768 PDT I (176007298) telnet: Launching Telnet Server
2021-03-27 12:48:39.768 PDT I (176007298) ssh: Launching SSH Server
2021-03-27 12:48:39.788 PDT I (176007318) ovms-server-v2: Status: Network is up, so attempt network connection

The last logged activity is to start server v2, and I do have TLS
enabled, so this may indicate a problem with the new WolfSSL
integration.  Does this sound similar to any of the other crashes seen

                                                        -- Steve

More information about the OvmsDev mailing list