Fwd: BACKUP: LTO Jason Geosystems BV AMANDA MAIL REPORT FOR April 3, 2003
I try to backup a windows (nt4) disk using smbclient But I get the following error: FAILED AND STRANGE DUMP DETAILS: /-- hyperion //sosos/lan lev 0 FAILED [/usr/bin/smbclient got signal 11] sendbackup: start [hyperion://sosos/lan level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/bin/smbclient -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | added interface ip=172.17.0.8 bcast=172.17.0.255 nmask=255.255.255.0 | added interface ip=172.16.217.1 bcast=172.16.217.255 nmask=255.255.255.0 | added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 ? ERRDOS - ERRbadfile opening remote file \DATA\DOC\BRF\GENE\G3132_rem_amb libië.doc (\DATA\DOC\BRF\GENE\) ? ERRDOS - ERRbadfile opening remote file \DATA\DOC\BRF\GENE\tot 2700\G2653s_Mariëlle van Dijck.doc (\DATA\DOC\BRF\GENE\tot 2700\) ? ERRDOS - ERRbadfile opening remote file \DATA\DOC\BRF\GENE\tot 2700\G2662m_mariëlle_van_dijck.doc (\DATA\DOC\BRF\GENE\tot 2700\) [similar errors snipped] ? Error reading file \DATA\PD\projects\present\GeostatisticalInversion\RelatedInfo\GSLIB\gslib77\BIN\LUSIM.EXE. Got 0 bytes ? Didn't get entire file. size=125440, nread=0 [similar errors snipped] ? ERRDOS - 87 opening remote file \DATA\PD\projects\present\GeostatisticalInversion\RelatedInfo\GSLIB\gslib77\BIN\NSCORE.EXE (\DATA\PD\projects\present\GeostatisticalInversion\RelatedInfo\GSLIB\gslib77\BIN\) [similar errors snipped] sendbackup: error [/usr/bin/smbclient got signal 11] \ What am I doing wrong ? Also, Im curious where these 2 lines come from | added interface ip=172.16.217.1 bcast=172.16.217.255 nmask=255.255.255.0 | added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 172.17.0.8 is the IP adress of my linux box , but what are the other 2 Kind regards, -- Gerhard den Hollander Phone :+31-10.280.1515 Global IT Support manager Direct:+31-10.280.1539 Jason Geosystems BV Fax :+31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: amrecover Problem
Hi there, ive got a Problem with amrecover on an Debian GNU/Linux maschine. amrecover reports: No index records for disk for specified date If date correct, notify system administrator In debug files in /tmp i cant find any other Informations.Debugfile is there but the informations are the same shown on client. There is a backup on level 0 on specified date. In amanda.conf index yes is set on dumptype. - index is on the secified indexdir, so i can zcat it and see all files an directorys. Iam using tar (GNU tar 1.13.25), so it cant be the known bug on older gtar versions, and amanda version 2.4.2p2. Are there any solutions. I got the same error message on a recovery attempt some time back, and it was caused by a permission problem that prevented the backup config from being read correctly. Note that the config files are read by amandad (amrecover is just a client application that interacts with amandad), which is usually executed as amanda, so the files need to be readable by that user. Also, amandad apparently has (or had) a bug that prevents some file open problems from being reported in the logs. In other words, you probably need to chmod or chown one or more of the config files (in my case it was the tapelist) to make them readable by amandad. Greetings Daniel
Error Configuration Tapeless
I have followed the next explanation :
http://amanda.sourceforge.net/cgi-bin/fom?auth=ckd2128107166efile=191
But I have many problem to backup
$amchech DailySet1
Amanda Tape Server Host
Check-amcheck-server: fatal slot 1:
file:/stock/web/tape1: not a device fileERROR: new tape not found in
rack (expecting a new tape)NOTE:
skipping tape-writable testServer check took 0.158 seconds
Amanda Backup Client Hosts
CheckClient check: 1 host checked in
0.031 seconds, 0 problems found
(brought to you by Amanda 2.4.2p2)
A copy out of amanda.conf :
runtapes
1
tpchanger
"chg-multi"
changerfile
"/etc/amanda/DailySet1/chg-multi.conf"tapedev
"file:/stock/web/tape1"
tapetype
HARD-DISK
labelstr
"^DailySet1[0-9][0-9]*$"
define tapetype HARD-DISK
{ comment "Hard disk instead of
tape" length 1 mbytes}
define dumptype hard-disk-dump
{ comment "Back up to hard disk
instead of tape - using dump"
options index, no-hold priority
high}
define dumptype hard-disk-tar
{ comment "Back up to hard disk
instead of tape - using tar"
options index, no-hold program
"GNUTAR"}
A copy out of chg-multi.conf :
multieject 0
gravity 0
needeject 0
ejectdelay 0statefile /var/lib/amanda/DailySet1/changer-status
firstslot 1lastslot 2
slot 1 file:/stock/web/tape1slot 2
file:/stock/web/tape2
Amanada Data Timeout Problem with CygWin
I might be making progress; I'm not sure. For those who haven't been following... The amanda client under cygwin will reset the data connection without sending the final goodbye message and thus the server ignores all the backup data. To fix this, I removed the aclose of the various sockets from the start_backup functions and added them to after the parse_backup_messages in the main sendbackup.c file. The theory is that by not doing a close from within the main program, then there would be no RST packet going out. This has worked! However... When the client runs, the server gets the following: /-- watertown. /home/watertown lev 1 FAILED [data timeout] sendbackup: start [watertown.ott.precidia.com:/home/watertown level 1] sendbackup: info BACKUP=/usr/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/usr/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | Total bytes written: 10240 (10kB, ?B/s) \ The client on watertown things it ran just fine: sendbackup: debug 1 pid 312 ruid 0 euid 0: start at Thu Apr 3 20:24:58 2003 /usr/local/lib/amanda/sendbackup: version 2.4.3 parsed request as: program `GNUTAR' disk `/home/watertown' device `/home/watertown' level 1 since 2003:4:2:1:20:34 options `|;bsd-auth;compress-fast;index;exclude-file=^(#|Backup.of)|.(bak|tmp|fla|fst|hex|lib|lst|m 51|wav|mp3|mpg|mpeg|avi|mov|obj|omf|prn|swp)$|~$;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.014: stream_server: waiting for connection: 0.0.0.0.546 sendbackup: time 0.016: stream_server: waiting for connection: 0.0.0.0.547 sendbackup: time 0.016: stream_server: waiting for connection: 0.0.0.0.548 sendbackup: time 0.018: waiting for connect on 546, then 547, then 548 sendbackup: time 0.030: stream_accept: connection from 10.0.1.2.4285 sendbackup: time 0.032: stream_accept: connection from 10.0.1.2.4286 sendbackup: time 0.034: stream_accept: connection from 10.0.1.2.4287 sendbackup: time 0.035: got all connections sendbackup: time 0.036: spawning /usr/bin/gzip in pipeline sendbackup: argument list: /usr/bin/gzip --fast sendbackup-gnutar: time 0.085: pid 3644: /usr/bin/gzip --fast sendbackup-gnutar: time 0.090: doing level 1 dump as listed-incremental from /var/lib/amanda/gnutar-lists/watertown.ott. precidia.com_home_watertown_0 to /var/lib/amanda/gnutar-lists/watertown.ott.precidia.com_home_watertown_1.new sendbackup-gnutar: time 0.104: doing level 1 dump from date: 2003-04-01 1:25:14 GMT sendbackup: time 0.191: spawning /usr/local/lib/amanda/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /home/watertown --listed-incremental /var/lib/amanda/gnuta r-lists/watertown.ott.precidia.com_home_watertown_1.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amand a/sendbackup._home_watertown.20030403202458.exclude . sendbackup: time 0.271: started index creator: /usr/bin/tar -tf - 2/dev/null | sed -e 's/^\.//' sendbackup-gnutar: time 0.284: /usr/local/lib/amanda/runtar: pid 700 sendbackup: time 0.673: 53:size(|): Total bytes written: 10240 (10kB, ?B/s) sendbackup: time 0.746: index created successfully Well, somewhat fine, anyway. I was expecting more log messages at the end. I captured the entire thing with tcpdump (server=10.0.1.2; watertown=10.0.3.10): 20:07:04.028278 10.0.1.2.861 10.0.3.10.10080: udp 450 (DF) 20:07:04.272743 10.0.3.10.10080 10.0.1.2.861: udp 50 20:07:05.387130 10.0.3.10.10080 10.0.1.2.861: udp 111 20:07:05.401699 10.0.1.2.861 10.0.3.10.10080: udp 50 (DF) 20:25:57.682163 10.0.1.2.869 10.0.3.10.10080: udp 325 (DF) 20:25:57.922821 10.0.3.10.10080 10.0.1.2.869: udp 50 20:25:58.238240 10.0.3.10.10080 10.0.1.2.869: udp 232 20:25:58.238493 10.0.1.2.869 10.0.3.10.10080: udp 50 (DF) 20:25:58.239760 10.0.1.2.4285 10.0.3.10.546: S 1481763151:1481763151(0) win 5840 mss 1460,sackOK,timestamp 263338811 20:25:58.240392 10.0.3.10.546 10.0.1.2.4285: S 3382986306:3382986306(0) ack 1481763152 win 17520 mss 1460,nop,wscale 20:25:58.240469 10.0.1.2.4285 10.0.3.10.546: . ack 1 win 5840 nop,nop,timestamp 263338811 0 (DF) 20:25:58.241478 10.0.1.2.4286 10.0.3.10.547: S 1484517405:1484517405(0) win 5840 mss 1460,sackOK,timestamp 263338811 20:25:58.242113 10.0.3.10.547 10.0.1.2.4286: S 3383044113:3383044113(0) ack 1484517406 win 17520 mss 1460,nop,wscale 20:25:58.242204 10.0.1.2.4286 10.0.3.10.547: . ack 1 win 5840 nop,nop,timestamp 263338811 0 (DF) 20:25:58.243212 10.0.1.2.4287 10.0.3.10.548: S 1477361282:1477361282(0) win 5840 mss 1460,sackOK,timestamp 263338811 20:25:58.243850 10.0.3.10.548 10.0.1.2.4287: S 3383096864:3383096864(0) ack 1477361283 win 17520 mss 1460,nop,wscale 20:25:58.243949 10.0.1.2.4287 10.0.3.10.548: . ack 1 win 5840 nop,nop,timestamp 263338811 0 (DF) 20:25:58.251751 10.0.3.10.547 10.0.1.2.4286: P 1:72(71) ack 1 win 17520 nop,nop,timestamp
Re: Error Configuration Tapeless
On Fri, 4 Apr 2003, Audrey BROCHET wrote:
You must use at least the 2.4.3 version of amanda to be able
to backup in a file instead of a tape.
I have followed the next explanation :
http://amanda.sourceforge.net/cgi-bin/fom?auth=ckd2128107166efile=191
But I have many problem to backup
$amchech DailySet1
Amanda Tape Server Host Check
-
amcheck-server: fatal slot 1: file:/stock/web/tape1: not a device file
ERROR: new tape not found in rack
(expecting a new tape)
NOTE: skipping tape-writable test
Server check took 0.158 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.031 seconds, 0 problems found
(brought to you by Amanda 2.4.2p2)
A copy out of amanda.conf :
runtapes 1
tpchanger chg-multi
changerfile /etc/amanda/DailySet1/chg-multi.conf
tapedev file:/stock/web/tape1
tapetype HARD-DISK
labelstr ^DailySet1[0-9][0-9]*$
define tapetype HARD-DISK {
comment Hard disk instead of tape
length 1 mbytes
}
define dumptype hard-disk-dump {
comment Back up to hard disk instead of tape - using dump
options index, no-hold
priority high
}
define dumptype hard-disk-tar {
comment Back up to hard disk instead of tape - using tar
options index, no-hold
program GNUTAR
}
A copy out of chg-multi.conf :
multieject 0
gravity 0
needeject 0
ejectdelay 0
statefile /var/lib/amanda/DailySet1/changer-status
firstslot 1
lastslot 2
slot 1 file:/stock/web/tape1
slot 2 file:/stock/web/tape2
--
Eric Doutreleau
I.N.T | Tel : +33 (0) 160764687
9 rue Charles Fourier | Fax : +33 (0) 160764321
91011 Evry France | email : [EMAIL PROTECTED]
Re: chg-zd-mtx issue ?
Pablo, I see this problem intermittently and not always at slot 9, I've seen it at 1, 4 probably others. I don't know why the bus would have degraded when it had been working fine but the boxes are rackmounted and on rails and my next step will be to follow the suggestions of shaking the cables and tightening the screws. If you first run chg-zd-mtx -reset and then a amcheck conf, do you receive the same message or it works ok? If you only load tapes in the first 6 slots, do you still receive the same message? I'm having a similar problem , but if I only use the first 6 slots then it works ok.- Kind Regards. _ Pablo Jejcic Smartweb Senior system Administrator School of Computing - Robert Gordon University [EMAIL PROTECTED] T:44-(0)1224-262797 F:44-(0)1224-262790 _ ``The nice thing about standards is that there are so many to choose from. And if you really don't like all the standards you just have to wait another year until the one arises you are looking for.'' A. Tanenbaum, ``Introduction to Computer Networks' _ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Cuttler Sent: 03 April 2003 21:34 To: [EMAIL PROTECTED]; Chris Knight Subject: chg-zd-mtx issue ? Amanda 2.4.4 Solaris 9 LTO tape in Storedge 9 jukebox (ie HP c7145 jukebox) mtx 1.2.17rel mtx -f /dev/scsi/changer/c5t4d0 inquiry Product Type: Medium Changer Vendor ID: 'HP ' Product ID: 'C7145 ' Revision: '233S' Attached Changer: No This is very intermittent... amdump always runs successfully amcheck and amlabel, usually good, sometimes a little less so amtape _always_ fails in the same manner. Actually I was seeing a higher rate of success with amanda 2.4.3 on Solaris 8 but with the 2.4.4 chg-zd-mtx script. I'm sorry, I don't recall the version of mtx I was using on Solaris 8. Please tell me what additional diagnostic information I can provide, I just didn't want to include the kitchen sink. amlabel ninfo NTNWKLY10 slot 3 labeling tape in slot 3 (/dev/rmt/0cn): rewinding, reading label, not an amanda tape rewinding, writing label NTNWKLY10, checking labelBus error (core dumped) amcheck ninfo Amanda Tape Server Host Check - WARNING: holding disk /amanda/work: only 34403066 KB free (36700160 KB requested) amcheck-server: slot 3: date Xlabel NTNWKLY10 (first labelstr match) amcheck-server: slot 4: not an amanda tape amcheck-server: slot 5: date 20030327 label NEWTONR05 (no match) amcheck-server: slot 6: date 20030328 label NEWTONR06 (no match) amcheck-server: slot 7: date 20030331 label NEWTONR07 (no match) amcheck-server: slot 8: date 20030401 label NEWTONR08 (no match) amcheck-server: fatal slot 9: badly formed result from changer: 9 ERROR: error could not read result from /usr/local/libexec/chg-zd-mtx (got signal 10) (expecting tape NTNWKLY05 or a new tape) NOTE: skipping tape-writable test Server check took 459.881 seconds Amanda Backup Client Hosts Check Client check: 7 hosts checked in 2.112 seconds, 0 problems found (brought to you by Amanda 2.4.4) cat chg-zd-mtx.conf firstslot=1 lastslot=9 #cleanslot=3 AUTOCLEAN=0 autocleancount=99 havereader=1 offlinestatus=0 OFFLINE_BEFORE_UNLOAD=0 thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
debug flags
Hi- A question and an observation. I just made a small change to the format of one of the reports and rebuilt and re-installed Amanda. I was in the server-src directory and, as root, I did a make and a make install. Afterwards, several of the files in /usr/local/libexec had the wrong permissions and were not executable by Amanda. Are there options I can put in my xinit.d/Amanda file on a client so that I will get a log on the client? I think planner is hung now. JLM Jeremy Mordkoff Tatara Systems 978-206-0808 (direct) 978-206-0888 (fax) injustice anywhere threatens justice everywhere -- Dr. Martin Luther King
Re: Error Configuration Tapeless
On Fri, Apr 04, 2003 at 03:42:08PM +0200, Audrey BROCHET wrote: I have followed the next explanation : http://amanda.sourceforge.net/cgi-bin/fom?auth=ckd2128107166efile=191 But I have many problem to backup $amchech DailySet1 Amanda Tape Server Host Check - amcheck-server: fatal slot 1: file:/stock/web/tape1: not a device file ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 0.158 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.031 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) Backup to disk was not supported til recently. Get version 2.4.4. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanada Data Timeout Problem with CygWin
I might be making progress; I'm not sure. [ snip ] So... Why does the server close (FIN) all three connections only 1 second after opening them? I can find no messages in the server logs as to why this might have happened. Don't know my networking and tcpdump, so I'm asking off list. No problem. I CC'd the list again, though, because of the new findings I've included below. With ordinary files, after a fork one of the pair of processes will often close the file descriptors it does not need. But this leaves them open in the related process. Under unix, yes. It seems that under CygWin this behavior is not exactly the same, though what the full difference is, I can't really say. When I removed the close in the calling process, then I got past the original problem which was the connection getting reset once all the data had finished passing instead of a proper fin. Does this also happen with the network connections and could your FIN messages just be closing one of multiple references to the connection? All three network connections (data, mesg, index) are closed by the server for no apparent reason that I saw. You did give me an idea, though, and I went back in to the tcp dump and looked at the actual contents going back forth. Unfortunately, I didn't caputer the full packets but the first 40 bytes or so does indicate that: - the amount of data sent was very small (471 bytes) - the index consisted of only a few directories (109 bytes) - the mesg channel ended with Total bytes written: 10240... (277 bytes) The interesting thing is that these three things happened in the reverse order! The Total bytes written message came first, followed by the index list followed by the data. What would the amanda server think of that? Perhaps I need to create some more changes or just force a full dump so there would be more information to pass around? Brian ( [EMAIL PROTECTED] ) --- The future is not set. There is no fate but what we make for ourselves. -- JC
Re: debug flags
On Fri April 4 2003 10:04, Jeremy L. Mordkoff wrote: Hi- A question and an observation I just made a small change to the format of one of the reports and rebuilt and re-installed Amanda. I was in the server-src directory and, as root, I did a make makes must always be done as the user who runs amanda, usually 'amanda'. This sets all the ownership perms correctly. As root, back out of the srcdir and do a chown -R user:group srctree, where user:group is usually 'amanda' and group is usually 'disk' (or whatever you've used before), then do the make install again, which should fix it. [...] Are there options I can put in my xinit.d/Amanda file on a client so that I will get a log on the client? I think planner is hung now. Probably, but I've no experience, so I cannot recommend how. [...] -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.25% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: chg-zd-mtx issue ?
Jon,
My error - I'd intended to cc the list.
Jon,
Gene,
I'm uncertain how to unravel the core file - but I did find one
in one of my amanda directories and for lack of proper training
ran strings on it.
This is interesting (I think)...
This is pulled from several pages down and I'm afraid it might
highlight something in the changer script, chg-zd-mtx.
So I will try running chg-zd-mtx commands and see if I can't
induct an error.
coredump
blocks
nofiles
descriptors
memory
kbytes
unlimited
unlimited
unlimited
08:46 - status 0, result
t 3 to drive 0 (/dev/rmt/0cn)
to Storage Element 9...done
( H
!#$%'()*+,-./0123456789:;=[EMAIL PROTECTED]
PQRSTUVWXYZ{|}~
loadslot clean
Exit 2 none unknown option: $cmd
esac
Exit 2 none $myname: should not get here
-clea
eSUNW_OST_OSCMD
/usr/local/libexec/chg-zd-mtx
On Fri, Apr 04, 2003 at 12:03:19PM -0500, Gene Heskett wrote:
Unforch, this didn't get to the list according to the headers here
That's me, and my disliked by some, habit of replying privately.
Brian.
On Fri April 4 2003 11:24, Brian Cuttler wrote:
Jon,
Gene,
I've pulled all of the cables and connectors, power cycled
the drives.
Oh, I have two of these jukeboxes each with one LTO drive.
Brian,
just one other thought on termination. Most SCSI adapters today
are wide bus, most tape drive/changers narrow. A possible result
is that half the bus could be left unterminated. My SCSI adapter
has separate busses for wide and narrow devices. I always make
sure the narrow devices are on the correct ?channel?. I think
there are special cables providing termination to the extra
leads and narrowing the bus if you must use a wide channel.
Re Gene's comments on LUN's, I have to ask again, can you use
mtx to manipulate the changers? I.e. is it functional at that
level? And same for mt for the drive maipulations. And dd for
read and write. As some point it will be good to know if it
is an amanda problem or if at lower levels.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: chg-zd-mtx issue ?
Gene, Jon, This useful ? In order from newest file to eldest... Personally I don't see an error here but the command that produced these (and other files) was amtape ninfo update amtape: scanning all 9 slots in tape-changer rack: slot 3: date Xlabel NTNWKLY10 Bus error (core dumped) # cat amtape.20030404133143.debug amtape: debug 1 pid 20316 ruid 110 euid 110: start at Fri Apr 4 13:31:43 2003 changer: got exit: 0 str: 3 9 1 1 changer: got exit: 0 str: 3 /dev/rmt/0cn changer_label: NTNWKLY10 for slot 3 changer: got exit: 0 str: 3 9 1 1 changer_query: changer return was 9 1 1 changer_query: searchable = 1 changer_label: calling changer -label NTNWKLY10 changer: got exit: 0 str: 3 /dev/rmt/0cn # cat chg-zd-mtx.20030404133149000.debug chg-zd-mtx: debug 1 pid 20624 ruid 110 euid 110: start at Fri Apr 4 13:31:49 2003 13:31:49 Arg info: $# = 2 $0 = /usr/local/libexec/chg-zd-mtx $1 = -label $2 = NTNWKLY10 13:31:49 Running: /usr/local/sbin/mtx status 13:31:50 Exit code: 0 Stdout: Storage Changer /dev/scsi/changer/c5t4d0:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag = AF6411L1 Storage Element 1:Full :VolumeTag=AF6410L1 Storage Element 2:Full :VolumeTag=AF6402L1 Storage Element 3:Empty:VolumeTag= Storage Element 4:Full :VolumeTag=AF6412L1 Storage Element 5:Full :VolumeTag=AF6394L1 Storage Element 6:Full :VolumeTag=CLNI55L1 Storage Element 7:Full :VolumeTag=AF6396L1 Storage Element 8:Full :VolumeTag=AF6398L1 Storage Element 9:Full :VolumeTag=AF6397L1 13:31:50 Config info: firstslot = 1 lastslot = 9 cleanslot = -1 cleancycle = 120 offline_before_unload = 0 unloadpause = 0 autoclean = 0 autocleancount = 99 havereader = 1 driveslot = 0 poll_drive_ready = 3 max_drive_wait = 120 13:31:50 STATUS - currently loaded slot = 3 - currently loaded barcode = AF6411L1 13:31:50 LABEL- Adding label NTNWKLY10 with barcode AF6411L1 for slot 3 into /usr/local/etc/amanda/ninfo/chg-zd-mtx-barcodes - already synced 13:31:50 Exit (0) - 3 /dev/rmt/0cn chg-zd-mtx: pid 20714 finish time Fri Apr 4 13:31:50 2003 Then a new core file # cat chg-zd-mtx.20030404133149.debug chg-zd-mtx: debug 1 pid 20526 ruid 110 euid 110: start at Fri Apr 4 13:31:49 2003 13:31:49 Arg info: $# = 1 $0 = /usr/local/libexec/chg-zd-mtx $1 = -info 13:31:49 Running: /usr/local/sbin/mtx status 13:31:49 Exit code: 0 Stdout: Storage Changer /dev/scsi/changer/c5t4d0:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag = AF6411L1 Storage Element 1:Full :VolumeTag=AF6410L1 Storage Element 2:Full :VolumeTag=AF6402L1 Storage Element 3:Empty:VolumeTag= Storage Element 4:Full :VolumeTag=AF6412L1 Storage Element 5:Full :VolumeTag=AF6394L1 Storage Element 6:Full :VolumeTag=CLNI55L1 Storage Element 7:Full :VolumeTag=AF6396L1 Storage Element 8:Full :VolumeTag=AF6398L1 Storage Element 9:Full :VolumeTag=AF6397L1 13:31:49 Config info: firstslot = 1 lastslot = 9 cleanslot = -1 cleancycle = 120 offline_before_unload = 0 unloadpause = 0 autoclean = 0 autocleancount = 99 havereader = 1 driveslot = 0 poll_drive_ready = 3 max_drive_wait = 120 13:31:49 STATUS - currently loaded slot = 3 - currently loaded barcode = AF6411L1 13:31:49 INFO - first slot: 1 - current slot: 3 - loaded slot: 3 - last slot: 9 - slot list: 1 2 3 4 5 6 7 8 9 - can go backwards: 1 - havereader: 1 13:31:49 Exit (0) - 3 9 1 1 chg-zd-mtx: pid 20614 finish time Fri Apr 4 13:31:49 2003
Re: chg-zd-mtx issue ?
Ok, getting smarter... following your suggestion # truss amtape ninfo newtonl Tail of the output (I can script if if you want more) amtapewrite(2, a m t a p e, 6) = 6 : scanning all write(2, : s c a n n i n g a.., 15) = 15 9write(2, 9, 1) = 1 slots in tape-changer rack: write(2,s l o t s i n t a.., 29) = 29 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 4 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 5 so_socketpair(0xFFBFFB48) = 0 close(4)= 0 fork() = 21854 close(5)= 0 read(6, 2 / d e v / r m t / 1.., 1024) = 15 wait() = 21854 [0x] close(6)= 0 write(10, c h a n g e r : g o t.., 41) = 41 open64(/dev/rmt/1cn, O_RDONLY)= 4 brk(0x0002FEC8) = 0 brk(0x00035EC8) = 0 ioctl(4, MNTIOC_NMNTS, 0xFFBFF258) = 0 read(4, A M A N D A : T A P E.., 32768)= 32768 close(4)= 0 slot write(2, s l o t , 5) = 5 2write(2, 2, 1) = 1 : date write(2, : d a t e , 7)= 7 20030403write(2, 2 0 0 3 0 4 0 3, 8) = 8 label write(2,l a b e l , 7)= 7 NEWTONL02write(2, N E W T O N L 0 2, 9) = 9 write(2, \n, 1) = 1 write(10, c h a n g e r _ l a b e.., 36) = 36 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 4 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 5 so_socketpair(0xFFBFFA50) = 0 close(4)= 0 fork() = 21962 close(5)= 0 read(6, 2 9 1 1\n, 1024) = 8 wait() = 21962 [0x] close(6)= 0 write(10, c h a n g e r : g o t.., 34) = 34 write(10, c h a n g e r _ q u e r.., 40) = 40 write(10, c h a n g e r _ q u e r.., 30) = 30 write(10, c h a n g e r _ l a b e.., 48) = 48 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 4 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 5 so_socketpair(0xFFBFFAC8) = 0 close(4)= 0 fork() = 22058 close(5)= 0 read(6, 2 / d e v / r m t / 1.., 1024) = 15 wait() = 22058 [0x] close(6)= 0 write(10, c h a n g e r : g o t.., 41) = 41 Incurred fault #5, FLTACCESS %pc = 0xFF0C37F4 siginfo: SIGBUS BUS_ADRALN addr=0x000248F2 Received signal #10, SIGBUS [default] siginfo: SIGBUS BUS_ADRALN addr=0x000248F2 Gene, Jon, This useful ? In order from newest file to eldest... Personally I don't see an error here but the command that produced these (and other files) was amtape ninfo update amtape: scanning all 9 slots in tape-changer rack: slot 3: date Xlabel NTNWKLY10 Bus error (core dumped) # cat amtape.20030404133143.debug amtape: debug 1 pid 20316 ruid 110 euid 110: start at Fri Apr 4 13:31:43 2003 changer: got exit: 0 str: 3 9 1 1 changer: got exit: 0 str: 3 /dev/rmt/0cn changer_label: NTNWKLY10 for slot 3 changer: got exit: 0 str: 3 9 1 1 changer_query: changer return was 9 1 1 changer_query: searchable = 1 changer_label: calling changer -label NTNWKLY10 changer: got exit: 0 str: 3 /dev/rmt/0cn # cat chg-zd-mtx.20030404133149000.debug chg-zd-mtx: debug 1 pid 20624 ruid 110 euid 110: start at Fri Apr 4 13:31:49 2003 13:31:49 Arg info: $# = 2 $0 = /usr/local/libexec/chg-zd-mtx $1 = -label $2 = NTNWKLY10 13:31:49 Running: /usr/local/sbin/mtx status 13:31:50 Exit code: 0 Stdout: Storage Changer /dev/scsi/changer/c5t4d0:1 Drives, 9 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag = AF6411L1 Storage Element 1:Full :VolumeTag=AF6410L1 Storage Element 2:Full :VolumeTag=AF6402L1 Storage Element 3:Empty:VolumeTag= Storage Element 4:Full :VolumeTag=AF6412L1 Storage Element 5:Full :VolumeTag=AF6394L1 Storage Element 6:Full :VolumeTag=CLNI55L1 Storage Element 7:Full :VolumeTag=AF6396L1 Storage Element 8:Full :VolumeTag=AF6398L1 Storage Element 9:Full :VolumeTag=AF6397L1
Re: chg-zd-mtx issue ?
On Fri, Apr 04, 2003 at 01:56:13PM -0500, Brian Cuttler wrote: Ok, getting smarter... following your suggestion # truss amtape ninfo newtonl Tail of the output (I can script if if you want more) amtapewrite(2, a m t a p e, 6) = 6 : scanning all write(2, : s c a n n i n g a.., 15) = 15 9write(2, 9, 1) = 1 slots in tape-changer rack: write(2,s l o t s i n t a.., 29) = 29 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 4 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 5 so_socketpair(0xFFBFFB48) = 0 close(4)= 0 fork() = 21854 close(5)= 0 read(6, 2 / d e v / r m t / 1.., 1024) = 15 wait() = 21854 [0x] close(6)= 0 write(10, c h a n g e r : g o t.., 41) = 41 open64(/dev/rmt/1cn, O_RDONLY)= 4 brk(0x0002FEC8) = 0 brk(0x00035EC8) = 0 ioctl(4, MNTIOC_NMNTS, 0xFFBFF258) = 0 read(4, A M A N D A : T A P E.., 32768)= 32768 close(4)= 0 slot write(2, s l o t , 5) = 5 2write(2, 2, 1) = 1 : date write(2, : d a t e , 7)= 7 20030403write(2, 2 0 0 3 0 4 0 3, 8) = 8 label write(2,l a b e l , 7)= 7 NEWTONL02write(2, N E W T O N L 0 2, 9) = 9 write(2, \n, 1) = 1 write(10, c h a n g e r _ l a b e.., 36) = 36 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 4 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 5 so_socketpair(0xFFBFFA50) = 0 close(4)= 0 fork() = 21962 close(5)= 0 read(6, 2 9 1 1\n, 1024) = 8 wait() = 21962 [0x] close(6)= 0 write(10, c h a n g e r : g o t.., 34) = 34 write(10, c h a n g e r _ q u e r.., 40) = 40 write(10, c h a n g e r _ q u e r.., 30) = 30 write(10, c h a n g e r _ l a b e.., 48) = 48 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 4 so_socket(PF_UNIX, SOCK_STREAM, 0, , 1) = 5 so_socketpair(0xFFBFFAC8) = 0 close(4)= 0 fork() = 22058 close(5)= 0 read(6, 2 / d e v / r m t / 1.., 1024) = 15 wait() = 22058 [0x] close(6)= 0 write(10, c h a n g e r : g o t.., 41) = 41 Incurred fault #5, FLTACCESS %pc = 0xFF0C37F4 siginfo: SIGBUS BUS_ADRALN addr=0x000248F2 Received signal #10, SIGBUS [default] siginfo: SIGBUS BUS_ADRALN addr=0x000248F2 OK, of course that is only system calls. There is probably a printf in the .c file that corresponds to that write. It is writing to file descriptor 10, you can find above an open that returns a 10 ( = 10) to see the file name but it probably is /tmp/amanda/???debug???. The write succeeded, tried to write 41 bytes and the return ( = 41) says it did so successfully. So, the trick now is to find the C code that caused the write and figure what happened next. That is likely where the occured. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
mail is bouncing
On Fri April 4 2003 10:33, Jon LaBadie wrote: and I jumped in on the thread, but now I'm getting bounce messages from your server Jon, that read like this: Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.1.1 Remote-MTA: dns; jgcomp.com (68.46.49.200) Diagnostic-Code: smtp; 550 5.7.1 Rejected: 206.46.170.172 listed at unconfirmed.dsbl.org Sounds like you need to thump something or somebody. :-) -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.25% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Bouncing email to Jon
I just tried to reply to your private email Jon, and got this: Return-Path: To: [EMAIL PROTECTED] From: Mail Administrator [EMAIL PROTECTED] Reply-To: Mail Administrator [EMAIL PROTECTED] Subject: Mail System Error - Returned Mail Date: Fri, 4 Apr 2003 16:53:35 -0600 Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; Boundary_ _= 5816955(13884)1049496815 Status: R X-Status: N X-KMail-EncryptionState: X-KMail-SignatureState: This Message was undeliverable due to the following reason: Your message was not delivered because the return address was refused. The return address was '[EMAIL PROTECTED]' Please reply to [EMAIL PROTECTED] if you feel this message to be in error. === And the attachment content is the same as before. My message to you that generated that bounce. Is this going to be a verizon problem? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.25% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
blacklisted verizon mail server
Jon; I've sent a nastygram to [EMAIL PROTECTED] in an attempt to get this fixed. We'll see if they use their own list and it bounces. Yup, it did, as did my attempted forward of the bounce message to [EMAIL PROTECTED] regarding it. But a seperate message to postmaster went thru. I've also sent a similar msg, but a bit less nasty to [EMAIL PROTECTED] That one hasn't bounced. Me, a spammer? Thats hillarious. Nosy maybe, a bit of a knowitall too (old farts usually get that way, in case no one has noticed :), but a spammer? Boggles the mind. Good Grief even! Its raining here, sporadicly, and I have to work the graveyard at the transmitter tonight. Its beginning to get the wobblies according to the operators. And I haven't managed to get all the mud off my old 4wd pickup truck from my last trip up there. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.25% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: blacklisted verizon mail server
Does your outgoing mail go thru out013pub.verizon.net [206.46.170.44]? That server is blacklisted becasue it is an open relay. I had to whitelist the verizon.net domain because some of my employer's customers use verizon addresses and the admins at verizon insist that that server is not an open relay. I tested it. It _is_ an open relay. Here is a copy of a test email from abuse.net -- begin Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.heronforge.net (Postfix) with ESMTP id 72C279001E for [EMAIL PROTECTED]; Fri, 4 Apr 2003 18:35:04 -0800 (PST) Received: from mail.cpl.net [216.117.199.213] by localhost with POP3 (fetchmail-6.2.0) for [EMAIL PROTECTED] (single-drop); Fri, 04 Apr 2003 18:35:04 -0800 (PST) Received: by luke.cpl.net (mbox carville) (with Cubic Circle's cucipop (v1.31 1998/05/13) Fri Apr 4 18:33:58 2003) X-From_: [EMAIL PROTECTED] Fri Apr 4 18:30:37 2003 Received: from out013.verizon.net (out013pub.verizon.net [206.46.170.44]) by luke.cpl.net (8.11.3/8.11.3) with ESMTP id h352Ual71791 for [EMAIL PROTECTED]; Fri, 4 Apr 2003 18:30:36 -0800 (PST) Received: from www.abuse.net ([208.31.42.77]) by out013.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with SMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Fri, 4 Apr 2003 20:31:37 -0600 To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: Test for susceptibility of [206.46.170.44] to third-party mail relay Date: Sat, 05 Apr 2003 02:31:34 GMT Message-Id: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] X-Sender-IP: 209.189.103.195 X-Envelope: [EMAIL PROTECTED] - [EMAIL PROTECTED] X-jf: 20010528, 1:1,2:1,3:0,4:0,ad:0,bo:0,di:1,do:1,he:1,ip:1,us:1 Lines: 14 Content-Type: X-UID: 11462 This is a test of third-party mail relay, generated via the Network Abuse Clearinghouse at http://www.abuse.net. Target host = 206.46.170.44 verizon.net Test performed by [EMAIL PROTECTED] from 209.189.103.195 A well-configured mail server should NOT relay third-party email. Otherwise, the server is subject to abuse by vandals and spammers, and probable blacklisting by recipients of the unwanted third-party e-mail. For information on how to secure a mail server against third-party relay, visit URL: http://www.mail-abuse.org/tsi/. -- end I also tested by the good 'ol telnet to port 25 and type in the commands by hand method. On Friday April 04 2003 04:26 pm, Gene Heskett wrote: Jon; I've sent a nastygram to [EMAIL PROTECTED] in an attempt to get this fixed. We'll see if they use their own list and it bounces. Yup, it did, as did my attempted forward of the bounce message to [EMAIL PROTECTED] regarding it. But a seperate message to postmaster went thru. I've also sent a similar msg, but a bit less nasty to [EMAIL PROTECTED] That one hasn't bounced. Me, a spammer? Thats hillarious. Nosy maybe, a bit of a knowitall too (old farts usually get that way, in case no one has noticed :), but a spammer? Boggles the mind. Good Grief even! Its raining here, sporadicly, and I have to work the graveyard at the transmitter tonight. Its beginning to get the wobblies according to the operators. And I haven't managed to get all the mud off my old 4wd pickup truck from my last trip up there.
Þok olduk ya
merhaba tatlim bana bi iyilik yap buraya gir
Anybody using....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello amanda-users, I'm looking at a Dell PV122t tape library, with the optional barcode reader. According to my contact at Dell: - PV122t is similar to Adic's FASTSTOR 2 Is anyone currently using either of these two tape libraries? These are LTO drives. Thanks in advance JBB - --- Jonathan B. Bayer mailto:[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (MingW32) iD4DBQE+jlp48frsPBZFgFcRAstsAKCmS8KMvFvdq46oATVxVmPeY2kqtwCTBOew jsKR6QZvmh6jzovBN+L4LQ== =+ihg -END PGP SIGNATURE-
