[Bug]: Max retries exceeded with url: /v2/models/cancer-classifier/infer
See original GitHub issueMLRun Version checks
-
I have checked that this issue has not already been reported.
-
I have confirmed this bug exists on the latest version of the MLRun Kit.
Reproducible Example
original 01-mlrun-basics.ipynb, issues see attached jupyter notebook, you can see this error in case of call serving_fn.invoke("/v2/models/cancer-classifier/infer", body=my_data)
Issue Description
in case of call serving_fn.invoke("/v2/models/cancer-classifier/infer", body=my_data)
I got
OSError: error: cannot run function at url http://127.0.0.1:54652/v2/models/cancer-classifier/infer, HTTPConnectionPool(host='127.0.0.1', port=54652): Max retries exceeded with url: /v2/models/cancer-classifier/infer (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f175c75b070>: Failed to establish a new connection: [Errno 111] Connection refused'))
see jupyter Uploading 01-mlrun-basics.ipynb.txt…
Expected Behavior
Invoke without this issue, it can have relation to https://github.com/mlrun/mlrun/issues/2102
Python Version
3.8.8
MLRun Version
1.2.0
Additional Information
No response
Issue Analytics
- State:
- Created 9 months ago
- Comments:9
Top GitHub Comments
you can see the error you had was:
OSError: error: cannot run function at url http://127.0.0.1:54652...
it cannot reach the address due to the wrong 127.0.0.1 address setting , in my case the address was the host IP (192.168.0.182)@j0terry i answered it in the other issue:
you cannot use 127.0.0.1 (local address), since it will be local to the client container, you need to use the host address which will allow routing to the other containers… in windows you can see that with
ipconfig
, best to choose a stable address (not using DHCP, e.g. the WSL address), this is clearly explained in the documentation:Your HOST_IP address can be found using the ipconfig shell command, it is recommended to select an address that does not change dynamically (for example the IP of the vEthernet interface).
for PowerShell:
Your HOST_IP address can be found using the Get-NetIPConfiguration cmdlet, it is recommended to select an address that does not change dynamically (for example the IP of the vEthernet interface).