-
Notifications
You must be signed in to change notification settings - Fork 583
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
Library was not correctly initialized in Arctic #965
Comments
I don't think it is worth spending time on this issue. I moved the database back to a shared one |
Hi Tom - can you give us a precise description of your environment, old and new please? from the error message snippet in your email I'd guess you have a credentials problem. Probably worth checking you can login to the new server from wherever you're running the python.
Cheers
Duncan
On Jul 4, 2022, at 4:37 PM, Tom Neugebauer ***@***.***> wrote:
Closed #965<#965> as completed.
—
Reply to this email directly, view it on GitHub<#965 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA7RFW4AOW3WVAXQDYCGBWDVSMAJXANCNFSM52SOPOUQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi @dunckerr After downsizing the mongodb to the exact setting it was before I still get this error message. What information about the environment do you need? Cheers Tom |
Hi guys,
I have been using the free mongodb version for over a year together with arctic and everything was working fine.
I recently upgraded my mongodb from a shared to a dedicated service.
From my personal machine and a server everything is running f.
I have a second server and I get the following error message
arctic.exceptions.LibraryNotFoundException: Library X was not correctly initialised in <Arctic at xxxxx...
.. the error message goes on talking about SSL: CERTIFICATE_VERIFY_FAILED
I have the server IP on the white list. The weird thing is the code is working from my laptop and the other server but not on the second server i.e. I can rule out something is wrong with the code or the databases in mondodb.
Any idea what I could do?
Many thanks
Tom
The text was updated successfully, but these errors were encountered: