[Ovmsdev] MQTT and Ovms Server v3
mark at webb-johnson.net
Sat Jul 21 22:30:09 HKT 2018
I have seen the same. I think it must be car->server, as it appears in retained messages.
Most likely a bug in our modifications to the mongoose library, but I’ve reviewed the code and can’t find it. I will keep looking.
> On 20 Jul 2018, at 9:14 PM, Robin O'Leary <ovmsdev at caederus.org> wrote:
> On Thu, Jul 19, 2018 at 11:30:18PM +0100, Robin O'Leary wrote:
>> I did notice some odd things though. Over a period of several hours,
>> there were three occasions where mosquitto_sub showed the topic name
>> truncated to "ovms/caederus/xxx/metr". The values were different
>> each time, and each was a plausible value from a different topic.
>> I'm now running tcpdump to see if the truncation is from car->server or
>> server->client, but of course it hasn't happened since.
> Hmm, I wonder if it could be related that the module crashed and
> rebooted at some point. The web status page says:
> Last boot was 12425 second(s) ago
> Time at boot: 2018-07-20 08:48:33 GMT
> This is reset #1 since last power cycle
> Detected boot reason: Crash (8/14)
> Crash counters: 1 total, 0 early
> Last crash: IllegalInstruction exception on core 0
> PC : 0x00000000 PS : 0x00000000 A0 : 0x00000000 A1 : 0x00000000
> A2 : 0x00000000 A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000000
> A6 : 0x00000000 A7 : 0x00000000 A8 : 0x00000000 A9 : 0x00000000
> A10 : 0x00000000 A11 : 0x00000000 A12 : 0x00000000 A13 : 0x00000000
> A14 : 0x00000000 A15 : 0x00000000 SAR : 0x00000000 EXCCAUSE: 0x00000000
> EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000
> Version: 3.1.008-62-gcdb67ef/ota_1/ro2 (build idf v3.1-dev-1583-g0fb2019f Jul 19 2018 11:04:42)
> There doesn't seem to be much useful information there; any suggestions
> how to track down the cause?
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
More information about the OvmsDev