2 years ago
I already paid for the plan to have more resources, but my database still crashes. These are the logs I'm getting. The database has the resources allocated at maximum. How could you solve this problem?
WiredTiger recoveryTimestamp
/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never' in this binary version
vm.maxmapcount is too low
Updated wire specification
current featureCompatibilityVersion value
Clearing temp directory
Initializing cluster server parameters from disk
Flow Control is enabled on this deployment
Initializing full-time diagnostic data capture
Setting new configuration state
Timestamp monitor starting
Listening on
Listening on
Listening on
Waiting for connections
mongod startup complete
container event container died
Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost
Writing fatal message
Writing fatal message
Writing fatal message
BACKTRACE
Frame
Frame
ⓘ Deployment information is only viewable by project members and Railway employees.
1 Replies
2 years ago
Modifiqué el tamaño del disco duro, y se solucionó mi problema!
Status changed to Solved brody • over 1 year ago