Hi,
When I start bacula-dir 5.2.5 with the -t switch, I get a series of messages about orphaned buffers.
bacula-dir: smartall.c:404 Orphaned buffer: bacula-dir 7 bytes at 21a8e88 from parse_conf.c:416
bacula-dir: smartall.c:404 Orphaned buffer: bacula-dir 10 bytes at 21bff18 from inc_conf.c:598
bacula-dir: smartall.c:404 Orphaned buffer: bacula-dir 10 bytes at 21c0908 from inc_conf.c:598
bacula-dir: smartall.c:404 Orphaned buffer: bacula-dir 10 bytes at 21c1458 from inc_conf.c:598
bacula-dir: smartall.c:404 Orphaned buffer: bacula-dir 10 bytes at 21c1dc8 from inc_conf.c:598
bacula-dir: smartall.c:404 Orphaned buffer: bacula-dir 10 bytes at 21c2738 from inc_conf.c:598
bacula-dir: smartall.c:404 Orphaned buffer: bacula-dir 10 bytes at 21c2ef8 from inc_conf.c:598
Without -t, it starts clean.
Is(or was) this something that only rears its head when you are verifying the configuration, or is it something I should pay more attention to?
Google came up with this:
The "Orphaned buffer" message suggests that some field of an item in the
config
is being initialized more than once.
I don’t have any double (repeated) entries in my configuration that I know of, but there might be (not sure) some settings in
jobdefs or schedules that are being overridden in individual job definitions, or something like that.
Is that a bad idea?
Thanks for any reactions.