Azure App Service Nodejs sqlite3 lock issue - CIFS mount noblr

Question

I've been experiencing difficulties to use sqlite3 node module in an Azure Web app Nodejs (Linux Code Hosting)

First node-gyp failed to build the sqlite3 module with NodeJS 14 LTS but succeeds with NodeJS 12 LTS, see this other thread.
Then it failed to run the first and simple "CREATE TABLE" statement of myExpressApp, see the attached app-service.log for the error SQLITE_BUSY: database is locked.

It took me sometimes to finally found the explanation on stackoverflow:

The problem is that /home is mounted as CIFS filesystem which can not deal with SQLite3 lock.

So this workaround suggests to use sqlite PRAGMA journal_mode=wal; whcih does fix my SQLITE_BUSY: database is locked error.
However I would have prefer to add the noblr option to the CIFS filesystem mount as suggested in the previous workaround.

But I'm using the Azure App Service NodeJS Quick Start and I couldn't find how I could set such an option. Could you please [78775-app-service.log][8]point me into the right direction?

Answer 1

Hi @Sébastien Perin per our email discussion, I'm posting my response here to help the broader community. File system mounts isn't something that can be changed by you as it's done in the backend when the app service is first created.

One option that could work is mounting your /databse folder to an Azure File storage mount under Path Mappings on the Configuration blade, see https://learn.microsoft.com/en-us/azure/app-service/configure-connect-to-azure-storage?pivots=container-linux.

The mount path should match the folder directory of your database path e.g. /home/site/wwwroot/database and storage container should be the name of your File share container.

Regards,
Ryan

Answer 2

Hi @Ryan Hill ,

I hope you're doing well. I also have same problem with Linux based Azure app service and sqlite3 database.
I tried your solution but no luck. I'm still getting "General error: 5 database is locked".