Re: Failure on W2k client

2001-04-04 Thread Hurf Sheldon

Hi folks,
Both amanda:sendsize and smbclient are OK, it is the interaction that is the
problem.
This started with my question re: read_socket_with_timeout errors
in sendsize.debug. The error is generated from lib/util_sock.c in
samba  code. From the logs smbclient is noting a failed open to
amanda:sendsize.
Smbclient takes it own error message as an indicator to
use the next address resolution scheme and  continues to attempt to connect.
Sendsize has
noted the socket open failure and declared "session setup failed: code 0";
since the smbclient
process hasn't died yet, sendsize continues to log information from the
smbclient it spawned.
A few things could happen  here. Sendsize could kill and respawn an
error-reporting smbclient,
or wait to call the session off  until smbclient exits; Smbclient could march
through the host
resolution options  before reporting a failed open, thus not confusing
amanda:sendsize.
The reason, probably, that a "wins" first host lookup works for is that the
smbclient file descriptor is not
a socket and a different set of routines are used to perform the open, which
for what
ever reason are more robust or less verbose, thereby not causing sendsize to
make
determination that the session failed. We have a choice of where to make the
fix.
Changing amanda:sendsize to wait for smbclient to exit before declaring a
failed session
would make amanda more robust;  changing smbclient to wait until the full
gamut of host resolution
options have been tried before reporting errors would also fix this problem
from an amanda
perspective but may cause other smb-dependent apps to suffer.  Having amanda
handle the different
possiblities smbclient presents seems a good way to go..
Does anyone careto look at the code? sendsize.c line 504, maybe...

We have a tentative thesis that the initial problem may be caused by the NIC
being put to sleep
in "powersaving" mode during inactive times (night) which is why we can't
re-produce
the problem during the day. We did uncheck the bit that does this in the 3Com
w2k driver
but didn't reboot the system. We saw no change last night so we'll try
rebooting the
sucker this afternoon.

thanks,
hurf

--
Todd Pfaff wrote:

 Ok, I think finally understand what Marty is trying to say.  Marty, there
 are many people on this list who have been using samba for years and
 understand it very well and how it interacts with amanda, and if we
 couldn't understand the gist of your initial question, don't blame our
 lack of understanding of the english language. :-)

 Marty says his samba setup works, but because of the fallback from wins to
 broadcast the lookup takes longer than amanda is willing to wait.  Amanda
 times out and as far as amanda is concerned, smbclient failed.  I'm not
 even sure what the implications of this are or how to make it work more
 efficiently, I'm just interpreting what he stated.

 Marty, is this correct?

 Now, this said, I still think the problem is with samba.  You should 'fix'
 your samba setup so that it doesn't take so long to do a lookup.

 Todd

 On Wed, 4 Apr 2001, David Lloyd wrote:

  Marty!
 
  I suggest you put your asbestos, flame resistant suit on...
 
   Again: THIS IS NOT AMANDA'S FAULT!  IT IS SMBCLIENT'S FAULT!
 
  You obviously cannot understand what I am saying, or you have not
  followed this thread. If you cannot understand English I will have this
  translated into any other language that I have a character set for:
 
  SMBCLIENT CAN CONTACT MY WINDOWS 2000 SERVER. IT DOES NOT FAIL. IT WORKS
  VIA BROADCAST AND AMANDA FAILS TO SEE THAT IT WORKS.
 
  Or to reword this:
 
  SAMBA IS ABLE TO CONTACT MY WINDOWS 2000 SERVER; SMBCLIENT CAN CONTACT
  IT. HOWEVER, IT DOES THIS VIA BROADCAST AND AMANDA FAILS.
 
  As far as I'm concerned SMB is working correctly. It is setup to use
  wins, wins fails and it therefore contacts my Windows 2000 server by
  broadcast and connects. Perfectly.
 
  So how is it smbclient's fault when smbclient works? I can't understand
  your English...
 
  DSL
 

 --
 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 \

--
Hurf Sheldon
Dir. Research Systems
Program of Computer Graphics
580 Rhodes Hall, Hoy Rd.
Cornell University
Ithaca, N.Y. 14853

voice:607 255 6713 fax:607 255 0806
email: [EMAIL PROTECTED]
http://www.graphics.cornell.edu/~hurf/





Failure on W2k client

2001-04-02 Thread Hurf Sheldon

Hi Folks,

Backing up shared folders (not full disk) a PC (Dell 420 dual
1ghz/W2k/sp1/15k-rpm UW scsi),
we are getting this intermittent error:

herman//rodney/workII lev 0 FAILED [disk //rodney/workII offline on
herman?]

"herman" is the amanda system (  FreeBSD
4.2-STABLE/"Amanda-2.4.2"/smbclient 2.0.7 )

this seems to be initiated by an error in sendsize (from sendsize.debug)

sendsize: argument list: "smbclient" "\\rodney\workII" "-d" "0"\
"-U" "backup_user%secret" "-E" "-W" "PC-GROUP" "-c" "archive
0;recurse;du"
added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0

added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0

added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0

added interface ip=128.84.247.9 bcast=128.84.247.255 nmask=255.255.255.0

read_socket_with_timeout: timeout read. read error = Connection reset by
peer.
session setup failed: code 0

The multiple "added interface" messages we don't see in any
successful transactions.
.
Repeatedly running smbclient by hand:
`smbclient '\\rodney\workII' -U backup_user%secret -d 0 -E -W DOMAIN -c
'archive 0;recurse;du'
we see only single interface messages, no errors or timeouts. We do
notice that the response is
instantaneous. Is it possible that the quick response is confusing
sendsize?

We are backing up other NT and W2k clients successfully and only see
this error on this client.

any help appreciated.
thanks,
hurf

Hurf Sheldon
Dir. Research Systems
Program of Computer Graphics
580 Rhodes Hall, Hoy Rd.
Cornell University
Ithaca, N.Y. 14853

voice:607 255 6713 fax:607 255 0806
email: [EMAIL PROTECTED]
http://www.graphics.cornell.edu/~hurf/





ERRDOS smbclient returns 1 problem

2001-03-23 Thread Hurf Sheldon

Hi,
We are having consistient problems* with a particular user's data.
We've had the same problem on two very different machines
(both Dell, one  NT4.0/sp6, the other W2K/sp1 ) - we've checked out and
changed network
cables and path to the system - I did see in the archives
a similar problem which had to do with large files and some settings in
the network interface.
The data does include some large (50mb) Power Point files (ppt).
We would appreciate any suggestions including diagnostic procedures.
thanks,
hurf

*representative error posts
? ERRDOS - ERRbadfile opening remote file \COM
S417\CS417_S01\5_Graphics_Hardware\WEB3_Sampling.ppt
(\COMS417\CS417_S01\5_Graphics_Hardware\)
? Expected SMBtrans2 response, got command 0x2d
? ERRDOS - ERRbadfile listing \COM S417\CS417_S01\6_Perception\*
? Error reading file \COM S417\CS417_S01\7_Color
Science\022601_LECTURE_perception_v6.ppt : ERRDOS - ERRbadfile
? Didn't get entire file. size=17660416, nread=0
? Expected SMBtrans2 response, got command 0x08
? ERRDOS - ERRbadfile listing \COM S417\CS417_S01\7_Color Science\OLD\*
? Error reading file \COM S417\CS417_S01\7_Color
Science\SUPER_LECTURE_perception_v6.ppt : ERRDOS - ERRbadfile
? Didn't get entire file. size=17881600, nread=0
? ERRDOS - ERRbadfile opening remote file \COM S417\CS417_S01\7_Color
Science\WEB_perception_v6.ppt (\COM S417\CS417_S01\7_Color Science\)
? Expected SMBtrans2 response, got command 0x2d
? ERRDOS - ERRbadfile listing \COM S417\CS417_S01\8_Review\*
? Error reading file \COM S417\CS417_S01\administration\Review.ppt :
ERRDOS - ERRbadfid
? Didn't get entire file. size=8650752, nread=0
? ERRDOS - ERRbadfile opening remote file \COM S417\CS417_S01\ARCH
375_Note.doc (\COM S417\CS417_S01\)
? invalid mid from server!
sendbackup: error [/usr/local/bin/smbclient returned 1]

-
--
Hurf Sheldon
Program of Computer Graphics
580 Rhodes Hall, Hoy Rd.
Cornell University
Ithaca, N.Y. 14853

voice:607 255 6713 fax:607 255 0806
email: [EMAIL PROTECTED]
http://www.graphics.cornell.edu/~hurf/





Re: ERRDOS smbclient returns 1 problem

2001-03-23 Thread Hurf Sheldon

Hi John,
Thanks for the advice.
kind regards,
hurf

"John R. Jackson" wrote:

 We are having consistient problems* with a particular user's data.
 ...
 ? ERRDOS - ERRbadfile opening remote file \COM
 S417\CS417_S01\5_Graphics_Hardware\WEB3_Sampling.ppt
 (\COMS417\CS417_S01\5_Graphics_Hardware\)
 ? Expected SMBtrans2 response, got command 0x2d
 ...

 I think you're asking the wrong group.  This is clearly a Samba issue
 and you need to be asking them (or searching their archives), not the
 Amanda group.  Someone on the Amanda group may know the answer because
 they just happen to also know Samba, but asking the Samba group has got
 to have a better chance of success.

 ... I did see in the archives
 a similar problem which had to do with large files and some settings in
 the network interface.
 The data does include some large (50mb) Power Point files (ppt).

 50 MBytes is not large when it comes to backups.  20 GBytes is large.  :-)

 hurf

 John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]






A list of implementation questions

2001-01-18 Thread Hurf Sheldon

Hi Folks,

Our amanda was set up by set up by someone who has moved on.
I feel like I have a pretty good handle on it after 6mos. It has worked
reliably. I've learned to add/delete disks, manipulate some of the
config options and have succcessfully "twinned" our master configuration
so I can test migration of our tape device from one platform to another
as 
well as change the config for a different tape device.
As time has passed our needs have progressed and I'm
unsure of the best way to proceed. I also have some questions re: day to
day
operations.

Our present setup is  Amanda-2.4.2-19990920 on an HPUX 10.2 system
backing up
a heterogeneous environment of NT, Irix, FreeBSD and HPUX systems to
an Overland 4000LX 15tape/1drive DLT. We are backing up the NT systems
via Samba.

Changes needed: 
1: Move the drive to a PC based system - right now we have a FreeBSD
4.2-Stable
system on a dual 266mhz P-II ASUS P2B-D mother board and an Adaptec
2930CU SCSI adapter.

2: Add backup for a Dell PowerVault 705 NAS device and Windows 2000
systems 

3: Do archival backups

3a: use a second magazine

4: resolve authentication error

Related questions:
1: When we move the Overland to the FreeBSD PC and run amlabel, we get 
errors in the system log file and the DLT goes out to lunch - we setup
an HP SureStore 2300 6 tape DDS as a test and saw some similar errors
but 
after the tapes were labeled they subsided: 
(ch0:ahc0:0:0:1): MOVE MEDIUM. CDB: a5 20 0 0 0 3 0 1 0 0 0 0 
(ch0:ahc0:0:0:1): ILLEGAL REQUEST asc:3b,d
(ch0:ahc0:0:0:1): Medium destination element full
ch: warning: could not map element source address 0d to a valid element
type
(sa0:ahc0:0:0:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM
command to clear this state.

Neither the FreeBSD list nor Overland has had any insight into this...

2: We can't directly access the NAS disks - how would we give dump
instructions
to a system that has it mounted via NFS or SMB? I thought Amanda used
tar
on Unix but a dump request to an Irix system with the NAS mounted failed 
"disk /remote/nas01/2 offline on nimble". A remote SMB mount can't be in
turn shared so when trying to backup via smbclient we get:
"PC SHARE //lassiter/N access error: host down or invalid password?"

3: How can we configure amanda to do only level 0 or only incremental
backups?
We'd like to (say) run level 0 over the weekend to one tape set and
incrementals to
another, with an eye to adding a second tape machine and do level 0 to
one and
incrementals to the other.

3a: To use a second 15 tape magazine, is there a way to setup
amanda.conf to count
all 30 tapes sequentially? The problem seems to be that Amanda thinks
there is 
30 slots if there are 30 tapes, so the chio routines fail. We'd like to
have it stop 
the tapers, ask for the next magazine and start at slot 1 again.

4: We compiled the latest Amanda for FreeBSD (VERSION="Amanda-2.4.2")
which included
patches for Windows 2000 via smbclient - that works fine now. We are
getting "auth" 
errors on the  cd /usr/local/amanda/FreeBSD system that we built as the
tape server:
" ERROR: vermeer: [access as backup not allowed from
[EMAIL PROTECTED]]\
amandahostsauth failed " - Did we miss something - I'm not able to track
this down.

5: What other Amanda guidance/support resources are available?

6: Just out of curiosity, is anyone working on a gui configuration
interface for Amanda?

my apologies for the "laundry list"

thanks in advance for any help

hurf



 Hurf Sheldon, Dir. Research Systems  email:
[EMAIL PROTECTED]
 Program of Computer Graphics voice:607 255 6713 fax:607 255 0806
 580 Rhodes Hall, Cornell University 
http://www.graphics.cornell.edu/~hurf/
 Ithaca, N.Y. 14853