Home-assistant_v2.db-shm OR home-assistant_v2.db-wal does not exist

Configuration
1

Ran the Check Home Assistant configuration to check my current build (0.108.6) against 0.109, and got the following errors. I went to the terminal and can’t find these files and i have never seen these files before. Anyone know what is going on?

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing... 
starting version 3.2.9
[14:29:14] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:29:15] INFO: Setup udev devices
[14:29:15] INFO: Don't worry, this temporary installation is not overwriting your current one.
[14:29:15] INFO: Installing Home Assistant: latest...
[14:29:15] INFO: Please be patient, this might take a few minutes...
WARNING: You are using pip version 20.0.2; however, version 20.1 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
[14:30:14] INFO: Installed Home Assistant 0.109.0
[14:30:14] INFO: Making a copy of your configuration for checking...
cp: can't stat '/config/home-assistant_v2.db-shm': No such file or directory
cp: can't stat '/config/home-assistant_v2.db-wal': No such file or directory
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
2

These 2 files are created when recorder updates the database, and deleted after the update statement finished. So they exist only briefly.

3

So my research led me to stackoverflow on this and figured this is the case too. However, i guess my main question is how do i have the addon skip over this so that I can truly understand how my config meets with the new 109 build?

4

I don’t think the add-on has a problem with those 2 files.

5

OK well i ran it again this morning, with no changes, and it ran this time around. The only difference is that this morning 0.109.1 was already released and in the changelog i noticed that there was a mention to a bug fix for sqllite. Not at all sure if this is at all related, and there is a good chance it is not related but it is the only key difference from running this addon yesterday vs this morning.

Make sqlalchemy engine connect listener recorder specific ([@bdraco](https://github.com/bdraco) - [#34908](https://github.com/home-assistant/core/pull/34908)) ([recorder docs](https://www.home-assistant.io/integrations/recorder/)) (breaking change)
6

I’m seeing this as well, at least for the last several releases. I restart the “Check Home Assistant configuration” Addon, restart HA, reboot and obviously none of these seems to resolve the issue. It’s down to luck basically, right?

7

Yup it goes away. I would just ignore this error honestly.