rsync 2.4.6 hanging on HPUX11 only over firewall.
We are running rsync 2.4.6 on HPUX-11and using it to push a document-root from a staging area to several servers running rsync in daemon mode. The rsync client syncs successfully to modules on the same server and to most other machines, but hangs when trying to syncronise across a firewall (from SECURE zone to DMZ) (The firewall port IS OPEN!!) During a normal release where there are rougly less than 200 changed files the syncronisation across the firewall runs fine. However it hangs when we try and sync the entire document-root ( or a large subset of it). It appears to wait for several minutes with no new messages in the logs and no packets being exchanged. Eventually it may carry and then hang on another file. After spending 2 days trying to compile 2.5.5 and then finding it didn't work at all ( my memory tells me that it was an error at line 150 of io.c ) we are not keen on moving up to 2.5.5 just yet! I've looked through the mailing list archives and found Wayne Davison's rsync-nohang.patch was suggested to fix similar problems, but this seems to be available for the 2.5.X releases. We are interested in finding out whether the wayne-nohang patches can be applied to 2.4.6. How widely has this patch been implemented, and has anyone found any problems with it? Do people think it is likely to solve our problems? What is the basic idea behind how it solves the problem? Also has anyone found any problems with rsyncing through firewalls where they haven't had the problem for the same files where there is no firewall? Unfortunately as the problems we have are only exhibiting themselves on our production servers we very limited by what diagnostics we are allowed to run and we havent managed to get the same symptoms to exhibit themselves on our (supposedly identical) test machines. I know theres a lot of questions here, but I have spent a good deal of time trying to work out the issue and have hit a bit of a brick wall, so any comments and suggestions would be greatly appreciated. Regards Mark Hyde - Get an SMS alert to your mobile every time you get an email. That's ANY mobile phone. Register for FREE with t-email at www.t-email.co.uk to access your email and contacts via web and WAP - -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync 2.4.6 hanging on HPUX11 only over firewall.
On Mon, Dec 09, 2002 at 01:49:40PM +, rsyncuser wrote: We are interested in finding out whether the wayne-nohang patches can be applied to 2.4.6. My older patches for 2.4.6 had got moved aside after they got incorporated into the main distribution. However, I just put them back in their original spot so they can be accessed again. The most important patch was the simplest: http://www.clari.net/~wayne/rsync-nohang1.patch This patch ensures that data coming from the generator to the sender does not overflow and block during the final phase of the transfer on the sending side (but not necessarily at the final file, due to the buffering on the outgoing connection). The current code waited around for the remote process to end without reading the incoming data stream, which was a very bad idea if the -v option was turned on. The second patch fixed a much rarer bug -- one that should only get tickled if a good number of the files fail to transfer correctly on the first try and need to be resent: http://www.clari.net/~wayne/rsync-nohang2.patch An older version of this patch was included in the Red Hat sources for a while, so it was pretty widely tested: http://www.clari.net/~wayne/old/rsync-nohang.patch (Note that this patch contains the nohang1 patch as well.) The reasoning behind this patch is that there is a data channel from the receiver to the generator that tells it what files to retry. This data channel is left totally unread until all files are handled in pass 1. This means that it can block if enough files need to be resent. My patch keeps this data channel clear by reading it whenever data appears and setting flags on what files to resend during the retry phase. I'm thinking about writing a new patch for the latest rsync that causes these need-to-retry files to be immediately resent by the generator to the sender instead of buffering them (with proper signaling to ensure that retry files get their alternate block-sizes set). Perhaps this solution would finally allow this bug to be put to rest (since it's not yet fixed in the main code). ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync stoped syncing
On Mon, Dec 09, 2002 at 04:36:41PM +0100, Markus Lamers wrote: rsync -auvxz --delete --exclude-from /root/.rsync/home-daily.exc /home slave:/ I suspect the home-daily.exc file is at fault. What does it contain? ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
RSync on Netware
Hello, I have ported rsync 2.5.5 to Netware and would like to, at least, contribute the binary so that people can download it. It says on the website to use the bug tracking system to do this, but since that isn't working, I thought I would try this. Thanks for any help or direction. Lee -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
when using --backup-dir: why not make_bak_dir() . . .
here (in keep_backup())?
--- backup.c.orig Mon Dec 9 17:02:36 2002
+++ backup.cMon Dec 9 17:03:50 2002
@@ -273,6 +273,7 @@
/* move to keep tree if a file */
if(!kept) {
+ make_bak_dir(fname,backup_dir);
if (!robust_move (fname, keep_name))
rprintf(FERROR, keep_backup failed %s - %s : %s\n,
fname, keep_name, strerror(errno));
this reconstructs parent directory permissions more in keeping with
my (humble) expectations, in addition to being consistent with the
way all ~S_IFREG links' parents are produced
just curious
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: SPAM on List...
On 9 Dec 2002, John E. Malmberg [EMAIL PROTECTED] wrote: If it was on any of the reputable blocking lists, I would not be able to receive any of the SAMBA lists, and you would be getting the bounces. It has since been removed from some of them. I.P. based blocking has shown to be the only thing that motivates some domains to act on abuse reports. I really don't care about abuse reports anymore. There is an inexhaustible supply of other spam sources. Desirable as it may be to have ISPs behave properly, it will not reduce the amount of spam. And the bounce message can contain an alternate contact means such as a web form if someone needs a white-listing. A major goal of this exercise is to reduce or eliminate the number of messages that require manual handling because they waste admin time, and they are often dropped. Our previous experience was that IP blacklists have significant false-positive and false-negative rates. In addition, IP blacklists seem to often go mad when the admins start pursuing a campagin against some ISP in a way that does not agree with our goals. For example, the previously-reputable ORBS server blacklisted most of Australia a few years ago. Basically I want the decisions to be made by samba team admins, not by other people. Some time last fall apparently Korea passed an OPT-OUT with the equivalent of ADV in the headers law. Right after that, list that I subscribe to at a major university went from 2 spams a week to over 8 spams a day. 99% from Korea. We no longer accept any mail from Korea. :-( Now the other thing to consider is that when the filter makes a mistake and deletes a legitimate message, it is quite a while before the sender figures out, if at all that the message did not get through. Our filter sends intelligible, actionable bounce messages. This is an enormous improvement of the previous system, which said something like error 10. If the message is bounced, the sender knows immediately, and can use the alternate contact information, such as a web form to request a whitelisting. As RFC 2822 requires, mail to postmaster is not filtered, and is read by a human. People can report problems there. They also know that there is probably a problem with their ISP or with the particular block list, and they have the information needed to fix it. That's bogus. If my ISP is blocked it is very difficult for me to change -- at home I am on a 12 month contract with my DSL provider, for example. Even if I did move, it's very unlikely that my leaving would persuade them to change/enforce their AUP. People with business hosting are in a even more difficult situation. Filtering makes spam your problem. Using a blocking list makes spam the problem of the ISP sending the spam. Eventually almost noone will accept e-mail from them, either from local blocking lists, or public ones. You describe a long-term solution in which spam-friendly ISPs are gradually ostracised. I'm not quite sure I believe you that there is a clear distinction, that bonafide ISPs are really able to stop spam, and that being ostracised will ever really cut them off. But regardless, these are long-term, global measures.What I care about is reducing admin load and spam transmission on samba.org right now. Our bogofilter setup seems to be doing *extremely well* at just that; I can see it catching many more messages and getting far fewer false positives before, and it is no longer necessary to clear queues by hand. I looked through the queue when I installed it and there were many posters who just happened e.g. to be from China and whose messages were basically dropped. Unless people have specific complaints about the new setup I intend to keep going along this path. -- Martin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: SPAM on List...
Martin Pool wrote: You describe a long-term solution in which spam-friendly ISPs are gradually ostracised. I'm not quite sure I believe you that there is a clear distinction, that bonafide ISPs are really able to stop spam, and that being ostracised will ever really cut them off. But regardless, these are long-term, global measures. Unfortunately it does look like long term measures, but I have two postmasters (unpaid volunteers) that can keep their domains very spamfree by two different methods of blocking list maintenance. Both were motivated mainly by bandwidth costs in their methods. But I can not second guess your duties and resources. What I care about is reducing admin load and spam transmission on samba.org right now. I understand. We both have our opinions on the matter. Our bogofilter setup seems to be doing *extremely well* at just that; I can see it catching many more messages and getting far fewer false positives before, and it is no longer necessary to clear queues by hand. I looked through the queue when I installed it and there were many posters who just happened e.g. to be from China and whose messages were basically dropped. Unless people have specific complaints about the new setup I intend to keep going along this path. I will agree that the SAMBA lists are being kept more spam free than some of the other mail servers that I get e-mail on. And while you are saying that you are not in favor of using blocking lists, you are blocking Korea by some method, but that could be just something that bogofilter has figured out. It is your servers and your decisions on how to allocate your resources. No spam blocking method is 100%. And I am not complaining about your efforts. I was just posting some methods of spam blocking in use, and of course my bias opinions on them. And as before, unless specifically addressed to on the subject, I do not intend to post further on this topic on this list. -John [EMAIL PROTECTED] Personal Opinion Only -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
include-exclude patterns
Hi, I just subscribe to ask you a question about patterns in exclude-include files. I just want some folders to be rsynced to a remote machine. What I tried is : IncludeFile - /etc/ /var/lib/zope/ - /* --- result of $$ rsync -avvrn --delete --delete-excluded --include-from=/backup-include -e ssh / /backup is expand file_list to 4000 bytes, did move including directory etc because of pattern /etc/ excluding directory usr because of pattern /* excluding directory bin because of pattern /* excluding directory var because of pattern /* excluding directory boot because of pattern /* excluding directory dev because of pattern /* excluding directory home because of pattern /* excluding directory lib because of pattern /* excluding directory mnt because of pattern /* excluding directory proc because of pattern /* excluding directory root because of pattern /* excluding directory sbin because of pattern /* excluding directory tmp because of pattern /* excluding directory floppy because of pattern /* excluding directory cdrom because of pattern /* excluding directory initrd because of pattern /* done What about /var/lib/zope/ ? I lost my afternoon on this Could you explain me what I am missing ? thanks -- marco -- Clé PGP publique : https://iftbqp.mine.nu/marco.asc -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: include-exclude patterns
On Tue, Dec 10, 2002 at 12:08:54AM -0500, marco wrote: Hi, I just subscribe to ask you a question about patterns in exclude-include files. I just want some folders to be rsynced to a remote machine. What I tried is : IncludeFile - /etc/ /var/lib/zope/ - /* --- result of $$ rsync -avvrn --delete --delete-excluded --include-from=/backup-include -e ssh / /backup is expand file_list to 4000 bytes, did move including directory etc because of pattern /etc/ excluding directory usr because of pattern /* excluding directory bin because of pattern /* excluding directory var because of pattern /* excluding directory boot because of pattern /* excluding directory dev because of pattern /* excluding directory home because of pattern /* excluding directory lib because of pattern /* excluding directory mnt because of pattern /* excluding directory proc because of pattern /* excluding directory root because of pattern /* excluding directory sbin because of pattern /* excluding directory tmp because of pattern /* excluding directory floppy because of pattern /* excluding directory cdrom because of pattern /* excluding directory initrd because of pattern /* done What about /var/lib/zope/ ? I lost my afternoon on this Could you explain me what I am missing ? You forgot to include /var/ and /var/lib/ so it never even sees /var/lib/zope/ -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync stoped syncing
Am Mon, 2002-12-09 um 18.37 schrieb Wayne Davison: Hi Wayne, On Mon, Dec 09, 2002 at 04:36:41PM +0100, Markus Lamers wrote: rsync -auvxz --delete --exclude-from /root/.rsync/home-daily.exc /home slave:/ I suspect the home-daily.exc file is at fault. What does it contain? As I already said .. it worked in the beginning. The file only contains the following two lines: oracle/ labtimer/bin/ ..wayne.. kind regards Markus -- Markus Lamers [EMAIL PROTECTED] Labor Prof. Seelig Kollegen -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
