Why does the console command ./craft db/restore expect the info table to exist and contain a row? There is also no option to ignore a non-existing info or empty info table.

When we create automated restore procedures via Jenkins, this causes the restore to fail, because the DB is e.g. empty.


  • Not a direct solution, but maybe a workaround would be to run install/craft in your CD pipeline (would need to specify all optional parameters to avoid it needing input). This will create all missing tables, so the restore should work.
    – MoritzLost
    Jun 16 at 15:43
  • There's an issue for this here: github.com/craftcms/cms/issues/7028. I just tested it on the latest Craft and while you do get that message, the database is also properly restored, so it's more of a UI issue. Did you verify the database was properly restored on Jenkins? Going to go ahead and vote to close here, but feel free to add a comment on the existing GH issue.
    – Brad Bell
    Jun 17 at 18:02
  • Hmm. We had the issue at a customer's staging installation yesterday, where the info table existed, but was empty, and the restore failed. Only after manually inserting the single row in the info table I was able to restore the full database. Jun 18 at 7:08

The issue is confirmed and solved in 3.6.18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.