View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000678 | bareos-core | director | public | 2016-08-03 12:24 | 2019-12-18 15:25 |
| Reporter | iodun | Assigned To | stephand | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | Linux | OS | OpenSUSE Leap | OS Version | 42.1 |
| Product Version | 15.2.2 | ||||
| Summary | 0000678: BVFS Fatal Error (duplicate key value violates unique constraint) | ||||
| Description | 02-Aug 21:36 miv-bareos-dir JobId 809: No Jobs found to prune. 02-Aug 21:36 miv-bareos-dir JobId 809: Begin pruning Files. 02-Aug 21:36 miv-bareos-dir JobId 809: No Files found to prune. 02-Aug 21:36 miv-bareos-dir JobId 809: End auto prune. 03-Aug 10:32 miv-bareos-dir JobId 0: Fatal error: bvfs.c:289 bvfs.c:289 insert INSERT INTO PathHierarchy (PathId, PPathId) VALUES (1130194,1127962) failed: ERROR: duplicate key value violates unique constraint "pathhierarchy_pkey" DETAIL: Key (pathid)=(1130194) already exists. 03-Aug 10:32 miv-bareos-dir JobId 0: Fatal error: bvfs.c:263 bvfs.c:263 query SELECT PPathId FROM PathHierarchy WHERE PathId = 1127777 failed: ERROR: current transaction is aborted, commands ignored until end of transaction block 03-Aug 10:32 miv-bareos-dir JobId 0: Fatal error: bvfs.c:263 bvfs.c:263 query SELECT PPathId FROM PathHierarchy WHERE PathId = 1127982 failed: ERROR: current transaction is aborted, commands ignored until end of transaction block 03-Aug 10:32 miv-bareos-dir JobId 0: Fatal error: bvfs.c:263 bvfs.c:263 query SELECT PPathId FROM PathHierarchy WHERE PathId = 1127589 failed: ERROR: current transaction is aborted, commands ignored until end of transaction block (...) 03-Aug 10:33 miv-bareos-dir JobId 0: Fatal error: bvfs.c:263 bvfs.c:263 query SELECT PPathId FROM PathHierarchy WHERE PathId = 1176129 failed: ERROR: current transaction is aborted, commands ignored until end of transaction block 03-Aug 10:33 miv-bareos-dir JobId 0: Fatal error: bvfs.c:263 bvfs.c:263 query SELECT PPathId FROM PathHierarchy WHERE PathId = 1175189 failed: ERROR: current transaction is aborted, commands ignored until end of transaction block 03-Aug 10:33 miv-bareos-dir JobId 0: Fatal error: bvfs.c:421 bvfs.c:421 query INSERT INTO PathVisibility (PathId, JobId) SELECT a.PathId,526 FROM ( SELECT DISTINCT h.PPathId AS PathId FROM PathHierarchy AS h JOIN PathVisibility AS p ON (h.PathId=p.PathId) WHERE p.JobId=526) AS a LEFT JOIN (SELECT PathId FROM PathVisibility WHERE JobId=526) AS b ON (a.PathId = b.PathId) WHERE b.PathId IS NULL failed: ERROR: current transaction is aborted, commands ignored until end of transaction block 03-Aug 10:33 miv-bareos-dir JobId 0: Error: bvfs.c:425 bvfs.c:425 update UPDATE Job SET HasCache=1 WHERE JobId=526 failed: ERROR: current transaction is aborted, commands ignored until end of transaction block 03-Aug 10:33 miv-bareos-dir: ERROR in output_formatter.c:633 Failed to send result as json. Maybe result message to long? Message length = 176 03-Aug 10:34 miv-bareos-dir: ERROR in output_formatter.c:633 Failed to send result as json. Maybe result message to long? Message length = 39 | ||||
| Additional Information | There were no running backup jobs and as you can see in the logs above the last job finished 02-Aug 21:36. Today morning (03-Aug 10:32) the director started spamming lots of error messages related to BVFS. Since 03-Aug 10:34 it is silent again and I have no idea what happened. What exactly is bareos telling me here? Why it started all of a sudden without any jobs running? | ||||
| Tags | No tags attached. | ||||
 |
Did you remember if you were using the bareos-webui at that time. The first .bvfs construction can take a lot of time, and most of users think that it is stuck. So a big majority simply stop it, or reload the webpage. (restore) It will work most of the time when people then change the client to restore (often to a smaller fileset) then the table are cleanup and fillup again correctly, which explain why you didn't see messages afterward. |
|
|
Fix committed to bareos bareos-16.2 branch with changesetid 6791. |
|
bareos: bareos-16.2 b333fe98 2016-11-24 22:53 Ported: N/A Details Diff |
Prevent from duplicate key violations on concurrent .bvfs_update When multiple .bvfs_update were run concurrently, duplicate key violations could occur on the PathHierarchy table, which lead to aborted transactions. Fixes 0000678: BVFS Fatal Error (duplicate key value violates unique constraint) |
Affected Issues 0000678 |
|
| mod - src/cats/bvfs.c | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-08-03 12:24 | iodun | New Issue | |
| 2016-08-30 22:40 | tigerfoot | Note Added: 0002340 | |
| 2016-11-10 16:15 | joergs | Assigned To | => stephand |
| 2016-11-10 16:15 | joergs | Status | new => assigned |
| 2016-12-03 11:49 | stephand | Changeset attached | => bareos bareos-16.2 b333fe98 |
| 2016-12-03 11:49 | stephand | Note Added: 0002459 | |
| 2016-12-03 11:49 | stephand | Status | assigned => resolved |
| 2016-12-03 11:49 | stephand | Resolution | open => fixed |
| 2019-12-18 15:25 | arogge | Status | resolved => closed |
