-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Can't connect to shared database #8944
Comments
It seems like there are no version differences between one machine that it worked on and another that it didn't work on... Details for the Windows Machine that had NO issues:JabRef 5.7--2022-06-29--92b7d7a Edition Windows 10 Pro Details for the Windows Machine that had issues:JabRef 5.7--2022-06-29--92b7d7a Edition Windows 10 Pro |
Hm:
|
is #8788 fixed in 5.6? if so I can try that. |
Edit: The fix for 8788 was after the release of 5.6, so if it is broken in 5.7, but not broken in 5.6 ... |
i did try all those things i noted above in the current 5.7 development (main) build at that date. |
To do:
|
I tested locally with a Postgres install here on my mac and that works fine. The error you posted indicates a general connection error to the database. Some network problems probably. Tested both JabRef 5.7--2022-06-20--41edd28 and the latest dev snapshot from yesterday Edit// Can you connect with a tool like pgAdmin? If the DB is reachable with that one? https://www.pgadmin.org/ |
Yes I tried that. I used Datagrip by netbrains to check if I at least can connect to the postgres server locally as well as on a machine where jabref couldn't connect. And I in fact was able to connect both times. It may be that Datagrip does lookup the hostname when I connect to the database via the IP. Which would mask that bug/error. I will try that with another tool again tomorrow. |
Weirdly it seems to work if I connect with the hostname of the postgres server but not with the respective IP... |
I looked into the code and thought about it very hard. I believe it's either an issue with the postgres server configuration, the network, a bug in JDBC or the use of it in Jabref. |
It might be a JDBC or postgres issue thing. |
this bug seems to only exist in the Windows version of jabref. Connecting via IP as well as via Hostname works fine on Linux machines... |
JabRef version
Latest development branch build (please note build date below)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build
Steps to reproduce the behaviour
Appendix
On one windows devices it DID work, on two others it didn't. To test if it's the firewall blocking the connection I deactivated it but to no avail.
I tried to directly connect to the database (from an windows machine, where jabref was not able to connect) via Datagrip and that worked. So it seems like it is a bug in Jabref..
Do you have any idea what the problem might be? It may be a bug, but why would it work on one windows machine but not the other ones?
Build date 29.06.2022
Log File
The text was updated successfully, but these errors were encountered: