-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milvus Lite on Unix, lock file and refuse to connect #195
Comments
This is an error message from sqlite3. There may be a limitation or problem with the underlying file system that is causing the database to be locked. Try running it in a different directory. |
I'm having the same issue on mac os, the lock is not removed. |
I am having the same issue! |
Same problem here on Fedora 40. |
@junjiejiangjjj |
I have run the script thousands of times on both Mac and Ubuntu, and I have not been able to reproduce this issue. |
Trying to use Milvus Lite on Unix, a user repeatedly gets a lock file and error message they cannot connect to Milvus Lite.
Code used:
https://milvus.io/docs/quickstart.md
Error message:
E20240722 17:51:48.802269 71268 collection_meta.cpp:94] [SERVER][CreateTable][milvus] Create table failed, errs: database is locked
E20240722 17:51:48.802600 71268 server.cpp:73] [SERVER][main][milvus] Init milvus failed
Failed to create new connection using: 6aa54c5d05b945488b9f5fc0bc5500c1
File /anaconda/envs/test/lib/python3.11/site-packages/pymilvus/client/grpc_handler.py:150, in GrpcHandler._wait_for_channel_ready(self, timeout)
148 self._setup_identifier_interceptor(self._user, timeout=timeout)
149 except grpc.FutureTimeoutError as e:
--> 150 raise MilvusException(
151 code=Status.CONNECT_FAILED,
152 message=f"Fail connecting to server on {self._address}, illegal connection params or server unavailable",
153 ) from e
154 except Exception as e:
155 raise e from e
MilvusException: <MilvusException: (code=2, message=Fail connecting to server on unix:/tmp/tmp4da_2ec6_test.db.sock, illegal connection params or server unavailable)>"
}:cry:
The text was updated successfully, but these errors were encountered: