Re: Amanda Client
On Monday 23 April 2007, James Wilson wrote:
>Are you talking about the /etc/xinetd.d/amanda file? in my case it is
>amandabackup.
>
That is not the usual name for that file. What distro are you running?
OTOH, the actual name of that file isn't terribly important, but the contents
are, and should generally resemble this, although the server locations could
change depending on your packaging system, and of course the FQDN too:
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons & such it needs
service amanda
{
only_from = coyote.coyote.den
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
}
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
===
which will result in those 3 'service's being registered with xinetd for ready
availability in the event they are called upon. As far as xinetd is
concerned there is zero difference in how it works if the file was broken up
into 3 pieces at the service keyword, and named jimbo, bubba and teri-sue, or
this all in one file was named after a BC comic strip character. Its what is
in the file(s) that that count. :-)
>Pavel Pragin wrote:
>> James Wilson wrote:
>>> Hey All,
>>>
>>>I have amanda version 2.5.0p2 I have installed version 2.5.0p2-4
>>> for the amanda client. I have added the amanda server and the amanda
>>> user in the .amandahost file on the client I checked the
>>> /etc/services and all the amanda ports are there. But when I try to
>>> do an amcheck tape this is what I get. It's been awhile since I have
>>> added a client, am I missing something?
>>>
>>> WARNING: ifx-se-02.transolutions.net: selfcheck request failed:
>>> timeout waiting for ACK
>>> Client check: 1 host checked in 30.036 seconds, 1 problem found
>>
>> Hello,
>> It sound like you are trying to use "bsd" authentication to connect to
>> a client that is using "bsdtcp". You either need to upgrade to the
>> 2.5.1 server or change the client to run "bsd". These changes need to
>> be made in the xientd service for amanda.
>> Thank You
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Dirksen's Three Laws of Politics:
(1) Get elected.
(2) Get re-elected.
(3) Don't get mad, get even.
-- Sen. Everett Dirksen
dead processes
Hi all, I am running Amanda for a linux network backup. The server is a Fedora Core 3 box with : amanda-2.4.4p3-1 amanda-client-2.4.4p3-1 amanda-server-2.4.4p3-1 The client is a Centos 4.3 box with : amanda-client-2.4.4p3-1 I occasionally get failures to backup this client (it is the big one with a large list of DLEs). The errors are always time-outs during estimates. Like this: gilmore/backedup/home lev 0 FAILED [Estimate timeout from gilmore] gilmore/backedup/project lev 0 FAILED [Estimate timeout from gilmore] ... It seems like this happens about 1 out of every 5 runs... so far I've just learned to skip a day and hope nothing bad happens that day - not very good. My assumption was that I should upgrade to 2.5.x as then I can use the lighter, less accurate estimate methods rather than the default estimate method. However, this weekend I had a fail with a data timeout: gilmore/nonbackedup/work3/backups/glen lev 0 FAILED [data timeout] Now whenever I do a amcheck I get: WARNING: gilmore: selfcheck reply timed out. Meanwhile, on the client gilmore if I check all the amanda processes I get: [EMAIL PROTECTED] amanda]# ps aux | grep amanda amanda 11570 0.0 0.0 3104 884 ?DApr20 0:00 /usr/lib/amanda/sendbackup amanda 12910 0.0 0.0 3944 796 ?DApr20 0:00 /usr/lib/amanda/selfcheck amanda8768 0.0 0.0 2400 796 ?D11:48 0:00 /usr/lib/amanda/selfcheck amanda9104 0.0 0.0 2888 888 ?Ss 13:36 0:00 amandad amanda9105 0.0 0.0 3432 792 ?D13:36 0:00 /usr/lib/amanda/selfcheck amanda9106 0.0 0.0 00 ?Z13:36 0:00 [amandad] Note the "selfchecks" that are running with "D" process state - meaning they are sleeping in the kernel and are uninterruptible and therefore unkillable. So - it looks like I need to reboot my client before I can get a backup from it again, which is a little harsh. I was wondering whether anyone knows why Amanda client 2.4.4 would get wedged like that, is there something I can do to minimize the problem? Also, if anyone has ideas about avoiding the estimate issues all together, I would appreciate any advice. Don
Re: "STRANGE" dump summaries
On Mon, Apr 23, 2007 at 01:25:21PM -0400, Guy Dallaire wrote:
> If I remember well, You have to edit the source code and have amanda
> consider it "normal".
>
> Can't recall where exactly in the source code, but there is a list of
> keywords that amanda is loomnking for in the tar output, that you can edit.
>
> That's the beauty of open source, you can modify the code to suit your
> needs.
>
I've not looked at 2.5 code, but in earlier versions it was near the
beginning of "client-src/sendbackup-gnutar.c" (about line 50).
Lines of the form:
AM_NORMAL_RE(""),
can be added to the table. would be replaced with an appropriate
Regular Expression specifying the message to consider "normal". That is
a comma at the end of the macro.
>
> 2007/4/23, Lee, Raymond <[EMAIL PROTECTED]>:
> >
> >Hi,
> >
> >I'm running Amanda 2.5.1p3 with tar 1.16. As I understand, 2.5.1p3
> >ignores tar 1.16's return code of 1 when it encounters "file changed as
> >we read it". I verified that my files are still backed up even when
> >this happens. However, is it possible to get Amanda to stop reporting
> >this as "STRANGE" in the amdump mail reports?
> >
> >Thanks,
> >Ray
> >
> >
> >This communication is the property of Qwest and may contain confidential
> >or
> >privileged information. Unauthorized use of this communication is strictly
> >prohibited and may be unlawful. If you have received this communication
> >in error, please immediately notify the sender by reply e-mail and destroy
> >all copies of the communication and any attachments.
> >
> >
>>> End of included message <<<
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda Client
James Wilson wrote: Hey All, I have amanda version 2.5.0p2 I have installed version 2.5.0p2-4 for the amanda client. I have added the amanda server and the amanda user in the .amandahost file on the client I checked the /etc/services and all the amanda ports are there. But when I try to do an amcheck tape this is what I get. It's been awhile since I have added a client, am I missing something? WARNING: ifx-se-02.transolutions.net: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.036 seconds, 1 problem found Hello, It sound like you are trying to use "bsd" authentication to connect to a client that is using "bsdtcp". You either need to upgrade to the 2.5.1 server or change the client to run "bsd". These changes need to be made in the xientd service for amanda. Thank You
Re: Amanda Client
James Wilson wrote: Are you talking about the /etc/xinetd.d/amanda file? in my case it is amandabackup. Pavel Pragin wrote: James Wilson wrote: Hey All, I have amanda version 2.5.0p2 I have installed version 2.5.0p2-4 for the amanda client. I have added the amanda server and the amanda user in the .amandahost file on the client I checked the /etc/services and all the amanda ports are there. But when I try to do an amcheck tape this is what I get. It's been awhile since I have added a client, am I missing something? WARNING: ifx-se-02.transolutions.net: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.036 seconds, 1 problem found Hello, It sound like you are trying to use "bsd" authentication to connect to a client that is using "bsdtcp". You either need to upgrade to the 2.5.1 server or change the client to run "bsd". These changes need to be made in the xientd service for amanda. Thank You Hello, I think I made a mistake in my last post. I thought you were using 2.5.0 server and 2.5.1 client, but you are not, so I dont think bsd and bsdtcp conflict is the problem. Please post the contents of /etc/xientd.d/amandabackup on the client. Also run "netstat -a | grep amanda" on the client and post the output. Thank You
Re: Amanda Client
Are you talking about the /etc/xinetd.d/amanda file? in my case it is amandabackup. Pavel Pragin wrote: James Wilson wrote: Hey All, I have amanda version 2.5.0p2 I have installed version 2.5.0p2-4 for the amanda client. I have added the amanda server and the amanda user in the .amandahost file on the client I checked the /etc/services and all the amanda ports are there. But when I try to do an amcheck tape this is what I get. It's been awhile since I have added a client, am I missing something? WARNING: ifx-se-02.transolutions.net: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.036 seconds, 1 problem found Hello, It sound like you are trying to use "bsd" authentication to connect to a client that is using "bsdtcp". You either need to upgrade to the 2.5.1 server or change the client to run "bsd". These changes need to be made in the xientd service for amanda. Thank You
Amanda Client
Hey All, I have amanda version 2.5.0p2 I have installed version 2.5.0p2-4 for the amanda client. I have added the amanda server and the amanda user in the .amandahost file on the client I checked the /etc/services and all the amanda ports are there. But when I try to do an amcheck tape this is what I get. It's been awhile since I have added a client, am I missing something? WARNING: ifx-se-02.transolutions.net: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.036 seconds, 1 problem found
Re: "STRANGE" dump summaries
If I remember well, You have to edit the source code and have amanda consider it "normal". Can't recall where exactly in the source code, but there is a list of keywords that amanda is loomnking for in the tar output, that you can edit. That's the beauty of open source, you can modify the code to suit your needs. I myself modified amanda reporting so the the day (mon, tue, wed) is written on my tape labels so they are easier to manage/sort in the vault. 2007/4/23, Lee, Raymond <[EMAIL PROTECTED]>: Hi, I'm running Amanda 2.5.1p3 with tar 1.16. As I understand, 2.5.1p3 ignores tar 1.16's return code of 1 when it encounters "file changed as we read it". I verified that my files are still backed up even when this happens. However, is it possible to get Amanda to stop reporting this as "STRANGE" in the amdump mail reports? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
"STRANGE" dump summaries
Hi, I'm running Amanda 2.5.1p3 with tar 1.16. As I understand, 2.5.1p3 ignores tar 1.16's return code of 1 when it encounters "file changed as we read it". I verified that my files are still backed up even when this happens. However, is it possible to get Amanda to stop reporting this as "STRANGE" in the amdump mail reports? Thanks, Ray This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
