Hello,
On 02/24/2016 05:50 PM, Heitor Faria wrote:
> *Minor correction:
>
> cat /usr/sbin/baculejo
> =>8 Cut Here >8===
> DIR_NAME=hfaria-K46CB-dir
> DIR_ADDRESS=localhost
>
> echo " Director {
> Name = $DIR_NAME
> DIRport = 9101
> Address = $DI
On 02/24/2016 04:41 PM, Heitor Faria wrote:
>
>> Hello,
>>
>> Does bacula have any feature where, depending upon the UID of the unix user
>> executing the bconsole program, one can choose different restrictions for
>> the console and this would all be specified in one config file?
>
> Hello, Pete
Hello,
Does bacula have any feature where, depending upon the UID of the unix user
executing the bconsole program, one can choose different restrictions for
the console and this would all be specified in one config file?
Thank you!
-pete
-
On 02/18/2016 11:15 PM, Kern Sibbald wrote:
> I rewrote large parts of fstype.c (not all) in Branch-7.4, so I recommend that
> you start by upgrading to 7.4.0. If the problem still persists, which should
> not happen, or another one shows up, please report it.
7.4.0 fixed the problem!
Thank you!
Hello,
On 02/18/2016 08:13 PM, Kern Sibbald wrote:
> At some point, I rewrote a good part of fstype, because one of the previous
> authors wrote code that had more than the average number of bugs that we see
> in
> Bacula.
>
> However, I do not remember rewriting that code, and from what I see f
Hello,
I read the 7.2.0 codes and changed my fstype in the Options to just
be the ones that are actually supported and that I use.
However, it still faulted.
I tracked down the segfault to this line (bacula 7.2.0) fstype.c:271:
bstrncpy(ff_pkt->last_fstypename, fstype, sizeof(ff_pkt->last_fstyp
Hello,
I have some additional knowledge.
I thought maybe the problem was that onefs should be in the "default"
options block.
But if I change the fileset to this, the client segfaults when running
the estimate command on it:
FileSet {
Name = "Machine Heavy-Weight NO RDBMS"
Include {
Hello,
I'm using bacula 7.2.0 and I have a fileset that looks like this:
FileSet {
Name = "Machine Heavy-Weight NO RDBMS"
Include {
Options {
# DANGER: This will allow this FileSet to cross file system
# boundaries.
onefs = no
fstyp
On 01/29/2016 01:56 AM, Eric Bollengier wrote:
> Hello Peter,
>
> On 01/28/2016 10:09 PM, Peter Keller wrote:
>>
>> In bacula 7.2.0, in the Options block in a FileSet, if I specify something
>> like
>> accurate=s5, in what order is it tested? I ask because I&#
Hello,
In bacula 7.2.0, in the Options block in a FileSet, if I specify something like
accurate=s5, in what order is it tested? I ask because I'd prefer the order of
check size first, then md5 sum--from the cheapest check to most expensive
check. The manual doesn't say (or I couldn't find it).
Th
On 01/18/2016 11:29 AM, Peter Keller wrote:
> Hello!
>
> On 12/29/2015 03:12 AM, Kern Sibbald wrote:
>> The only current possibility is to not permit the help command. Making the
>> help
>> command recognized which commands are permitted would be a significant
Hello!
On 12/29/2015 03:12 AM, Kern Sibbald wrote:
> The only current possibility is to not permit the help command. Making the
> help
> command recognized which commands are permitted would be a significant project
> which is not currently on our task list. However, it would be nice if someone
On 01/04/2016 07:26 PM, Daniel Bareiro wrote:
> On 04/01/16 13:19, Peter Keller wrote:
>> since they were missing the LSB stuff and the creation of the pidfile
>> directory
>> and subsys directory. I found that they would work when tested by hand, but
>> not
>>
On 01/04/2016 10:19 AM, Peter Keller wrote:
> And, for me, it was postgres
I meant it was just postgresql, as in I believe you choose one or the other for
bacula.
> I believe /etc/init.d/bacula-dir is the script you are running, so:
>
> # sh -x /etc/init.d/bacula-dir
This shou
On 01/04/2016 09:00 AM, pietersnld wrote:
> Found the same in the source code (7.2)
>
> /*
> * Given a Unix date return the week of the year.
> * The returned value can be 0-53. Officially
> * the weeks are numbered from 1 to 53 where week1
> * is the week in which the first Thursday of the
On 01/04/2016 09:45 AM, Daniel Bareiro wrote:
> I think LSB lines are correct:
>
>
> ### BEGIN INIT INFO
> # Provides: bacula-dir
> # Required-Start:$network
> # Should-Start: bacula-fd postgresql mysql
Shouldn't
Hello,
On 01/04/2016 05:49 AM, Daniel Bareiro wrote:
> Hi all and Happy New Year!!
[snip]
>> Dec 26 11:31:04 baculatest bacula-dir[3045]: Starting Bacula Director:
>> bacula-dir
>> --
>>
>> But I do not see the running processes:
On 12/29/2015 03:12 AM, Kern Sibbald wrote:
> Hello,
>
> The only current possibility is to not permit the help command. Making the
> help
> command recognized which commands are permitted would be a significant project
> which is not currently on our task list. However, it would be nice if some
Hello,
I notice in Bacula 7.2.0 that when I set up a restricted console, the help
command still gives me all commands, including the invalid ones. Is there
a way to configure bacula such that, in the context of a restricted console,
'help' will only tell me commands that I'm allowed to invoke? Or,
Hello,
I'd like to implement Copy Jobs for offsite backups and would like to know
if there is any particularly good wisdom about doing so and also in the
context of Volume sizes. I'm also interested in bandwidth limiting for said
Copy Jobs, which I see Bacula can do. Has that worked well in practi
On 12/26/2015 10:21 AM, Kern Sibbald wrote:
> Hello Peter,
>
> One more question: Is the client for which this Catalog error is
> occurring a Windows machine?
Nope, it is an x86_64 Linux Debian 8.0 box, technically a DomU on a Xen
Linux Debian Dom0 machine.
Thank you!
-pete
-
Hello,
On 12/25/2015 02:01 AM, Kern Sibbald wrote:
> On 12/25/2015 08:11 AM, Kern Sibbald wrote:
>> On 12/25/2015 01:33 AM, Peter Keller wrote:
>>>> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
>>>> digest. bdb.h:101 Update failed: af
Hello,
> 23-Dec 18:47 DIR:xxx.yyy.zzz JobId 4: Error: Catalog error updating file
> digest. bdb.h:101 Update failed: affected_rows=0 for UPDATE File SET
> MD5='oGhRwHZ+y+mWb+fv9ppFrA' WHERE FileId=6148914691236517205
Also, I just noticed, 6148914691236517205 is 0x in Hex, which
is
On 12/24/2015 02:16 PM, Kern Sibbald wrote:
> Well, 4GB Volume size seems very small to me. I would start with
> something like 50GB and possibly make them bigger if there are more than
> a few thousand Volumes.
The manual is sometimes ambiguous about things like a good Volume size.
I chose 4GB b
Hello,
I'm a new user who has just set up bacula on a couple of
machines. During my initial tests, things were working fine, but
when I went into production I started seeing these errors. These
errors only appear to happen when a backup is big enough to cross
volume size boundaries. (I keep my vol
25 matches
Mail list logo
