 |
Hello, could you share you Messages and Daemon configuration please ? Check also if you have any XXXXX.mail left in /var/lib/bareos/ directory ? Maybe your backup server is sending from time to time too much message and hit a rate limit parameter on one server in mail path ? Or the message is dropped by some software in the mail delivery chain, thinking its a junk/spam/else ... This are the only reasons I can think about, and of course is not related to bareos: I've got 100% of bareos mail since more a decade. Let see if you configuration show something that can hurt messages. |
|
|
Yes, there are indeed many *.mail files left in the /var/lib/bareos directory! Here are my messages *.conf files (not modified from bareos 18, but maybe need to be?): Messages { Name = Daemon Description = "Message delivery for daemon messages (no job)." mailcommand = "/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \<%r\>\" -s \"Bareos daemon message\" %r" mail = root = all, !skipped, !audit # (0000002) console = all, !skipped, !saved, !audit append = "/var/log/bareos/bareos.log" = all, !skipped, !audit append = "/var/log/bareos/bareos-audit.log" = audit } Messages { Name = Standard Description = "Reasonable message delivery -- send most everything to email address and to the console." operatorcommand = "/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \<%r\>\" -s \"Bareos: Intervention needed for %j\" %r" mailcommand = "/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \<%r\>\" -s \"Bareos: %t %e of %n %l\" %r" operator = root = mount # (0000003) mail = root = all, !skipped, !saved, !audit # (0000002) console = all, !skipped, !saved, !audit append = "/var/log/bareos/bareos.log" = all, !skipped, !saved, !audit catalog = all, !skipped, !saved, !audit } As far as my mail config, I am using postfix (and dovecot, to retrieve the messages on an admin host) and have not observed any errors in the mail logs. There are no additional mail systems (MTAs?) in the mail "path" -- it is simply one host, running director, storage, postfix, and dovecot and another host running thunderbird to read the messages. This same arrangement works in my bareos 18 setup, which is where I got most of my config files for bareos 21. |
|
|
I probably need to remark that I have bareos 18 running on devuan ascii (debian 9) and bareos 21 on devuan chimaera (debian 11). I suppose there could be differences in the mail systems between the two, but I have mostly implemented both mail systems from the defaults out-of-the-box. Since those *.mail files are sitting in /var/lib/bareos, I am assuming bareos director still has not sent them? Does it not retry after some period of time? |
|
|
Nothing special in your config (you already report the changes of %c and %n between 18 and newer version) Usually if there are files .mail left that should mean the job is still running. If the job is terminated, and the .mail are still there's that mean they are just orphans. This can be the case when the director crash followed by a restart (depending how the systemd unit service is setup) but a crash is normally noticed in machine logs and systemctl status. |
|
|
I had to change %c to %n due to a change in the behavior in bareos 21. But that is a superficial change anyway. The jobs were not running, afaik. But if I notice missing emails again, I'll double check. I am not aware of crashes -- these jobs run overnight, automatically, per the schedule object set up for them. Devuan does not use systemd/systemctl, but I can still look at the system logs if/when this occurs again. I have not observed missing emails for several days now. |
|
|
1 missing email today. This time, though, I do not see any *.mail messages in /var/lib/bareos. I looked at the source to the mail messages that did make it to the other system, and mapped them to the mail.log messages on the bareos system. It appears that there was another message that did get processed by the mail server on the bareos system that does not map to any message received by my mail reader. It seems likely that this is not a bareos problem after all. I will continue looking at this problem on my side for now. I'd say to close this issue for now. |
|
|
doesn't seems to be a bareos problems. Not reproducible in any of automated tests here. |
- Anonymous
