2 years ago
mongodb kept crashing on free tier. i upgraded to a hobby tier. increased volume to 5GB. MongoDB now not crashing but my other service cannot access mongodb anymore (i can access mongodb through the UI in railway).
the error from the server trying to reach the mongodb service:
Starting Container
message="Started server process [2]" color_message="Started server process [\u001b[36m%d\u001b[0m]" filename="server.py" funcName="serve" level="info" levelname="INFO" lineno=77
message="Waiting for application startup." filename="on.py" funcName="startup" level="info" levelname="INFO" lineno=48
message="Application startup complete." filename="on.py" funcName="startup" level="info" levelname="INFO" lineno=62
message="Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit)" color_message="Uvicorn running on \u001b[1m%s://%s:%d\u001b[0m (Press CTRL+C to quit)" filename="server.py" funcName="_log_started_message" level="info" levelname="INFO" lineno=209
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)')>]>"
message="" asctime="2024-07-04 19:20:53,218" client_addr=null level="info" request_line=null status_code=null
0 Replies
2 years ago
Please do not create duplicate cross posts.
Status changed to Archived brody • over 1 year ago