On 05/25/2012 01:01 AM, Toomas Aas wrote:
Hello!
While exploring the recent GNU tar --one-file-system flag seems to
have no effect issue, I forced some DLEs with 'amadmin force'. My
understanding of 'force' has been that it forces the DLE to do a full
backup on next run, and then returns to
Hello Jean-Louis!
What are the first two lines of their info file,
.../curinfo/kuller.raad.tartu.ee/_storage/info
.../curinfo/kuller.raad.tartu.ee/_storage_lists/info
A command of 0 means there is no force command.
Both files begin with these two lines:
version: 0
command: 0
So it
On 05/25/2012 08:27 AM, Toomas Aas wrote:
Hello Jean-Louis!
What are the first two lines of their info file,
.../curinfo/kuller.raad.tartu.ee/_storage/info
.../curinfo/kuller.raad.tartu.ee/_storage_lists/info
A command of 0 means there is no force command.
Both files begin with these two
On Fri, 25 May 2012 10:13:16 -0600
Charles Curley charlescur...@charlescurley.com wrote:
A program must be root to bind to any port between 1 and 1023
(inclusive).
I use:
backup@dzur:~$ amgetconf DailySet1 unreserved-tcp-port
5,50100
backup@dzur:~$
Open mouth, insert foot. Just
On 05/25/2012 11:39 AM, Brian Cuttler wrote:
New installation
Amanda 3.3.0 installed on openSUSE 12.1 (Asparagus) (x86_64)
kaveri:/etc/amanda/kaveri # amgetconf kaveri unreserved-tcp-port
1025,65535
How about reserved-tcp-port?
However the
Charles,
Jean-Louis,
I did include the amgetconf reserved-tcp-port info in my email,
I get the same results you do.
I am logged in as root when running amcheck.
I was afraid that was an IPv6 error, was running it out of the
box and didn't expect it to be turned on.
How do I turn off IPv6?
On 05/25/2012 02:02 PM, Brian Cuttler wrote:
On Fri, May 25, 2012 at 01:06:45PM -0400, Brian Cuttler wrote:
Charles,
Jean-Louis,
I did include the amgetconf reserved-tcp-port info in my email,
I get the same results you do.
I am logged in as root when running amcheck.
I was afraid that was
On Friday, May 25, 2012 02:24:39 PM Brian Cuttler did opine:
Charles,
Jean-Louis,
I did include the amgetconf reserved-tcp-port info in my email,
I get the same results you do.
I am logged in as root when running amcheck.
You should not be able to do that Brian. Yes, I have to be root,
On Fri, May 25, 2012 at 01:06:45PM -0400, Brian Cuttler wrote:
Charles,
Jean-Louis,
I did include the amgetconf reserved-tcp-port info in my email,
I get the same results you do.
I am logged in as root when running amcheck.
I was afraid that was an IPv6 error, was running it out of
Thank you - Amcheck running now, client==server.
Will test and then add other clients.
thank you - Brian
On Fri, May 25, 2012 at 02:07:49PM -0400, Jean-Louis Martineau wrote:
On 05/25/2012 02:02 PM, Brian Cuttler wrote:
On Fri, May 25, 2012 at 01:06:45PM -0400, Brian Cuttler wrote:
On Fri, 25 May 2012 14:07:49 -0400
Jean-Louis Martineau martin...@zmanda.com wrote:
disable = no
server_args = -auth=bsdudp amdump
}
This is a config for bsdudp auth.
Either fix xinetd for bsdtcp or use bsdudp.
But you are using bsdtcp
Either
On Fri, 25 May 2012 14:07:49 -0400
Jean-Louis Martineau martin...@zmanda.com wrote:
disable = no
server_args = -auth=bsdudp amdump
}
This is a config for bsdudp auth.
Either fix xinetd for bsdtcp or use bsdudp.
But you are using bsdtcp
Either
On Fri, May 25, 2012 at 02:28:06PM -0400, gene heskett wrote:
On Friday, May 25, 2012 02:24:39 PM Brian Cuttler did opine:
Charles,
Jean-Louis,
I did include the amgetconf reserved-tcp-port info in my email,
I get the same results you do.
I am logged in as root when running
On Friday, May 25, 2012 02:51:32 PM Brian Cuttler did opine:
On Fri, May 25, 2012 at 02:28:06PM -0400, gene heskett wrote:
On Friday, May 25, 2012 02:24:39 PM Brian Cuttler did opine:
Charles,
Jean-Louis,
I did include the amgetconf reserved-tcp-port info in my email,
I get the
On Friday, May 25, 2012 06:21:41 PM Charles Curley did opine:
On Fri, 25 May 2012 14:07:49 -0400
Jean-Louis Martineau martin...@zmanda.com wrote:
disable = no
server_args = -auth=bsdudp amdump
}
This is a config for bsdudp auth.
Either fix
I'm working on upgrading to amanda v3.3.1. I thought I had read that one
should
update the backup-server first, and then the clients at will. Perhaps I made
up the
at will bit.
The server works fine at 3.3.1
The server is also a client; so it is at v3.3.1 too and this works fine.
Other
16 matches
Mail list logo
