Thanks for the reply, Ana. But the mail *was* from Bacula. My
bacula-dir.conf looks like this:

Messages {
  Name = Daemon
  mailcommand = "/usr/local/bin/my_smtp -h mailhub -f \"\(Bacula\) \<
bac...@example.com\>\" -s \"Bacula daemon message\" %r"

...so I can debug those sneaky mail problems :-) . /usr/local/bin/my_smtp
logs the behavior; here is its code:

echo ARGUMENTS: 1:"'$1'" 2:"'$2'" 3:"'$3'" 4:"'$4'" 5:"'$5'" 6:"'$6'"
7:"'$7'" 8: "'$8'" | logger -p mail.info
/usr/sbin/bsmtp -d 10 "$@" 2>&1 | logger -p mail.info

And indeed, the mail log shows the event taking place at 11:00, the time
the mail was sent:

Aug  9 11:00:01 ch0-backup-01 logger: ARGUMENTS: 1:'-h' 2:'mailhub' 3:'-f'
4:'(Bacula) <bac...@example.com>' 5:'-s' 6:'Bacula daemon message'
7:'i...@example.com' 8: ''
Aug  9 11:00:01 ch0-backup-01 logger: mailhub <-- 220 mailhub.example.com
ESMTP Postfix
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub --> 220
mailhub.example.com ESMTP Postfix
Aug  9 11:00:01 ch0-backup-01 logger: mailhub.example.com --> HELO
ch0-backup-01
Aug  9 11:00:01 ch0-backup-01 logger: mailhub <-- 250 mailhub.example.com
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub --> 250
mailhub.example.com
Aug  9 11:00:01 ch0-backup-01 logger: ch0-backup-01 --> MAIL FROM:<
bac...@example.com>
Aug  9 11:00:01 ch0-backup-01 logger: mailhub <-- 250 2.1.0 Ok
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub --> 250
2.1.0 Ok
Aug  9 11:00:01 ch0-backup-01 logger: ch0-backup-01 --> RCPT TO:<
i...@example.com>
Aug  9 11:00:01 ch0-backup-01 logger: mailhub <-- 250 2.1.5 Ok
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub --> 250
2.1.5 Ok
Aug  9 11:00:01 ch0-backup-01 logger: ch0-backup-01 --> DATA
Aug  9 11:00:01 ch0-backup-01 logger: mailhub <-- 354 End data with
<CR><LF>.<CR><LF>
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub --> 354
End data with <CR><LF>.<CR><LF>
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:594-0 From: (Bacula) <
bac...@example.com>
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:597-0 Subject: Bacula
daemon message
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:625-0 Sender:
bacula@ch0-backup-01
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:630-0 To:
i...@example.com bsmtp: bsmtp.c:637-0
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:650-0 Date: Sun, 09
Aug 2015 11:00:01 +0000 (UTC)
Aug  9 11:00:01 ch0-backup-01 logger: ch0-backup-01 --> .
Aug  9 11:00:01 ch0-backup-01 logger: mailhub <-- 250 2.0.0 Ok: queued as
921D72056F
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub --> 250
2.0.0 Ok: queued as 921D72056F
Aug  9 11:00:01 ch0-backup-01 logger: ch0-backup-01 --> QUIT
Aug  9 11:00:01 ch0-backup-01 logger: mailhub <-- 221 2.0.0 Bye
Aug  9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub --> 221
2.0.0 Bye




*- Mike Schwager*

*  Linux Network Engineer, Mocho Trading LLC*
*  312-646-4783 Phone    312-637-0011 Cell    312-957-9804 Fax*


On Mon, Aug 10, 2015 at 9:00 PM, Ana Emília M. Arruda <
emiliaarr...@gmail.com> wrote:

> Hello Michael,
>
> It seems not to be an issue with Bacula. Instead, maybe this mail had been
> queued in your system and relayed at a later time.
>
> Best regards,
> Ana
>
> On Mon, Aug 10, 2015 at 11:01 AM, Michael Schwager <
> mschwa...@mochotrading.com> wrote:
>
>> Hello,
>> Yesterday (Sunday) I received an email from bacula-dir but I don't know
>> why. It contains old authentication error messages from a week ago (see
>> below) that I'd rectified on the 03 August later in the day. I don't know
>> why I received this message now, and I'd like to prevent it from recurring.
>> ...It makes my boss anxious. :-)
>>
>> The mail was sent at 11:00 UTC. There is no other job scheduled in
>> bacula-dir or in cron that would take place at the time this email was
>> sent. My maillog is consistent with that. I have verified that the mail
>> came from bacula-dir
>>
>> I wonder if a start of the bacula director would send an email, but I
>> just tried it and it did not send the email again (see the cron operations
>> that are performed, below). Does bacula-dir send error messages that are <=
>> 1 week old, upon startup?
>>
>> At 11:00 UTC my system performs the following from cron, in order to
>> perform a binary backup:
>> ​systemctl stop bacula-dir
>> ​systemctl stop bacula-sd
>> ​systemctl stop bacula-fd​
>> systemctl stop mysqld
>> ​(copy database dir)
>> ​systemctl start mysqld
>> systemctl start bacula-fd
>> ​systemctl stop bacula-sd
>> ​systemctl stop bacula-dir
>>
>> ​Thanks for any help.
>>
>>
>> *- Mike Schwager*
>>
>> *  Linux Network Engineer, Mocho Trading LLC*
>> *  312-646-4783 <312-646-4783> Phone    312-637-0011 <312-637-0011>
>> Cell    312-957-9804 <312-957-9804> Fax*
>>
>>
>> ---------- Forwarded message ----------
>> From: Bacula <backup@
>> ​example​
>> .com>
>> Date: Sun, Aug 9, 2015 at 6:00 AM
>> Subject: Bacula daemon message
>> To: it@
>> ​example.com
>>
>>
>> 02-Aug 22:24 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director
>> unable to authenticate with Storage daemon at "
>> -backup-01.example.com:9103 <http://backup-01.example.com:9103>".
>> Possible causes:
>> Passwords or names not the same or
>> Maximum Concurrent Jobs exceeded on the SD or
>> SD networking messed up (restart daemon).
>> Please see
>> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000
>> for help.
>> 03-Aug 02:38 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director
>> unable to authenticate with Storage daemon at "
>> http://backup-01.example.com:9103";. Possible causes:
>> Passwords or names not the same or
>> Maximum Concurrent Jobs exceeded on the SD or
>> SD networking messed up (restart daemon).
>> Please see
>> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000
>> for help.
>> 03-Aug 02:49 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director
>> unable to authenticate with Storage daemon at "
>> http://backup-01.example.com:9103";. Possible causes:
>> Passwords or names not the same or
>> Maximum Concurrent Jobs exceeded on the SD or
>> SD networking messed up (restart daemon).
>> Please see
>> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000
>> for help.
>>
>>
>

-- 
This message is for the named person(s) use only. It may contain 
confidential proprietary or legally privileged information. No 
confidentiality or privilege is waived or lost by any mistransmission. If 
you receive this message in error, please immediately delete it and all 
copies of it from your system, destroy any hard copies of it and notify the 
sender. You must not, directly or indirectly use, disclose, distribute, 
print, or copy any part of this message if you are not the intended 
recipient. Mocho Trading LLC reserves the right to monitor all e-mail 
communications through its networks. Any views expressed in this message 
are those of the individual sender, except where the message states 
otherwise and the sender is authorized to state them to be the views of any 
such entity.
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to