ps2sunvalley

And now it looks like my appdata share is gone.

My 1TB cache filled last night and now none of my dockers are working, nor is the mover moving files to the array. I've searched around and it seems a likely fix was to delete and recreate the docker img, but that seems to do nothing. Any other possibilities? Here's what the Unraid log looks like: text error warn system array login Mar 9 10:26:34 unRaidServer kernel: loop: Write error at byte offset 4339773440, length 4096. Mar 9 10:26:34 unRaidServer kernel: loop: Write error at byte offset 4345737216, length 4096. Mar 9 10:26:34 unRaidServer kernel: I/O error, dev loop2, sector 8479888 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:34 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:34 unRaidServer kernel: I/O error, dev loop2, sector 8476120 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:34 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:34 unRaidServer kernel: I/O error, dev loop2, sector 8487768 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Mar 9 10:26:34 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 11, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:36 unRaidServer root: YouTube-DL: Could not download icon https://raw.githubusercontent.com/SmartPhoneLover/unraid-docker-templates/main/templates/icons/youtube-dl.png Mar 9 10:26:36 unRaidServer kernel: loop: Write error at byte offset 13762560, length 4096. Mar 9 10:26:36 unRaidServer kernel: loop: Write error at byte offset 13639680, length 4096. Mar 9 10:26:36 unRaidServer kernel: loop: Write error at byte offset 10248773632, length 4096. Mar 9 10:26:36 unRaidServer kernel: loop: Write error at byte offset 6615793664, length 4096. Mar 9 10:26:36 unRaidServer kernel: I/O error, dev loop2, sector 26880 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Mar 9 10:26:36 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 12, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:36 unRaidServer kernel: I/O error, dev loop2, sector 26640 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:36 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 13, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:36 unRaidServer kernel: I/O error, dev loop2, sector 20017136 op 0x1:(WRITE) flags 0x100000 phys_seg 4 prio class 2 Mar 9 10:26:36 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 14, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:36 unRaidServer kernel: I/O error, dev loop2, sector 12921472 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:36 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 15, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:36 unRaidServer kernel: loop: Write error at byte offset 6615797760, length 4096. Mar 9 10:26:36 unRaidServer kernel: I/O error, dev loop2, sector 12921480 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:36 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 16, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:39 unRaidServer kernel: loop: Write error at byte offset 14807040, length 4096. Mar 9 10:26:39 unRaidServer kernel: I/O error, dev loop2, sector 28920 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:39 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 17, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:40 unRaidServer kernel: loop: Write error at byte offset 4339773440, length 4096. Mar 9 10:26:40 unRaidServer kernel: loop: Write error at byte offset 4345737216, length 4096. Mar 9 10:26:40 unRaidServer kernel: I/O error, dev loop2, sector 8476120 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:40 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 18, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:40 unRaidServer kernel: I/O error, dev loop2, sector 8487768 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Mar 9 10:26:40 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 19, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:41 unRaidServer kernel: loop: Write error at byte offset 10248773632, length 4096. Mar 9 10:26:41 unRaidServer kernel: loop: Write error at byte offset 2895626240, length 4096. Mar 9 10:26:41 unRaidServer kernel: loop: Write error at byte offset 13762560, length 4096. Mar 9 10:26:41 unRaidServer kernel: loop: Write error at byte offset 2723389440, length 4096. Mar 9 10:26:41 unRaidServer kernel: I/O error, dev loop2, sector 20017136 op 0x1:(WRITE) flags 0x100000 phys_seg 4 prio class 2 Mar 9 10:26:41 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 20, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:41 unRaidServer kernel: I/O error, dev loop2, sector 5655520 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:41 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 21, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:41 unRaidServer kernel: loop: Write error at byte offset 4478357504, length 4096. Mar 9 10:26:41 unRaidServer kernel: I/O error, dev loop2, sector 26880 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Mar 9 10:26:41 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 22, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:41 unRaidServer kernel: I/O error, dev loop2, sector 8746792 op 0x1:(WRITE) flags 0x100000 phys_seg 3 prio class 2 Mar 9 10:26:41 unRaidServer kernel: I/O error, dev loop2, sector 5319120 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Mar 9 10:26:41 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 23, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:41 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 24, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:43 unRaidServer kernel: loop: Write error at byte offset 1954234368, length 4096. Mar 9 10:26:43 unRaidServer kernel: I/O error, dev loop2, sector 3816864 op 0x1:(WRITE) flags 0x1800 phys_seg 3 prio class 2 Mar 9 10:26:43 unRaidServer kernel: loop: Write error at byte offset 880492544, length 4096. Mar 9 10:26:43 unRaidServer kernel: I/O error, dev loop2, sector 1719712 op 0x1:(WRITE) flags 0x1800 phys_seg 3 prio class 2 Mar 9 10:26:43 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 25, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:43 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 26, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:43 unRaidServer kernel: loop: Write error at byte offset 1946599424, length 4096. Mar 9 10:26:43 unRaidServer kernel: I/O error, dev loop2, sector 3801952 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 2 Mar 9 10:26:43 unRaidServer kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 27, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:43 unRaidServer kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Mar 9 10:26:43 unRaidServer kernel: BTRFS info (device loop2: state E): forced readonly Mar 9 10:26:43 unRaidServer kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. Mar 9 10:26:43 unRaidServer kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure Mar 9 10:26:45 unRaidServer kernel: lo_write_bvec: 22 callbacks suppressed Mar 9 10:26:45 unRaidServer kernel: loop: Write error at byte offset 4339773440, length 4096. Mar 9 10:26:45 unRaidServer kernel: loop: Write error at byte offset 4341702656, length 4096. Mar 9 10:26:45 unRaidServer kernel: loop: Write error at byte offset 4342730752, length 4096. Mar 9 10:26:45 unRaidServer kernel: blk_print_req_error: 22 callbacks suppressed Mar 9 10:26:45 unRaidServer kernel: I/O error, dev loop2, sector 8476120 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:45 unRaidServer kernel: btrfs_dev_stat_inc_and_print: 22 callbacks suppressed Mar 9 10:26:45 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 50, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:45 unRaidServer kernel: I/O error, dev loop2, sector 8479888 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:45 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 51, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:45 unRaidServer kernel: I/O error, dev loop2, sector 8481896 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:45 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 52, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:46 unRaidServer root: YouTube-DL: Could not download icon https://raw.githubusercontent.com/SmartPhoneLover/unraid-docker-templates/main/templates/icons/youtube-dl.png Mar 9 10:26:51 unRaidServer kernel: loop: Write error at byte offset 13639680, length 4096. Mar 9 10:26:51 unRaidServer kernel: loop: Write error at byte offset 10241699840, length 4096. Mar 9 10:26:51 unRaidServer kernel: loop: Write error at byte offset 10246664192, length 4096. Mar 9 10:26:51 unRaidServer kernel: I/O error, dev loop2, sector 26640 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:51 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 53, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:51 unRaidServer kernel: I/O error, dev loop2, sector 20003320 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:51 unRaidServer kernel: loop: Write error at byte offset 10643460096, length 4096. Mar 9 10:26:51 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 54, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:51 unRaidServer kernel: loop: Write error at byte offset 10643468288, length 4096. Mar 9 10:26:51 unRaidServer kernel: I/O error, dev loop2, sector 20013016 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:51 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 55, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:51 unRaidServer kernel: I/O error, dev loop2, sector 20788008 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Mar 9 10:26:51 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 56, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:26:51 unRaidServer kernel: I/O error, dev loop2, sector 20788024 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Mar 9 10:26:51 unRaidServer kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 57, rd 0, flush 0, corrupt 0, gen 0 Mar 9 10:27:16 unRaidServer root: YouTube-DL: Could not download icon https://raw.githubusercontent.com/SmartPhoneLover/unraid-docker-templates/main/templates/icons/youtube-dl.png

That makes sense, however I am pretty sure that is working fine as when I look at logs from PiHole my query is returned exactly as it should be. Does anyone think it would be possible to destroy the container and start building fresh? Like if I don't touch the database and point the new container to it will it work? Or will it just be using the same files in /appdata and not really do anything?

So I have been having a problem accessing my nextcloud server. I cannot reach it internally by internal:port no matter what and also my nginx proxy manager has been giving me 502 bad gateway errors for a while too. The straw that may have broken the camel's back was when I moved my DNS provider for my domain over to cloudflare in order to begin using cloudflare tunnels for other apps. As it seems accessing NC through the tunnel is wildly against the TOS for the tunnel I would like to revert back to using NPM for reverse proxying. I use cloud.mydomain.com to access and I am sure that there is a CNAME record pointing cloud.mydomain.com over to nextcloud***.duckdns.org which then of course directs to my public IP. This all appears to be working correctly. Any ideas within the NC container on things I could have jacked up to break the access to my NC instance? I also tested the container via unraid CLI using occ commands to ensure that the container is actually working, and it seems like it is chugging along perfectly.

Yeah, it is logical, however I didn't do anything to change the config that would have broken this. I have changed the containers over to bridge mode and still getting 502 bad gateway from within and outside my home network. And for the container I can open up the console and do some CLI with Nextcloud using some occ commands. Digging into the logs for nextcloud I see a bunch of these entries: 192.168.69.166 - - [08/Mar/2023:20:28:41 -0600] "GET / HTTP/2.0" 500 289 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15" That IP is the IP of the computer I am attempting access from and it makes sense. If I scroll back through the logs you can see logs from before this got messed up showing my username and my public facing IP as what is accessing the container.

I'm using Linuxserver.io container. I basically set everything up back in the day with the SpaceInvaderOne tutorial. Attached is a picture of my docker page showing the port mappings.

Edit: After starting to troubleshoot from the start of this thread her is what happens when I attempt to get to my container: # curl -sS https://192.168.69.102:444/ >/dev/null && echo "Container is reachable" curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to 192.168.69.102:444 Note: my domain is used instead of revealing the domain I own I have no idea what I have done that has completely borked my reverse proxy, but I hope someone could help figure out what happened. Summary, I've been using Nextcloud on unraid docker running through reverse proxy since around 2018 via SpaceInvaderOne tutorial. Sometime last fall the LetsEncrypt docker stopped working and I was able to successfully move it over to NginxProxyManager docker. Last week I changed ISPs and something got wacky and I am not sure what happened. I was also using the reverse proxy for access to Ombi from outside my network. I somehow got Nextcloud working on NPM but I have been troubleshooting the ombi part for over a week. Today, I decided to try to fix ombi by routing it through a cloudflare tunnel, so I moved my domain's DNS over to cloudflare and created the tunnel to ombi with no issues. I was going to attempt to move over Nextcloud as well, however I eventually read that violates the TOS of cloudflare tunnels, so I went to revert nextcloud back to NPM. Now whenever I try to go to cloud.mydomain.com I end up with a 502 bad gateway message. Not sure what I have messed up here, but something is wrong. My NPM and Nextcloud docker exist on the same proxynet network on docker which I set up back in the day thanks to u/SpaceInvaderOne , as for setting up NPM, I used the tutorial set up by Ibracorp. My network looks like this: ATT fiber > BGW320 gateway in passthrough mode > TP Link R605 router > Ports 80 & 443 forwarded to unraidip:180/1443 Right now I have cloudflare dns pointing cloud.mydomain.com to nextcloud***.duckdns.org with a dns record only as that is handling my dynamic dns, which seems to be working correctly. Here is what my nextcloud config file looks like right now, sanitized for personal info Note: I cannot access nextcloud within my network by typing 192.168.69.102:444 Thanks for the help

I'm having the same issue right now.

I'm having same issue here. Exactly what did you wipe?

I've been having a problem lately that eventually it seems the connection will drop and torrents will be auto-added but cannot connect to peers, show availability as 0 and get stuck at 0. Restarting the container and re-adding torrents manually will get them going again. Using PIA as my vpn provider. Anyone else experiencing this?

Well I broke my NC docker. Now getting the This version of Nextcloud is not compatible with > PHP 7.3. You are currently running 7.4.14. I tried the manual upgrade process via the terminal but it just does this: Linux 4.19.107-Unraid. Last login: Fri Jan 22 20:06:47 -0600 2021 on /dev/pts/0. root@unRaidServer:~# docker exec -it nextcloud bash root@5b88b245dc63:/# sudo -u abc php7 /config/www/nextcloud/occ maintenance:mode --on This version of Nextcmv /config/www/nextcloud /config/www/nextcloud-backuprrently running 7.4.14.root@5b88b245dc63:/# mv /config/www/nextcloud /config/www/nextcloud-backup root@5b88b245dc63:/# Any quick fixes or did I really jack this one up?

Just wanted to come and say I am too experiencing the same thing. Honestly I will probably just dig out an old windows laptop to create my USB, but you may want to warn users that the create utility will not work with macOS 10.15.4

An update was released this morning. Mine is working fine now.

And of course it looks like they don't keep older versions up on their docker hub page... so I guess we wait for a fix.

I am currently having the same problem.

It happened to me! (not actually excited) I'm adding a significant amount of media at the moment and I got a server down notification from Tautulli. Sqlite3: Sleeping for 200ms to retry busy DB. terminate called after throwing an instance of 'soci::soci_error' what(): sqlite3_statement_backend::loadOne: database is locked ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.2.1297-4b7ace214/PLEX MEDIA SERVER/4b038dd7-6f17-16f2-6b6beba4-37a6c664.dmp Sqlite3: Sleeping foStarting Plex Media Server. That's what my log on the Plex docker looks like right now I'm not sure what to do with the crash reports from Plex though... Attached is a very current diagnostics from unraid. Also I just restarted the docker and it looks like it is back up and running as normal. unraidserver-diagnostics-20190717-0212.zip

Honestly for me guys, it's come and go on this DB crashing thing. Plex has been working fairly stable from what I can tell (my watching, and other family members with no complaints, same house and remote). But I do see this message in my Plex docker log from time to time: Sqlite3: Sleeping for 200ms to retry busy DB It's not there now, and someone is watching something so frankly, idk wtf is going on.

What if you're like me and when you change directory from /mnt/user to met/cache Plex gets caught in an infinite crash loop?

Okay so my Plex docker is finally throwing this message up in its logs like 1000 times. The container appears to be working (I can browse and play media right now, for the moment) Sqlite3: Sleeping for 200ms to retry busy DB. Attached is diagnostics, currently on 6.7.2 unraidserver-diagnostics-20190705-2330.zip

Yep, appdata only exists on the cache drive.

Is anyone else having issues changing the mapping to the appdata? I've been using /mnt/user/appdata/PlexMediaServer/ for 1.5 years. If I try to only change the mapping in the docker config to /mnt/cache/appdata/PlexMediaServer/ I get this error on an infinite loop: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.2.1297-4b7ace214/PLEX MEDIA SERVER/55e3a89d-90b5-b4b2-3afbf75b-4e9ba94f.dmp Starting Plex Media Server. terminate called after throwing an instance of 'std::runtime_error' And then when I change the directory back to /mnt/user/appdata/PlexMediaServer/ everything returns to normal, and eventually I may get an SQLite error (haven't seen it in a few days now). I'm on 6.7.2 right now.

Just for my info, what are the main symptoms of a corrupt database and how can one confirm that their database is corrupt?

But that would allow things to still run while the app data is in /mnt/user/appdata/PlexMediaServer/ but then get caught in a crash loop when I only change the directory in the docker template to /mnt/cache/appdata/PlexMediaServer/ ? Here is what the specific entry in the docker log looks like when I do that ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.2.1297-4b7ace214/PLEX MEDIA SERVER/55e3a89d-90b5-b4b2-3afbf75b-4e9ba94f.dmp Starting Plex Media Server. terminate called after throwing an instance of 'std::runtime_error' And then when I change the directory back to /mnt/user/appdata/PlexMediaServer/ everything returns to normal, and then randomly the DB will start giving that SQLite error.

I tried that, and in the logs when the container restarted it just gets caught in a crash loop.

Running this docker currently on 6.7.0 I've been having recent issues with Plex recognizing that new files have been added to the library. I have Plex set to "Scan my Library Automatically" but this has become hit or miss over the last week or so, and now it seems broken as I have had to force a library scan the last couple of days in order to get content added. I have even changed my setting for "Library scan interval" from daily (at night when the maintenance tasks run) to every 15 minutes, and that seems to be broken. Today I look in the Plex docker logs and I find a bunch of this: Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Is this causing the problem? Is this related to the apparent issues with 6.7.x?