Connection to pycelonis after 2.0 upgrade

Hi Rahul,

let me see if I can help you out!

Is the EMS_connetion a custom made module from your side? If so, could you share the code that is being triggered in that module? That would make it more easy to help you debug the gode.

Generally speaking, it could be that some functionality you used to connect to Pycelonis has been deprecated with PyCelonis 2.0. Is your approach to connect to PyCelonis 2.0 in line with the following code chunk?

from pycelonis import get_celonis

api_token = "<paste your personal API Key here>"

celonis = get_celonis(api_token=api_token, key_type="USER_KEY") # key_type is optional

>>> [2022-01-01 10:00:00] INFO: Login successful! Hello bob.ross@celonis.com. PyCelonis Version: X.X.X

>>> [2022-01-01 10:00:00] INFO: Your key has following permissions: 

Hi Jasper,

Thank you for your reply

Yes it is a custom module. It is just trying to bypass some proxy and checking if its being run in the IBC or in the local system and just connecting likewise.

Yes it includes the following line of code but with a bit different class types(in general, yes)

I think these two screenshots would help you figuring it out.

Thanks

Hi Rahul,

Only thing that I notice is that the URL is not being passed into get_celonis() when running in the cloud, could that be the issue?

If you try to connect to Celonis with these credentials in a very basic set up, let's say a Jupyter notebook in which you just run the get_celonis() code, do you still get the same error?

Best,

Jasper

Hi jasper,

There isnt any issue while connecting the same code in IBC.

And now the issue is when im trying to connect from the local system to IBC so it wouldnt go to that else part at all

Thank you

When running from IBC, by default get_celonis assumes URL = local team, API credentials = the one associated to the ML workbench app.

When running from your local machine you need to explicit both.

Hi Guillermo,

Yes true. Therefore we have implemented the URL and API and rest of the necessary parameters for the local machine

Screenshot below:

Yes, sorry, my bad.

Questions:

• did it work before from your local machine?
• what pycelonis version are you using? Is it the same as before, when it worked from your local machine?
• I think getaddrinfo error is related to dns... can you resolve the URL hostname from your local machine?

Yes it was working before upgrading to pycelonis 2.0.1

I have implemented this in an env , so that the other env is still having 1.7.4 and im able to connect to IBC

The old pyclonis was 1.7.4 and now after upgrading to 2.0.1 this issue is started

Im sorry i didnt get your last question.

Nah don't worry. If the old script in 1.7.4 is in the same machine and is managing to connect, pretty sure the name resolution is not the problem.

It should be something related to changes in the pycelonis.

A wild shot: Checking here https://celonis.github.io/pycelonis/2.0.1/tutorials/executed/01_quickstart/02_celonis_basics/#12-connect-to-the-ems one possibility is that you are passing the the login struc the parameter "url" , but it seems it is expecting "base_url" instead

Maybe is that. In 1.7.4 get_celonis expects parameter "url"

https://celonis.github.io/pycelonis/1.7.4/reference/get_celonis/

and in 2.0.1 expects "base_url"

https://celonis.github.io/pycelonis/2.0.1/reference/pycelonis/

HTH

Hi Guillermo,

It is still the same after changing the url.

Damm, this is odd.... no promises, but I will try to replicate the problem in my laptop, to see if I can think on some hypothesis

Ok, still testing. But, the more I dig, the more sure is a problem external to pycelonis. Getaddrinfo means that you can not resolve the hostname into an IP.

This link can give you some ideas, as I think you said something about proxy?....

https://stackoverflow.com/questions/7334199/getaddrinfo-failed-what-does-that-mean

Also, can you try to do a wget connect to the url? Or code from the same environment some python that use curl or similar to do a simple wget to that url?

If you get same error, that means is a problem of your python environment or your box.

HTH

Sure il check the link with wget

but here is the screenshot for wget