Logging problem

[jw schultz]

On Tue, Aug 05, 2003 at 01:19:43PM +0200, René van der Kroft wrote:
> At 01:04 30-7-2003 -0700, you wrote:
> 
> >> The follwing error showed up today in the logfile:
> >>
> >> Received disconnect from IP: 2: fork failed: Resource temporarily
> >> unavailable^M
> >> rsync: connection unexpectedly closed (0 bytes read so far)
> >> rsync error: error in rsync protocol data stream (code 12) at io.c(150)
> >> _exit_cleanup(code=12, file=io.c, line=150): about to call exit(12)
> >
> >You have run out of a system resource on the server.  I'd
> >suggest you look in the system logs.
> 
> 
> Today I received the error again:
> 
>         Received disconnect from IP: 2: fork failed: Resource temporarily 
> unavailable
> 
>         rsync: connection unexpectedly closed (0 bytes read so far)
>         rsync error: error in rsync protocol data stream (code 12) at 
> io.c(150)
>         rsync error: partial transfer (code 23) at main.c(578)
> 
> I've checked the system logs to check if the system was out of resouces but 
> I can't find anything.
> Is there's something else what it could be?

That message is not coming from anywhere in rsync.  This
must be coming from a library.  I notice a "^M" on the end
of it.  Either the other end is windows or this message has
been cooked (stty).  

I cannot say what resource is temporarily unavailable.  It
might have run out of pids or, more likely, memory.  In
either case if fork failed rsync will quickly exit freeing
up resources.  If you feel daring you could run a fork bomb
to confirm that it is fork hitting a limit.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt