Balena persistent logs failed to start

[majorz]

The affected device logs reveal:

May 30 11:22:46 localhost balena-persistent-logs[1624]: mv: cannot create regular file '/var/cache/balena-config-vars': File exists
May 30 11:22:46 localhost systemd[1]: balena-persistent-logs.service: Main process exited, code=exited, status=1/FAILURE
May 30 11:22:46 localhost systemd[1]: balena-persistent-logs.service: Failed with result 'exit-code'.
May 30 11:22:46 localhost systemd[1]: Failed to start Balena persistent logs.

This seems to be a racing condition inside balena-config-vars. The cache file is checked for existence, it does not exist, but at the time it is about to be created another instance of balena-config-vars seems to have already created it.

I could not find this reported before - probably because it is rare problem and also hard to spot unless one is looking whether persistent logs were really started.

Restarting the failed balena-persistent-logs service resolved the issue.

[jellyfish-bot]

[majorz] This has attached https://jel.ly.fish/1d93b1d2-6470-419f-b698-e450ff6581d6

[jellyfish-bot]

[kb2ma] This has attached https://jel.ly.fish/a5f69925-3b94-44ef-b824-93b39b15aad2