[Ovmsdev] OVMS Server v3

Mark Webb-Johnson mark at webb-johnson.net
Mon Mar 9 14:20:01 HKT 2020


Craig,

The message 'ovms-server-v3: Tx event server.v2.connecting’ is confusing. It means that ovms-server-v3 is transmitting it’s received event ’server.v2.connecting’ to the MQTT server. The transmitter of the event was presumable server-v2.

The big issue I see is ‘W (269308) gsm-mux: Frame overflow (2048 bytes)’. That would imply the GSM comms is messed up. Surprised anything works after that.

Regards, Mark.

> On 9 Mar 2020, at 1:48 PM, Craig Leres <leres at xse.com> wrote:
> 
> I'm not sure if this is related or not but I just noticed that both of
> my cars were offline WRT the iphone app. The status page shows V2
> connected but there were events shown that it was
> disconnecting/reconnecting. I've been running with V2 TLS enabled ever
> since it was possible. But I see that unchecking that box allows me to
> connect.
> 
> I'm using 3.2.010-30 (Since Sep 29th). I appended some log monitor
> output (with V2 TLS enabled). It sort of looks like there might be some
> interaction between V2 and V3 (I've also had my modules connection to a
> mosquito server with TLS enabled).
> 
> 		Craig
> 
> W (269308) gsm-mux: Frame overflow (2048 bytes)
> I (270038) webserver: HTTP POST /api/execute
> I (270048) webcommand: HttpCommandStream[0x3fa400b8]: 1850360 bytes
> free, executing: server v2 start
> I (270058) ovms-server-v2: Status: Server has been started
> I (270068) ovms-server-v3: Tx event server.v2.waitnetwork
> I (270078) ovms-server-v2: OVMS Server v2 running
> I (270098) ovms-server-v2: Connection is api.openvehicles.com:6870 ????
> I (270108) ovms-server-v2: Status: Connecting...
> I (270128) ovms-server-v3: Tx event server.v2.connecting
> W (270398) ovms-server-v2: Connection failed
> E (270398) ovms-server-v2: Status: Error: Connection failed
> I (270418) ovms-server-v3: Tx event server.v2.waitreconnect
> I (270628) ovms-server-v2: Status: Disconnected
> I (270648) ovms-server-v3: Tx event server.v2.waitreconnect
> I (290128) ovms-server-v2: Connection is api.openvehicles.com:6870 ????
> I (290128) ovms-server-v2: Status: Connecting...
> I (290168) ovms-server-v3: Tx event server.v2.connecting
> W (290608) ovms-server-v2: Connection failed
> E (290608) ovms-server-v2: Status: Error: Connection failed
> E (290618) mongoose: mg_ssl_mbed_log      0x3fa577a4
> mbedtls_ssl_flush_output() returned -1 (-0x0001)
> E (290618) mongoose: mg_ssl_mbed_log      0x3fa577a4 ssl_write_record()
> returned -1 (-0x0001)
> E (290618) mongoose: mg_ssl_mbed_log      0x3fa577a4
> mbedtls_ssl_write_handshake_msg() returned -1 (-0x0001)
> E (290618) mongoose: mg_ssl_if_mbed_err   0x3fa577a4 SSL error: -1
> W (290618) ovms-server-v2: Connection failed
> E (290618) ovms-server-v2: Status: Error: Connection failed
> I (290678) ovms-server-v3: Tx event server.v2.waitreconnect
> I (290748) ovms-server-v3: Tx event server.v2.waitreconnect
> I (290978) ovms-server-v2: Status: Disconnected
> I (290988) ovms-server-v3: Tx event server.v2.waitreconnect



More information about the OvmsDev mailing list