Error when creating SigNoz service
Anonymous
PROOP

10 months ago

When I tried to deploy SigNoz to railway, I've got an error from signoz service

Attachments

9 Replies

Railway
BOT

10 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!


10 months ago

Hello,

Can you please link the template you used?


Status changed to Awaiting User Response Railway 11 months ago


Anonymous
PROOP

10 months ago


Status changed to Awaiting Railway Response Railway 11 months ago


10 months ago

Have you modified the services since deploying the template?


Status changed to Awaiting User Response Railway 11 months ago


Anonymous
PROOP

10 months ago

I have actually by adding env variable RAILWAY_RUN_UID=0. The solution that i get is from railway documentation about volume.


Status changed to Awaiting Railway Response Railway 11 months ago


10 months ago

I have asked the template maintainer to take a look.


Status changed to Awaiting User Response Railway 11 months ago


brody

I have asked the template maintainer to take a look.

Anonymous
PROOP

10 months ago

Thank you!


Status changed to Awaiting Railway Response Railway 11 months ago


grayalex49
PRO

10 months ago

I'm getting the error "unknown flag: --config" when deploying a new instance from the signoz template.


nageshbansal
FREE

a month ago

Hey Folks, Sorry for the delay. unknown flag: --config is due to a SigNoz CLI change that broke the old template's start command. We've rebuilt the template with Foundry; the start command is fixed, so a fresh deploy of the updated template works without any tweaks.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...