Error Message!!

tim.conway at tim.conway at
Sat Jan 12 03:16:09 EST 2002

Almost certainly, something is already using port 873 - probably a 
previous invocation of rsync --daemon, or you have inetd listening to it 
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 at willy
/cadappl/encap/packages>netstat -an |grep 873
      *.873                *.*                0      0     0      0 LISTEN
Tools at willy
/cadappl/encap/packages>ps -ef |grep rsync
Tools at willy
/cadappl/encap/packages>grep 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 
Good luck.

Tim Conway
tim.conway at
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(nnnnnnnnnnnn, 
".\n" '
"There are some who call me.... Tim?"

"David Nickel Jr." <dnickel at>
Sent by: rsync-admin at
01/11/2002 08:49 AM

        To:     "Rsync Mailing List" <rsync at>
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        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?

More information about the rsync mailing list