Hi AtoM Users,
two days ago we had to delete about 2000 Digital Object and their Archival Descriptions, after several minutes the server returned a 504, and since then the mysql is using up to 350% CPU, when trying to access a bigger archival description php-fpm crashes and needs a restart. Any idea whats going on and how to resolve this without restoring a full backup.
We are using the Percona MySQL on AtoM 2.4.2
Already tried to:
+) restart all services (mysql, memcached, fpm,nginx, gearman, workers)
+) restarted the entire server
+) php symfony cc
+) php symfony propel:build-nested-set which crashed after about 30mins complaining about a Lock
Any Ideas on how to resolve this?
Thanks in advance
greets
Raphael