SuiteCRM 8.9.1 was installed on AWS Aurora Serverless, user accounts (with admin priv.s) created, original fake data cleared out, new data loaded. A few weeks later, suddenly:
- user accounts (but not the original admin account) were mysteriously dropped
- new data that had been loaded was mysteriously gone
- the old fake data including the fake users were restored.
Anyone else experience this mysterious and frustrating occurrence? I’ve see it happen at least twice.
Hard to rely on SuiteCRM if this repeatedly happens.
How did you do the initial setup, through some automation? Seems to me more like a case of backup restore or rollback kind of thing.
Did you check Aurora logs?
Hello,
I never faced this issue. Your case very strange. May need to double check suitecrm logs then & PHP logs to investigate the issue
I used AWS CDK to deploy the Mysqll DB on Aurora Serverless V2, and the PHP code on ECS Fargate. When CDK ran, it spun both up and connected, and initialized the state using the SuiteCRM fake data. Then we cleared out the fake data, imported real data and created user accounts.
After a few weeks, I tried to login (which i used to be able to do successfully) but the account was gone. I was able to login using the original admin account, but then could see that all the imported data was gone, and the fake data which had been cleared out was back in the database.
I believe what happened is that something triggered the ECS Fargate (i.e. Docker container) to get replaced with a new instance which had the default initialization behavior and fake data which caused it to re-initialize the state of the system seen upon initial spin-up. I think I need to find a way to persist the customized state (user accounts, Studio-modified structure, our imported data) so that a Docker container replacement doesn’t re-initialize but instead keeps the latest state.
Anyone else experience something similar?
-keith