FastAPI and Cognee as a tool

[LStromann]

=Hi,

I am using LangGraph with Cognee. There is a tool that uses cognee.search to get some results.

Before starting the FastAPI server, I cognify the documents that I have. However, when a tool call is made to cognee.search and I try to run cognify again, it throws an error due to a lock.

I want the process to work like this:

If the cognifying process is already going on, the tool should return that the process is in progress.

Even when the tool call is made, the cognifying process should start.

This discussion was automatically pulled from Discord.

[LStromann]

hey <@1359229044578582699> cognee has a lock mechanism that prevents multiple cognify operations from running simultaneously it is designed to prevent database corruption and ensure data integrity

you can use existing cognify_status tool available in cognee mcp that allows you to track pipeline status

[LStromann]

But after the tool call what If I want to start the process again

[LStromann]

after it completes you can restart the cognify process by checking the status first and then initiating a new cognify operation

[LStromann]

Let me try

[LStromann]

╰────────────────────────────────╯

2025-12-26T08:09:22.159585 [error ] Failed to initialize Kuzu database: IO exception: Could not set lock on file : /home/chinu_tensor/OpsRabbit-v2/.venv/lib/python3.12/site-packages/cognee/.cognee_system/databases/cognee_graph_kuzu.lock
See the docs: https://docs.kuzudb.com/concurrency for more information. [cognee.shared.logging_utils]

Pipeline failed: IO exception: Could not set lock on file : /home/chinu_tensor/OpsRabbit-v2/.venv/lib/python3.12/site-packages/cognee/.cognee_system/databases/cognee_graph_kuzu.lock
See the docs: https://docs.kuzudb.com/concurrency for more information.

I get this when i do cognify after tool call

[LStromann]

can you add this to your .env
SHARED_KUZU_LOCK=true

[LStromann]

what's the error now

[LStromann]

SHARED_KUZU_LOCK=true
this requires redis right??

[LStromann]

Yes kuzu lock feature uses redis

[LStromann]

it worked without redis

[LStromann]

how did it work without redis

[LStromann]

What is you env setup

[LStromann]

If you uses 'SHARED_KUZU_LOCK=false' it uses local threading lock instead of redis

[LStromann]

It is true

[LStromann]

idk Ig i did the cognifying process earlier due to that it worked

[LStromann]

hi <@1373135538147692604>