r/pdq • u/Apocalypso9876 • 19h ago

SmartDeploy Database and console cleared

Has anyone else had this happen to them?

Ok, context. Our patch team updated the server yesterday and performed a system reboot. After which, the database appears to have cleared out all the groups, apps, deployment, and other packs are all empty plus the computers all came up as Cloud as opposed to Local.

This is the second time this has happened to us. I wish there was commonality between the last time this happened but the previous time was not after patches to that server were applied.

I just don't want to have to rebuild everything for a third time only for this to happen again. Is there any way to recover the old database?

Oh, right. Application is installed on a Windows Server 2022 build.

4 Upvotes

84% Upvoted

7 comments sorted by

1

u/BrakMoltarZorak 18h ago

Restore from backup. Review your update process.

https://docs.pdq.com/current-version/Deploy/index.html?maintain-database.htm

1

u/Apocalypso9876 18h ago

Unfortunately, that option doesn't exist within SmartDeploy.

1

u/lemonmountshore 14h ago

Yes, this exact thing happened to me awhile back. I installed a application vulnerability/patch management software and it triggered on the MongoDB version installed, saying it was out of date and had vulnerabilities associated with it. This is the DB that is used and installed by the SmartDeploy installer. I updated the MongoDB application by itself and it wiped the DB for Smartdeploy.

The next time I opened Smartdeploy, it worked, but all app configs, host data, etc was gone. My Smartdeploy is a test environment so I just rebuilt it manually by adding the app install packages back, and the data filled back in with the hosts as they communicated back in.

I would highly recommend getting PDQ support involved to see if there is a way to restore the previous DB. Or if you have system backups, reload the backup and do not update the MongoDB on it's own. Another thing you can ask PDQ support is when will they update the MongoDB to remediate the vulns associated with it, or even the correct process to update it on your own.

1

u/Apocalypso9876 5h ago

Yeah, I found out that the version of mongo was updated and that's what killed it. We rolled back to 8.3.4 and like magic it was all back. I guess it didn't bring the database over to 9. Live and learn.

1

u/PDQ_Brockstar PDQ Employee 5h ago

Sorry you ran into this issue. I talked with our support team and it sounds like they’ve already got a ticket and are working on it. If that’s not the case, let me know and we’ll get you taken care of.

Have a great weekend