I've been seeing lots of "exec_query: database is locked" messages from SBFspot, running on Linux with sqlite-3.6.20-1.el6.x86_64. This causes data points to not be inserted into the database, AFAICS.
```
Error: exec_query() returned : database is locked
Executed Statement: UPDATE Inverters SET Name='SB 3000TL-US-22 100',Type='SB
+3000TLUS-22',SW_Version='02.61.31.R' WHERE Serial=1234567800
```
I'm running two separate inverters, each with their own .cfg file, but they are run sequentially and it looks like this is caused by SBFspotUploadDaemon accessing the SBFspot.db file at the same time.
I've made a small patch to have the exec_query() code retry the operation several times before reporting an error, which seems to have fixed most of the problems. There are still occasional complaints from a few code paths that don't use exec_query() but my SQL knowledge isn't good enough to know if I can resubmit those queries (e.g. day_data, event_data), and they don't happen nearly as often.
A small patch against 3.0.7 is attached.
Comments: Upgrade to sqlite-3.8.10.2-3 seems to have solved the problem
```
Error: exec_query() returned : database is locked
Executed Statement: UPDATE Inverters SET Name='SB 3000TL-US-22 100',Type='SB
+3000TLUS-22',SW_Version='02.61.31.R' WHERE Serial=1234567800
```
I'm running two separate inverters, each with their own .cfg file, but they are run sequentially and it looks like this is caused by SBFspotUploadDaemon accessing the SBFspot.db file at the same time.
I've made a small patch to have the exec_query() code retry the operation several times before reporting an error, which seems to have fixed most of the problems. There are still occasional complaints from a few code paths that don't use exec_query() but my SQL knowledge isn't good enough to know if I can resubmit those queries (e.g. day_data, event_data), and they don't happen nearly as often.
A small patch against 3.0.7 is attached.
Comments: Upgrade to sqlite-3.8.10.2-3 seems to have solved the problem