Service crashed without relevant logs
Several times, my app started, launched a periodic scraping function, and then failed. The specific steps are:
- Setup API session
- Initialize scraping step
- Identify expired subjects to scrape
- In order, make API requests.
- Use the
success attribute to identify bad requests.
- It crashes after this point.
By the way, this isn't a crawler, it's just caching important API responses every couple hours.
Solution:Jump to solution
Don't know how to mark; but I'm really stupid. Apparently I was really stupid/sleepy and didn't notice it was a fatal raise. Ugh.
8 Replies
Project ID:
N/AIt restarted like this several times until Railway stopped and marked it officially as 'crashed'.
The line with "Error loading .env file" is a debug log that appears at the very start.
Project ID: 62dd250d-2e15-466e-a400-138129e331f6
if there isn't any logs then your app isn't logging, please add more verbose logging
I have logs everywhere; I honestly have no idea where I would add logs here. How do I debug a crash that has zero pointers to the source?
Generally, when my app crashes, it's a fatal crash and it logs to console. I've never experienced one that didn't come with a stack trace.
It did it again lalst night
nothing obvious from metrics
!solved
!solve
Solution
Don't know how to mark; but I'm really stupid. Apparently I was really stupid/sleepy and didn't notice it was a fatal raise. Ugh.