-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig White wrote:
> On Thu, 2007-07-26 at 00:04 -0400, Ryan Novosielski wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Troy Daniels wrote:
>>> Hi,
>>>
>>> Coming at this issue with fresh eyes I noticed you seem to have replaced
>>>
On Fri, 2007-07-27 at 01:09 +0200, Arno Lehmann wrote:
> Hi,
>
> > Volume Poll Interval = 30; # hopefully 30 minutes
>
> That should be 30 seconds; simple integers are - almost always in
> Bacula - interpreted as seconds.
>
> > Close on Poll = yes;
> > Maximum Open Wait = 1080; # hopeful
Hi,
27.07.2007 00:34,, Craig White wrote::
> On Thu, 2007-07-26 at 00:04 -0400, Ryan Novosielski wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Troy Daniels wrote:
>>> Hi,
>>>
>>> Coming at this issue with fresh eyes I noticed you seem to have replaced
>>> the 'delete_catalog_ba
On Thu, 2007-07-26 at 00:04 -0400, Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Troy Daniels wrote:
> > Hi,
> >
> > Coming at this issue with fresh eyes I noticed you seem to have replaced
> > the 'delete_catalog_backup' script call in your catalog backup job wit
Hi,
26.07.2007 05:02,, Troy Daniels wrote::
> Hi,
>
> Coming at this issue with fresh eyes I noticed you seem to have replaced
> the 'delete_catalog_backup' script call in your catalog backup job with
> 'end_of_backup.sh'
>
> Unless I'm mistaken, I believe this script is run by the Director, n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Troy Daniels wrote:
> Hi,
>
> Coming at this issue with fresh eyes I noticed you seem to have replaced
> the 'delete_catalog_backup' script call in your catalog backup job with
> 'end_of_backup.sh'
>
> Unless I'm mistaken, I believe this script is
Hi,
Coming at this issue with fresh eyes I noticed you seem to have replaced
the 'delete_catalog_backup' script call in your catalog backup job with
'end_of_backup.sh'
Unless I'm mistaken, I believe this script is run by the Director, not
the storage daemon.
By default IIRC, the director runs
Hi,
26.07.2007 01:56,, Craig White wrote::
...
>> as the bacula user, with the tape drive unmounted from bacula (or the
>> SD stopped), try
>> mt -f /dev/nst0 rewind
>> and
>> ... eject
>>
>> If that works - great. If it doesn't, you should at least get an error
>> message. If it's 'permission d
Hi,
26.07.2007 00:47,, Craig White wrote::
> On Thu, 2007-07-26 at 00:11 +0200, Arno Lehmann wrote:
>> Hi,
>>
>> 25.07.2007 23:54,, Craig White wrote::
>>> the 'end_of_backup.sh' script doesn't successfully eject the tape.
>>>
>>> dmesg says:
>>> MTSETDRVBUFFER only allowed for root
>> This should
On Thu, 2007-07-26 at 00:11 +0200, Arno Lehmann wrote:
> Hi,
>
> 25.07.2007 23:54,, Craig White wrote::
> > the 'end_of_backup.sh' script doesn't successfully eject the tape.
> >
> > dmesg says:
> > MTSETDRVBUFFER only allowed for root
>
> This should not matter here.
>
> > bacula log says:
> >
Hi,
25.07.2007 23:54,, Craig White wrote::
> the 'end_of_backup.sh' script doesn't successfully eject the tape.
>
> dmesg says:
> MTSETDRVBUFFER only allowed for root
This should not matter here.
> bacula log says:
> 25-Jul 08:27 SRV1: RunAfter: /dev/tape: Permission denied
> 25-Jul 08:27 SRV1:
the 'end_of_backup.sh' script doesn't successfully eject the tape.
dmesg says:
MTSETDRVBUFFER only allowed for root
bacula log says:
25-Jul 08:27 SRV1: RunAfter: /dev/tape: Permission denied
25-Jul 08:27 SRV1: RunAfter: /dev/tape: Permission denied
# grep bacula /etc/group
disk:x:6:root,bacula
b
On Tuesday 15 November 2005 12:18, [EMAIL PROTECTED] wrote:
> El Martes, 15 de Noviembre de 2005 12:05, escribió:
> > On Tuesday 15 November 2005 12:07, [EMAIL PROTECTED] wrote:
> > > El Lunes, 14 de Noviembre de 2005 16:38, [EMAIL PROTECTED] escribió:
> > >
> > > Hi there... can anybody help me?
>
El Martes, 15 de Noviembre de 2005 12:05, escribió:
> On Tuesday 15 November 2005 12:07, [EMAIL PROTECTED] wrote:
> > El Lunes, 14 de Noviembre de 2005 16:38, [EMAIL PROTECTED] escribió:
> >
> > Hi there... can anybody help me?
>
> Either run your SD as root, or ignore the log entries ... I don't f
On Tuesday 15 November 2005 12:07, [EMAIL PROTECTED] wrote:
> El Lunes, 14 de Noviembre de 2005 16:38, [EMAIL PROTECTED] escribió:
>
> Hi there... can anybody help me?
Either run your SD as root, or ignore the log entries ... I don't find this to
be a problem.
>
> > Hi to @all.
> >
> > I
El Lunes, 14 de Noviembre de 2005 16:38, [EMAIL PROTECTED] escribió:
Hi there... can anybody help me?
> Hi to @all.
>
> I have installed bacula and running but the user and group that use with
> the director is root and I know that an security issue explain that is
> better to use ot
Hi to @all.
I have installed bacula and running but the user and group that use
with the
director is root and I know that an security issue explain that is better to
use other user (like bacula). In my debian sarge the default installation run
bacula-director as bacula user bu
Hi,
I'm running Bacula (package version 1.36.2-2sarge1) on Debian Sarge with
a 2.4.27-2-686 kernel and a SCSI DDS4 tape.
Bacula is running as user "bacula", which is member of the "tape" group.
I get the following logs in the kernel messages (dmesg's output):
st0: Block limits 1 - 16777215 bytes
18 matches
Mail list logo
