 |
does "sudo -u bareos bareos-dir -t" test the configuration OK? |
|
|
root@backup:~# sudo -u bareos bareos-dir -t bareos-dir: ERROR TERMINATION at lib/parse_conf_state_machine.cc:128 Config error: expected an equals, got: { : line 1, col 9 of file /etc/bareos/bareos-dir.d/fileset/WindowsAll.conf FileSet { root@backup:~# |
|
|
Thank you for the feedback! It seems like the parser thinks it is inside of a resource definition and reads "FileSet" as a keyword, expecting it to be followed by an equals sign ("="). Could you attach that configuration file (as it is) to this bug, so I can try to reproduce this and find out what is going wrong? Would you also take a look at the other configuration files in the fileset directory? |
|
|
Here is my Fileset, it was working with 18.2.5 for a year: FileSet { Name= "WindowsAll" Enable VSS = No Include { Options { Signature = MD5 Compression = GZIP Drive Type = fixed IgnoreCase = yes aclsupport = no xattrsupport = no WildFile = "[A-Z]:/pagefile.sys" WildFile = "[A-Z]:/hiberfil.sys" WildFile = "*.mp4" WildDir = "[A-Z]:/RECYCLER" WildDir = "[A-Z]:/$RECYCLE.BIN" WildDir = "[A-Z]:/System Volume Information" Exclude = yes } File = "c:/Freigaben/" File = "c:/Lampey/" } } and I checked my other filesets, all filesets are original since first install, no changes made Are there any problems with old clients?? On my MS Server 2011 17.2.5 is running ... edit: after updating the win machine to 19.2.6 same error Thomas |
|
|
Seems to me that you did not close the "FileSet" Section with a "}"... This should be at the last line... |
|
|
@RSmit no, checked it, I think forgot one } with the copy&paste 3 times { and 3 times } edited my older post |
|
|
I will need an example how to trigger this. Either your director configuration (i.e. /etc/bareos/bareos-dir.d) in a tarball, preferably with the passwords removed. If you don't want to upload it here (which I can totally understand) you can send it to me via e-mail: andreas.rogge@bareos.com If you can reduce the configuration to the bare minimum that is required to reproduce the problem, that would save a lot of my time. |
|
|
I have tried your config file in one of my Directors, but it doesn't fail... So the problem might be somewhere else... The syntax your using has not changed as far as I can tell... Some things to try for general troubleshooting: - Have you tried to run you Director in Debug 200 (bareos-dir -d 200) mode? This helps me a lot when I have configuration problems. - What happens if remove the ".conf" from your WindowsAll config file and start the director? Note: there can be an other message from a Job missing this config... - Might there be a /etc/bareos/bareos-dir.conf file from an earlier version of Bareos? (long shot, but you never know...) - Can you start your Director if you remove the ".conf" from all your config files in [bareos]/client/, [bareos]/fileset/, [bareos]/schedule and [bareos]/job (where [bareos] = /etc/bareos/bareos-dir.d/)... If so re-add ".conf" to the config files one by one an try to restart the director... If not, you could send the remaining config to Andreas... |
|
|
@arogge @RSmit Aftes several tests and your tips, i got my director running tested it with gdb and debuglevel 200, gdb told me a list of config files to read. I checked all these configs and couldn't see any syntax errors. Then I saw, I had some older test configs under /etc/bareos, but all these were renamed without ".conf". I moved these files to my home dir, and the director started! My suggestion: the director tries to read these files, what he shouldn't not have to do. perhaps, check this for coming versions, and/or give a hint to the manual for other users Thomas |
|
|
Something more detailed than "I had some older test configs under /etc/bareos" would really help to reproduce this. |
|
|
@arogge @RSmit here are examples, used it for testing after first install (I began with 17.2.x): /etc/bareos/bareos-dir.d/job/server01.job Job { Name = server01.job Client = server01-fd JobDefs = Windows } /etc/bareos/bareos-dir.d/jobdef/windows JobDefs { Name = "Windows" Type = Backup Level = Incremental FileSet = "WindowsAll" # selftest fileset (0000013) Schedule = "AISched" Storage = File Messages = Standard Pool = Incremental Priority = 10 Write Bootstrap = "/var/lib/bareos/%c.bsr" Full Backup Pool = Full # write Full Backups into "Full" Pool (0000005) Differential Backup Pool = Differential # write Diff Backups into "Differential" Pool (0000008) Incremental Backup Pool = Incremental # write Incr Backups into "Incremental" Pool (0000011) } I renamed that files (removed the .conf) to prevent bareos using it. After moving that old files to my home dir, the director started up. Thomas |
|
|
As we can't reproduce this, we will closed it. |
- Anonymous
