trouble running coiled on the cloud #265
Comments
|
I decided to create a brand new Python environment using conda and tried again. This is the list of packages that were installed (py312) PS C:\Users\thoma> conda list packages in environment at C:\Users\thoma\anaconda3\envs\py312:Name Version Build Channelbzip2 1.0.8 he774522_0 Unfortunately, I received the same error messages using this new environment as before |
|
Hi, Thanks for trying out Coiled! Could you give me your coiled account so that I can look into what went wrong exactly? The second environment looks a bit strange, coiled is missing in there for example. Did you activate this environment before booting the new cluster? |
|
I created the second env and just ran the colied.exe that was created in the first env. What should I have done? I'm actually having some trouble logging in to coil. Each time I've tried this morning I get This site can’t be reached cloud.coiled.io took too long to respond. Checking the connection When I created my account initially I used Google to log in. My email is [email protected] |
|
Ok, I created a new environment like this (py312) PS C:\Users\thoma> conda create -n coiled-dataframe -c conda-forge python=3.10 coiled dask s3fs ==> WARNING: A newer version of conda exists. <== Please update conda by running Or to minimize the number of packages updated during conda update use Package Planenvironment location: C:\Users\thoma\anaconda3\envs\coiled-dataframe added / updated specs: The following packages will be downloaded: Then activated it and tried -re-running the coiled command (coiled-dataframe) PS C:\Users\thoma> conda activate coiled-dataframe The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
My coiled user name is thomas-reid |
|
Hi Thomas! This error is often a sign of network restrictions preventing the machine from reaching the Dask scheduler running in AWS. (E.g. perhaps network rules that prevent making connections outside the VPC you're in, or something along those lines.) We have ways around that, but as you might imagine, they tend to be a little (not a lot) more involved than the setup process you've been through. Maybe we should talk to help me learn more about your situation and plans for Coiled? I've sent a note about scheduling. |
|
Thanks Thomas, looking forward to talking tomorrow. A couple debugging checks that would be helpful:
(I expect this to fail in the same way Coiled is currently failing for you.)
(This will tell us if the failure is specific to Coiled.)
|
|
For some reason, I don't know why, as I didn't do anything, it all seems to be working now
|
|
Patrick, for some reason it's all working now. I'm not sure why. Screenshot
attached. I've updated the github issue and
happy to close this down. We can cancel the meeting we had scheduled for
later today
…On Mon, Dec 18, 2023 at 8:01 PM David Chudzicki ***@***.***> wrote:
Thanks Thomas, looking forward to talking tomorrow.
A couple debugging checks that would be helpful:
1. Can aiohttp talk to Coiled (in the Python environment you're trying
to run Coiled in):
(I expect this to fail in the same way Coiled is currently failing for
you.)
import asyncio
import aiohttp
async def main():
async with aiohttp.ClientSession() as session:
async with session.get('https://cloud.coiled.io') as resp:
print(resp.status)
print(await resp.text())
asyncio.run(main())
1. Can aiohttp talk to *Google* (or anything else) (in the Python
environment you're trying to run Coiled in):
(This will tell us if the failure is specific to Coiled.)
import asyncio
import aiohttp
async def main():
async with aiohttp.ClientSession() as session:
async with session.get('https://google.com') as resp:
print(resp.status)
print(await resp.text())
asyncio.run(main())
1. Can we curl to Coiled? (This will distinguish between problems in
the Python environment you've set up, and problems on your machine
generally.)
curl -vvI https://cloud.coiled.io/
1. Can we curl to Google?
curl -vvI https://google.com
—
Reply to this email directly, view it on GitHub
<#265 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFHMTFPCEVO6I6NKTYULEXTYKCOLLAVCNFSM6AAAAABAZF76H6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRRGQ4TMMBWGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi, I signed up to Coiled and went through the process to connect to my AWS account etc ... The CloudFormation stack seemed to create OK and all looked good. However, when I tried the "echo hello world" example I received the following error. I'm running on Windows 11 Desktop.
(base) C:\Users\thoma>coiled run echo "Hello, world"
C:\Users\thoma\anaconda3\Lib\site-packages\paramiko\transport.py:219: CryptographyDeprecationWarning: Blowfish has been deprecated
"class": algorithms.Blowfish,
╭──────────────────────── Running echo 'Hello, world' ─────────────────────────╮
│ │
│ Details: .. │
│ │
│ Scanning Environment ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ │
│ │
│ Region: .. Uptime: 0 │
│ VM Type: .. Approx cloud cost: $0.00/hr │
│ Total cost: $0.00 │
│ │
╰──────────────────────────────────────────────────────────────────────────────╯
Traceback (most recent call last):
File "C:\Users\thoma\anaconda3\Lib\site-packages\aiohttp\connector.py", line 980, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs) # type: ignore[return-value] # noqa
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\asyncio\base_events.py", line 1085, in create_connection
raise exceptions[0]
File "C:\Users\thoma\anaconda3\Lib\asyncio\base_events.py", line 1069, in create_connection
sock = await self._connect_sock(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\asyncio\base_events.py", line 973, in _connect_sock
await self.sock_connect(sock, address)
File "C:\Users\thoma\anaconda3\Lib\asyncio\selector_events.py", line 634, in sock_connect
return await fut
^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\asyncio\selector_events.py", line 674, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
TimeoutError: [Errno 10060] Connect call failed ('18.164.68.57', 443)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "C:\Users\thoma\anaconda3\Scripts\coiled.exe_main.py", line 7, in
File "C:\Users\thoma\anaconda3\Lib\site-packages\click\core.py", line 1128, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\click\core.py", line 1053, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\click\core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\click\core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\click\core.py", line 754, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\cli\run.py", line 274, in run
start_run(
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\cli\run.py", line 419, in start_run
coiled.add_interaction(
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\core.py", line 2927, in add_interaction
with Cloud() as cloud:
^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\core.py", line 314, in init
self._sync(self._start)
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\core.py", line 537, in _sync
return cast(_T, sync(self.loop, func, *args, **kwargs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\distributed\utils.py", line 418, in sync
raise exc.with_traceback(tb)
File "C:\Users\thoma\anaconda3\Lib\site-packages\distributed\utils.py", line 391, in f
result = yield future
^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\tornado\gen.py", line 767, in run
value = future.result()
^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\context.py", line 112, in async_wrapper
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\core.py", line 417, in _start
self.user, self.token, self.server, memberships = await handle_credentials(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\utils.py", line 395, in handle_credentials
user_dict = await _fetch_data(
^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\backoff_async.py", line 151, in retry
ret = await target(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\coiled\utils.py", line 299, in _fetch_data
response = await session.request("GET", f"{server}{endpoint}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\aiohttp\client.py", line 536, in _request
conn = await self._connector.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\aiohttp\connector.py", line 540, in connect
proto = await self._create_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\aiohttp\connector.py", line 901, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\aiohttp\connector.py", line 1209, in _create_direct_connection
raise last_exc
File "C:\Users\thoma\anaconda3\Lib\site-packages\aiohttp\connector.py", line 1178, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\thoma\anaconda3\Lib\site-packages\aiohttp\connector.py", line 988, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host cloud.coiled.io:443 ssl:default [Connect call failed ('18.164.68.57', 443)]
The text was updated successfully, but these errors were encountered: