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.

Sign up for GitHub

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

Jump to bottom

Server heath severe, returns nil server version to app #72

Open

crspybits opened this issue May 27, 2018 · 3 comments

Owner

crspybits commented May 27, 2018

For some time before this also, AWS had been reporting 96% memory used.

This occurred while I was doing a download of all images with SharedImages.

Owner Author

crspybits commented May 28, 2018

Is there just insufficient memory in the EC2 instance to support this server? If so, how do I generally monitor the amount of memory remaining?

Owner Author

crspybits commented May 28, 2018 •

edited

Loading

It seems you have to do some installations to allow general purpose memory monitoring:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/mon-scripts.html
https://www.youtube.com/watch?v=QdSKm-3Oebo
https://engageinteractive.co.uk/blog/aws-cloudwatch-reporting-ram-disk-usage-and-more
https://stackoverflow.com/questions/41507790/monitoring-memory-usage-for-multiple-ec2-instances

See also: https://www.cyberciti.biz/faq/linux-check-memory-usage/
https://www.linuxatemyram.com

Owner Author

crspybits commented May 28, 2018

These free -m invocations were during single refresh on SharedImages soon after a reboot of the production server.

crspybits mentioned this issue

Issue Natasha got today: Bad server version crspybits/SharedImages#99

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment