Hi all, we’re getting deploy failures but are not seeing any deploy logs. Is there a common fix for this issue?
Note: this is a python3 service so I’m not sure why we’re seeing Node warnings.
Rollbacks are also failing.
Hi there,
As far as why you’re seeing a note about Node versions, we currently include Node in all our Native Environments.
In the interest of unblocking you as soon as possible, could you try the following:
- Specify a NODE_VERSION environment variable (shouldn’t matter which since you’re not using it,
20.0.0would work) - If that doesn’t work, suspend this service and re-create it as a new service
Let me know if either of these work for you. It would be great to keep your suspended service around so I can have our team take a look into it.
Regards,
Matt
Also, could you share how to debug a situation like this in the future? Am I always able to SSH into the box even if the deploy fails?
Hi there,
One last test - could you try deploying to a different region, maybe Ohio?
Could you also send me your the Service ID where this is happening? Feel free to open a support ticket from the dashboard if you don’t want to share this information on the public forum.
Regards,
Matt
Hi there,
I did end up finding other references to this error message. This isn’t something you’d be able to debug via SSH.
I’ll escalate this to our engineering team to investigate further
Regards,
Matt
I tried to deploy the MERN project first i tried to deploy the backend code but it failed to deploy the project
Namratha_Shiva_Praka - Are you also seeing an Invalid node version specification error in your service logs? If so, can you share your service id?
If you’re seeing some other error please open a new support ticket or community topic and include the errors logs you’re seeing.
Gave this a shot and it still fails. I ssh’d into the box and even though it claims it’s installing poetry using POETRY_VERSION, when I check poetry does not exist at this path.
Oct 21 04:07:34 PM ==> Using Poetry version 1.5.1 via environment variable POETRY_VERSION
Oct 21 04:07:34 PM ==> Docs on specifying a Poetry version: https://render.com/docs/poetry-version
Oct 21 04:07:34 PM ==> Installing Poetry version 1.5.1
Oct 21 04:08:06 PM Retrieving Poetry metadata
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM # Welcome to Poetry!
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM This will download and install the latest version of Poetry,
Oct 21 04:08:06 PM a dependency and package manager for Python.
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM It will add the `poetry` command to Poetry's bin directory, located at:
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM /opt/render/project/poetry/bin
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM You can uninstall at any time by executing this script with the --uninstall option,
Oct 21 04:08:06 PM and these changes will be reverted.
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM Installing Poetry (1.5.1)
Oct 21 04:08:06 PM Installing Poetry (1.5.1): Creating environment
Oct 21 04:08:06 PM Installing Poetry (1.5.1): Installing Poetry
Oct 21 04:08:06 PM Installing Poetry (1.5.1): Creating script
Oct 21 04:08:06 PM Installing Poetry (1.5.1): Done
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM Poetry (1.5.1) is installed now. Great!
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM You can test that everything is set up by executing:
Oct 21 04:08:06 PM
Oct 21 04:08:06 PM `poetry --version`
Any way to escalate this to get this resolved? I’ve spent multiple days already debugging and this is blocking us.
I did some digging and this failure only happens when the disk is attached.
Have you seen anything similar?
Hello,
The team is releasing a fix to address the Invalid node version specification error from the first message in this thread.
I see you’ve opened a support ticket for your follow-up question, we’ll continue working through that issue via the ticket to avoid duplicating efforts.
Regards,
Matt
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.