Luckily I still had the backups I'd taken 2 months ago when I changed
the SE hardware. Also, that particular table is fairly static, so
reinstating it wasn't as bad as for some of the other tables.
John
On 09/06/2016 15:10, Sam Skipsey wrote:
> Huh, that's fairly terrifying, given how important dpm_fs is as a table.
> I guess you don't have a backup with it actually present?
>
> Sam
>
> On Thu, Jun 9, 2016 at 12:09 PM John Hill <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
> On 09/06/2016 11:35, John Hill wrote:
> > I've just rebooted my SE (dpm 1.8.10) to bring it up to the latest
> > kernel. On reboot, dpm fails to start and I'm getting
> >
> > mysql_query error: Table 'dpm_db.dpm_fs' doesn't exist
> >
> > in the logs. This sounds like a database corruption - what's the best
> > way to recover from this situation?
> >
> > John
>
> To answer my own question, I've recovered the situation by recreating
> the table and populating via a puppet run. The scary thing is that
> looking at my database backups, this table has been missing for at least
> 10 days - so it wasn't a problem caused by the reboot (though the
> symptoms were of course provoked by it).
>
> John
>
|