Re: Error message Killed: 9?
On Mon, Aug 18, 2008 at 11:57:43AM -0400, [EMAIL PROTECTED] wrote: which gives me the error Killed: 9 when it terminates. That's not an rsync error, but is likely to be a shell message that says that something else killed rsync. I'd suggest checking the system log files and/or process history files to see if something/someone killed it. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Error message when trying to sync
On Thu 29 Apr 2004, Ryan Holowaychuk wrote: I am getting the following error [EMAIL PROTECTED] etc]# rsync 192.168.100.25::backup You're missing the local target (or source, depending on what you were trying to do). rsync: failed to connect to 192.168.100.25: Connection refused rsync error: error in socket IO (code 10) at clientserver.c(83) Is there actually a rsync daemon running in 192.168.100.25 ? Connection refused generally means that there is no process listening to the TCP port in question (or it's firewalled). What does telnet 192.168.100.25 873 give? Also a connection refused? Then it's not an rsync problem per se. Paul Slootman -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Error message
On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: Hello when i get this message what is wrong: /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be stored in data type Regards Boris Dunno. That error message is not in the rsync source. Since you don't say what platforms are involved, what the commandline or other config info is, the context of the message, or what version of rsync it would be difficult to say. My best guess is that the filename is too long for the destination filesystem but that seems unlikely because rsync creates its own error messages for that. Confirm that you can create a file 10 chars longer than the actual file then try again with more info. -- 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: Error message
The versions of the different machines I use are the initiating machine : Sun 450 Solaris 8 Rsync 2.5.5 The machine that I try to copy from : IBM rs6000 AIX 4.3 Rsync 2.3.1 The command I use is /usr/local/bin/rsync -au -q --stats --progress --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 /diskbackup/kanal1/maximus/ The error message comes when he tries to copy that file mentioned below which is 14GB big it is not the filesystem or the name of the file because it worked with ncftpget. But that program has other problems that I will not mention here. Regards Boris -Original Message- From: jw schultz [mailto:[EMAIL PROTECTED]] Sent: 23. januar 2003 11:34 To: '[EMAIL PROTECTED]' Subject: Re: Error message On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: Hello when i get this message what is wrong: /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be stored in data type Regards Boris Dunno. That error message is not in the rsync source. Since you don't say what platforms are involved, what the commandline or other config info is, the context of the message, or what version of rsync it would be difficult to say. My best guess is that the filename is too long for the destination filesystem but that seems unlikely because rsync creates its own error messages for that. Confirm that you can create a file 10 chars longer than the actual file then try again with more info. -- 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 -- 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: Error message
On Thu, Jan 23, 2003 at 12:36:52PM +0100, Boris Gegenheimer wrote: The versions of the different machines I use are the initiating machine : Sun 450 Solaris 8 Rsync 2.5.5 The machine that I try to copy from : IBM rs6000 AIX 4.3 Rsync 2.3.1 The command I use is /usr/local/bin/rsync -au -q --stats --progress --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 /diskbackup/kanal1/maximus/ The error message comes when he tries to copy that file mentioned below which is 14GB big it is not the filesystem or the name of the file because it worked with ncftpget. But that program has other problems that I will not mention here. Regards Boris You might check the error strings in /usr/include. I haven't either of those systems available to me to check. I can say that a 14GB file may have some issues with the checksum blocksize. With the default blocksize of 700 the file will use some 20 million block checksums which is likely to cause collision problems. Try using --block-size=32768 I can't say that is the problem but even if it isn't a large blocksize is in order. Version 2.5.6 will have an adaptive block-size. -Original Message- From: jw schultz [mailto:[EMAIL PROTECTED]] Sent: 23. januar 2003 11:34 To: '[EMAIL PROTECTED]' Subject: Re: Error message On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: Hello when i get this message what is wrong: /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large to be stored in data type Regards Boris Dunno. That error message is not in the rsync source. Since you don't say what platforms are involved, what the commandline or other config info is, the context of the message, or what version of rsync it would be difficult to say. My best guess is that the filename is too long for the destination filesystem but that seems unlikely because rsync creates its own error messages for that. Confirm that you can create a file 10 chars longer than the actual file then try again with more info. -- 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 -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- 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: Error message
On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer [EMAIL PROTECTED] wrote: +-- | The versions of the different machines I use are the initiating machine : | Sun 450 | Solaris 8 | Rsync 2.5.5 | | The machine that I try to copy from : | IBM rs6000 | AIX 4.3 | Rsync 2.3.1 | | The command I use is | /usr/local/bin/rsync -au -q --stats --progress | --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 | /diskbackup/kanal1/maximus/ | | The error message comes when he tries to copy that file mentioned below | which is 14GB big it is not the filesystem or the name of the file because | it worked with ncftpget. | But that program has other problems that I will not mention here. [...] | On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: | Hello when i get this message what is wrong: | | /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large | to be stored in data type | | Regards Boris [...] +-X8 I have also seen that message with times before 1970. This is the standard text for EOVERFLOW. /Michael -- This space intentionally left non-blank. -- 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: Error message
With file sizes over 2GB I'd suspect problems with 31-bit numbers being returned from stat() et. al. The rsync version you have on AIX is very old, and more recent versions handle large files better. The first thing to do is to upgrade rsync your AIX machine. - Dave On Thu, Jan 23, 2003 at 01:44:42PM +0100, Michael Salmon wrote: On Thursday, January 23, 2003 12:36:52 PM +0100 Boris Gegenheimer [EMAIL PROTECTED] wrote: +-- | The versions of the different machines I use are the initiating machine : | Sun 450 | Solaris 8 | Rsync 2.5.5 | | The machine that I try to copy from : | IBM rs6000 | AIX 4.3 | Rsync 2.3.1 | | The command I use is | /usr/local/bin/rsync -au -q --stats --progress | --rsync-path=/usr/local/bin/rsync maximus:/ptsfs2 | /diskbackup/kanal1/maximus/ | | The error message comes when he tries to copy that file mentioned below | which is 14GB big it is not the filesystem or the name of the file because | it worked with ncftpget. | But that program has other problems that I will not mention here. [...] | On Thu, Jan 23, 2003 at 10:55:32AM +0100, Boris Gegenheimer wrote: | Hello when i get this message what is wrong: | | /PTS.0.db2inst1.NODE.CATN.20030123062324.001: Value too large | to be stored in data type | | Regards Boris [...] +-X8 I have also seen that message with times before 1970. This is the standard text for EOVERFLOW. /Michael -- This space intentionally left non-blank. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- 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: Error Message!!
Almost certainly, something is already using port 873 - probably a previous invocation of rsync --daemon, or you have inetd listening to it already. On a commandline invocation, rsync forks, so invoking it twice in a row without killing the first one or having the first one die, makes the second invocation fail, unless you specify different ports for each one. In this example, rsync is run from inetd, though not active at the moment. Tools@willy /cadappl/encap/packagesnetstat -an |grep 873 *.873*.*0 0 0 0 LISTEN Tools@willy /cadappl/encap/packagesps -ef |grep rsync Tools@willy /cadappl/encap/packagesgrep rsync /etc/services /etc/inetd.conf /etc/inetd.conf:rsync stream tcp nowait root/usr/bin/rsync rsyncd --daemon /etc/services:rsync 873/tcp rsyncd # rsync daemon Good luck. Tim Conway [EMAIL PROTECTED] 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), .\n ' There are some who call me Tim? David Nickel Jr. [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/11/2002 08:49 AM To: Rsync Mailing List [EMAIL PROTECTED] cc: (bcc: Tim Conway/LMT/SC/PHILIPS) Subject:Error Message!! Classification: When rsync starts I get the following messages in my log file Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync: bind failed on port 873 Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync error: error in socket IO (code 10) at socket.c(361) Anybody know what might be causing this? David
RE: Error Message!!
Well, there you go. rsyncd is already set up on your system. You don't run rsync, inetd does. The way it's set up makes it nice for testing, too, as you just edit the conf file and test it. If this is, in fact, another installation of rsyncd, which you shouldn't mess with, you'll have to call rsync --daemon with --port=something and --config-file=something to use your alternate setup. If, on the other hand, this is your installation, but you wish to manually start rsync, you'll have to comment out (or delete) the rsync line in /etc/inetd.conf and HUP inetd. What you've go, however, is better, in my opinion. The doc you reference describes a directly-run rsyncd. If you did your install from that, you wouldn't have done the inetd.conf setup, so it looks like you've got a previous setup on your system. If it's your system now, just edit /etc/rsyncd.conf as needed. changes are instantaneous, affecting subsequent calls to the daemon. test = rsync localhost:: should list your modules. Tools@willy /users/Toolsgrep \\[ /etc/rsyncd.conf [big] [big1] [ToolSyncModules] Tools@willy /users/Toolsrsync localhost:: big big1 ToolSyncModules Tools@willy /users/Tools This way, rsyncd also doesn't take any resources until it's invoked. Tim Conway [EMAIL PROTECTED] 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), .\n ' There are some who call me Tim? David Nickel Jr. [EMAIL PROTECTED] 01/11/2002 09:41 AM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: Subject:RE: Error Message!! Classification: I am falling this article http://www.freebsddiary.org/rsync.php on installing and configuring rysnc to mirror the web directories of my two web servers. here is the output netstat -an |grep 873 tcp4 0 0 *.873 *.* LISTEN tcp46 0 0 *.873 *.*LISTEN grep 873 /etc/services rsync 873/tcp # Rsync Daemon grep rsync /etc/inetd.conf rsync stream tcp nowait root/usr/local/bin/rsync rsyncd --daemon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, January 11, 2002 11:32 AM To: David Nickel Jr. Subject: RE: Error Message!! That's why i included the part about indetd.conf and services. Most likely, your inetd is configured to handle port 873. The fact that you have two listeners on 873 tell me, however, that it may not be for rsync, as rsync is a TCP-only application, and only one thing can have a port/protocol listener open, so the other port 873 you see is probably something listening on UDP, else, you're seeing a listener and a connection. lsof and some versions of fuser can be used to determine what is using a port. poke around the man pages to find it. If those aren't available, send me the output of netstat -an |grep 873;grep 873 /etc/services and if there's something found in services, grep first word on the line from services /etc/inetd.conf Tim Conway [EMAIL PROTECTED] 303.682.4917 Philips Semiconductor - Longmont TC 1880 Industrial Circle, Suite D Longmont, CO 80501 Available via SameTime Connect within Philips, n9hmg on AIM perl -e 'print pack(, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), .\n ' There are some who call me Tim? David Nickel Jr. [EMAIL PROTECTED] 01/11/2002 09:19 AM To: Tim Conway/LMT/SC/PHILIPS@AMEC cc: Subject:RE: Error Message!! Classification: Thanks for the info. I used netstat there are two occurances of port 873 listening... how do I kill them. When I grep ps I rsync is not running.. David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, January 11, 2002 11:16 AM To: David Nickel Jr. Cc: Rsync Mailing List Subject: Re: Error Message!! Almost certainly, something is already using port 873 - probably a previous invocation of rsync --daemon, or you have inetd listening to it already. On a commandline invocation, rsync forks, so invoking it twice in a row without killing the first one or having the first one die, makes the second invocation fail, unless you specify different ports for each one. In this example, rsync is run from inetd, though not active at the moment. Tools@willy /cadappl/encap/packagesnetstat -an |grep 873 *.873*.*0 0 0 0 LISTEN Tools@willy /cadappl/encap/packagesps -ef |grep rsync Tools@willy /cadappl/encap/packagesgrep rsync /etc/services /etc/inetd.conf /etc/inetd.conf:rsync stream tcp nowait root/usr/bin/rsync rsyncd --daemon /etc/services:rsync 873
