Re: [Bacula-users] Bacula daemon message- where did it come from?
Apologies for the late response to this thread. Michael is correct in that
these daemon messages are Bacula created and not delivered when created. Not
only the example that he provided, but when an attempt to connect to the
director from an unknown and invalid client will generate these messages. They
only appear in the bacula log and the mail log when the director is shutdown,
not when the incident occurs. I consider this a bug in Bacula. Not only a
bug, but a security bug because the delay in reporting prevents responsive
action if required. I have checked my messages and traced them to our security
team probing our systems for security holes. I just don't see this from Bacula
until the next director shutdown. Where Bacula keeps the messages until then,
I do not know.
Patti Clark
Linux System Administrator
RD Systems Support Oak Ridge National Laboratory
From: Michael Schwager
mschwa...@mochotrading.commailto:mschwa...@mochotrading.com
Date: Thursday, August 13, 2015 at 1:09 PM
To: Heitor Faria hei...@bacula.com.brmailto:hei...@bacula.com.br
Cc: bacula-users
bacula-users@lists.sourceforge.netmailto:bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula daemon message- where did it come from?
On Wed, Aug 12, 2015 at 8:15 AM, Heitor Faria
hei...@bacula.com.brmailto:hei...@bacula.com.br wrote:
I agree with Ana with the fact it is probably not a bug. Even in the hypothesis
Bacula is sending delayed messages this is the reason there is a time stamp on
each log message. Yes: the connection error happened. Yes: daemon messages can
be annoying and sometime lead incautious users to confusion if they only
receive the message after the error is solved. But you can always opt out this
messages or don't send them to the boss. =)
For the record and benefit of any future Google searches (and I believe this
problem is solved in any case), it may be instructive for the user to have
Bacula call a script (as I have done) rather than bsmtp directly. Over the
course of my Bacula installation I needed to verify the correct operation of
all the component pieces of messaging delivery so I created a frontend to
bsmtp. Bacula calls that, rather than bsmtp itself, so I can see what it is
trying to do before it even gets to the mail system.
What I know is this:
1. Bacula sent a message at 11:00 UTC. This is not a hypothesis, it's a
fact; in fact, this line in the script:
echo ARGUMENTS: 1:'$1' 2:'$2' 3:'$3' 4:'$4' 5:'$5' 6:'$6' 7:'$7'
8: '$8' | logger -p mail.infohttp://mail.info
http://mail.info
produced this line in the mail.log:
Aug 9 11:00:01 ch0-backup-01 logger: ARGUMENTS: 1:'-h' 2:'mailhub' 3:'-f'
4:'(Bacula) bac...@example.commailto:bac...@example.com' 5:'-s' 6:'Bacula
daemon message' 7:'i...@example.commailto:7%3a%2...@example.com' 8: ''
2. Its subject line as you can see was Bacula daemon message which matches
the following entry in my bacula-dir.conf:
Messages {
Name = Daemon
mailcommand = /usr/local/bin/my_smtp -h mailhub -f \\(Bacula\)
\bac...@example.commailto:bac...@example.com\\ -s \Bacula daemon
message\ %r
mail = i...@mochotrading.commailto:i...@mochotrading.com = all, !skipped
append = /var/log/bacula/daemon.log = all, !skipped
}
3. It contained information that was over a week old.
4. I didn't know why.
5. Curiously, precisely the same time (at 11:00 UTC) I stop the Bacula
daemons. Some time later I restart them.
6. I don't want it to happen again.
Opting out of alerts is very dangerous. They are always telling you something.
They may be telling you that there is a problem in your system, or they may be
a false alarm. Either way, they are telling you something should be fixed.
Otherwise soon you are ignoring daemon messages as a nuisance and then you
REALLY have some explaining to your boss when you miss the one that alerts you
to a real problem!
In this case, it looks like there was a problem in the Bacula system that Kern
repaired.
- Mike Schwager
Linux Network Engineer, Mocho Trading LLC
312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax
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
Re: [Bacula-users] Bacula daemon message- where did it come from?
My mailbox is in CDT (5 hours behind UTC). The backup host is in UTC, hence the log entries (and mail headers, too, btw) show times in UTC. This is why I created the logging frontend script: in order to debug Becula's mail messaging, I want to see what *Bacula* is trying to do; I don't want to get confused by mail system problems. So: Clearly, Bacula had sent one and only one daemon message from our mail server at 11:00 UTC on that day. In that mail message were daemon messages that were a little over a week old. In any event, Kern updated the Bacula code to hopefully solve this problem. *- Mike Schwager* * Linux Network Engineer, Mocho Trading LLC* * 312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax* On Tue, Aug 11, 2015 at 9:06 PM, Ana Emília M. Arruda emiliaarr...@gmail.com wrote: Hello Michael, From your first post, the header of the email shows a 6:00 AM time, not the 11:00 AM. Are your sure they are the same e-mails? Is there any other e-mail in bac...@example.com mailbox that arrived at 11:00 AM? -- Forwarded message -- From: Bacula backup@ example .com Date: Sun, Aug 9, 2015 at 6:00 AM Subject: Bacula daemon message To: it@ example.com Best regards, Ana Looking carefully your first post, the e-mail sent with the authentication error took place at 6 am and not 11 am. This log register do not seems to be the log for your error message. Instead it seems to be an e-mail sent by bacula after restarting. Em ter, 11 de ago de 2015 às 15:21, Michael Schwager mschwa...@mochotrading.com escreveu: On Tue, Aug 11, 2015 at 8:49 AM, Martin Simmons mar...@lispworks.com wrote: Looks like a bug to me (I've just created http://bugs.bacula.org/view.php?id=2159). Thanks. I have contributed to your bug report. *- Mike Schwager (aka, The Most Greyish of Gnomes)* * Linux Network Engineer, Mocho Trading LLC* * 312-646-4783 312-646-4783 Phone312-637-0011 312-637-0011 Cell312-957-9804 312-957-9804 Fax* 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 -- 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
Re: [Bacula-users] Bacula daemon message- where did it come from?
On Wed, Aug 12, 2015 at 8:15 AM, Heitor Faria hei...@bacula.com.br wrote:
I agree with Ana with the fact it is probably not a bug. Even in the
hypothesis Bacula is sending delayed messages this is the reason there is a
time stamp on each log message. Yes: the connection error happened. Yes:
daemon messages can be annoying and sometime lead incautious users to
confusion if they only receive the message after the error is solved. But
you can always opt out this messages or don't send them to the boss. =)
For the record and benefit of any future Google searches (and I believe
this problem is solved in any case), it may be instructive for the user to
have Bacula call a script (as I have done) rather than bsmtp directly. Over
the course of my Bacula installation I needed to verify the correct
operation of all the component pieces of messaging delivery so I created a
frontend to bsmtp. Bacula calls that, rather than bsmtp itself, so I can
see what it is trying to do *before it even gets to the mail system*.
What I know is this:
1. Bacula sent a message at 11:00 UTC. This is not a hypothesis, it's a
fact; in fact, this line in the script:
echo ARGUMENTS: 1:'$1' 2:'$2' 3:'$3' 4:'$4' 5:'$5' 6:'$6'
7:'$7' 8: '$8' | logger -p mail.info
http://mail.info
produced this line in the mail.log:
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: ''
2. Its subject line as you can see was Bacula daemon message which
matches the following entry in my bacula-dir.conf:
Messages {
Name = Daemon
mailcommand = /usr/local/bin/my_smtp -h mailhub -f \\(Bacula\) \
bac...@example.com\\ -s \Bacula daemon message\ %r
mail = i...@mochotrading.com = all, !skipped
append = /var/log/bacula/daemon.log = all, !skipped
}
3. It contained information that was over a week old.
4. I didn't know why.
5. Curiously, precisely the same time (at 11:00 UTC) I stop the Bacula
daemons. Some time later I restart them.
6. I don't want it to happen again.
Opting out of alerts is very dangerous. They are always telling you
something. They may be telling you that there is a problem in your system,
or they may be a false alarm. Either way, they are telling you something
should be fixed. Otherwise soon you are ignoring daemon messages as a
nuisance and then you REALLY have some explaining to your boss when you
miss the one that alerts you to a real problem!
In this case, it looks like there was a problem in the Bacula system that
Kern repaired.
*- Mike Schwager*
* Linux Network Engineer, Mocho Trading LLC*
* 312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*
--
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
Re: [Bacula-users] Bacula daemon message- where did it come from?
Hi all, If I didn’t misunderstand anything, Michael said he checked the Received headers as well. Those indicate at what time the message arrived at different mail servers along its path, I assume they show that bsmtp passed it to the local outgoing mail server at 11:00 ? BTW, I would never trust the ‘Date’ header. Some mail programs fill it in when you compose the mail, some when you actually send it (it could sit in your outbox for a while), and some don’t include it at all and rely on the mail server to add it. And to make things worse, if you use MS Outlook on Exchange, it doesn’t even show its value in the message list, it shows the time it arrived in your mailbox instead (for example Ana’s mail I’m replying to has a timestamp of 4:06 inside, but in Outlook’s message list it says 4:09). From: Ana Emília M. Arruda [mailto:emiliaarr...@gmail.com] Sent: 12 August 2015 4:06 To: Michael Schwager mschwa...@mochotrading.com Cc: Bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Bacula daemon message- where did it come from? Hello Michael, From your first post, the header of the email shows a 6:00 AM time, not the 11:00 AM. Are your sure they are the same e-mails? Is there any other e-mail in bac...@example.commailto:bac...@example.com mailbox that arrived at 11:00 AM? -- Forwarded message -- From: Bacula backup@ example .com Date: Sun, Aug 9, 2015 at 6:00 AM Subject: Bacula daemon message To: it@ example.comhttp://example.com/ Best regards, Ana Looking carefully your first post, the e-mail sent with the authentication error took place at 6 am and not 11 am. This log register do not seems to be the log for your error message. Instead it seems to be an e-mail sent by bacula after restarting. Em ter, 11 de ago de 2015 às 15:21, Michael Schwager mschwa...@mochotrading.commailto:mschwa...@mochotrading.com escreveu: On Tue, Aug 11, 2015 at 8:49 AM, Martin Simmons mar...@lispworks.commailto:mar...@lispworks.com wrote: Looks like a bug to me (I've just created http://bugs.bacula.org/view.php?id=2159). Thanks. I have contributed to your bug report. - Mike Schwager (aka, The Most Greyish of Gnomes) Linux Network Engineer, Mocho Trading LLC 312-646-4783tel:312-646-4783 Phone312-637-0011tel:312-637-0011 Cell 312-957-9804tel:312-957-9804 Fax 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.netmailto:Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula daemon message- where did it come from?
Hello Luc, Thank you for the explanation. BTW I had being thinking if this was not due because of a timezone mismatch configuration in the mail server/relay (supposing the datetime was filled by the SMTP server and not client). I'm still believing in a system mail problem instead of a bacula issue, since as far as I know bacula do not store theses messages for later delivering (acting as a mail relay in this case). Best regards, Ana Em qua, 12 de ago de 2015 às 03:41, Luc Van der Veken luc...@wimionline.com escreveu: Hi all, If I didn’t misunderstand anything, Michael said he checked the Received headers as well. Those indicate at what time the message arrived at different mail servers along its path, I assume they show that bsmtp passed it to the local outgoing mail server at 11:00 ? BTW, I would never trust the ‘Date’ header. Some mail programs fill it in when you compose the mail, some when you actually send it (it could sit in your outbox for a while), and some don’t include it at all and rely on the mail server to add it. And to make things worse, if you use MS Outlook on Exchange, it doesn’t even show its value in the message list, it shows the time it arrived in your mailbox instead (for example Ana’s mail I’m replying to has a timestamp of 4:06 inside, but in Outlook’s message list it says 4:09). *From:* Ana Emília M. Arruda [mailto:emiliaarr...@gmail.com] *Sent:* 12 August 2015 4:06 *To:* Michael Schwager mschwa...@mochotrading.com *Cc:* Bacula-users@lists.sourceforge.net *Subject:* Re: [Bacula-users] Bacula daemon message- where did it come from? Hello Michael, From your first post, the header of the email shows a 6:00 AM time, not the 11:00 AM. Are your sure they are the same e-mails? Is there any other e-mail in bac...@example.com mailbox that arrived at 11:00 AM? -- Forwarded message -- From: *Bacula* backup@ example .com Date: Sun, Aug 9, 2015 at 6:00 AM Subject: Bacula daemon message To: it@ example.com Best regards, Ana Looking carefully your first post, the e-mail sent with the authentication error took place at 6 am and not 11 am. This log register do not seems to be the log for your error message. Instead it seems to be an e-mail sent by bacula after restarting. Em ter, 11 de ago de 2015 às 15:21, Michael Schwager mschwa...@mochotrading.com escreveu: On Tue, Aug 11, 2015 at 8:49 AM, Martin Simmons mar...@lispworks.com wrote: Looks like a bug to me (I've just created http://bugs.bacula.org/view.php?id=2159). Thanks. I have contributed to your bug report. *- Mike Schwager* * (aka, The **Most Greyish of Gnomes)*** * Linux Network Engineer, Mocho Trading LLC* * 312-646-4783 312-646-4783 Phone312-637-0011 312-637-0011 Cell312-957-9804 312-957-9804 Fax* 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 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula daemon message- where did it come from?
Hello Luc, Thank you for the explanation. BTW I had being thinking if this was not due because of a timezone mismatch configuration in the mail server/relay (supposing the datetime was filled by the SMTP server and not client). I'm still believing in a system mail problem instead of a bacula issue, since as far as I know bacula do not store theses messages for later delivering (acting as a mail relay in this case). I agree with Ana with the fact it is probably not a bug. Even in the hypothesis Bacula is sending delayed messages this is the reason there is a time stamp on each log message. Yes: the connection error happened. Yes: daemon messages can be annoying and sometime lead incautious users to confusion if they only receive the message after the error is solved. But you can always opt out this messages or don't send them to the boss. =) Regards, === Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified Administrator II Do you need Bacula training? https://www.udemy.com/bacula-backup-software/?couponCode=bacula-list I do Bacula training and deploy in any city of the world. More information: http://bacula.us/ +55 61 8268-4220 Site: http://bacula.us FB: heitor.faria === Best regards, Ana Em qua, 12 de ago de 2015 às 03:41, Luc Van der Veken luc...@wimionline.com escreveu: Hi all, If I didn’t misunderstand anything, Michael said he checked the Received headers as well. Those indicate at what time the message arrived at different mail servers along its path, I assume they show that bsmtp passed it to the local outgoing mail server at 11:00 ? BTW, I would never trust the ‘Date’ header. Some mail programs fill it in when you compose the mail, some when you actually send it (it could sit in your outbox for a while), and some don’t include it at all and rely on the mail server to add it. And to make things worse, if you use MS Outlook on Exchange, it doesn’t even show its value in the message list, it shows the time it arrived in your mailbox instead (for example Ana’s mail I’m replying to has a timestamp of 4:06 inside, but in Outlook’s message list it says 4:09). From: Ana Emília M. Arruda [mailto: emiliaarr...@gmail.com ] Sent: 12 August 2015 4:06 To: Michael Schwager mschwa...@mochotrading.com Cc: Bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Bacula daemon message- where did it come from? Hello Michael, From your first post, the header of the email shows a 6:00 AM time, not the 11:00 AM. Are your sure they are the same e-mails? Is there any other e-mail in bac...@example.com mailbox that arrived at 11:00 AM? -- Forwarded message -- From: Bacula backup@ example .com Date: Sun, Aug 9, 2015 at 6:00 AM Subject: Bacula daemon message To: it@ example.com Best regards, Ana Looking carefully your first post, the e-mail sent with the authentication error took place at 6 am and not 11 am. This log register do not seems to be the log for your error message. Instead it seems to be an e-mail sent by bacula after restarting. Em ter, 11 de ago de 2015 às 15:21, Michael Schwager mschwa...@mochotrading.com escreveu: On Tue, Aug 11, 2015 at 8:49 AM, Martin Simmons mar...@lispworks.com wrote: Looks like a bug to me (I've just created http://bugs.bacula.org/view.php?id=2159 ). Thanks. I have contributed to your bug report. - Mike Schwager (aka, The Most Greyish of Gnomes) Linux Network Engineer, Mocho Trading LLC 312-646-4783 Phone 312-637-0011 Cell 312-957-9804 Fax 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 -- ___ Bacula-users mailing list Bacula-users
Re: [Bacula-users] Bacula daemon message- where did it come from?
Hello Michael, From your first post, the header of the email shows a 6:00 AM time, not the 11:00 AM. Are your sure they are the same e-mails? Is there any other e-mail in bac...@example.com mailbox that arrived at 11:00 AM? -- Forwarded message -- From: Bacula backup@ example .com Date: Sun, Aug 9, 2015 at 6:00 AM Subject: Bacula daemon message To: it@ example.com Best regards, Ana Looking carefully your first post, the e-mail sent with the authentication error took place at 6 am and not 11 am. This log register do not seems to be the log for your error message. Instead it seems to be an e-mail sent by bacula after restarting. Em ter, 11 de ago de 2015 às 15:21, Michael Schwager mschwa...@mochotrading.com escreveu: On Tue, Aug 11, 2015 at 8:49 AM, Martin Simmons mar...@lispworks.com wrote: Looks like a bug to me (I've just created http://bugs.bacula.org/view.php?id=2159). Thanks. I have contributed to your bug report. *- Mike Schwager (aka, The Most Greyish of Gnomes)* * Linux Network Engineer, Mocho Trading LLC* * 312-646-4783 312-646-4783 Phone312-637-0011 312-637-0011 Cell312-957-9804 312-957-9804 Fax* 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 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula daemon message- where did it come from?
hi,
check the mail-headers ('received-from' etc.) to find out
which servers were involved.
Michael Schwager schrieb:
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 Phone312-637-0011 Cell312-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#SECTION0026
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#SECTION0026
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#SECTION0026
for help.
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Mit besten Grüßen / Kind Regards
Andreas Nastke
IT System Management
g/d/p Markt- und Sozialforschung GmbH
Ein Unternehmen der Forschungsgruppe g/d/p
Richardstr. 18
D-22081 Hamburg
Fon: +49 (0)40 / 29876-117
Fax: +49 (0)40 / 29876-127
nas...@gdp-group.com
www.gdp-group.com
Sitz der Gesellschaft ist Hamburg, Handelsregister Hamburg, HRB 40482
Geschäftsführer: Christa Braaß, Volker Rohweder
---
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient please notify the sender and delete
this e-mail from your whole system. Any unauthorised copying, disclosure
or distribution of the material in this e-mail is strictly forbidden.
---
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula daemon message- where did it come from?
On Mon, 10 Aug 2015 09:01:43 -0500, Michael Schwager said: 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 Looks like a bug to me (I've just created http://bugs.bacula.org/view.php?id=2159). __Martin -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula daemon message- where did it come from?
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 $@ 21 | 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
CRLF.CRLF
Aug 9 11:00:01 ch0-backup-01 logger: bsmtp: bsmtp.c:130-0 mailhub -- 354
End data with CRLF.CRLF
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 + (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 Phone312-637-0011 Cell312-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 Phone312-637-0011 312-637-0011
Cell312-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
Re: [Bacula-users] Bacula daemon message- where did it come from?
On Tue, Aug 11, 2015 at 8:49 AM, Martin Simmons mar...@lispworks.com wrote: Looks like a bug to me (I've just created http://bugs.bacula.org/view.php?id=2159). Thanks. I have contributed to your bug report. *- Mike Schwager (aka, The Most Greyish of Gnomes)* * Linux Network Engineer, Mocho Trading LLC* * 312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax* -- 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
Re: [Bacula-users] Bacula daemon message- where did it come from?
On Tue, Aug 11, 2015 at 1:21 AM, Andreas Nastke nas...@gdp-group.com
wrote:
check the mail-headers ('received-from' etc.) to find out
which servers were involved.
I did that, but in any event my own logging (see my reply to Ana on this
thread) shows that Bacula certainly sent a message, and it was at that time.
*- Mike Schwager*
* Linux Network Engineer, Mocho Trading LLC*
* 312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax*
--
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
Re: [Bacula-users] Bacula daemon message- where did it come from?
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 Phone312-637-0011 312-637-0011 Cell312-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#SECTION0026 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#SECTION0026 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#SECTION0026 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 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
