Hi Zack,
Sorry to hear this. First time I see that error.
What are the specs of your machine? If you are running out of memory (a very small EC2) you can disable the NLP container. It uses some resources you may want to recover.
Just to narrow this down I went and looked at your server:
Its seems like one of your custom views is involved in the issue since the general Content one is not throwing that error.
I also see Drupal is still on 8.9.2. I would recommend (so all matches) that you move to 8.9.13 first.
But also I see you just upgraded from mysql 5.17 to Mysql 8. (Which is done automatically by the container). Because of that, I would recommend checking on the mysql error logs first when that view error happens
docker logs -f esmero-db and see if there is some info
I would also do a docker-compose down and then a docker-compose up -d and check the logs for initialization issues.
Lastly:
Using docker-compose you can affect almost any setting directly without editing the my.cnf
So for adding a larger buffer, try adding this.
command: mysqld --default-authentication-plugin=mysql_native_password --max_allowed_packet=256M
You will notice that MYSQL has a flag for the sort buffer
So you can add at the end of the command
--sort-buffer-size=262144 (262144 is the default)
docker-compose down and then up -d
OR
docker-compose db restart (works sometimes but not sure it will get settings so down/up is a safer approach)
That said
You may want to check how much space you have left on your hard drive for mysql and if the permissions of the DB folder are the correct. Since may times buffer issues are because MYSQL can not write back to storage.
Keep me updated. If you do not solve this I can give it a try later tonight
PS: sorry, I wanted to share the instructions via email before noon but got derailed but a calls.
Diego Pino Navarro
Assistant Director for Digital Strategy
Archipelago architect
Metropolitan New York Library Council
PO Box 2084
New York, NY 10108