Article delegate-en/3404 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: delegate crashing
21 Jul 2006 00:22:44 GMT (Yutaka Sato)
The DeleGate Project


In message <> on 07/20/06(17:31:53)
you info <> wrote:
 |Sorry to bother you at this address, but every mail sent to 
 | is refused with the error below.
 |Failed to deliver to ''
 |SMTP module(domain reports:
 |  message text rejected by
 |  554 Forbidden by rule

This forum does not accept messages from addresses which seem not of
a human, as "info@..".  Sorry for the inconvenience.
I'm sending this reply message to the forum.

 |------ delegate error report follows ---
 |We use delegate internally to proxy two dozen or so of clients. We

You seem using DeleGate as a proxy for HTTP on Windows, setting
TIMEOUT=standby with the value larger than 60seconds, is this right?

 |upgraded from 9.0.5 to 9.2.3 and now experience intermittent aborts (see
 |log excerpt below).
 |Apparently Delegate crashes sometimes when accessing gmail.

What does this "abort" and "crash" mean?

 |Thank you very much,
 |I have just tried 9.0.6 - it crashes.  9.0.5 seems the last release
 |without this problem.
The cause of "VStr overflow" is clear.  It is because the buffer of
32 bytes is not enough for "HUPENV=x/x/x/x/y1,y2,y3,y4,...".
This is a string to represent and inherit the socket environment on
restart by (possibly emulated) SIGHUP on Windows.
So I expanded the buffer, nchild[32] in delegated.c:sigHUPX(), and
uploaded the expanded version as

I suppose this is caused when you specify multiple ports to accept clients
as "-Pp1,p2,p3..."

The problem is why this "kill Frozen Sticky" is caused to emulate SIGHUP.
I think the LOGFILE of your DeleGate, if it's not disabled, will show the
reason.  Especially, lines including a word "Sticky" will give us great

In DeleGate/9.0.6, I implemented "shared lock" on Windows and applied
it to the mutual exclusion for access to the socket (the socket to accept
the clients).  Apparently it is the direct trigger of "kill Frozen Sticky"
on Windows, which might be activated with long TIMEOUT=standby or so...

 (long TIMEOUT=standby ?) -> (shared lock on Win) -> "kill Frozen Sticky"
                    -> (SIGHUP(0) in service on Win) -> "VStr overflow"

Anyway I coped with large TIMEOUT=standby value in 9.2.4-pre1 and hope
it solves your problem.

 |07/18 16:52:31 [278]-P192.168.101.4:8119 E-F: kill Frozen Sticky*8 (61s)
 |07/18 16:53:07 [278]-P192.168.101.4:8119 VStr overflow in Xsprintf
 |(9.2.3:delegated.cpp:1197) 4/4/32 156A3B4-156A3D0-156A3D3 (19) ,%d

  9 9   Yutaka Sato <>
 ( ~ )  National Institute of Advanced Industrial Science and Technology
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]