There was a problem with the query...

[pierrolaloune]

Hi there! 👋

We're currently on an exciting project where we're attempting to pull some data from BIEN. Specifically, we're looking to run the following command to gather information on the Provence-Alpes-Côte d'Azur region in France:

france_plot <- BIEN_plot_state(country = "France", state = "Provence-Alpes-Côte d'Azur")

However, we've hit a bit of a snag. We encountered this error message:

There was a problem with the query. This is most often due to internet connection issues, but may also be due to other factors such as an outdated version of the package.

Finally, this code
france_plot <- BIEN_plot_country(country = "France") take a huge amount of time (1 hour still running) is it a server issue ?

We've double-checked our internet connection, which seems strong and stable, and we've also made sure that both the package and R are up to date.

Our goal is to delve deep into the Mediterranean region's biodiversity by extracting data on all species within the area, which means we're looking at a broader scope than just a single region in France.

Could you perhaps shed some light on how we might overcome this error? Any tips or suggestions would be greatly appreciated. We're all ears for any ideas or advice you might have to help us navigate through this!

Thanks a bunch! 🌿

[fariadamasceno]

Hi Pierre, hi everyone,

I opted to include my message here instead of creating a new issue because the error I'm facing might be related to the problem @pierrolaloune encountered. @bmaitner, please let me know if it would be better to open a new issue instead.

I used RBIEN at the beginning of March for accessing SALVIAS data and it worked perfectly fine; thank you for such a nice resource! However, right now I am facing problems when querying to the server using any BIEN_ function.

For example, running the function BIEN_plot_list_datasource() returns the following error message:
Error in postgresqlNewConnection(drv, ...) :
RPosgreSQL error: could not connect [email protected]:5432 on dbname "public_vegbien": connection to server at "vegbiendev.nceas.ucsb.edu" (128.111.85.31), port 5432 failed: Connection refused
Is the server running on that host and accepting TCP/IP connections?

I installed the package again, both from GitHub and from CRAN but it didn't solve the problem.

Could you please give me some guidance on how alternatively connect to the BIEN server?

Thank you a lot in advance!

[bmaitner]

Hi @fariadamasceno and @pierrolaloune ! Apologies for the slow response, @pierrolaloune (I've been busy with a ton of projects and travel so far this year).

@fariadamasceno this seems to be a server side issue. I know our lead developer has had to make some changes lately, but I had thought we were done with those for a bit. This issue seems to have arisen over night, as I was able to execute BIEN queries yesterday. I'll look into this.

@pierrolaloune , once we've got BIEN back working I'll take a look into your issue

[bmaitner]

@fariadamasceno: this was a server-side issue related to a POSTGRES update. The issue has been fixed and queries are now working as expected.

[fariadamasceno]

@bmaitner, fantastic! Thank you for such a quick fixing! :)

[tristanubaldi]

Hi, I try to use BIEN R package today and I have encountered the same problem than @fariadamasceno, but I can't solve it, I got this message:
Error in postgresqlNewConnection(drv, ...) : RPosgreSQL error: could not connect [email protected]:5432 on dbname "public_vegbien": could not connect to server: Operation timed out Is the server running on host "vegbiendev.nceas.ucsb.edu" (128.111.85.31) and accepting TCP/IP connections on port 5432?
Do you know why I'm having this problem?
Thank you in advance for your help ;)

[bmaitner]

Hi @tristanubaldi , I just checked and was able to query the BIEN database successfully, so it seems like the server is up and running as expected. This error may be due to a firewall on either your computer or at your institution that blocks SQL connections. If the block is at the institution-level, running the query from another location is often easier than fighting with an IT department about settings. If the issue is on your computer, you might just have to toggle the settings on your computer's firewall. Hope this helps!

[tristanubaldi]

Thanks @bmaitner, indeed the problem must have come from the connection from my institution, I just tried again at home and everything works perfectly, thank you and sorry for the inconvenience! :)

[bmaitner]

No worries! We've got a developer working on an API now, so hopefully that option will be available to sidestep the firewall issue in the coming months!

…

On Thu, Nov 14, 2024 at 9:34 AM Tristan Ubaldi ***@***.***> wrote: Thanks @bmaitner <https://github.com/bmaitner>, indeed the problem must have come from the connection from my institution, I just tried again at home and everything works perfectly, thank you and sorry for the inconvenience! :) — Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACU5QAPINVQ6DTXJAT4A7CL2ASYF7AVCNFSM6AAAAABRYUWUYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZWGUYDSMRQGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>