2 hours ago
Hello Railway Support,
My production cron service SPY_QQQ_Trading is crashed. Its persistent volume spy_qqq_trading-volume is mounted at /app/data.
The CLI commands railway service files list /app/data --json and railway service files list /app --json both fail with:
Failed to initialize SFTP session — Timeout
I need to inspect and restore an existing strategy-state file in /app/data/paper/ without overwriting any existing files. The service currently fails during startup, and I do not want to restart it until the state has been safely reconciled.
Could you help restore access to the service filesystem or advise on a safe way to inspect and restore the file on the persistent volume?
Thank you.
3 Replies
Status changed to Awaiting Railway Response Railway • about 2 hours ago
an hour ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 hour ago
an hour ago
Your service must be online for you to view its files. Alternatively, you can unmount the volume, deploy a Filebrowser instance, and mount the volume to your Filebrowser service. You’ll be able to view the contents of your volume from there.
an hour ago
Thanks for the guidance. My service currently crashes during startup, and I need to recover or inspect the existing contents of the persistent volume mounted at /app/data before allowing the trading workflow to run again.
Can you confirm the safest procedure for temporarily deploying a Filebrowser service and mounting the existing volume spy_qqq_trading-volume without formatting, initializing, or overwriting its contents? Should I detach the volume from the crashed service first, and how should I ensure the volume is mounted read-only if possible?
I need to preserve the existing paper-trading strategy state and inspect it before restarting the original service.
an hour ago
When you detach the volume, IIRC the service might deploy. To abort, go to the deployments tab of the service, click on the 3 dots of the active deployment, and abort it. IIRC there isn’t a way to make the volume readonly. You’d just need to make sure you don’t perform any destructive actions when viewing the filesystem.