Re: amcheck asking for tape in slot 2. Only have one tape drive.
Hello, and thank you for your email. I shall be out of the office until Tuesday 4th May. Should your email require urgent attention, the please contact David Adams or email [EMAIL PROTECTED] Regards, William Hargrove
Re: Novell and Amanda
Hello, and thank you for your email. I shall be out of the office until Tuesday 4th May. Should your email require urgent attention, the please contact David Adams or email [EMAIL PROTECTED] Regards, William Hargrove
Re: Novell and Amanda
Hi, Gavin,
on Donnerstag, 29. April 2004 at 16:36 you wrote to amanda-users:
>>You backup via Samba yes - haven't personally had to do this ("If it's
>>on your Windows PC it doesn't get backed up." is my policy) so I'll let
>>someone else answer that.
GH> So the smbclient on the Linux box just gets into the windows 2000 server shares
etc.?
Look up docs/SAMBA.
Note that there are several restrictions in using smbclient so far.
Don't expect bare-metal-recovery-style ...
It is sufficient for backing up data-shares right now.
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
Re: amcheck asking for tape in slot 2. Only have one tape drive.
Hi, Sören Edzen, on Donnerstag, 29. April 2004 at 12:41 you wrote to amanda-users: SE> The only thing I have in my amanda.conf that mentions changer is SE> 'tpchanger'. Could it be that? I think so. If you don't have a changer (even a human one) comment that out. >From example/amanda.conf: > if you decide not to use a tape changer, you may > comment them all out. So : # tpchanger .. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: crossed signals ???
On Thursday 29 April 2004 14:30, Michael D Schleif wrote: >Can somebody please explain these errors: > >[compress got signal 11, /usr/bin/smbclient got signal 13] > >[compress got signal 11, /bin/tar got signal 13] > >[index got signal 11, /usr/bin/smbclient got signal 13] > >One of my Debian clients, running kernel 2.6.2, has recently > developed these maladies. Fortunately, most of its DLE's backup > successfully, and these maladies are intermittent. Nevertheless, > when a DLE presents one of these errors, all subsequent DLE's also > FAIL ;< > >What do you think? That its time to let memtest86 run for a couple of days on that system. I'd suspect the memory is coming down with alzheimers. -- 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) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: crossed signals ???
Michael D Schleif wrote: > [compress got signal 11, /usr/bin/smbclient got signal 13] Weren't mysterious signal 11's often an indication of failing RAM modules? The classical `test' on linux was to compile the kernel; if that segfaults at different places, the verdict was faulty memory most of the time. (The other process, smbclient or tar, would logically get a SIGPIPE when trying to read from the defunct compress.) Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
crossed signals ???
Can somebody please explain these errors: [compress got signal 11, /usr/bin/smbclient got signal 13] [compress got signal 11, /bin/tar got signal 13] [index got signal 11, /usr/bin/smbclient got signal 13] One of my Debian clients, running kernel 2.6.2, has recently developed these maladies. Fortunately, most of its DLE's backup successfully, and these maladies are intermittent. Nevertheless, when a DLE presents one of these errors, all subsequent DLE's also FAIL ;< What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: dd question
Dege, Robert C. wrote: Most of the time, I'll get the header information, but every so often I have to run the command twice for the system to successfully read the tape. i.e.: bash$ dd if=/dev/tape bs=32k 0+0 records in 0+0 records out bash$ dd if=/dev/tape bs=32k AMANDA: TAPESTART DATE 20180319 TAPE SIMNET-02 1+0 records in 1+0 records out Maybe the first time the tape is not rewound? E.g. amcheck uses the nonrewinding device, and lets the tape positioned just after the label (but in that case you By opening it as /dev/tape, it gets rewound automatically. You can see it like this: $ amcheck -s daily ... finds correct tape ... $ mt -t /dev/nst1 status SCSI 2 tape drive: File number=0, block number=1, partition=0. Tape block size 0 bytes. Density code 0x30 (AIT-1 or MLR3). Soft error count since last status=0 General status bits on (101): ONLINE IM_REP_EN # !!! We are positioned on file 0, block 1 $ dd if=/dev/st1 bs=32k 0+0 records in 0+0 records out # we tried to read block 2 of the header, which is only 32K large # we read 0 byte, signaling EOF. # But we used /dev/st1, and the tape is rewound now $ mt -t /dev/nst1 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x30 (AIT-1 or MLR3). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN # Now are at the BOT (Beginning Of Tape), file 0, block 0 $ dd if=/dev/st1 bs=32k AMANDA: TAPESTART DATE 20040331 TAPE DAILY-08 1+0 records in 1+0 records out # And this time we find the header -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amcheck asking for tape in slot 2. Only have one tape drive.
Hello, and thank you for your email. I shall be out of the office until Tuesday 4th May. Should your email require urgent attention, the please contact David Adams or email [EMAIL PROTECTED] Regards, William Hargrove
Re: amcheck asking for tape in slot 2. Only have one tape drive.
On Thu, Apr 29, 2004 at 12:41:27PM +0200, Sören Edzen wrote: > * Jon LaBadie <[EMAIL PROTECTED]> [2004-04-28 23:49]: > [snip] > > Does your amanda.conf file claim a changer is in use? > [/snip] > The only thing I have in my amanda.conf that mentions changer is > 'tpchanger'. Could it be that? > > Below is a part off my amanda.conf. I haven't included tape and > holding disk definitions and settings that I know are local, to save space. I they > are needed, please > let me know. > > [snip] > # amanda.conf - > runtapes 1# number of tapes to be used in a single run of amdump > tpchanger "chg-manual"# the tape-changer glue script Perhaps someone else can pick up this thread for you. I've not used the changer script "chg-manual". Neither have I used a non-changer device with amanda. Looking at the chg-manual source it does have code relating to "slots", probably trying to emulate an actual changer device by having you manually changed the tapes when a new tape is required. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: dd question
Hello, and thank you for your email. I shall be out of the office until Tuesday 4th May. Should your email require urgent attention, the please contact David Adams or email [EMAIL PROTECTED] Regards, William Hargrove
Re: dd question
On Thu, Apr 29, 2004 at 07:59:51AM -0700, Dege, Robert C. wrote: > > Every so often, I'll run the following command to quickly see which amanda tape is > currently in my tape drive: > > # dd if=/dev/nst0 bs=32k > > Most of the time, I'll get the header information, but every so often I have to run > the command twice for the system to successfully read the tape. i.e.: > > bash$ dd if=/dev/tape bs=32k > 0+0 records in > 0+0 records out > > bash$ dd if=/dev/tape bs=32k > AMANDA: TAPESTART DATE 20180319 TAPE SIMNET-02 > > 1+0 records in > 1+0 records out > > > Any idea why this happens? I tend to use mt and mtx manually a good bit. Often when I do an "mt status" it shows some error condition. Then a second mt status works normally the actual status. Doesn't explain why the "error condition" exists, but if you are seeing the same thing, maybe the first dd is seing the error, that clears it, then the second one works. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
dd question
Every so often, I'll run the following command to quickly see which amanda tape is currently in my tape drive: # dd if=/dev/nst0 bs=32k Most of the time, I'll get the header information, but every so often I have to run the command twice for the system to successfully read the tape. i.e.: bash$ dd if=/dev/tape bs=32k 0+0 records in 0+0 records out bash$ dd if=/dev/tape bs=32k AMANDA: TAPESTART DATE 20180319 TAPE SIMNET-02 1+0 records in 1+0 records out Any idea why this happens? -Rob
Re: Novell and Amanda
On Thursday, 29.04.2004 at 15:36 +0100, Gavin Henry wrote: > >Out of interest, why is your existing backup software insufficient > >for your purposes? > > The admin doesn't know how to use it [...] Fair enough :-) Dave. -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
RE: Novell and Amanda
>Basically, there should be no problem doing that. An AMANDA server
>doesn't really need to be anything special - a faster machine should
>give you faster throughput to the tapes, of course, until you reach the
>limit of the drives.
OK.
>Also, get a LARGE holding disk - or possibly more than one. If you are
>planning to backup up to 200GB, you will benefit from having at least
>that much as holding disk, ideally many times that space. A couple of
>cheap IDE disks would be best.
Agreed,
>You backup via Samba yes - haven't personally had to do this ("If it's
>on your Windows PC it doesn't get backed up." is my policy) so I'll let
>someone else answer that.
So the smbclient on the Linux box just gets into the windows 2000 server shares etc.?
>Don't know this tape drive, but if it is supported by your chosen
>operating system and by AMANDA, then that won't be a problem.
Need to check.
>Out of interest, why is your existing backup software insufficient for
>your purposes?
The admin doesn't know how to use it, and I think Amanda is simpler in the long run.
It's very much like Arkeia, tape pools and all that. I hated that one.
Gavin.
Re: Novell and Amanda
On Thursday, 29.04.2004 at 15:11 +0100, Gavin Henry wrote:
> >We have a Debian box which mounts our Netware server's disks as ncpfs
> >filesystems - and we add these mount points to the AMANDA disklist.
>
> This is what I had in mind. We have 6 Windows servers; AD, SQL,
> Citrix/E-mail/Exchange and 3 other windows 98 call logger machines and
> one last one for the PABX. 1 Netware 4 box. 1 AIX 4.0.
>
> I could get an old box, not sure what spec, install Fedora on it (my
> choice) and hang the HP Ultrium multitape drive off it and back them
> all up.
Basically, there should be no problem doing that. An AMANDA server
doesn't really need to be anything special - a faster machine should
give you faster throughput to the tapes, of course, until you reach the
limit of the drives.
Also, get a LARGE holding disk - or possibly more than one. If you are
planning to backup up to 200GB, you will benefit from having at least
that much as holding disk, ideally many times that space. A couple of
cheap IDE disks would be best.
> The tapes are 200GB each. I could use the novelclient to log
> as admin and then mess with the AIX one too. I take it the windows
> boxes would be via their shares? How would samba be configured for
> this?
You backup via Samba yes - haven't personally had to do this ("If it's
on your Windows PC it doesn't get backed up." is my policy) so I'll let
someone else answer that.
> >If you have any more questions, knowing a bit more about what you have
> >in mind would be helpful.
>
> I am not the admin here, but he is really struggling with Back falling
> all the time.
>
>
> Hardware:
> HP Ultrium 1 LTO StorageWorks 1/8 autoloader with C7971A 200GB Tapes
Don't know this tape drive, but if it is supported by your chosen
operating system and by AMANDA, then that won't be a problem.
> Current Software:
> BrightStor ARCServe backup Version 9 (Build 2020)
Out of interest, why is your existing backup software insufficient for
your purposes?
Dave.
--
Dave Ewart
[EMAIL PROTECTED]
Computing Manager, Epidemiology Unit, Oxford
Cancer Research UK
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
RE: Novell and Amanda
>We have a Debian box which mounts our Netware server's disks as ncpfs >filesystems - and we add these mount points to the AMANDA disklist. This is what I had in mind. We have 6 Windows servers; AD, SQL, Citrix/E-mail/Exchange and 3 other windows 98 call logger machines and one last one for the PABX. 1 Netware 4 box. 1 AIX 4.0. I could get an old box, not sure what spec, install Fedora on it (my choice) and hang the HP Ultrium multitape drive off it and back them all up. The tapes are 200GB each. I could use the novelclient to log as admin and then mess with the AIX one too. I take it the windows boxes would be via their shares? How would samba be configured for this? >If you have any more questions, knowing a bit more about what you have >in mind would be helpful. I am not the admin here, but he is really struggling with Back falling all the time. Hardware: HP Ultrium 1 LTO StorageWorks 1/8 autoloader with C7971A 200GB Tapes Current Software: BrightStor ARCServe backup Version 9 (Build 2020) Gavin.
Re: Novell and Amanda
Gavin Henry wrote: > Is it possible to backup Novell 4 via Amanda via a HP Ultra multitape > drive? Assuming you aren't talking about actually running AMANDA on the Novell server itself, you should be able to do something here. We have a Debian box which mounts our Netware server's disks as ncpfs filesystems - and we add these mount points to the AMANDA disklist. Works fine. Strangely, when we had the same config on a Red Hat box, although the backups would work OK, AMANDA (or tar or whatever) couldn't figure out how to do level 1 and higher backups (something to do with the file modification dates visible over ncpfs). If you have any more questions, knowing a bit more about what you have in mind would be helpful. Dave. -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
Re: amdump: request timed out.. already read FAQ & troubleshooting
This one time, at band camp, Kris Vassallo wrote: >One day last week after AMANDA had been running fine for months it >just broke and I now am seeing this in my email log daily: What's your etimeout set to, and how big is the filesystem on host.domain:/backup/repo and /home ? I've just had the very same thing in the last week, and after some fiddling I found it was timing out when trying to get the estimates. I boosted etimeout to 3600 and the dump succeeded this morning. >Amanda Backup Client Hosts Check > >Client check: 3 hosts checked in 0.226 seconds, 0 problems found I was seeing this too, because of course the check doesn't require seeking over some 95G of data. I think the etimeout is a bit of a hack, though, and would prefer to see some ping mechanism in the protocol so that clients can let the server know that they're still alive and doing stuff. -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg
Re: amcheck asking for tape in slot 2. Only have one tape drive.
Hello, and thank you for your email. I shall be out of the office until Tuesday 4th May. Should your email require urgent attention, the please contact David Adams or email [EMAIL PROTECTED] Regards, William Hargrove
Re: amcheck asking for tape in slot 2. Only have one tape drive.
* Jon LaBadie <[EMAIL PROTECTED]> [2004-04-28 23:49]: [snip] > Does your amanda.conf file claim a changer is in use? [/snip] The only thing I have in my amanda.conf that mentions changer is 'tpchanger'. Could it be that? Below is a part off my amanda.conf. I haven't included tape and holding disk definitions and settings that I know are local, to save space. I they are needed, please let me know. [snip] # amanda.conf - runtapes 1 # number of tapes to be used in a single run of amdump tpchanger "chg-manual" # the tape-changer glue script tapedev "/dev/nst0" # the no-rewind tape device to be used rawtapedev "/dev/nst0" # the raw device to be used (ftape only) labelstr "^zampo-[0-9][0-9]*$" # label constraint regex: all tapes must match infofile "/var/lib/amanda/zampo/curinfo"# database DIRECTORY logdir "/var/lib/amanda/zampo"# log directory indexdir "/var/lib/amanda/zampo/index" # index directory dumpcycle 1 weeks bumpdays 7 bumpsize 20 Mb bumpmult 2 runspercycle 1 tapecycle 1 tapes dtimeout 1800 ctimeout 30 tapebufs 20 [/snip] -- Sören Edzen, Sjöfartsgatan 22A, 97437 Luleå, Sweden Phone: 0920-255133, Cell: 070-6531975 mailto: [EMAIL PROTECTED]
Novell and Amanda
Is it possible to backup Novell 4 via Amanda via a HP Ultra multitape drive? ** Kind Regards, Gavin Henry. BEng (Hons) MIEE Engineer Invsat Ltd. Discovery Drive, Arnhall Business Park, Westhill, Aberdeen, AB32 6FG. www.invsat.com Tel: + 44 (0) 1224 428453 Fax:+ 44 (0) 1224 428401 e-mail: [EMAIL PROTECTED] ** The information contained in the message above may be privileged and confidential and is intended for the use of the individual or entity named above. If you are not the intended recipient, please contact the sender as soon as possible and be aware that copying, disclosure, distribution or use of this information is prohibited.
Re: amdump: request timed out.. already read FAQ & troubleshooting
Increase the "etimeout", see below. Kris Vassallo wrote: Increase the "etimeout", see below. amandad: debug 1 pid 12359 ruid 33 euid 33: start at Wed Apr 28 23:59:01 2004 Completely off topic, but I find it more "logical" to run the backup just after midnight, instead of just before, in the case where 2 minutes don't matter. In that case there is no confusion on the date of backup: the backup dated 29-Apr-2004 is the one from the early morning, and the date on the report is exactly the same. In your case the backup would be labelled 28-Apr-2004, and the corresponding report would be dated 29-Apr-2004. Completely off-topic anyway. amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-C0710608 SEQ 1083221943 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9f00;maxdumps=1;hostname=venus.berkeley-da.com; GNUTAR /backup/repo 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index; GNUTAR /home 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index; amandad: time 0.001: sending ack: Amanda 2.4 ACK HANDLE 000-C0710608 SEQ 1083221943 The client received a packet asking for the service "sendsize" and ackownledged it. You mentioned there were two debugfiles. I would have expected that the first "amandad" debug file contained the request for service "noop" with the acknowledgement. The "noop" request just exchanges the features between the client and server. amandad: time 0.001: bsd security: remote host venus.berkeley-da.com user amanda local user amanda amandad: time 0.001: amandahosts security check passed amandad: time 0.001: running service "/usr/lib/amanda/sendsize" amandad: time 600.977: got packet: To me this seems like /usr/lib/amanda/sendsize has not yet finished, and the etimeout of 300 seconds times 2 DLE's kicked in. There should be sendsize.DATETIME.debug file too. amandad: time 4244.080: sending REP packet: After 4244 seconds, 1 hours 10 minutes, sendsize finished, but the server already gave up waiting for it: Amanda 2.4 REP HANDLE 000-C0710608 SEQ 1083221943 OPTIONS features=feff9f00; /home 0 SIZE 209076080 /backup/repo 0 SIZE 323990 The /home filesystem uses over 200 Gbyte. Is that correct? I hope your tape is large enough. Increase etimeout, and/or divide the /home in more manageable pieces. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amdump: request timed out.. already read FAQ & troubleshooting
There is 1GB of physical memory available and 2 GB of swap available. I
would assume that one would see things exiting abnormally in the logs
though if the memory was bottoming out? In any case, the remote machines
seem to get backed up fine but when it comes to backing itself up then
there is a problem which makes me think that if it was a memory issue
then all of the backups would fail, not just the localhost... right?
You prompted me to go back and look at the logs, in doing so it seems as
if I get 2 X of each log per run which I didn't notice before and now I
am seeing some problems. I can't tell if this is a permissions problems
or if this is something else. Attached are the logs containing the
problems. A little more info is that as soon as I had these problems I
went and switched the name from localhost to the FQDN of the machine in
both .amandahosts as well as disklist in hopes this would fix the
problem. I hope I didn't make anything worse, it sure didn't make
anything better.
On Thu, 2004-04-29 at 01:06, Paul Bijnens wrote:
> Kris Vassallo wrote:
>
> > - I am getting debug logs in /tmp/amanda
>
> What kind of debug logs? There should be a log from amandad with
> the protocol packets in it, and sendsize log, and a sendbackup log,
> and to run{tar,dump} logs.
> Which are there, compare it carefully with one that did succeed.
> Maybe send it to the list, (or to me if you believe too much sensitive
> information is in it).
>
> One of the stupid things that bit me once was running out of swap
> space: amcheck did succeed, but anything using more memory crashed
> without traces in the logs.
>
amandad: debug 1 pid 12359 ruid 33 euid 33: start at Wed Apr 28 23:59:01 2004
amandad: version 2.4.3
amandad: build: VERSION="Amanda-2.4.3"
amandad:BUILT_DATE="Thu Feb 13 11:14:37 EST 2003"
amandad:BUILT_MACH="Linux stripples.devel.redhat.com 2.4.20-2.41smp #1 SMP Sun
Feb 9 09:47:42 EST 2003 i686 i686 i386 GNU/Linux"
amandad:CC="gcc"
amandad:CONFIGURE_COMMAND="'./configure' '--host=i386-redhat-linux'
'--build=i386-redhat-linux' '--target=i386-redhat-linux-gnu' '--program-prefix='
'--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin'
'--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include'
'--libdir=/usr/lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib'
'--sharedstatedir=/usr/com' '--mandir=/usr/share/man' '--infodir=/usr/share/info'
'--enable-shared' '--with-index-server=localhost'
'--with-gnutar-listdir=/var/lib/amanda/gnutar-lists'
'--with-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda'
'--with-group=disk' '--with-gnutar=/bin/tar'"
amandad: paths: bindir="/usr/bin" sbindir="/usr/sbin"
amandad:libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
amandad:RDEV_PREFIX="/dev/r" DUMP="/sbin/dump"
amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient"
amandad:GNUTAR="/bin/tar" COMPRESS_PATH="/usr/bin/gzip"
amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail"
amandad:listed_incr_dir="/var/lib/amanda/gnutar-lists"
amandad: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
amandad:DEFAULT_TAPE_SERVER="localhost"
amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
amandad: time 0.000: got packet:
Amanda 2.4 REQ HANDLE 000-C0710608 SEQ 1083221943
SECURITY USER amanda
SERVICE sendsize
OPTIONS features=feff9f00;maxdumps=1;hostname=venus.berkeley-da.com;
GNUTAR /backup/repo 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index;
GNUTAR /home 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index;
amandad: time 0.001: sending ack:
Amanda 2.4 ACK HANDLE 000-C0710608 SEQ 1083221943
amandad: time 0.001: bsd security: remote host venus.berkeley-da.com user amanda local
user amanda
amandad: time 0.001: amandahosts security check passed
amandad: time 0.001: running service "/usr/lib/amanda/sendsize"
amandad: time 600.977: got packet:
Amanda 2.4 REQ HANDLE 000-C0710608 SEQ 1083221943
SECURITY USER amanda
SERVICE sendsize
OPTIONS features=feff9f00;maxdumps=1;hostname=venus.berkeley-da.com;
GNUTAR /backup/repo 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index;
GNUTAR /home 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index;
amandad: time 600.977: received dup P_REQ packet, ACKing it
amandad: time 600.977: sending ack:
Amanda 2.4 ACK HANDLE 000-C0710608 SEQ 1083221943
amandad: time 1201
Re: amdump: request timed out.. already read FAQ & troubleshooting
/tmp has 1.8 GB free (all other partitions have plenty of space as well) and I did a dig on the name as well as checked the /etc/hosts file and the correct information comes back from both of them. I have tried to start amdump as the user amanda by running "amdump DailySet1" and I get the same thing kicked back to me in the email with no errors coming back to me on the terminal. On Thu, 2004-04-29 at 00:52, [EMAIL PROTECTED] wrote: > may be your DNS was altered. check it out via dig/nslookup > > another strange thing I've had somtime was that the filesystem for the logs > / tmp was running out of space... check it with df -k > > have you ever tried to start it manually? the same error occurs? > > > > > > > Kris Vassallo To: [EMAIL PROTECTED] > . > <[EMAIL PROTECTED]> cc: (bcc: Arne Briesenick/DBS/GDB) > > Sent by: Subject:amdump: request timed > out.. already read FAQ & troubleshooting > [EMAIL PROTECTED] [Deutsche Boerse Systems:Virus checked] > > rg > > > > > > 29.04.2004 09:37 > > > > > > > > > > One day last week after AMANDA had been running fine for months it > just broke and I now am seeing this in my email log daily: > > FAILURE AND STRANGE DUMP SUMMARY: > host.domain /backup/repo lev 0 FAILED [Request to host.domain.com > timed out.] > host.domain /home lev 0 FAILED [Request to host.domain.com timed > out.] > (with host.domain being a FQDN which the machine can resolve) > > - I am getting debug logs in /tmp/amanda > - I have checked that amandaidx and amandad are both enabled in > xinetd.d and have restarted xinetd.d > - running "su - amanda -c "amcheck DailySet1" " reveals: > Amanda Backup Client Hosts Check > > Client check: 3 hosts checked in 0.226 seconds, 0 problems found > > - The host that is having the problem is also the server, yet it is > backing up 2 other hosts just fine. > - I have the FQDN in .amandahosts > - Running amandad as the amanda user causes ~30 of hanging before it > times out like its supposed to > - There is nothing about amandad or xinetd being broken in > /var/log/messages > > I am starting to run out of hair to pull out! Does anyone have any > ideas on what could be causing this?
Re: amdump: request timed out.. already read FAQ & troubleshooting
Kris Vassallo wrote:
- I am getting debug logs in /tmp/amanda
What kind of debug logs? There should be a log from amandad with
the protocol packets in it, and sendsize log, and a sendbackup log,
and to run{tar,dump} logs.
Which are there, compare it carefully with one that did succeed.
Maybe send it to the list, (or to me if you believe too much sensitive
information is in it).
One of the stupid things that bit me once was running out of swap
space: amcheck did succeed, but anything using more memory crashed
without traces in the logs.
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
Re: amdump: request timed out.. already read FAQ & troubleshooting [Deutsche Boerse Systems:Virus checked]
may be your DNS was altered. check it out via dig/nslookup another strange thing I've had somtime was that the filesystem for the logs / tmp was running out of space... check it with df -k have you ever tried to start it manually? the same error occurs? Kris Vassallo To: [EMAIL PROTECTED] . <[EMAIL PROTECTED]> cc: (bcc: Arne Briesenick/DBS/GDB) Sent by: Subject:amdump: request timed out.. already read FAQ & troubleshooting [EMAIL PROTECTED] [Deutsche Boerse Systems:Virus checked] rg 29.04.2004 09:37 One day last week after AMANDA had been running fine for months it just broke and I now am seeing this in my email log daily: FAILURE AND STRANGE DUMP SUMMARY: host.domain /backup/repo lev 0 FAILED [Request to host.domain.com timed out.] host.domain /home lev 0 FAILED [Request to host.domain.com timed out.] (with host.domain being a FQDN which the machine can resolve) - I am getting debug logs in /tmp/amanda - I have checked that amandaidx and amandad are both enabled in xinetd.d and have restarted xinetd.d - running "su - amanda -c "amcheck DailySet1" " reveals: Amanda Backup Client Hosts Check Client check: 3 hosts checked in 0.226 seconds, 0 problems found - The host that is having the problem is also the server, yet it is backing up 2 other hosts just fine. - I have the FQDN in .amandahosts - Running amandad as the amanda user causes ~30 of hanging before it times out like its supposed to - There is nothing about amandad or xinetd being broken in /var/log/messages I am starting to run out of hair to pull out! Does anyone have any ideas on what could be causing this? -- Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited.
amdump: request timed out.. already read FAQ & troubleshooting
One day last week after AMANDA had been running fine for months it just broke and I now am seeing this in my email log daily: FAILURE AND STRANGE DUMP SUMMARY: host.domain /backup/repo lev 0 FAILED [Request to host.domain.com timed out.] host.domain /home lev 0 FAILED [Request to host.domain.com timed out.] (with host.domain being a FQDN which the machine can resolve) - I am getting debug logs in /tmp/amanda - I have checked that amandaidx and amandad are both enabled in xinetd.d and have restarted xinetd.d - running "su - amanda -c "amcheck DailySet1" " reveals: Amanda Backup Client Hosts Check Client check: 3 hosts checked in 0.226 seconds, 0 problems found - The host that is having the problem is also the server, yet it is backing up 2 other hosts just fine. - I have the FQDN in .amandahosts - Running amandad as the amanda user causes ~30 of hanging before it times out like its supposed to - There is nothing about amandad or xinetd being broken in /var/log/messages I am starting to run out of hair to pull out! Does anyone have any ideas on what could be causing this?
