It's probably related to memory exhaust in the docker itself. For the backtrace, if you can setup the mailing then the backtrace might be sent out of the docker when the crash occur.
On Monday, 8 September 2025 at 19:48:31 UTC+2 Markus Dubois wrote: > after a long full backup run (16 TB), i got this on client side: > ____ > *** stack smashing detected ***: terminated > > BAREOS interrupted by signal 6: IOT trap > > bareos-fd, omvserver got signal 6 - IOT trap. Attempting traceback. > > exepath=/usr/sbin/ > > Calling: /usr/sbin/btraceback /usr/sbin/bareos-fd 10 /var/lib/bareos > > It looks like the traceback worked... > > Dumping: /var/lib/bareos/omvserver.10.bactrace > > ___ > > unfortunately it´s a docker container in docker swarm, so i cannot access > the trace file (at least i do not know how) > -- 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 view this discussion visit https://groups.google.com/d/msgid/bareos-users/febb358e-5bd3-43c1-aafb-714010995bfdn%40googlegroups.com.
