Migration error: munkireport: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: munkireport.serial_number

[Sam Tarr]

After upgrading to the newest version of munki reports I'm getting Migration error: munkireport: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: munkireport.serial_number at the top of all my pages. We were previously running a very old version. I believe it was 2.0.4. If I change the config.php to read $conf['allow_migrations'] = FALSE; the error does go away. I'm using SQLite Database. When I look at the database the munkireport table is completely empty. Looking at the  Has anyone run into this? Thanks

[A.E. van Bochoven]

If the munkireport table is empty you can just drop the table and let Munkireport recreate it.

sqlite3 /path/to/sqlite.db 'DROP table munkireport'

-Arjen

On 27 Mar 2015, at 14:18, Sam Tarr <samt...@gmail.com> wrote:

After upgrading to the newest version of munki reports I'm getting Migration error: munkireport: SQLSTATE[23000]: Integrity constraint violation: 19 UNIQUE constraint failed: munkireport.serial_number at the top of all my pages. We were previously running a very old version. I believe it was 2.0.4. If I change the config.php to read $conf['allow_migrations'] = FALSE; the error does go away. I'm using SQLite Database. When I look at the database the munkireport table is completely empty. Looking at the  Has anyone run into this? Thanks

--
You received this message because you are subscribed to the Google Groups "munkireport" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munkireport...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sam Tarr]

Thanks for your response. I just tried that and I get database disk image is malformed
I also tried it on a backup of the database that was taken before the upgrade. I'm thinking I may have to just delete the whole database and let the clients check back in a repopulate it.