On 4/3/26 02:43, Michael Balzer via OvmsDev wrote:
I did a quick test with CAN logging & regular logging enabled while charging, and found no issues. Both files get written correctly.
I didn't test driving, but the CAN logging system does not use vehicle metrics or events in any special way.
The file remaining at 0 bytes and unset time hints at a crash during your drive (before stopping the logger). Did you rule that out?
I don't know how to check module uptime but I know it logs the vin as soon as it sees it after booting and the most recent vin log was a couple of days before the logging attempt.
If so, do you have some plugins or scripts bound to events, that may interfere with logging?
No and /sd/scripts and /store/scripts are empty.
Don't expect the file meta data to change while the logger is running, other than the system logging, the CAN logging deliberately does no `fsync()` calls to keep running at maximum speed.
Right, I knew about that. The longest can capture I have is 29 minutes long and averages over 900 frames per second. Could my problem be that the can data rate is just too high? Looking at the log more closely I see it was having trouble connecting to the v2 server between 1:23am and 10:07am: 2026-04-02 01:23:31.847 PDT W (141523227) ovms-server-v2: Connection failed 2026-04-02 01:23:31.847 PDT E (141523227) ovms-server-v2: Status: Error: Connection failed 2026-04-02 01:23:31.857 PDT E (141523237) ovms-server-v2: Status: Connection lost, reconnecting [...] 2026-04-02 10:07:01.827 PDT W (172933207) ovms-server-v2: Connection failed 2026-04-02 10:07:01.827 PDT E (172933207) ovms-server-v2: Status: Error: Connection failed 2026-04-02 10:07:01.837 PDT E (172933217) ovms-server-v2: Status: Connection lost, reconnecting Perhaps unrelated. Craig