3 months ago
I'm trying to debug a deployment problem, but it appears that the deploy log is truncated. See attached.
The issue I'm working on is that I'm downloading a sqlite file from Railway S3 and that seems to be failing when deployed in Railway, but works locally. I tried setting RAILWAY_RUN_UID=0, but that didn't seem to help. I didn't think I'd need to setup a persistent Volume as I'm downloading with each launch.
Attachments
Pinned Solution
3 months ago
ig here you need to pass s3_settings rather than settings
5 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Open brody • 3 months ago
3 months ago
based on logs ..check line 61
2026-03-07T02:01:37.301089337Z [err] │ 58 │ def __init__(self, db_file, s3_settings=None): │
2026-03-07T02:01:37.301094583Z [err] │ 59 │ │ if not os.path.exists(db_file) and s3_settings is not None: │
2026-03-07T02:01:37.301099765Z [err] │ 60 │ │ │ logging.info('Aircraft database file not found, attempting │
2026-03-07T02:01:37.301105309Z [err] │ ❱ 61 │ │ │ self.download_database(settings)
dharmateja
based on logs ..check line 61 ``` 2026-03-07T02:01:37.301089337Z [err] │ 58 │ def __init__(self, db_file, s3_settings=None): │ 2026-03-07T02:01:37.301094583Z [err] │ 59 │ │ if not os.path.exists(db_file) and s3_settings is not None: │ 2026-03-07T02:01:37.301099765Z [err] │ 60 │ │ │ logging.info('Aircraft database file not found, attempting │ 2026-03-07T02:01:37.301105309Z [err] │ ❱ 61 │ │ │ self.download_database(settings) ```
3 months ago
ig here you need to pass s3_settings rather than settings
dharmateja
ig here you need to pass s3\_settings rather than settings
3 months ago
Hey, thanks! That resolves my bug, but not the truncated log issue.
That'll teach me to make a "small" change after local testing. And if the logs were complete, I would have seen the correct error at the bottom.
Status changed to Solved sam-a • 3 months ago
3 months ago
If your app exceeds the 500 log lines/second rate limit, excess lines are dropped. You can use the Log Explorer for more complete log history.
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved sam-a • 3 months ago
sam-a
If your app exceeds the 500 log lines/second rate limit, excess lines are dropped. You can use the [Log Explorer](https://docs.railway.com/observability/logs) for more complete log history.
3 months ago
Ah, I see. I've never used the Log Explorer before. From a user perspective, it would be good if the interface either allowed you to manually load those excess lines or at least link the user to the Log Explorer to aid discovery (with a note about the log rate limit).
Thanks for your help!
Status changed to Awaiting Railway Response Railway • 3 months ago
Status changed to Solved jkua • 3 months ago