similar to: wait4ifup

Displaying 20 results from an estimated 80000 matches similar to: "wait4ifup"

2004 Apr 23
1
Rsync Log Error
I have the latest rsync running on mandrake official 10. At 2:30 I run rsync --daemon from cron to run an offsite backup for all my customers. At 8:00 I run killall rsync. However my log files show the following: 2004/04/20 02:00:00 [2702] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20 02:00:59 [2707] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20
2004 Apr 22
2
Error?
I have the latest rsync running on mandrake official 10. At 2:30 I run rsync --daemon from cron to run an offsite backup for all my customers. At 8:00 I run killall rsync. However my log files show the following: 2004/04/20 02:00:00 [2702] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20 02:00:59 [2707] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20
2002 Mar 21
2
Start Rsync Error
Hi, I have installed rsync-2.4.6 version on Linux Redhat 6.2 (Kernel-2.2.14-5.0), after installed I tried to test the rsh and run "rsh remotehost /bin/true > out .dat". But it failed the error message was "Permission denied". I checked the permission all was okay, I forgot the rsh/csh methods and replaced by RSYNC_PROXY. Finally, it failed again. I would like to know that
2004 Oct 05
6
group change causing failure
OK, I searched through the archives and didn't find anything so I must be doing something stupid. I just compiled 2.6.3 and am trying to get it to run on linux 2.6.8.1 kernel with a more or less fedora core2 environment. I was trying between two systems but I have narrowed it down to what I believe is a pretty simple case. Here is my setup/test: Last login: Mon Oct 4 19:30:49 2004
2004 Dec 20
1
can not start rsync, address already in use
I am running the following command to start the rsync server manually rsync --daemon Then I am getting the following error 2004/12/20 22:41:40 [3396] rsyncd version 2.5.7 starting, listening on port 873 2004/12/20 22:41:40 [3396] rsync: open inbound socket on port 873 failed: Addres s already in use 2004/12/20 22:41:40 [3396] rsync error: error in socket IO (code 10) at socket.c (394) Can anybody
2004 May 04
2
rsync 2.6.2 --daemon Problem
Hi, I've a problem with rsync 2.6.2 and the daemon. I've installed it precisly as I did with 2.6.0 (I've tried before with 2.6.1 and was having the same problems as now with 2.6.2). When I try to a rsync --daemon command the rsync offcourse finishes, but in the log file it says 2004/05/04 21:15:10 [22369] rsyncd version 2.6.2 starting, listening on port 873 2004/05/04 21:15:10
2002 Jan 12
2
Error Message!!
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
2008 Aug 05
1
rsync problem after ssh upgrade
Hello. In my setup I collected logs from many hosts using ssh + rsync. It worked fine untill I upgraded OpenSSH from version 5.0p1 to 5.1p1 on those hosts running Slackware Linux. After upgrade nothing works as before. When I try to get logs connection breaks with the following message in syslog on the server side: Aug 4 15:34:44 srvhost sshd[8130]: Accepted publickey for user from
2006 Nov 20
1
Can't Start Rsync
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I run |#rsync --daemon and get this in /var/log/messages| #skywalker rsyncd[5522]: unable to bind any inbound sockets on port 873 #Nov 20 17:30:20 myserver rsyncd[5522]: rsync error: error in socket IO (code 10) at socket.c(482) [receiver=2.6.8] I run it on FreeBSD 6.1. Does anyone know what does the problem relate to? -----BEGIN PGP SIGNATURE-----
2004 Jun 25
4
A question about connection refused
I install rsync in computer and run it as a daemon successfully, but when I run rsync command on another end to connect it. There is a error. The output is : opening tcp connection to 192.168.0.43 port 873 rsync: failed to connect to 192.168.0.43: Connection refused _exit_cleanup(code=10, file=clientserver.c, line=93): entered rsync error: error in
2005 Sep 27
3
"missing secret for user" using cygwin rsync on Windows XP Home
Hi, I'm trying to set up rsync to allow me to backup a number of Windows machine to a Windows XP Home server using Nasbackup. I can get rsync working fine but have been struggling for days to get user authentication working. /var/log/rsyncd.log 2005/09/27 13:46:37 [1352] rsyncd version 2.6.6 starting, listening on port 873 2005/09/27 13:47:50 [4088] auth failed on module modulename from
2005 Jun 07
2
@ERROR: auth failed on module
Hi, My nightly rsync jobs recently began to fail. I don't recall making any modifications to the rsync config files or upgrading rsync. Below is the error I receive when I try to rsync the home directory of serverA to serverB. Is there anything obviously wrong? Thanks. serverA rsync # rsync -arczv --delete --password-file=/etc/rsync/rsync.password /home 192.168.1.4::home @ERROR: auth failed
2004 May 09
2
[BUG] rsync 2.6.2
After upgrade from previous version I can't run rsync. 2004/05/09 10:40:54 [18630] rsyncd version 2.6.2 starting, listening on port 873 2004/05/09 10:40:54 [18630] rsync error: error in socket IO (code 10) at socket.c(466) strace shows that there is problem with listen() I've found patch on this lists: --- rsync-2.6.2/socket.c.orig 2004-05-08 23:25:11.979473336 +0200 +++
2004 Aug 16
2
[LLVMdev] cvsweb content is out-of-date
And here's why: > rsync -az --delete --exclude='#*' --stats --bwlimit=256 rsync://llvm.cs.uiuc.edu/LLVM/ /home/llvm/cvs > rsync: failed to connect to llvm.cs.uiuc.edu: Connection refused > rsync error: error in socket IO (code 10) at clientserver.c(83) John, can you please look into this? Most likely the xinetd needs to be restarted.I'm not sure when it started failing,
2002 Apr 16
3
Update: WARNING: --rsh or -e option ignored when connecting to rsyncdaemon]
the --pasword-file= option is only for passing a password to a rsync server, as you have set up with the rsync --daemon process. Your rsyncd.conf file is fine, too. The problem is that you aren't calling your rsync daemon from your commandline. You are trying to connect via rsync to host as axlink and start a 'rsync --sender' process, to transfer data within the ssh process.
2002 Aug 27
5
rsync: push_dir TESTDIR: No such file or directory
Hi all. I'm getting the following error when using rsync: nice -n 20 rsync -e "ssh -p30000" --recursive --verbose --verbose --checksum --times --modify-window 2 --port=31000 --dry-run /cygdrive/f/bkp/Doc/Builds/Buildsheets/ MYUSERNAME@MY.SERV.ER.IP:TESTDIR opening connection using ssh -p30000 -l MYUSERNAME MY.SERV.ER.IP rsync --server -vvntrc --modify-window=2 . TESTDIR
2004 Aug 16
0
[LLVMdev] cvsweb content is out-of-date
On Mon, Aug 16, 2004 at 09:56:57AM -0700, Reid Spencer wrote: > And here's why: > > > rsync -az --delete --exclude='#*' --stats --bwlimit=256 rsync://llvm.cs.uiuc.edu/LLVM/ /home/llvm/cvs > > rsync: failed to connect to llvm.cs.uiuc.edu: Connection refused > > rsync error: error in socket IO (code 10) at clientserver.c(83) > > John, can you please look
2003 Oct 07
2
error in rsync protocol data stream (code 12) at io.c
List, I am having trouble with a previously working rsync server. Version: > # rsync --version > rsync version 2.5.4 protocol version 26 > Copyright (C) 1996-2002 by Andrew Tridgell and others > <http://rsync.samba.org/> > Capabilities: 64-bit files, socketpairs, hard links, symlinks, > batchfiles, IPv6, 64-bit system inums, 64-bit internal inums
2003 Sep 12
1
rsync logfile - daemon does not log enough
I am running rsync version 2.56 in daemon mode on a server running Redhat 8.0. When I check my log file (located in /var/log/rsyncd.log), the only lines I see have to do with the server starting up, like so: 2003/09/11 16:53:42 [15025] rsyncd version 2.5.6 starting, listening on port 873 I would like to see output relating to connections, usernames etc., so I set up the following rsyncd.conf
2001 Nov 13
2
Ptoblem for update 2.4.1 -> 2.4.6
After installing nevest version of sync 2.4.6 from 2.4.1, sync --daemon wrote to logfile: 2001/11/13 12:27:46 [12261] rsyncd version 2.4.6 starting 2001/11/13 12:27:46 [12261] bind failed on port 873 2001/11/13 12:27:46 [12261] transfer interrupted (code 10) at socket.c(233) sync 2.4.1 worked normally... My question: Where i can find "WATHSNEW" or "CHANGES"