8 months ago
{
"builds": [
{
"src": "package.json",
"use": "@nixpacks/nixpacks",
"variables": {
"NODE_ENV": "production",
"NIXPACKS_ENABLE_SWAP": "1"
}
}
]
}
my railway.json
My previous deployment worked, but now new code changes are giving me error. My Code backend uses GROQ AI, can that be a reason.?
4 Replies
8 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
8 months ago
Have you tried a rollback?
Go to your previous deploy and click the 3 vertical dots icon to find the rollback button.
8 months ago
Now actually answering your question, yes, GROQ-AI can be the root cause if each inference/stream opens a new connection and they pile up. Either close them properly or lift the ulimit. You can add ulimit -n 4096 && npm start to your start command and the new deployment should work.
testuser123
Now actually answering your question, yes, GROQ-AI can be the root cause if each inference/stream opens a new connection and they pile up. Either close them properly or lift the ulimit. You can add ulimit -n 4096 && npm start to your start command and the new deployment should work.
8 months ago
You cannot modify this on Railway.
