Re: Which ports to open in which direction...
David Leangen wrote: http://wiki.zmanda.com/index.php/Configuration_with_iptables How does the ip_conntrack_amanda kernel module fits in here? I think that just using that module simplifies a lot of the setup. I'm not sure sure it handles amrecover connections though... -- 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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Verizon subscribers -- off topic
[Off topic] This isn't the first time I'm hit with this nonsense: I can't send mail to a Verizon email address. And I'm surely not alone. http://www.theinquirer.net/?article=23703 Just to let people know (Gene!) that I do send mail to them, I'm not ignoring them. But their provider is ignoring their users. Yes, I did fill out the whitelist request, twice already. Just enough to get one mail pass through, and then a few weeks later, it bounces again. If people with Verizon email addresses want to read my responses, it's time to switch providers. Pfeew, that reliefs the anger a bit... -- 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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * *** ---BeginMessage--- The original message was received at Mon, 5 Dec 2005 14:09:14 +0100 from noir1.be.xplanation.com [192.168.200.151] - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 Email from your Email Service Provider is currently blocked by Verizon Online's anti-spam system... Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block.) - Transcript of session follows - ... while talking to relay.verizon.net.: MAIL From:[EMAIL PROTECTED] SIZE=1966 550 Email from your Email Service Provider is currently blocked by Verizon Online's anti-spam system. The email sender or Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block. 554 5.0.0 Service unavailable Reporting-MTA: dns; smtp.xplanation.com Received-From-MTA: DNS; noir1.be.xplanation.com Arrival-Date: Mon, 5 Dec 2005 14:09:14 +0100 Final-Recipient: RFC822; mindfuq@verizon.net Action: failed Status: 5.0.0 Diagnostic-Code: SMTP; 550 Email from your Email Service Provider is currently blocked by Verizon Online's anti-spam system. The email sender or Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block. Last-Attempt-Date: Mon, 5 Dec 2005 14:09:16 +0100 ---BeginMessage--- [EMAIL PROTECTED] wrote: I started reading the Setup the Backup Client Hosts section of the Amanda docs, which immediately assumes that I have a folder ~dumpuser/. It's telling me to create an .amandahosts file within that directory. Portage did not create any such user. Is this a user that I need in addition to the amanda user? The client and server are the same machine in my case (for now). Just trying to clean up the docs, I can't find the section you mention. Have a look at http://wiki.zmanda.com/index.php/Quick_start . I'm interested in all the fuzzy things left unclear in that doc. -- 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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * *** ---End Message--- ---End Message---
Re: Verizon subscribers -- off topic
On Tue, 6 Dec 2005, Paul Bijnens wrote:
[Off topic]
This isn't the first time I'm hit with this nonsense: I can't send mail to a
Verizon email address. And I'm surely not alone.
http://www.theinquirer.net/?article=23703
Just to let people know (Gene!) that I do send mail to them, I'm not
ignoring them. But their provider is ignoring their users.
Yes, I did fill out the whitelist request, twice already. Just enough
to get one mail pass through, and then a few weeks later, it bounces
again.
If people with Verizon email addresses want to read my responses, it's time to
switch providers.
Pfeew, that reliefs the anger a bit...
I can confirm I cannot send email to Gene from work, but I can from home.
Apparently it's unrelated to the sender address, but related to the outgoing
SMTP server.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
how to dd if=... a chunked dump blob?
Given a whole dump blob that has landed in holding disk, I can look at it (for example, to answer the question Why is that so _big_?) with: dd if=foo.verilab.com._.1 bs=32k skip=1 | tar tfv - | sort +2nr | head This is pretty well documented. What if, instead, my dump blob is chunked, as in this case (1GB chunks): % ls -ltr foo.verilab.com._.__disc1.* -rw--- 1 amanda disk 1073741824 Nov 19 00:39 foo.verilab.com._.__disc1.1 -rw--- 1 amanda disk 123912192 Nov 19 00:40 foo.verilab.com._.__disc1.1.1 I can certainly do the same 'dd if=' game on the initial 1GB chunk, but what if I want to find the biggest thing across the whole blob (2 files in this case)? Thanks, Will
Re: how to dd if=... a chunked dump blob?
I asked: dd if=foo.verilab.com._.1 bs=32k skip=1 | tar tfv - | sort +2nr | head What if, instead, my dump blob is chunked, as in this case (1GB chunks): Alexander Jolk suggested (one of two possibilities): Well, you either do some shell magic: for i in foo.verilab.com._.1*; do dd if=$i bs=32k skip=1; done | tar tvf ... Gerhard den Hollander followed on with: or simply cat foo.verilab.com._.1* | dd bs=32k skip=1 | tar tfv - | sort +2nr | head Alexander's solution definitely works. Gerhard's solution may do something sensible, but I would classify it as wrong -- sorry :-( If each chunk has an Amanda header on it (as it appears it does), then you need something like Alexander's solution to strip them off. With Gerhard's solution, I get ... % cat *.0* | dd bs=32k skip=1 | tar tfv - | sort +2nr tar: Skipping to next header tar: Skipping to next header ... etc... ... which means 'tar' is having to do some guesswork, which I don't like. The results I'm seeing on my sample run suggest it is *not* skipping to the right place; i.e. the results are wrong. The Jolk way is the best way! Thanks for the useful thoughts, Will
Re: Verizon subscribers -- off topic
On Tuesday 06 December 2005 03:25, Paul Bijnens wrote: [Off topic] This isn't the first time I'm hit with this nonsense: I can't send mail to a Verizon email address. And I'm surely not alone. http://www.theinquirer.net/?article=23703 Just to let people know (Gene!) that I do send mail to them, I'm not ignoring them. But their provider is ignoring their users. Yes, I did fill out the whitelist request, twice already. Just enough to get one mail pass through, and then a few weeks later, it bounces again. If people with Verizon email addresses want to read my responses, it's time to switch providers. We would Paul, if there was another game in town. Whats the header say when its bounced? As a customer, I may be able to stick a brick under one corner of hell after I raise it. Pfeew, that reliefs the anger a bit... Can't say as I blame you, I'm often tempted to share a piece of my mind I can spare, but I've given so much away now I wonder if its beginning to show. :) -- 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.36% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: how to dd if=... a chunked dump blob?
On Tue, Dec 06, 2005 at 03:14:44PM +, Will Partain wrote: I asked: dd if=foo.verilab.com._.1 bs=32k skip=1 | tar tfv - | sort +2nr | head What if, instead, my dump blob is chunked, as in this case (1GB chunks): Alexander Jolk suggested (one of two possibilities): Well, you either do some shell magic: for i in foo.verilab.com._.1*; do dd if=$i bs=32k skip=1; done | tar tvf ... Gerhard den Hollander followed on with: or simply cat foo.verilab.com._.1* | dd bs=32k skip=1 | tar tfv - | sort +2nr | head Alexander's solution definitely works. Gerhard's solution may do something sensible, but I would classify it as wrong -- sorry :-( If each chunk has an Amanda header on it (as it appears it does), then you need something like Alexander's solution to strip them off. With Gerhard's solution, I get ... % cat *.0* | dd bs=32k skip=1 | tar tfv - | sort +2nr tar: Skipping to next header tar: Skipping to next header ... etc... ... which means 'tar' is having to do some guesswork, which I don't like. The results I'm seeing on my sample run suggest it is *not* skipping to the right place; i.e. the results are wrong. The Jolk way is the best way! AJ's is definitely a correct approach. An unchunked amanda tar dump consists of a long tar file with a 32KB header ||. So it looks like ||-. When it gets chunked an extra header is added to each chunk so it now looks like ||-, ||-, ||-. You could manually remove each header making tmp files of -, - and -, but each would not be a valid, complete, tar file by itself. Some of your archived files would be split by the end of one chunk and the beginning of the next chunk. Thus the skipping to next header (tar header) messages. But you could 'cat' the tmp files together into another big tmp file that would be the entire original tar dump. That could be fed to tar. AJ's nice solution automated the manual steps and eliminated the need for the temp files by piping directly to tar. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Verizon subscribers -- off topic
--On December 6, 2005 10:01:06 AM +0100 Geert Uytterhoeven
[EMAIL PROTECTED] wrote:
On Tue, 6 Dec 2005, Paul Bijnens wrote:
[Off topic]
This isn't the first time I'm hit with this nonsense: I can't send mail
to a Verizon email address. And I'm surely not alone.
http://www.theinquirer.net/?article=23703
Just to let people know (Gene!) that I do send mail to them, I'm not
ignoring them. But their provider is ignoring their users.
Yes, I did fill out the whitelist request, twice already. Just enough
to get one mail pass through, and then a few weeks later, it bounces
again.
If people with Verizon email addresses want to read my responses, it's
time to switch providers.
Pfeew, that reliefs the anger a bit...
I can confirm I cannot send email to Gene from work, but I can from home.
Apparently it's unrelated to the sender address, but related to the
outgoing SMTP server.
Gr{oetje,eeting}s,
Actually verizon can and does block based on a number of different
criteria, just as AOL does, the difference is verizon is completely
non-transparent as to what got you blocked, and who you can contact to get
you unblocked. They also seem to have *no* control over their own
automated systems whereas AOL atleast has some.
Re: Verizon subscribers -- off topic
On Tuesday 06 December 2005 04:01, Geert Uytterhoeven wrote:
On Tue, 6 Dec 2005, Paul Bijnens wrote:
[Off topic]
This isn't the first time I'm hit with this nonsense: I can't send
mail to a Verizon email address. And I'm surely not alone.
http://www.theinquirer.net/?article=23703
Just to let people know (Gene!) that I do send mail to them, I'm not
ignoring them. But their provider is ignoring their users.
Yes, I did fill out the whitelist request, twice already. Just enough
to get one mail pass through, and then a few weeks later, it bounces
again.
If people with Verizon email addresses want to read my responses,
it's time to switch providers.
Pfeew, that reliefs the anger a bit...
I can confirm I cannot send email to Gene from work, but I can from
home. Apparently it's unrelated to the sender address, but related to
the outgoing SMTP server.
I am on the horn with these turkey's right now, and getting a bit of
static.
For everybodies attention, change the address to
[EMAIL PROTECTED]
this will bypass the ALL filtering. I'll see if I can change that in
kmail, but they're saying this will take like 48-72 hours to implement
so its not effective till about friday.
So I'll try and remember to keep things posted here.
It looks like I'll need to resubscribe from the new address, damn!
Oh well, if it works I guess its ok, but having to tell everyone my new
address (the old one will still work too, for those for whom it worked
before) or at least those who cannot send me email. The problem with
that is that if they don't relay through a mailing list such as this
one, I'll not know they are having a problem. A bit like chicken vs
egg...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
[EMAIL PROTECTED]
In personal conversations with technical people, I call myself a
hacker. But when I'm talking to journalists I just say programmer or
something like that. -- Linus Torvalds
--
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.36% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Verizon subscribers -- off topic
On Tuesday 06 December 2005 11:22, Gene Heskett wrote:
On Tuesday 06 December 2005 04:01, Geert Uytterhoeven wrote:
On Tue, 6 Dec 2005, Paul Bijnens wrote:
[Off topic]
This isn't the first time I'm hit with this nonsense: I can't send
mail to a Verizon email address. And I'm surely not alone.
http://www.theinquirer.net/?article=23703
Just to let people know (Gene!) that I do send mail to them, I'm not
ignoring them. But their provider is ignoring their users.
Yes, I did fill out the whitelist request, twice already. Just
enough to get one mail pass through, and then a few weeks later, it
bounces again.
If people with Verizon email addresses want to read my responses,
it's time to switch providers.
Pfeew, that reliefs the anger a bit...
I can confirm I cannot send email to Gene from work, but I can from
home. Apparently it's unrelated to the sender address, but related to
the outgoing SMTP server.
I am on the horn with these turkey's right now, and getting a bit of
static.
For everybodies attention, change the address to
[EMAIL PROTECTED]
this will bypass the ALL filtering. I'll see if I can change that in
kmail, but they're saying this will take like 48-72 hours to implement
so its not effective till about friday.
So I'll try and remember to keep things posted here.
It looks like I'll need to resubscribe from the new address, damn!
Oh well, if it works I guess its ok, but having to tell everyone my new
address (the old one will still work too, for those for whom it worked
c/cannot/can/g
before) or at least those who cannot send me email. The problem with
that is that if they don't relay through a mailing list such as this
one, I'll not know they are having a problem. A bit like chicken vs
egg...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
[EMAIL PROTECTED]
In personal conversations with technical people, I call myself a
hacker. But when I'm talking to journalists I just say programmer
or something like that. -- Linus Torvalds
--
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.36% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
planner timeouts and udp packet size
Hi, I've got this amanda client (server and client at v2.4.5) with a 1.5TB raid splitted/chunked in ~70 DLEs (using gtar) and some of them don't make it to tape as the planner timeouts. Now, would someone be kind enough to jolt my memory as to what is the relationship between UDP packet size and the number/size of DLEs entries along with their exclude list? The FAQ mentions something about this (UDP packet size of 64Kb and results missing) but that might not be quite up to date. This raid partition has been splitted using quite a few 'exclude append ./blah' in the disklist and I wonder if it would be better to have them in a file on the client side rather than explicitely in the disklist file per se. Would that make any difference at all regarding what get stuffed in the UDP packets at the estimate phase -- making them smaller -- so that I wouldn't hit that hard limit? I hope this makes sense :) TIA, jf
diagnosing timeout failure
How do I fix this? It seems to be timing out when it shouldn't. I'm guessing that have somehow screwed up the tape setup or networking. I am trying to backup my Mac OSX server to a tape on my tapehost - an old Sun SparcStation. amcheck runs without errror and everything looks like it will work. It looks to me like sendsize completes OK. Then somehow the Xserver can't seem to communicate. Total bytes written: 12902594560 (12GB, 8.5MB/s) . sendsize: pid 17804 finish time Tue Dec 6 13:30:40 2005 Then amandad seems to be waiting for an ack. amandad: sending REP packet: Amanda 2.4 REP HANDLE 001-00051D30 SEQ 1133892428 OPTIONS maxdumps=1; / 0 SIZE 12600190 amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, retrying amandad: waiting for ack: timeout, giving up! amandad: pid 17803 finish time Tue Dec 6 13:31:30 2005
Re: planner timeouts and udp packet size
On Tue, Dec 06, 2005 at 12:06:19PM -0500, Jean-Francois Malouin wrote: Hi, I've got this amanda client (server and client at v2.4.5) with a 1.5TB raid splitted/chunked in ~70 DLEs (using gtar) and some of them don't make it to tape as the planner timeouts. Now, would someone be kind enough to jolt my memory as to what is the relationship between UDP packet size and the number/size of DLEs entries along with their exclude list? The FAQ mentions something about this (UDP packet size of 64Kb and results missing) but that might not be quite up to date. This raid partition has been splitted using quite a few 'exclude append ./blah' in the disklist and I wonder if it would be better to have them in a file on the client side rather than explicitely in the disklist file per se. Would that make any difference at all regarding what get stuffed in the UDP packets at the estimate phase -- making them smaller -- so that I wouldn't hit that hard limit? From a Dec. 2004 reply by Paul Bijenes: || || The problem seems to be in the reply packet. || || I've already seen problems with a UDP-packet overflow, but that's || unlikely. That problem happened with older versions where the UDP || size was only 8Kbyte or so. Currently it is 64K, but it could be || limited by the OS too, of course. The reply packet is usually larger || than the request packet, because it contains 1 to 3 lines for each || DLE (level 0, current level, current plus 1). || -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Amanda Success
Hello List, After a new admin botched up a migraton, Amanda came through and was able to recover files necessary to repair the damage done. Amrecover went smooth as butter! Many thanks to the Amanda team! -- Jim Summers School of Computer Science-University of Oklahoma -
Re: Amanda Success
2005/12/6, Jim Summers [EMAIL PROTECTED]: Hello List,After a new admin botched up a migraton, Amanda came through and wasable to recover files necessary to repair the damage done.Amrecoverwent smooth as butter!Many thanks to the Amanda team! --Jim SummersSchool of Computer Science-University of Oklahoma-Great. But please don't rant about the new admin. Nobody is perfect.
Re: Amanda Success
On Tuesday 06 December 2005 14:48, Jim Summers wrote: Hello List, After a new admin botched up a migraton, Amanda came through and was able to recover files necessary to repair the damage done. Amrecover went smooth as butter! And I take it said new admin has been suitably introduced to the cluebat? Many thanks to the Amanda team! I'm not that much of a contributor personally, but thanks for the flowers, I'm sure the rest of the group here appreciate them. -- 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.36% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Amanda Success
Thanks. Can you please add your information to the success stories page on the wiki(http://wiki.zmanda.com/index.php/Success_stories)? Any configuration information would help us others confidence to use Amanda. Paddy Amanda Developer On 12/6/05, Jim Summers [EMAIL PROTECTED] wrote: Hello List, After a new admin botched up a migraton, Amanda came through and was able to recover files necessary to repair the damage done. Amrecover went smooth as butter! Many thanks to the Amanda team! -- Jim Summers School of Computer Science-University of Oklahoma - -- Amanda documentation: http://wiki.zmanda.com Amanda forums: http://forums.zmanda.com
Re: how to dd if=... a chunked dump blob?
Alexander Jolk wrote: Will Partain wrote: dd if=foo.verilab.com._.1 bs=32k skip=1 | tar tfv - | sort +2nr | head [...] What if, instead, my dump blob is chunked, as in this case (1GB chunks): Well, you either do some shell magic: for i in foo.verilab.com._.1*; do dd if=$i bs=32k skip=1; done | tar tvf - | ... It will not work if you have more than 10 chunk files because the '*' wildcard will not list them in the correct order. You will have to list them manually. Jean-Louis or you use amrestore on the holding file. Alex
Re: Which ports to open in which direction...
On Tue, Dec 06, 2005 at 10:01:37AM +0100, Paul Bijnens enlightened us: David Leangen wrote: http://wiki.zmanda.com/index.php/Configuration_with_iptables How does the ip_conntrack_amanda kernel module fits in here? I think that just using that module simplifies a lot of the setup. I'm not sure sure it handles amrecover connections though... I just ran amrecover from a client outside my firewall with ip_conntrack_amanda handling everything just fine. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Amanda Success
Updated the wiki at: http://wiki.zmanda.com/index.php/Success_stories#Successful_Restore Hope this is what was needed. If not let me know and I can edit. Thanks again! Paddy Sreenivasan wrote: Thanks. Can you please add your information to the success stories page on the wiki(http://wiki.zmanda.com/index.php/Success_stories)? Any configuration information would help us others confidence to use Amanda. Paddy Amanda Developer On 12/6/05, Jim Summers [EMAIL PROTECTED] wrote: Hello List, After a new admin botched up a migraton, Amanda came through and was able to recover files necessary to repair the damage done. Amrecover went smooth as butter! Many thanks to the Amanda team! -- Jim Summers School of Computer Science-University of Oklahoma - -- Amanda documentation: http://wiki.zmanda.com Amanda forums: http://forums.zmanda.com
