Re: amcheck reports error: can't access a windows system
From: "Eric Wadsworth" [EMAIL PROTECTED] This was the tip I needed to resolve this, thanks John. It was actually more complex, becuase I am using FreeBSD's ports system to work with software applications. I modified the Makefile in the skeleton for the Amanda24 port to include this item in the configuration parameter section: --with-smbclient After doing a 'make deinstall' and then 'make' and then 'make install' the problem persisted, I assumed that my modification of the make file in the skeleton wasn't being perpetuated down to the level where it actually calls ./configure, so I dove into the "make deinstall" just removes the port from your system, and deletes the .install-done flag from the work directory. You need to do a "make clean" (after the "make deinstall") in order to re-build the port with your changes. Scot
amcheck reports error: can't access a windows system
In the disklist I have an entry like this: my.samba.server.here.com //ntsystem/chasm user-tar But when running amcheck, I get this result: Amanda Tape Server Host Check - /usr/dumps/amanda: 11852627 KB disk space available, that's plenty. NOTE: skipping tape-writable test. Tape DailySet1-000 label ok. Server check took 0.043 seconds. Amanda Backup Client Hosts Check ERROR: my.samba.server.here.com: [can not access //ntsystem/chasm (//ntsystem/chasm): No such file or directory] ERROR: my.samba.server.here.com: [SMBCLIENT program not available] Client check: 2 hosts checked in 0.101 seconds, 2 problems found. I double checked the samba connection, with this command: smbclient //ntsystem/chasm mypassword -U backup And it let me right in. The amanda system (with the tape drive) is also the samba server. The /etc/amandapass file contains this line: //ntsystem/chasm mypassword I assume that it is using the user 'backup' but I'm not sure. I installed it onto this FreeBSD system via the FreeBSD ports, so I never got a chance to run configure --with-samba-user. Any ideas what could be wrong?
Re: amcheck reports error: can't access a windows system
ERROR: my.samba.server.here.com: [SMBCLIENT program not available] Run "amadmin xx version | grep SAMBA". I'm betting you won't get any output, which means when you ran ./configure for the client, it could not find smbclient. Run "make distclean", make sure the Samba programs are in your PATH, then rerun ./configure. Look at the output and be sure it found them, then rebuild and re-install Amanda. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amcheck reports error: can't access a windows system
This was the tip I needed to resolve this, thanks John. It was actually more complex, becuase I am using FreeBSD's ports system to work with software applications. I modified the Makefile in the skeleton for the Amanda24 port to include this item in the configuration parameter section: --with-smbclient After doing a 'make deinstall' and then 'make' and then 'make install' the problem persisted, I assumed that my modification of the make file in the skeleton wasn't being perpetuated down to the level where it actually calls ./configure, so I dove into the /usr/ports/misc/amanda24/work/amanda-2.4.1p1 directory, did a 'make distclean' and then './configure' with the options from makefile in the skeleton pasted to the ./configure command. Then I backed up to /usr/ports/misc/amanda24 and ran 'make' and 'make install' again, and it seems to have solved that problem. Note that I'm far from being any kind of UNIX expert, so what I did could easily be the totally wrong way to solve this; I'm just hacking around trying to get stuff to work. Now I've got the infamous 'host down' error when I run amcheck, but this appears to be well documented. --- Eric On Thu, 2 Nov 2000, John R. Jackson wrote: ERROR: my.samba.server.here.com: [SMBCLIENT program not available] Run "amadmin xx version | grep SAMBA". I'm betting you won't get any output, which means when you ran ./configure for the client, it could not find smbclient. Run "make distclean", make sure the Samba programs are in your PATH, then rerun ./configure. Look at the output and be sure it found them, then rebuild and re-install Amanda. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
