View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001105bareos-corefile daemonpublic2019-07-26 14:532019-07-31 09:46
ReporterAndrew Clark Assigned Toarogge  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSCentOSOS Version7
Product Version18.2.5 
Summary0001105: Bareos-fd send data infinitely
Description
When I have try to do backup from client i have this:

infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536

Data sends on and on and on. Director has volume with this backup bigger than size of hard drive of a client. After I interrupt client, I have this in console:

[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
6
[root@infra-ipam.example.com:~]# infra-ipam.example.com (130): filed/backup.cc:1038-17631 Send data to SD len=65536
bash: syntax error near unexpected token `130'
Steps To Reproduce1. exec bareos-fd with this option bareos-fd -vd 99999 on a client
2. start backup job for this client
3. look what client sends to a console
4. constatly check size of a volume on backup directory
TagsNo tags attached.

Activities

arogge

arogge

2019-07-26 15:15

manager   ~0003524

Do a status client to see what file the bareos-fd is backing up.
Maybe it is a large sparse file and you don't have sparse-file support or compression enabled?
Andrew Clark

Andrew Clark

2019-07-26 15:37

reporter   ~0003525

Last edited: 2019-07-28 09:32

 # bareos-fd -xc
Director {
  Name = "bareos-mon"
  Description = "Restricted Director, used by tray-monitor to get the status of this file daemon."
  Password = "[md5]f2c762f5b5876b833ac821c46ac071a2"
  Monitor = yes
  MaximumBandwidthPerJob = 0
}

Director {
  Name = "infra-backup-01.example.com"
  Description = "Allow the configured Director to access this file daemon."
  Password = "[md5]a1bc2f998710c0a08f905901b7c98829"
  MaximumBandwidthPerJob = 0
}

FileDaemon {
  Name = "infra-ipam.example.com"
  PluginDirectory = "/usr/lib64/bareos/plugins"
  MaximumConcurrentJobs = 30
  MaximumNetworkBufferSize = 0
  Compatible = no
  MaximumBandwidthPerJob = 0
  AbsoluteJobTimeout = 0
  LmdbThreshold = 0
}

Messages {
   Name = "Standard"
   director = infra-backup-01.example.com = all,!skipped,!restored
}

How do I enable sparse-file support or compression in Bareos?
arogge

arogge

2019-07-26 15:40

manager   ~0003526

Both can be configured using Fileset Options. See https://docs.bareos.org/Configuration/Director.html#fileset-options-ressource
Andrew Clark

Andrew Clark

2019-07-26 16:01

reporter   ~0003527

Thank you! I have edited conf files, and checking right now.
And which directive enables status client?
arogge

arogge

2019-07-26 16:10

manager   ~0003528

just type "status client" in the bconsole
Andrew Clark

Andrew Clark

2019-07-30 10:14

reporter   ~0003534

Looks like option "sparse = yes" helped! Thank you very much!
I wonder, why I should not impact with this problem in version 17.2?
arogge

arogge

2019-07-31 09:34

manager   ~0003537

You probably didn't have that sparse file or it wasn't backed up.
The sparse behaviour has not been changed for quite a long time now.

Do you still need help with this or can we close it?
Andrew Clark

Andrew Clark

2019-07-31 09:43

reporter   ~0003539

It is strange, because nothing changes on servers, except that fact that I have updated bareos-fd version.
You can close this bug, but one more question I want to ask - is there any option in bareos that allows me
to watch which file is backing up at this moment? For instance, I can see in bareos-webui indexes and blocks
changing during backup, but what about files?
arogge

arogge

2019-07-31 09:45

manager   ~0003540

status client=<clientname> will report what file is currently being processed.

Issue History

Date Modified Username Field Change
2019-07-26 14:53 Andrew Clark New Issue
2019-07-26 15:15 arogge Status new => feedback
2019-07-26 15:15 arogge Note Added: 0003524
2019-07-26 15:37 Andrew Clark Note Added: 0003525
2019-07-26 15:37 Andrew Clark Status feedback => new
2019-07-26 15:40 arogge Status new => feedback
2019-07-26 15:40 arogge Note Added: 0003526
2019-07-26 16:01 Andrew Clark Note Added: 0003527
2019-07-26 16:01 Andrew Clark Status feedback => new
2019-07-26 16:10 arogge Status new => feedback
2019-07-26 16:10 arogge Note Added: 0003528
2019-07-28 09:32 Andrew Clark Note Edited: 0003525
2019-07-30 10:14 Andrew Clark Note Added: 0003534
2019-07-30 10:14 Andrew Clark Status feedback => new
2019-07-31 09:34 arogge Status new => feedback
2019-07-31 09:34 arogge Note Added: 0003537
2019-07-31 09:43 Andrew Clark Note Added: 0003539
2019-07-31 09:43 Andrew Clark Status feedback => new
2019-07-31 09:45 arogge Note Added: 0003540
2019-07-31 09:45 arogge Assigned To => arogge
2019-07-31 09:45 arogge Status new => resolved
2019-07-31 09:45 arogge Resolution open => no change required
2019-07-31 09:46 arogge Status resolved => closed