Skip to main content
Solved

SQLite file locked on FME_SHAREDRESOURCES_DATA

  • December 2, 2021
  • 5 replies
  • 166 views
jelle
Contributor
Forum|alt.badge.img+16
  • jelleContributor
  • Contributor

Hi all, 

 

I have a strange error message in FME Server. I try to create a sqlite file, but it says it is locked. This file did not exist before running the Workspace. Transaction starts at 0.

73	2021-12-2 16:37:35 | SQLite 3 Writer: Opening `\\fme-server******\resources\data\GIPOD\GIPOD_Beta_Token.sqlite' for write operation
74	2021-12-2 16:37:37 | SQLite 3 Writer: Failed to open database '\\fme-serve********\resources\data\GIPOD\GIPOD_Beta_Token.sqlite'. SQLite3 Engine error: `database is locked'
75	2021-12-2 16:37:37 | SQLITE3 writer: A fatal error has occurred. Check the logfile above for details
76	2021-12-2 16:37:37 | JSONExtractor (JSONQueryFactory): A fatal error has occurred. Check the logfile above for details
77	2021-12-2 16:37:37 | HTTPCaller_3 (HTTPFactory): A fatal error has occurred. Check the logfile above for details
78	2021-12-2 16:37:37 | AttributeKeeper (AttributeKeeperFactory): SQLITE3 writer: A fatal error has occurred. Check the logfile above for details
79	2021-12-2 16:37:37 | A fatal error has occurred. Check the logfile above for details
80	2021-12-2 16:37:37 | Bridge failed to output feature on tag `PYOUTPUT'
81	2021-12-2 16:37:37 | PythonCaller (PythonFactory): PythonFactory failed to process feature
82	2021-12-2 16:37:37 | PythonCaller (PythonFactory): A fatal error has occurred. Check the logfile above for details
83	2021-12-2 16:37:37 | Creator_XML_Creator (CreationFactory): A fatal error has occurred. Check the logfile above for details
84	2021-12-2 16:37:37 | SQLite 3 Writer: Aborting write operation
85	2021-12-2 16:37:37 | SQLite 3 Writer: Translation aborted -- rerun specifying "SQLite 3 Writer_START_TRANSACTION 0"

any thoughts?

 

best regards, 

Jelle

 

Best answer by jelle

jelle wrote:

Hi Niels, thank you for your answer.

When I publish a simple Workspace with SQLite or GPKG Readers/Writers, I get similar messages. Could it possibly have to do with the installation of FME Server, or access to certain installation folders?

My problem had to do with  https://www.sqlite.org/faq.html#q5: "But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time."

View original
Did this help you find an answer to your question?

5 replies

nielsgerrits
VIP
Forum|alt.badge.img+53

Do you have one writer or multiple writers accessing the same file?

Does this always fail? Can you create a dummy with a simple workspace only containing a Creator and a writer?

jelle
Contributor
Forum|alt.badge.img+16
  • jelleContributor
  • Author
  • Contributor
  • December 9, 2021
nielsgerrits wrote:

Do you have one writer or multiple writers accessing the same file?

Does this always fail? Can you create a dummy with a simple workspace only containing a Creator and a writer?

Hi Niels, thank you for your answer.

When I publish a simple Workspace with SQLite or GPKG Readers/Writers, I get similar messages. Could it possibly have to do with the installation of FME Server, or access to certain installation folders?

bruceharold
Contributor
Forum|alt.badge.img+17
  • bruceharoldContributor
  • Contributor
  • December 14, 2022
jelle wrote:

Hi Niels, thank you for your answer.

When I publish a simple Workspace with SQLite or GPKG Readers/Writers, I get similar messages. Could it possibly have to do with the installation of FME Server, or access to certain installation folders?

I get the same problem in Desktop Workbench, write a GPKG then use SQLExecutor to create a view and it errors with a read-only error.

jelle
Contributor
Forum|alt.badge.img+16
  • jelleContributor
  • Author
  • Contributor
  • Best Answer
  • December 15, 2022
jelle wrote:

Hi Niels, thank you for your answer.

When I publish a simple Workspace with SQLite or GPKG Readers/Writers, I get similar messages. Could it possibly have to do with the installation of FME Server, or access to certain installation folders?

My problem had to do with  https://www.sqlite.org/faq.html#q5: "But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time."

bruceharold
Contributor
Forum|alt.badge.img+17
  • bruceharoldContributor
  • Contributor
  • December 15, 2022
jelle wrote:

Hi Niels, thank you for your answer.

When I publish a simple Workspace with SQLite or GPKG Readers/Writers, I get similar messages. Could it possibly have to do with the installation of FME Server, or access to certain installation folders?

I'm using local disk, but thanks for the extra context.

Reply


Helpful Members This Week

Community Stats

30,985
Posts
117,433
Replies
38,764
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.