Re: amcheck: hostname lookup failures
> I am having difficulty getting amcheck to do a proper hostcheck... Ummm, it's not amcheck (or Amanda's) fault. They are just using what the system provides ... > ERROR: stallman: [host stallman.: hostname lookup failed] What this says is that amandad on the client (yes, I know you said it's the same machine) did a lookup of the IP address that connected to it and got back hostname "stallman.". Yes, it really got back that trailing dot. Then it tried to turn around and look that name up and it failed. > DNS is right, reverse lookups are right (the hostname is defined in > /etc/hosts, as well as in DNS, my nsswitch.conf file is set to files,dns, a > resolver can look it up, and can look up the reverse IP address). I beg to differ :-). Clearly something on your system is not doing the IP to host conversion properly. You might get these programs: ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyaddr.c ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyname.c and try them out. They use the exact same system call Amanda does. Try the gethostbyaddr one first with all the possibly IP addresses Amanda may have been given. I'll bet one of them returns "stallman.". > Micah John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amcheck: hostname lookup failures
I am having difficulty getting amcheck to do a proper hostcheck... The server is set to backup itself and that is it right now. The server's name is stallman and I get these errors and have performed as much diagnosis as I can according to the FAQs and searching the mailing list archives: Amanda Backup Client Hosts Check ERROR: stallman: [host stallman.: hostname lookup failed] Client check: 1 host checked in 0.334 seconds, 1 problem found. Running version 2.4.1p1 DNS is right, reverse lookups are right (the hostname is defined in /etc/hosts, as well as in DNS, my nsswitch.conf file is set to files,dns, a resolver can look it up, and can look up the reverse IP address). Why is there an extra dot in host "stallman." ? My config file doesn't have that dot. There are no system log messages that give any indication of problems. Amanda services are defined in /etc/services as follows: amanda 10080/udp # amanda backup services kamanda 10081/tcp # amanda backup services (Kerberos) kamanda 10081/udp # amanda backup services (Kerberos) amandaidx 10082/tcp # amanda backup services amidxtape 10083/tcp # amanda backup services I added the line to /etc/inetd.conf and sent a HUP to inetd: amanda dgram udp waitbackup /usr/sbin/tcpd /usr/lib/amanda/amandad amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped I've run amandad by hand with that path (/usr/lib/amanda/amandad) and it works (well, it runs, the file is there)... and I did it as the "backup" user. The backup user can run all the associated utilities. Using lsof -p 3516 (my inetd process is running on that PID), I get: inetd 3516 root6u IPv41206416UDP *:amanda inetd 3516 root7u IPv41206417TCP *:amandaidx (LISTEN) inetd 3516 root8u IPv41206418TCP *:amidxtape (LISTEN) I completely turned off all my firewalling rules and ran the amcheck to get the same problem. I added the following to /etc/hosts.allow: amindexd: x.x.x.x amidxtaped: x.x.x.x (these are my IP addresses) It looks as if /tmp/amanda/amandad.debug is getting updated, it has the following in it: sending ack: Amanda 2.4 ACK HANDLE 000-90300508 SEQ 985914398 amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-90300508 SEQ 985914398 ERROR [host stallman.: hostname lookup failed] amandad: got ack: Amanda 2.4 ACK HANDLE 000-90300508 SEQ 985914398 The amandad binary access time is indeed being accessed and updated. Thanks so much for your help! Micah -- Micah Anderson Collective Technologies www.colltech.com "To be and not to do is not to be at all"
Re: help me, more output from amcheck
Oops! > However the syntax David Lloyd gave was not quite right. It should be: > > host.your.domain disk-to-back-up dump-type Damned Samba backups in disklists and god knows what... :-( -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Re: HP - Pure Store DLT1 [new tape type]
>I've just produced this for an HP-Pure Store DLT1 drive. ... Thanks. Could you put it in the FAQ (www.amanda.org), please? >DSL John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: help me, more output from amcheck
>"disklist", line 15: disk dumptype expected >"disklist", line 16: disk dumptype expected >amcheck-clients: could not load "disklist" > >What's up with the two disklist lines, line 15 & 16? ... Well, that's pretty hard to tell since you didn't post your disklist. However the syntax David Lloyd gave was not quite right. It should be: host.your.domain disk-to-back-up dump-type >Also, I've not >specified any clients as yet in my amanda.conf, why is that last line >even there? Ummm, you don't put the list of clients to back up in amanda.conf. They go in the disklist file. >Andrew R. Falanga John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amdump Failure
>When I run amdump from the tape host I get no feedback while it is running. ... You're not supposed to. The results will be E-mail'd to you (or to whever is listed in "mailto" in amanda.conf). >When I check the log file, it appears fine until, near the end of the >file I get: > > > localhost /dev/hda1 lv 0 t 21495 s 644898 p 11411 > >dump of driver schedule after start degraded mode: > > Unfortunately, you chopped this off too soon. The implication is that Amanda dropped into degraded mode, i.e. it could no longer write to tape and started doing dumps to the holding disk only. But the empty list also implies it didn't have anything to do. >driver: send-cmd time 17.826 to taper: QUIT >writing taper command: Broken pipe This is probably fixed (over, and over again :-) in 2.4.2. >Does anyone have any thought as to the problem, and possible resolutions? Don't know without seeing the E-mail Amanda sent to you. It should list the reason it ran into trouble and dropped into degraded mode. A more cryptic version can be seen by looking at the log.MMDD.NN file. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
HP - Pure Store DLT1 [new tape type]
I've just produced this for an HP-Pure Store DLT1 drive. It looks about
right (the drives claim 40Gb). This was created with mt -f /dev/nst1
datcompression off and with the tapetype that comes with amanda-2.4.2p1.
define tapetype HP-DLT1E {
comment "just produced by tapetype program"
length 38751 mbytes
filemark 0 kbytes
speed 2756 kps
}
DSL
--
And though you turn from me
To glance behind
The Phantom of the Opera is there...
Inside your mind!
Re: amrecover : setdisk syntax
>I tried to set CWD as an environment variable ... Sorry. I wasn't clear. "CWD" is just a shorthand, not a real variable. Amanda asks a system library routine what your current working directory is. We should probably change that message (I've taken a note to do so). >I am testing with the root directory of my workstation "clark ... Everything looks like it is set up properly. So here's the problem: >amindexd: debug 1 pid 4270 ruid 11 euid 11 start time Thu Mar 29 10:36:15 2001 >amindexd: version 2.4.1p1 >... >> DISK /dev/hda1 >! /usr/sbin/amadmin Weekly find clark \^/dev/hda1\$ Amindexd ran this command and didn't get anything back. First, what user is associated with uid 11? Try running the above command as that user. What do you get back? The command is looking through your log.MMDD.NN files. Are they still there (look at the logfile parameter in amanda.conf for the location)? Are the permissions such that the user can access them? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: help me, more output from amcheck
Andrew! > Amanda Tape Server Host Check > - > /holdingtank: 8182314 KB disk space available, that's plenty. > NOTE: skipping tape-writable test. > Tape nwc0 label ok. > Server check took 17.913 seconds. > "disklist", line 15: disk dumptype expected > "disklist", line 16: disk dumptype expected > amcheck-clients: could not load "disklist" > > What's up with the two disklist lines, line 15 & 16? Well, it's expecting a dumptype. I'm not entirely certain how to say that in a different way. However, the disklist looks like: [lloy0076 ]% cat disklist host.your.domain dump-type The dump-type is found in amanda.conf. Typical names are "comp-user". If you specify a wrong dumptype or no dumptype then you'll get this kind of error. > Also, I've not > specified any clients as yet in my amanda.conf, why is that last line > even there? Well, because it couldn't figure out the disklist. It's related to the first problem, much like the domino effect - one problem causing another problem. DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Re: re-label any tape?
>There are 6 hosts. 3 of them are IP aliases on one of the hosts, >so four addresses are really the same host. I don't know if that matters. Uh, oh. That definitely matters. When Amanda runs something on a client, it asks the client to start amandad from inetd. Only one copy of amandad may be running at at time. The server side looks at the host name and knows better than to ask the same host more than once. But you "lied" to Amanda and it thinks those are separate hosts, so probably tried to start them all up. One of them "won" and the others failed. But it would be highly timing dependent exactly what the results were. >Seth John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
help me, more output from amcheck
Hello everyone, Well, things are progressing nicely. It working quite well. However, I need some help in figuring out what's going on here though. Here's the mail that was sent to me after the latest run of amcheck: Amanda Tape Server Host Check - /holdingtank: 8182314 KB disk space available, that's plenty. NOTE: skipping tape-writable test. Tape nwc0 label ok. Server check took 17.913 seconds. "disklist", line 15: disk dumptype expected "disklist", line 16: disk dumptype expected amcheck-clients: could not load "disklist" What's up with the two disklist lines, line 15 & 16? Also, I've not specified any clients as yet in my amanda.conf, why is that last line even there? -- Andrew R. Falanga, A+, CNA, CNE (NetWare 4 & 5) Network Engineer/Hostmaster Networks.Com, Inc.
Re: Samba Report
On Thu, 29 Mar 2001, Todd Pfaff wrote: > if you have the locate command on your system, try 'locate > sendbackup-gnutar' and see what that turns up. sorry, that should be 'locate sendbackup'. there is no program sendbackup-gnutar, the source module sendbackup-gnutar.c is used to build program sendbackup, but sendbackup-gnutar.c is where the smbclient calling code is found. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: linux + ait tape changer
Joe Sauer wrote: > > I'm currently running amnada on a solaris box w/ a 4 tape ait, cartrige > tape changer. > > I would like to change this to a Redhat linux box w/ a changer. I'm > interested to know what ait tape changers people out there are using w/ at > least 4 tapes. Not to mention any redhat specific info you might have. Using a Spectra Logic 2000 autoloader, with one AIT-1 drive and 15 tapes. The chg-scsi in amanda 2.4.2p1 seems to work well with the robot. I had to disable hardware compression with "mt datcompression off", but other than that, things are going fine. I'm using an Adaptec 2944 HVD scsi card, a Dell Pentium III 866Mhz, and RedHat 7.0. I've also tried Redhat 7.1 betas Fisher and Wolverine, with a 2.4.x kernel. I kept getting SCSI timeout errors when accessing the robot, so I went back to RedHat 7.0 and kernel 2.2.17. Ryan Cleary
amdump Failure
When I run amdump from the tape host I get no feedback while it is running. When I check the log file, it appears fine until, near the end of the file I get: localhost /dev/hda1 lv 0 t 21495 s 644898 p 11411 dump of driver schedule after start degraded mode: driver: state time 17.826 free kps: 7400 space: 7372800 taper: DOWN idle-dumpers: 8 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 17.826 if : free 6000 if LE0: free 400 if LOCAL: free 1000 driver: hdisk-state time 17.826 hdisk 0: free 3686400 dumpers 0 hdisk 1: free 3686400 dumpers 0 driver: QUITTING time 17.826 telling children to quit driver: send-cmd time 17.826 to dumper0: QUIT driver: send-cmd time 17.826 to dumper1: QUIT driver: send-cmd time 17.826 to dumper2: QUIT driver: send-cmd time 17.826 to dumper3: QUIT driver: send-cmd time 17.826 to dumper4: QUIT driver: send-cmd time 17.826 to dumper5: QUIT driver: send-cmd time 17.826 to dumper6: QUIT driver: send-cmd time 17.826 to dumper7: QUIT driver: send-cmd time 17.826 to taper: QUIT writing taper command: Broken pipe driver: FINISHED time 17.829 amdump: end at Thu Mar 29 14:24:45 EST 2001 Does anyone have any thought as to the problem, and possible resolutions? Thanks. Find the best deals on the web at AltaVista Shopping! http://www.shopping.altavista.com
linux + ait tape changer
I'm currently running amnada on a solaris box w/ a 4 tape ait, cartrige tape changer. I would like to change this to a Redhat linux box w/ a changer. I'm interested to know what ait tape changers people out there are using w/ at least 4 tapes. Not to mention any redhat specific info you might have. Thanks, Joe
Re: amrecover : setdisk syntax
"John R. Jackson" wrote:
> >Can't determine disk and mount point from $CWD
>
> Amanda takes your current working directory ($CWD) and tries to figure
> out what disk it is related to in disklist on the assumption you started
> amrecover from the client and disk you want to do the restore into.
> The message says it was not able to do that, which could be caused by
> any number of things.
>
I tried to set CWD as an environment variable in a variety of shells (bash,
csh, ksh)
export CWD=`pwd`
but alas I still got the complaint, "Can't determine disk and mount
point from $CWD"
>
> What disklist entry do you think should match your current working
> directory?
I am testing with the root directory of my workstation "clark, a Red Hat 7.0
PC" clark is my amanda server,
index server and tape server. Using amdump with (index = yes) I dumped
/dev/hda1, the root partition.
>From the "/" directory I executed amrecover. At the amrecover> prompt I
tried to set my disk with
the following results:
# amrecover -C Weekly -s clark -t clark -d /dev/nst0
AMRECOVER Version 2.4.2p1. Contacting server on clark. ...
220 clark AMANDA index server (2.4.1p1) ready.
200 Access OK
Setting restore date to today (2001-03-29)
200 Working date set to 2001-03-29.
200 Config set to Weekly.
200 Dump host set to clark.
Can't determine disk and mount point from $CWD
amrecover> setdisk /dev/hda1
598 Error: disk not found.
amrecover>
>
>
> Do you have index set to "yes" for the dumptype associated with that
> disk?
Yes, here are some excerpts from my amanda.conf and disklist
from amanda.conf:
...
infofile "/usr/local/etc/amanda/Weekly/curinfo" # database DIRECTORY
logdir "/usr/local/etc/amanda/Weekly" # log directory
indexdir "/usr/local/etc/amanda/Weekly" # index directory
tapelist "/usr/local/etc/amanda/Weekly/tapelist"# list of used tapes
define dumptype linux0 {
comment "Linux dump level 0"
program "DUMP"
dumpcycle 0
index yes
}
from disklist:
#
# clark
#
clark /dev/hda1 linux0
clark /dev/hda5 linux0
clark /dev/hda3 linux0
clark /dev/hda6 linux0
>
>
> >amrecover> setdisk /dev/hda1
> >598 Error: disk not found.
> That's the correct syntax, but again, it is not finding the index records
> that match "/dev/hda1". Same questions as above: is that a disklist
> entry, and do you have indexing turned on?
>
> One way to see what Amanda is working with is to look at your indexdir
> entry in amanda.conf. That points to a directory. In there is one
> directory per client, and in each client directory is one more directory
> for each disk (that has indexing turned on). Finally, in those
> directories, are the gzip'd index files themselves.
In my /usr/local/etc/amanda/Weekly directory there is a "clark" directory
with breaks out in an index tree holding the gzip'd files
[/usr/local/etc/amanda/Weekly]>cd clark
[/usr/local/etc/amanda/Weekly/clark]>ls
_dev_hda1/ _dev_hda3/ _dev_hda5/ _dev_hda6/
[/usr/local/etc/amanda/Weekly/clark]>cd _dev_hda1
[/usr/local/etc/amanda/Weekly/clark/_dev_hda1]>ls
20010326_0.gz 20010326_1.gz 20010328_0.gz 20010328_1.gz
[/usr/local/etc/amanda/Weekly/clark/_dev_hda1]>
>
>
> Note that Amanda is picky about things matching. For instance, if
> your disklist entry is "hda1", you cannot enter "/dev/hda1" (or the
> mount point). Some of that can be worked around with symlinks, but
> amrecover usually gets it right when properly set up.
>
> Another place to look for clues is /tmp/amanda/amindexd*debug on your
> server (clark).
Here is my amindexd.debug file
amindexd: debug 1 pid 4270 ruid 11 euid 11 start time Thu Mar 29 10:36:15
2001
amindexd: version 2.4.1p1
< 220 clark AMANDA index server (2.4.1p1) ready.
> SECURITY USER root
bsd security: remote host clark.purematrix.com user root local user operator
amandahosts security check passed
< 200 Access OK
> DATE 2001-03-29
< 200 Working date set to 2001-03-29.
> SCNF Weekly
< 200 Config set to Weekly.
> HOST clark
< 200 Dump host set to clark.
> DISK /
< 501 No index records for disk: /. Invalid?
> DISK root
< 501 No index records for disk: root. Invalid?
> DISK /dev/hda1
! /usr/sbin/amadmin Weekly find clark \^/dev/hda1\$
< 598 Error: disk not found.
> QUIT
< 200 Good bye.
amindexd: pid 4270 finish time Thu Mar 29 10:36:33 2001
>
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
begin:vcard
n:Brannigan;Paul
tel;fax:303-245-1025
tel;work:303-245-1045
x-mozilla-html:TRUE
adr:;;3434 47th St.;Boulder;Colorado;80301;USA
version:2.1
email;internet:[EMAIL PROTECTED]
title:Support Engineer
x-mozilla-cpt:;0
fn:Paul Brannigan
end:vcard
Re: Samba Report
uhhh, are you sure you have amanda-2.4.2p1 installed, and are you certain that you don't have a previous version installed somewhere? this looks suspiciously like you have an older version of sendbackup-gnutar running. in fact, i just had a close look at the 2.4.2p1 source code, and i guarantee you that whatever is running and generating the log below is not 2.4.2p1. it's likely 2.4.1x. if you have the locate command on your system, try 'locate sendbackup-gnutar' and see what that turns up. On Fri, 30 Mar 2001, David Lloyd wrote: > Hmmm! > > Amanda is running: > > sendsize.debug:sendsize: spawning "/usr/bin/smbclient" in pipeline > sendsize.debug:sendsize: argument list: "smbclient" > "\\THESHARE\thedirectory" "the_password" "-d" "0" "-U" "backup" "-E" > "-c" "archive 1;recurse;du" > > And it's working. Notably the command it says its running doesn't work > by hand so I suspect that it's a different command being implemented. > Now I'm getting more confused. I think I might point AMANDA at my remote > samba server and do a packet trace to work out EXACTLY what it is > sending over... > > > that is essentially what amanda is doing in the two different cases you've > > tried (plus a few more smbclient arguments that shouldn't affect the > > behaviour you're experiencing). if those commands do not work as > > expected, then solve the samba problem and amanda should work as expected. > > Then explain the above. > > > a note about this should probably be written in the docs/SAMBA file > > because 99% of the problems people have with amanda/samba backups are > > samba problems that should be debugged independently of amanda. > > Oh, I downloaded the patched version (as opposed to patching it myself) > and it displays the same behaviour... > > DSL > -- > And though you turn from me > To glance behind > The Phantom of the Opera is there... > Inside your mind! > -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
unsubscribe gtcopeland@earthlink.net
unsubscribe [EMAIL PROTECTED]
Re: re-label any tape?
+++ "John R. Jackson" <[EMAIL PROTECTED]>
+++ > WARNING: skipping tape test because amdump or amflush seem to be running;
+++ > WARNING: if they are not, you must run amcleanup.
+++
+++ This says there either an amdump/amflush is still running (you might
+++ check with "ps -fu ") or the previous run aborted and left
+++ stuff laying around (which is unusual, but can happen). As it says,
+++ if you don't find any evidence of things still active, run amcleanup to
+++ get it going (and run amcheck again to confirm).
John, Thanks..that helped...
The backups had some success last night
Actually, the most important part, the production application data was backed up
+++ > WARNING: eprod: selfcheck request timed out. Host down?
+++
+++ This is, without doubt, the number 1 problem that comes up here, so
+++ you're in good company. The FAQ at www.amanda.org has a number of items
+++ to check, so rather than going through that yet again here, give them a
+++ try and if it still won't work, post back with what you tried and what
+++ the results were.
I went through the FAQ section on amcheck.
There are no error messages in /var/adm/messages on either host.
BTW, three of the "hostnames" are actually virtual IP addresses,
since this is an HA cluster.
I cleaned /tmp/amanda on the backup host.
I did not think to clean it on the other hosts. I don't know if it matters.
/tmp/amcheck is writable on all hosts.
I'll include files I think are relevant to my problem, with comments/questions.
_root@s20_[/var/backup]:> cat log.amcheck
Amanda Tape Server Host Check
-
/var/dumps/amanda: 804746 KB disk space available, that's plenty.
ERROR: cannot overwrite active tape edgd129.
(expecting tape DailySet111 or a new tape)
NOTE: skipping tape-writable test.
Server check took 5.334 seconds.
Amanda Backup Client Hosts Check
WARNING: eprod: selfcheck request timed out. Host down?
Client check: 6 hosts checked in 30.283 seconds, 1 problem found.
(brought to you by Amanda 2.4.1p1)
_root@s20_[/var/backup]:>
There are 6 hosts. 3 of them are IP aliases on one of the hosts,
so four addresses are really the same host. I don't know if that matters.
_root@s20_[/var/backup]:> cat disklist
# VCS DISKS ##
prod /dg/dghome nocomp-root
qa1 /dg1/qa1 nocomp-user
qa2 /dg1/qa2 nocomp-user
# ETEST ##
etest /dev/vx/rdsk/rootvol nocomp-root
etest /var nocomp-root
etest /opt nocomp-root
etest /dg nocomp-root
etest /dg1 nocomp-root
### EPROD ##
eprod /dev/vx/rdsk/rootvol nocomp-root
eprod /var nocomp-root
eprod /opt nocomp-root
eprod /dg nocomp-root
eprod /dg1 nocomp-root
S20 ###
s20 /dev/rdsk/c0t3d0s0 nocomp-root -1
s20 /var nocomp-root -1
s20 /export/home nocomp-root -1
s20 is the backup host. prod, qa1, and qa2 are IP aliases on eprod
_root@s20_[/var/backup]:> cat amverify.29
Defects file is /tmp/amverify.5685/defects
amverify csd
Thu Mar 29 04:06:02 EST 2001
Using device /dev/rmt/0bn
Volume edgd0329, Date 20010329
Checked etest._var.20010329.0
Checked etest._dg.20010329.0
Re: Samba Report
Hmmm! Amanda is running: sendsize.debug:sendsize: spawning "/usr/bin/smbclient" in pipeline sendsize.debug:sendsize: argument list: "smbclient" "\\THESHARE\thedirectory" "the_password" "-d" "0" "-U" "backup" "-E" "-c" "archive 1;recurse;du" And it's working. Notably the command it says its running doesn't work by hand so I suspect that it's a different command being implemented. Now I'm getting more confused. I think I might point AMANDA at my remote samba server and do a packet trace to work out EXACTLY what it is sending over... > that is essentially what amanda is doing in the two different cases you've > tried (plus a few more smbclient arguments that shouldn't affect the > behaviour you're experiencing). if those commands do not work as > expected, then solve the samba problem and amanda should work as expected. Then explain the above. > a note about this should probably be written in the docs/SAMBA file > because 99% of the problems people have with amanda/samba backups are > samba problems that should be debugged independently of amanda. Oh, I downloaded the patched version (as opposed to patching it myself) and it displays the same behaviour... DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
Re: Samba Report
On Thu, 29 Mar 2001, David Lloyd wrote: > using 2.4.2p1...I assure you that: > > //NAME/directory user%password > > Doesn't work for me... what happens if you run: smbclient //NAME/directory -U user%password or smbclient //NAME/directory -U password that is essentially what amanda is doing in the two different cases you've tried (plus a few more smbclient arguments that shouldn't affect the behaviour you're experiencing). if those commands do not work as expected, then solve the samba problem and amanda should work as expected. a note about this should probably be written in the docs/SAMBA file because 99% of the problems people have with amanda/samba backups are samba problems that should be debugged independently of amanda. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Samba Report
Hi There! I have the 2.4.2 sources and pulled down the latest patch for 2.4.2. > Does it fail when you use amcheck? What's in /tmp/amanda/selfcheck*debug > on the Samba machine? No. > I assume the Samba machine is running Amanda 2.4.2+? That's where it > counts, not on the tape server. Hmmm My tape server is the samba machine. It needs to talk to my wins server, but smbclient is called locally. Therefore I think my samba server is using 2.4.2p1...I assure you that: //NAME/directory user%password Doesn't work for me... DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind!
