View Issue Details

IDProjectCategoryView StatusLast Update
0000707bareos-core[All Projects] directorpublic2019-10-14 14:40
ReporterhostedpowerAssigned To 
PrioritylowSeveritytweakReproducibilityalways
Status confirmedResolutionopen 
PlatformLinuxOSDebianOS Version8
Product Version16.2.4rc 
Fixed in Version 
Summary0000707: 13-Oct 21:02 bareos-dir JobId 0: Error: "fileset" directive in Job "Consolidate" resource is required, but not found.
Descriptionhttp://doc.bareos.org/master/html/bareos-manual-main-reference.html#QQ2-1-516

Job {
    Name = "Consolidate"
    Type = "Consolidate"
    Accurate = "yes"
    JobDefs = "DefaultJob"
}

Why would this require a fileset and some other directives which don't seem used?

Documentation: When used, it automatically trigger the consolidation of incremental jobs that need to be consolidated.

So it would be applied to any fileset?
TagsNo tags attached.
bareos-master: impactyes
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impactyes
bareos-16.2: action
bareos-15.2: impactno
bareos-15.2: action
bareos-14.2: impactno
bareos-14.2: action
bareos-13.2: impactno
bareos-13.2: action
bareos-12.4: impactno
bareos-12.4: action

Activities

joergs

joergs

2016-10-14 12:34

administrator   ~0002396

I recently modified the documentation in this respect, however the DefaultJob do contain a Fileset in the default installation. Have you changed your DefaultJob?
hostedpower

hostedpower

2016-10-14 12:48

reporter   ~0002398

Well I had another job defaults not containing any storage, pool , fileset or client and I had the error.

So the fileset is not really required, but it will give an error anyway when missing. Is that the right conclusion?

Also with storage, for me it was a bit confusing that it would store it potentially on the wrong place ... but I'm not an expert of course :)
joergs

joergs

2016-10-14 13:06

administrator   ~0002399

> So the fileset is not really required, but it will give an error anyway when missing. Is that the right conclusion?

yes. The reason is in the code. The default job type is Backup, and the required directives are set accordingly. For other job types some of these settings are ignored.
That is not pretty, but might have negative impact, if we would change this.
In the long run, we should change this.
b.braunger@syseleven.de

b.braunger@syseleven.de

2019-10-14 14:40

reporter   ~0003598

Are the any news about this behaviour? This also affects Restore Jobs which need the following dummy configuration

  Client = dummy_client
  Fileset = dummy_fileset
  Storage = dummy_storage
  Pool = dummy_pool

That is a pain to configure and confuses operators.

Issue History

Date Modified Username Field Change
2016-10-13 21:10 hostedpower New Issue
2016-10-14 12:32 joergs Assigned To => joergs
2016-10-14 12:32 joergs Status new => assigned
2016-10-14 12:34 joergs Note Added: 0002396
2016-10-14 12:34 joergs Status assigned => feedback
2016-10-14 12:34 joergs bareos-master: impact => yes
2016-10-14 12:34 joergs bareos-16.2: impact => yes
2016-10-14 12:34 joergs bareos-15.2: impact => no
2016-10-14 12:34 joergs bareos-14.2: impact => no
2016-10-14 12:34 joergs bareos-13.2: impact => no
2016-10-14 12:34 joergs bareos-12.4: impact => no
2016-10-14 12:48 hostedpower Note Added: 0002398
2016-10-14 12:48 hostedpower Status feedback => assigned
2016-10-14 13:06 joergs Note Added: 0002399
2016-10-14 13:07 joergs Assigned To joergs =>
2016-10-14 13:07 joergs Status assigned => confirmed
2016-10-14 13:07 joergs Product Version => 16.2.4rc
2019-10-14 14:40 b.braunger@syseleven.de Note Added: 0003598