-
-
Notifications
You must be signed in to change notification settings - Fork 634
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
429 Request Failed. #555
Comments
I got the following error:
|
Note that
|
For the first issue, it seems that you need to create another ticket to linode support to increase the limit of instances/Linodes, it seems that it is limited to 9. For the second one, this occurs because Interlace has some problem with python 3.10 which is installed in the docker container while trying to follow axiom install steps via docker. So the solution will be either changing python version inside the container to a version that works fine with Interlace or just adding the following line
|
@osamahamad just seeing this. Ty for troubleshooting. I’ll try to look into this sometime today, it seems like it could be related to this issue codingo/Interlace#163 About the rate limits, aside from making a support request the increase in instances/linodes, you’ll need to spin up in batches of 10 ( to be safe ). |
@0xtavian Hi @0xtavian , May I ask your advice on which provider I should use that does not require me to wait so much time to be able to spin up 100 instance easily? The reason because when I contacted Linode about increasing the limit, they replayed the following :
and 3-months period is so much ... |
@osamahamad im not sure tbh. The providers have limits on new accounts to prevent fraud, this is pretty consistent with all providers. |
How can I add this to AWS AMI so when I lunch axiom-fleet I don't have to ssh in individually can add these? |
@Jesse415 i have not gotten the chance to test AWS yet, but I see the issue you are facing. axiom/images/builders/aws.json Line 20 in bef03d0
For all other providers we use Ubuntu 20.04, you can see for AWS we are using ubuntu-jammy-22.04 , which uses the latest python by default. If you switch this to use Ubuntu 20.04, you shouldn’t have this issue as it’s not using the latest python. I’ll try to get around to testing today but if you can a chance before me, lmk if using Ubuntu 20.04 fixes this ( for all other providers we are using Ubuntu 20.04 for instances so we don’t run into this issue ).
@pry0cc any reason for using 22.04 for AWS by chance? |
About interlace, we should probably PR them and fix it for the latest python version. I also have it on my todo to use packer 1.8.0 in axiom-configure. Both of these are upstream issues that we can fix. For AWS, I'm using 22.04 just because it was readily available. It seemed to build just fine and I don't see any issue with it unless you do? |
Yep they are already aware of the issue and have identified the root cause codingo/Interlace#163, once this is fixed we shouldn’t have this issue anymore. I do worry about drift between the Ubuntu versions, which could make it somewhat difficult to reuse the same provisioners. I think we should keep consistent and only use Ubuntu 20.04 for instances to avoid these types of issues. I haven’t gotten a chance to pay with AWS but if I get a chance today, I’ll see if using 20.04 is a reliable option for AWS, unless of course there is some concern. Thanks all! |
I can confirm that changing line 20 to |
and issue with interlace resolved. Thanks |
┌──(kali㉿DESKTOP-6K4VUA2)-[/usr/lib/python3.10/collections] add the code written below in init.py file which is /usr/lib/python3.10/collections folder. |
@sanjay493 @Jesse415 @osamahamad |
I ran the following
This is what I got:
I'm using Linode.
I'm using axiom with docker latest version.
Why this is happening, is there any solution for it?
The text was updated successfully, but these errors were encountered: