The SQlite3 backend gives "create pin: database is locked" when attempting to create a pin

[SuzanneSoy]

./sips -dbdriver sqlite3 -db 'database.sqlite3?_fk=1' -addr ':8051' &
sleep 5
./sipsctl users add --dbdriver sqlite3 --db 'database.sqlite3?_fk=1' user-name
./sipsctl tokens add --dbdriver sqlite3 --db 'database.sqlite3?_fk=1' --user user-name

ipfs pin remote service add mysips http://my_domain:8051 TOKEN
echo 'Hi' > /tmp/hello
h=$(ipfs add --pin=false -Q /tmp/hello)
ipfs pin remote add --service=mysips --name=hi-example "$h"

2023/04/15 23:48:23 [INFO] (cmd/sips/sips.go:63) database opened at "database.sqlite3?_fk=1"
2023/04/15 23:48:23 [INFO] (cmd/sips/sips.go:66) running database migration
2023/04/15 23:48:23 [INFO] (cmd/sips/sips.go:105) starting server on ":8051"
2023/04/15 23:50:19 [ERROR] (cmd/sips/pinhandler.go:119) create pin: database is locked

[DeedleFake]

This is expected behavior, unfortunately, and one of the main reasons why the Postgres backend was added as well. SQLite3 doesn't allow multiple processes to access the same database file simultaneously. In order to run sipsctl, sips can't also be running.

Edit: Clarification: SQLite3 doesn't allow multiple concurrent write accesses to the database. SIPS does not coordinate this, so it will fail. I'll try to take a look when I get a chance to see if I can do something about it.

[SuzanneSoy]

The pin remote add action is done way after sipsctl exited, do you mean that if sipsctl is executed while sips is running, sips needs to be restarted otherwise its connection is broken? 🤔

I tried:

# Do the database init/migration and kill the sips server
./sips -dbdriver sqlite3 -db 'database.sqlite3?_fk=1' -addr ':8051' & PID=$!
sleep 5
kill $PID

# add the user and create its token
./sipsctl users add --dbdriver sqlite3 --db 'database.sqlite3?_fk=1' user-name
./sipsctl tokens add --dbdriver sqlite3 --db 'database.sqlite3?_fk=1' --user user-name

# Sstart sips again, now that sipsctl has finished working
./sips -dbdriver sqlite3 -db 'database.sqlite3?_fk=1' -addr ':8051' &

ipfs pin remote service add mysips http://my_domain:8051 TOKEN
echo 'Hi' > /tmp/hello
h=$(ipfs add --pin=false -Q /tmp/hello)
ipfs pin remote add --service=mysips --name=hi-example "$h"

and get the same error

[DeedleFake]

The pin remote add action is done way after sipsctl exited, do you mean that if sipsctl is executed while sips is running, sips needs to be restarted otherwise its connection is broken?

No, it definitely shouldn't need to be. You're right, I misread your initial post. Hmmm... Strange. I'll take a look when I get a chance.