R
Railway5mo ago
koombal

mongodb container keeps crashing today, no load on the server (no access at all...)

project id: 3c844d3f-4881-4397-a46c-69c77b48fcc0
Solution:
You're on the trial plan and are limited to 500GB Volumes, MongoDB can not happily run with only 500MB, you will need to upgrade to the Hobby plan for access to 5GB volumes, after the upgrade go into the volume's settings to grow it to 5GB.
Jump to solution
39 Replies
Percy
Percy5mo ago
Project ID: 3c844d3f-4881-4397-a46c-69c77b48fcc0
Solution
Brody
Brody5mo ago
You're on the trial plan and are limited to 500GB Volumes, MongoDB can not happily run with only 500MB, you will need to upgrade to the Hobby plan for access to 5GB volumes, after the upgrade go into the volume's settings to grow it to 5GB.
koombal
koombalOP5mo ago
ok, it was working fine for 10 days or so
Brody
Brody5mo ago
yep, you ran out of storage
koombal
koombalOP5mo ago
well, there were 2 records in one collection (really small ones, a few text/int fields) and another 40 records with mostly text. the server was not accessed for a few days so it's a bit weird that it started crashing. i deleted now all the 40 short text records and the server keeps crashing - are we sure this is the problem? there were no issues until yesterday, it never crashed. now it's empty and keeps crashing. how can i be certain that your infra is reliable when i go to prod?...
Brody
Brody5mo ago
I am absolutely certain, this happens all the time for trial users, 500MB is not enough to run MongoDB happily, nothing to do with the Railway platform itself and i would just like to clarify something since you said "your infra".. I don't work for railway
koombal
koombalOP5mo ago
well, just upgraded to hobby plan. keeps crashing. why is that?
Brody
Brody5mo ago
have you grown the volume?
koombal
koombalOP5mo ago
not sure how i tried redploying now it gives some error messages but not crashing now. but it seems it cannot create DB connection i can't find nowhere where to increase volume size
Brody
Brody5mo ago
as previously mentioned, go into the volumes settings and grow it to 5gb
koombal
koombalOP5mo ago
and no db connection where is volume settings
Brody
Brody5mo ago
click on the volume
koombal
koombalOP5mo ago
where is the volume no volume in settings
Brody
Brody5mo ago
the volume is attached to the service
koombal
koombalOP5mo ago
No description
Brody
Brody5mo ago
click on the volume, it is on the project canvas
koombal
koombalOP5mo ago
ok, found it
Brody
Brody5mo ago
I didn't know it needed finding :kekw:
koombal
koombalOP5mo ago
well, someone should do UX here i think it's working, thanks
koombal
koombalOP5mo ago
btw, the other service cannot connect to the DB now, anything that needs to be "rewired" somehow?
Brody
Brody5mo ago
please provide specific errors
koombal
koombalOP5mo ago
2024-07-04 19:12:16,499 (async_telebot.py:565 MainThread) ERROR - TeleBot: "mongodb.railway.internal:27017: [Errno -2] Name or service not known (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: <TopologyDescription id: 6686f3e3f69735632f71e88b, topology_type: Unknown, servers: [<ServerDescription ('mongodb.railway.internal', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('mongodb.railway.internal:27017: [Errno -2] Name or service not known (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>"
Brody
Brody5mo ago
are the two services in the same project
koombal
koombalOP5mo ago
i am trying to redploy yes, same project it was working before mongodb started crashing
Brody
Brody5mo ago
do you have the V2 runtime enabled
koombal
koombalOP5mo ago
it was on legacy - was it changed somehow or it was in legacy when i started the project?
Brody
Brody5mo ago
it was legacy when you started the project, switch to v2
koombal
koombalOP5mo ago
ok, but i think i still have the same error
Brody
Brody5mo ago
have you switched to the v2 runtime
koombal
koombalOP5mo ago
yep both are V2
koombal
koombalOP5mo ago
Starting Container Started server process [2] Waiting for application startup. Application startup complete. Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit) 2024-07-04 19:20:53,215 (async_telebot.py:565 MainThread) ERROR - TeleBot: "mongodb.railway.internal:27017: timed out (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: <TopologyDescription id: 6686f5de8bd11919f9ad8c52, topology_type: Unknown, servers: [<ServerDescription ('mongodb.railway.internal', 27017) server_type: Unknown, rtt: None, error=NetworkTimeout('mongodb.railway.internal:27017: timed out (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms)')>]>" this is the app
Brody
Brody5mo ago
use the bookmarklet please
koombal
koombalOP5mo ago
well, the tool is not "brave" browser friendly
Brody
Brody5mo ago
logs of the app please
Brody
Brody5mo ago
can you connect to the database locally
koombal
koombalOP5mo ago
yep any idea? something is messed up in internal networking? there? Should i create a ticket somewhere else?
Brody
Brody5mo ago
hobby users are only eligible for support from the community, so please be patient
Want results from more Discord servers?
Add your server