bacula fails to use /etc/mailname when setting the sender address in
outgoing status emails:
It seems to me that the above suggestion is system dependent. bsmtp is a
general mail sending program and attempts to use only Unix and Windows well
defined OS calls. As such I don't think the above
, at least on my machine, the man pages
say it is int, but /usr/include/sys/ioctl.h says it is unsigned long
int ...
Kern
commit 78c64f1757419550411778b75f1018727d8f4e18
Author: Kern Sibbald k...@sibbald.com
Date: Sat Dec 26 14:50:29 2009 +0100
Attempt to autoconfig ioctl_req_t
diff --git a/bacula
Thank you for the most recent information. That and what John wrote made me
realize that currently distinguish OS types, but in most of the code not
machine architecture. In your case, it is apparently a different definition
that depends on architecture.
I think this is rather easy to fix,
The documentation was not correct in that it did not take into account the
fact that volumes may be deleted from the pool. In fact, what the code
attempts to do is to create unique volume names without reusing old ones.
I have updated the manual to say:
If no variable expansion characters
Whenever Bacula marks a tape in error, it clearly prints that fact and why in
the Job Report, so it is not quite accurate to say that it is impossible to
distinguish between such a case and a case of a /real/ tape error.. Note,
more recent versions of Bacula permit logging job reports to the
This is possibly a confusion due to the Debian package name being
bacula-traymonitor, and the Bacula upstream named being bacula-tray-monitor.
The upstream code does have a bacula-tray-monitor manpage that is installed
during make install
Kern
Bacula Project Manager
--
To UNSUBSCRIBE, email
In re-reading my response to your requests, I realize that I misunderstood.
Sorry. What you are requesting is indeed possible. From the upstream point
of view, the problem I have is that although, it is a very good way of
organizing the conf files for larger organizations, it complicates the
The crash is not a bug but the only system independent way I have found to
cause Bacula to dump when there is some error. In this case, it is a user
syntax error that seems to be reasonably clear from the error messages. Once
the error messages are printed, Bacula induces a Seg Fault.
This
This is corrected in version 2.2.6 which will be released in the next few
weeks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fixed upstream.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fixed upstream in 2.2.6.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I'm not planning to implement this request since ConsoleFont is not a valid
directive for bconsole. If you don't want error messages, please use two
different
conf files.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Those messages are included so that users can detect security violations. It
is a daemon message so if you want you can direct it anywhere you want, but I
have no intention of removing it. At some time I may move them into a
security message class so that they can be bit bucketed if you are
I don't particularly like programs that include every file in a subdirectory,
so it is not likely that I'll be implementing this personally, because Bacula
already has an include method using @. However, if you really want this, I
suggest that someone submit a patch.
--
To UNSUBSCRIBE,
There is no simple solution that works in all cases that I am aware of. This
potential security problem (no worse than configuring your conf file with
world read permission) has been documented for quite a long time in the
manual.
We've added additional documentation to the scripts in
This appears to be a packaging problem because Bacula by default uses only
mail or its own bsmtp program for emailing Job reports. The only thing
necessary to have Bacula work out of the box is a valid user id and an smtp
address.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Technically you are correct if you look from the stand point of Full backups.
However, it has been called that a long time and no one really seems to be
confused. I'll accept a patch for it on the bacula-devel list, but I don't
think it is worth tweaking the files, and *all* the documentation
I agree, the PostgreSQL version of Bacula should not need SQLite3.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The Bacula console does not support ctl-z for suspending it. This is not a
bug, but a feature, and implementation of suspending is highly unlikely
unless some user contributes an appropriate patch.
If you want to submit a patch, please submit it to the bacula-devel list. If
you wish to submit
This is very likely some packaging problem somewhere because the Bacula
configure script automatically updates the make_catalog_backup script to have
the correct path to the appropriate database dump program. The full path is
not put on an environment variable, so it may seem that it is hard
Bacula by default installs a script that uses mtx. The problem for a packager
is that there is no easy way to know if the user really has an autochanger or
not. Most packages including all the rpms require mtx by default to avoid
any problem the user might have later.
--
To UNSUBSCRIBE,
There are two possible issues here. One is a packaging issue. If you package
Bacula to run as non-root, which can be done for both the Director and the
Storage daemon, then the packager must ensure that any new userid or group is
created when installing the package. For example, often the
It seems to me that there are a few issues here:
1. If you shutdown or upgrade a database while Bacula is running a Job, then
Bacula will fail. The solution is: don't do that. Bacula has no explicit
code to reconnect to a database after the database is successfully opened,
and we don't plan
I haven't read all the details of this bug report, but it seems to me that the
basic problem is that normally in major Bacula upgrade, e.g. 1.36.x - 1.38,
Bacula has new table formats. This has nothing to do with upgrading the SQL
engine, but is due to the fact that the Bacula SQL table format
I've taken another look at this bug report, and am convinced that my comment
of 9 Oct remains valid. The user did not upgrade his Storage daemon
configuration to include the new Autochanger resource, and thus Bacula fails
to function correctly.
I recommend that this bug be closed and marked as
wx-console had a number of bugs which were fixed, and unfortunately some of
those required making non-downward compatible changes, which is inevitable.
The .dir is in fact correct, but for it to work correctly, you must use the
same Director version (1.38.x) and not an older version.
You will
The Bacula manual recommends that you test your conf files with ./bacula-xx
-t ...
This will clearly indicate what is wrong and where (in 99.9% of the cases).
If you run Bacula as a daemon, due to the flexibility in Bacula error message
handling, it is very hard to get the user's attention, so
It is hard to be sure, but most likely you did not upgrade your bacula-sd.conf
file as is required for autochangers in switching from 1.38.11. As very
clearly indicated in the Release Notes and the manual, Bacula 1.38.11
requires a new Autochanger resource in order to function correctly with
This kind of problem is almost always due to the fact that Bacula was linked
against one version of mysql (e.g. 4.x) and you are using a different version
(e.g. 5.x).
I'm not a Debian user, so I cannot give the best advice, but in general,
either check what was linked in the original package
On Monday 09 October 2006 18:15, John Goerzen wrote:
On Mon, Oct 09, 2006 at 05:57:00PM +0200, Kern Sibbald wrote:
Finally, yes Bacula does use SEGFAULT to generate tracebacks when it
aborts,
because it is the only portable way of doing so (the Unix abort() is not
portable
From the statistics you show, the backup does not appear slow to me. The
reason you might think it is slow is because you are comparing apples and
oranges.
On the one hand, you measure the time to to a non-compressed tar on a local
machine sending the output down an extremely hi-speed bit
Hello,
This is indeed a problem, and not one that I consider an upstream bug. The
basic problem is that Bacula cecks if it can open the database prior to
becoming a daemon and thus prior to dropping root privilege. It is the only
way, it can properly print the message and exit.
When it
Hello,
Yes, the tcpwrappers name that the daemons look for in libwrap is not the
daemon name. This is because there can be multiple simultaneous Bacula
daemons running on the same machine. They simply use different .conf files.
The fact that you must use the daemon Name as defined in the
Hello,
This kind of problem happens frequently if the SD is not being run as root and
there are not sufficient permissions for the SD to access the script or the
directory in which the script resides. Make sure that the user (don't count
on the group as changing the group on the command line
Hello,
I have recently integrated all the man pages into the upstream Bacula source
code, and I noticed this problem and corrected it. I've also added more
substance to some of the man pages and hope to get through them all in the
next few months.
This correction will appear upstream in
Hello,
Bacula is fully multiple threaded, which means you can issue Bacula commands
at any time. Each command must complete (e.g. database listing, ...) prior
to issuing the next command, and in some cases, if you attempt to use a tape
drive to label a tape and the drive is busy, the command
Hello,
I think you have some good ideas here that a number of users would want. The
best way to get something like this implemented is to do it yourself (after
discussing it on the bacula-users list), then submit a patch against the
current CVS to the bacula-devel list.
If you wish to submit
Hello,
The programs such as btape that need a drive to work ABORT when it cannot
find/open the drive. The only portable way of ensuring the program ABORTs is
to generate a seg fault, so the behavior you have noted is a bit unusual but
normal.
I recommend closing this bug report.
--
To
Hello,
No configuration paths of any kind are programmed into the binaries. Thus
they look where you have specified on the command line for their
configuration file. If you don't specify one, they look in the current
directory, and then die if one is not found.
If you want a simple one line
Hello,
There was indeed a problem in producing the document because under certain
circumstances LaTeX does not permit includes within includes. This caused
the missing section.
This has been *long* ago corrected. If someone would like to correct this,
edit docs/manual/dirdconf.tex and
Hello,
The debug listing below confirms that the problem is coming from the
foreach... loop that is examining the Devices attached to the Autochanger.
It is impossible for the pointer to be NULL, which is apparently what is
happening, which indicates to me a g++ bug.
Could you tell me what
On Friday 25 February 2005 11:01, Samuele Giovanni Tonon wrote:
hi,
A bug request was filled against debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296648
i think that this is most a feature than a bug, however, what the user
pointed out (that MAX_SLAVE is hardcoded instead of
Hello,
Thanks for the bug report. In the future, it would be helpful to send
them to [EMAIL PROTECTED] instead of the bacula-users
list.
This is actually a bug in MySQL, or at least the version you are using
since, unless I am mistaken, the SQL standard requires table names to be
case
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285316
Docbook is no longer used for apcupsd. The directory will remain for a
few releases for historical reference. The manual has now been converted
to texinfo format, so it is found in apcupsd/doc/texi. To build it
simply cd to that directory
The problem here is that the only person who understands the po stuff
left the project. Since you do not seem to be too sure about the problem
(I think it's not necessary to make this distinction), and I don't
know anything about this stuff the best tactic is to do nothing.
Now, if someone
I may be missing something, but I don't see the need for this feature.
You can do what you want today by simply modifying apccontrol to do your
action script rather than complicating apcupsd.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
If the submitter of this bug report would like us to include his idea in
the apcupsd release, we will be glad to do so. For that to happen, we
will need a small document describing it and how to use it as well as
the full script. I'm not sure we will integrate it into the mainstream
code (I
This is a good idea. I've added it to the things to do for the next or
subsequent release.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I believe that we have given you the tools necessary to do what you want
by using apcupsd.conf directives and event scripts. This is discussed in
the release notes in a recent release -- if not the current release then
look in doc/techlogs.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
49 matches
Mail list logo
