mbrown
September 24, 2024, 7:24am
1
If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
In which Wildbook did the issue occur?
What operating system were you using? (eg. MacOS 10.15.3)
What web browser were you using? (eg. Chrome 79)
What is your role on the site? (admin, researcher, etc)
What happened?
What did you expect to happen?
What are some steps we could take to reproduce the issue?
jason
September 24, 2024, 4:19pm
2
Thanks @mbrown
I have fixed the site. I am going to add SMS messaging to our monitoring to try to prevent this further when outages happen during our late night hours.
mbrown
September 25, 2024, 6:49am
3
SMS messaging would be great. Or perhaps some way for us to reboot the system from afar? It’s been challenging to come across this error message in the morning and lose a day of GiraffeSpotting while we wait for the rest of the world to wake up.
mbrown
September 25, 2024, 1:27pm
4
After it was fixed this morning, some of our team reported another Bad Gateway Error this afternoon, 9-25-2024.
jason
September 25, 2024, 2:03pm
5
Thank you.
Yes, the improvements I made to the notification system (SMS alerting) helped us catch that within 20 minutes. The server was restarted.
I am going to look for a quiet moment and quickly upgrade the VM with more vCPUs and RAM to see if this is a resource limit we’re hitting.
Thanks,
mbrown
September 25, 2024, 2:12pm
6
Excellent! That sound great.
jason
September 25, 2024, 8:12pm
7
More RAM and vCPUs added. Now monitoring to see if that helps resolve the back-toback outages.