Someone have deleted the PTR record of this server. Now i have added it, and
amanda works perfectly.
I thought that was a dns problem, but i was convinced that amanda uses only
forward lookup zone.
Thanks to all for help.
Giovanni
p.s. Sorry again for bad english.
Le samedi 02 juillet 2005 à 13:31 -0400, Jon LaBadie a écrit :
On Sat, Jul 02, 2005 at 06:17:11PM +0200, Eric DOUTRELEAU wrote:
Hi
with changing index to index yes it didn't solved my problem.
and the output if the commands give me the same output.
the only thing that i can see
On Tuesday 05 July 2005 05:15, Eric Doutreleau wrote:
[...]
On Fri, Jul 01, 2005 at 05:36:18PM +0200, ERic Doutreleau
wrote:
Indeed i have index yes for almost type except some that are
realted to my problems.
i will test that that night
thanks for your answer
Hello
I can confirm this problem. It looks like a bug with 2.95.4
gcc --version
2.95.4
System: 4.10-RELEASE-p3
I've installed gcc 3.4 and recompiled amanda 2.4.5 with it. It works
now. Amanda 2.4.5 works with FreebSD 5.4 so I chose gcc 3.4. Perhaps it
works with other 3.x gcc too
Regards,
I've just added exclude lists as per the examples in the online
documentation, with the following configuration:
exclude list optional .amanda.excludes
However, amcheck now complains on every item in the disklist for a
*single* host, that it [Can't open exclude file '/filepath' :
Permission
Here's another little oddity I've been noticing: when using the
chg-zd-mtx changer script, even though I've set autoclean to 0 and
cleanslot to 7, when I do an amtape update it *always* loads and runs
the cleaning tape, and does a cleaning cycle. This, in turn, screws up
the update.
Is this
Graeme Humphries wrote:
I've just added exclude lists as per the examples in the online
documentation, with the following configuration:
exclude list optional .amanda.excludes
However, amcheck now complains on every item in the disklist for a
*single* host, that it [Can't open exclude file
--On Tuesday, July 05, 2005 09:51:36 -0600 Graeme Humphries [EMAIL PROTECTED]
wrote:
I've just added exclude lists as per the examples in the online
documentation, with the following configuration:
exclude list optional .amanda.excludes
However, amcheck now complains on every item in the
On Tue, 2005-07-05 at 11:41 -0500, Frank Smith wrote:
amcheck runs as your Amanda user and may not have permissions to the
directory where your exclude file lives.
I *thought* I had amanda running as root on the client, but I may be
wrong. It doesn't complain that it can't access any of those
On Tue, 2005-07-05 at 18:07 +0200, Stefan G. Weichinger wrote:
As you have read the docs, this file should be specified relative to the
DLE on the client.
Yep. I want it to, like shown in the docs, just look for
a .amanda.excludes file in the root of every share I'm backing up.
I'd suggest
On Tue, 2005-07-05 at 12:55 -0400, Jon LaBadie wrote:
Do your slot numbers, first slot to last slot include the
slot with the cleaning tape?
Yeah, I had a typo in my changer config file that was breaking this.
Once I fixed that, it worked fine. :P
If like my DDS3 changer, amanda may not be
On Tue, Jul 05, 2005 at 09:56:52AM -0600, Graeme Humphries wrote:
Here's another little oddity I've been noticing: when using the
chg-zd-mtx changer script, even though I've set autoclean to 0 and
cleanslot to 7, when I do an amtape update it *always* loads and runs
the cleaning tape, and does
--On Tuesday, July 05, 2005 10:47:59 -0600 Graeme Humphries [EMAIL PROTECTED]
wrote:
On Tue, 2005-07-05 at 11:41 -0500, Frank Smith wrote:
amcheck runs as your Amanda user and may not have permissions to the
directory where your exclude file lives.
I *thought* I had amanda running as root
On Tue, 2005-07-05 at 12:07 -0500, Frank Smith wrote:
You really shouldn't be running Amanda as root, but as a separate
user. When you run 'make install' as root it installs the executables
that need root access suid root. Then when your backups run it can
access everything necessary.
I've
below is the error message from the amdump.X. My OS is solaris 8. thanks
for your help.
m5413.drsite.univision.com $ cat amdump.1
amdump: start at Tue Jul 5 13:21:10 EDT 2005
amdump: datestamp 20050705
planner: pid 5866 executable /usr/local/libexec/planner version 2.4.4p4
planner: build
khalid maqsudi wrote:
below is the error message from the amdump.X. My OS is solaris 8. thanks
for your help.
[...]
changer: opening pipe to: /usr/local/libexec/chg-zd-mtx -info
changer: got exit: 2 str: none cannot determine first slot
taper: could not get changer info: cannot determine
On Tue, Jul 05, 2005 at 11:19:09AM -0600, Graeme Humphries wrote:
In my experience the error occurs if Amanda can't access the directory
to see if the file is there. Perhaps the docs need to be rephrased.
I'd rather just have any permission related error ignored if the
optional keyword
On Tue, 2005-07-05 at 16:50 -0500, Frank Smith wrote:
You can do what I do, just ignore the errors from amcheck that you
know are bogus.
That's probably what I'll end up doing, but I know that for me it's
generally bad practice, because it means that eventually I'll just stop
paying attention
Title: Re: exclude list optional not working?
On Tue, 2005-07-05 at 23:14 +0200, Paul Bijnens wrote:
- or if the file is not readable: in that case amanda trusts the
suid-root runtar executable so that gnutar can read the contents of
the file, never mind the permissions.
But Amanda does
Title: Re: exclude list optional not working?
On Tue, 2005-07-05 at 15:34 -0400, Jon LaBadie wrote:
If there were no exclude file, then the admin can reasonably
feel that it is not contributing to the list of excluded file.
Thus no error on setting optional is reasonable.
But what about
Graeme Humphries wrote:
I'd rather just have any permission related error ignored if the
optional keyword is used. Is there a situation where we *would* want it
to hard error out on an optional exclude list if it can't get into the
directory the exclude list is supposed to be in?
Amanda will
On Tuesday 05 July 2005 12:47, Graeme Humphries wrote:
On Tue, 2005-07-05 at 11:41 -0500, Frank Smith wrote:
amcheck runs as your Amanda user and may not have permissions to
the directory where your exclude file lives.
I *thought* I had amanda running as root on the client, but I may be
wrong.
On Tuesday 05 July 2005 13:19, Graeme Humphries wrote:
On Tue, 2005-07-05 at 12:07 -0500, Frank Smith wrote:
You really shouldn't be running Amanda as root, but as a separate
user. When you run 'make install' as root it installs the
executables that need root access suid root. Then when your
On Tuesday 05 July 2005 12:55, Jon LaBadie wrote:
On Tue, Jul 05, 2005 at 09:56:52AM -0600, Graeme Humphries wrote:
Here's another little oddity I've been noticing: when using the
chg-zd-mtx changer script, even though I've set autoclean to 0 and
cleanslot to 7, when I do an amtape update it
--On Tuesday, July 05, 2005 15:20:15 -0600 Graeme Humphries [EMAIL PROTECTED]
wrote:
On Tue, 2005-07-05 at 23:14 +0200, Paul Bijnens wrote:
- or if the file is not readable: in that case amanda trusts the
suid-root runtar executable so that gnutar can read the contents of
the file,
25 matches
Mail list logo
