View Issue Details

IDProjectCategoryView StatusLast Update
0001022bareos-core[All Projects] directorpublic2019-03-13 18:51
Reporterder_andrewAssigned Toarogge 
PrioritynormalSeverityminorReproducibilityrandom
Status feedbackResolutionopen 
Platformx86_64OSCentOSOS Version7 (Core)
Product Version17.2.4 
Target VersionFixed in Version 
Summary0001022: Error message upon create volume
DescriptionI have this pattern for volume name:
Label Format = "$Storage-$Level-$JobId-$Day-$WeekDay-$Minute-$Second"

The job is successfully complited, but randomly message occure:
JobId 112049: Error: sql_create.c:444 Volume "ke047-bkp2-sd-Incremental-112049-17-3-0-14" already exists.

It's not possible IMHO :) because of "JobId 112049" and $JobId.

About a couple of month ago it was upgrade from 16.2.4 to 17.2.4.
Additional Information17-Oct 18:00 ms001-brbkp01-dir JobId 112049: Start Backup JobId 112049, Job=ke047-mx1-job.2018-10-17_18.00.07_49
17-Oct 18:00 ms001-brbkp01-dir JobId 112049: Max configured use duration=86,400 sec. exceeded. Marking Volume "ke047-bkp2-sd-Incremental-111627-16-2-0-17" as Used.
17-Oct 18:00 ms001-brbkp01-dir JobId 112049: Created new Volume "ke047-bkp2-sd-Incremental-112049-17-3-0-14" in catalog.
17-Oct 18:00 ms001-brbkp01-dir JobId 112049: Error: sql_create.c:444 Volume "ke047-bkp2-sd-Incremental-112049-17-3-0-14" already exists.
17-Oct 18:00 ms001-brbkp01-dir JobId 112049: Using Device "FileStorage01" to write.
17-Oct 18:00 bareos-sd JobId 112049: Elapsed time=00:00:04, Transfer rate=6.427 M Bytes/second
17-Oct 18:00 ms001-brbkp01-dir JobId 112049: sql_create.c:872 Insert of attributes batch table done
17-Oct 18:00 ms001-brbkp01-dir JobId 112049: Bareos ms001-brbkp01-dir 17.2.4 (21Sep17):
  Build OS: x86_64-redhat-linux-gnu redhat CentOS Linux release 7.4.1708 (Core)
  JobId: 112049
  Job: ke047-mx1-job.2018-10-17_18.00.07_49
  Backup Level: Incremental, since=2018-10-16 18:00:15
  Client: "ke047-mx1-fd" 17.2.4 (21Sep17) x86_64-redhat-linux-gnu,redhat,CentOS Linux release 7.4.1708 (Core) ,CentOS_7,x86_64
  FileSet: "CentOS7-common" 2018-09-17 18:00:00
  Pool: "CentOS7-common-ke047-Inc" (From Job IncPool override)
  Catalog: "ms001-brbkp01" (From Client resource)
  Storage: "ke047-bkp2-sd" (From Pool resource)
  Scheduled time: 17-Oct-2018 18:00:07
  Start time: 17-Oct-2018 18:00:16
  End time: 17-Oct-2018 18:00:24
  Elapsed time: 8 secs
  Priority: 10
  FD Files Written: 37
  SD Files Written: 37
  FD Bytes Written: 25,703,427 (25.70 MB)
  SD Bytes Written: 25,708,405 (25.70 MB)
  Rate: 3212.9 KB/s
  Software Compression: 86.6 % (gzip,gzip)
  VSS: no
  Encryption: no
  Accurate: no
  Volume name(s): ke047-bkp2-sd-Incremental-112049-17-3-0-14
  Volume Session Id: 277
  Volume Session Time: 1537967550
  Last Volume Bytes: 40,415,797 (40.41 MB)
  Non-fatal FD errors: 1
  SD Errors: 0
  FD termination status: OK
  SD termination status: OK
  Termination: Backup OK -- with warnings
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

der_andrew

der_andrew

2019-02-14 06:50

reporter   ~0003260

Upgrade to 18.2.5. The same issue...
arogge

arogge

2019-03-13 18:51

developer   ~0003286

The code does a "SELECT MediaId FROM Media WHERE VolumeName='%s'" (replacing %s with the volume-name) and then checks whether the database returns a row.
You can check this by executing the above query when the issue occurs and see wether the volume already exists in the catalog.

Issue History

Date Modified Username Field Change
2018-10-18 14:54 der_andrew New Issue
2019-02-14 06:50 der_andrew Note Added: 0003260
2019-03-13 18:51 arogge Assigned To => arogge
2019-03-13 18:51 arogge Status new => feedback
2019-03-13 18:51 arogge Note Added: 0003286