-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement]: Warning: connect.session() MemoryStore is not designed for a production environment #2538
Comments
Thank you for posting this. I am troubleshooting why Audiobookshelf crashes every week or two and I saw this error message. Good to know it is not related to my issue. |
Glad it helped! If you can provide logs around the crash, that will help narrow it down. If you haven't already done so, change your server log level to Debug. You may also need to look at the Docker or systemctl logs (depending on how you are running the server) because those logs can catch more information than ABS itself does for crashes. Please post those logs/description in a new issue or on Discord so this issue doesn't get a ton of unrelated comments. :) |
Having this issue as well. Based on info logs, mine seems to crash after updating podcasts. I've set the logger to debug and will post results when it crashes next. INFO logs from crash/startup
|
Periodic crashes are unrelated to the MemoryStore warning. This warning is given as part of the startup logs and is not related to the crash. Please open a new issue for debugging the crash. |
Fixed in v2.12.0. |
Reverted in 2.12.2 to prevent the server becoming unresponsive after 24 hours. |
if have a similar msg (Warning: connect.session() MemoryStore is not |
See the original message for this thread. This has been updated for the next release. |
Fixed in v2.13.0. |
Describe the feature/enhancement
There have been a few reports in recent weeks around express-rate-limit using
memory-store
. This issue is to provide context.MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process.
This warning does not matter for ABS, but has been causing some confusion for users.
https://express-rate-limit.mintlify.app/reference/stores
The MemoryStore is only used to provide rate limiting and does not end to be very robust since it is designed for a single server and rebooting does not affect the rate limiting feature for ABS (ABS only tracks for the past 60 seconds).
Potential changes:
rate-limit-memcached
. That seems to be the lightest replacement but adds a dependencyThe text was updated successfully, but these errors were encountered: