Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
SQL Database Backup Failure
-
The SQL backup has failed and I got this error:
Lobby Historian - Event active notification Urgent 00:05:00 - Backup Failed for File: no file because multiple points Note This event requires a manual acknowledgement for it to become inactive
The other backups were successful.
The ma.log shows these couple items. There was nothing else of note:
ERROR 2018-10-04T00:05:00,019 (com.serotonin.m2m2.rt.maint.work.DatabaseBackupWorkItem$DatabaseBackupTask.run:274) - java.lang.NumberFormatException: multiple points ERROR 2018-10-04T00:05:00,019 (com.serotonin.m2m2.rt.maint.work.DatabaseBackupWorkItem$DatabaseBackupTask.run:274) - java.lang.NumberFormatException: multiple points INFO 2018-10-04T00:05:00,022 (com.serotonin.m2m2.rt.maint.work.BackupWorkItem.execute:101) - Starting backup WorkItem. INFO 2018-10-04T00:05:02,188 (com.serotonin.m2m2.rt.maint.work.BackupWorkItem.execute:181) - Finished backup WorkItem.
Here is my configuration:
The mount point is mounted and working correctly.
I initiated the backup manually and it works perfectly fine without errors.
It could just be a fluke, but maybe there is something that could be fixed and I thought y'all should know.
-
Hi mihairosu,
It could just be a fluke, but maybe there is something that could be fixed and I thought y'all should know.
I suspect it was caused by some pretty rare timing, from searching the error. But I think you did guide me to something wrong and to be fixed, so thanks! https://github.com/infiniteautomation/ma-core-public/commit/ae274256866f504595a82de4424fc3c0100e86b0
Edit: looks like there's another issue - one that makes the 'rare timing' extremely probable. Fixing... https://github.com/infiniteautomation/ma-core-public/commit/168d42721207d134cb9a8121919ebc1c86e5635f
-
Okay great!
Yeah I've never seen this error since we got Mango, for all these years.