Bug in the builder that no longer works
ProjectId = 32e7c04c-c58a-41a6-9e8c-320a473294f7
The
Build Logs no longer receives build logs from the Redeploy command and ends up with an error in Deploy Logs.
And the Restart command is Not found
The command script is located in the package.json file of my Github repo node index.js and the builder version is NIXPACKS_NODE_VERSION=18. All other settings values are provided by default.
Thank you for your help.10 Replies
Project ID:
32e7c04c-c58a-41a6-9e8c-320a473294f7please provide your package.json and your logs https://bookmarklets.up.railway.app/log-downloader/
The Railway cli was able to work again to allow the builder to be restarted. The Railway up command had not worked in previous days.
The service is active again, also the problem is propagating among the 9 other servers, the Github cli, Github action, on two of them seems to work. So I'll give you some time to find your bug. For my part I am now able to get around the problem.
Please keep me informed of the progress of the problem.
Here my
Build Logs:
Here my Deploys Logs:
Here my View Logs:
Here my package.json file:I'm sorry but at this time I don't see how this in an issue with Railway, I have not seen any reports of any similar issues since you opened the thread, the problems you are running into are likely due to a misconfiguration on your part, as for what the misconfigurations could be, I unfortunately have no clue, I don't quite understand what you're trying to tell us
A Railway bug prevents the builder from starting for another 7 of my servers via the graphical interface.
Once in my service, I click on the three small dots, those next to 'View Logs', I launch
Redeploy and I obtain logs after 6 minutes which fit into one line:
No build logs found for deployment
Do the elements I provided allow you to resolve the problem?have you tried triggering a build by pushing an empty github commit?
and id just like to note that i dont work for railway
Testing the commit cannot be done now, but the Github cli works for two of my servers which restart via Github actions.
are you calling the graphql api?
No, no graphql api.
The dependencies of the package.json file that I provided can tell you what the monitor does, it listens to events coming from providers.
sorry this isnt an issue with railway