perhaps you could try to run the fd in debug mode adding -d100 or 200 you normally can also set debug mode on fd from bconsole then also installing debuginfo rpm and try to report the full backtrace.
On July 7, 2017 6:04:40 PM GMT+03:00, Jason Bailey <[email protected]> wrote: >Hi all, > >I'm trying to track down a really strange problem in which bareos-fd >will segfault with the message that there's an error in smartall.c:229. > >I also get an error like this: Overrun buffer: len=304976 >addr=7f68803d7038 allocated: accurate_htable.c:56 called from >accurate_htable.c:204. > >I set the backup job in question to "accurate = no" and gave it another > >go with the same results. I've also tried running the job with spooling > >disabled -- I get the same result with no extra info to do further >troubleshooting. > >The system experiencing this issue has what seems to be plenty of free >disk space and memory. The only really helpful I've got is the previous > >message about smartall.c. > >Suggestions? The system is CentOS 6.9 VM running version 16.2.4 of the >Bareos file daemon. > >Jason Bailey -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
