Logs: a thread and a queue for each log; build-time defaults

Once 3proxy runs (after the first configuration is in force, so after a
daemon's fork), each logger has a thread of its own writing from a
queue, and a client never waits for a log: ODBC, RADIUS, a full disk or
a pipe nobody reads hold up only that log's thread.

A queued line is fixed size: the part of struct clientparam logging
reads (everything before the filters: addresses, counters, names and
credentials, which hold no pointer it follows but srv), the time it was
logged, and its text, 256 bytes inline or a copy of its own if longer.
The thread formats it: struct tm is per call now, timechanged() and
dologname() included, and the type's format() takes the time.

minlogqueue (64) slots are allocated as the thread starts and kept,
maxlogqueue (4096) lines are queued at most. A line which finds the
queue full is dropped and counted on the last one queued; once that is
written, "Log X has its queue full, N records dropped" goes to where
errors go. A log which fails is no longer written to the error log
instead: its lines are dropped and counted while it is retried every
minute, and the count is told when it is open again, or when it was
reopened after failed writes.

A service which ended is stopped at once (srvstop(): sockets, listener,
its clients gone), but freed (srvrelease()) through its log's queue,
behind the lines which refer to it and to its configuration: the event
is part of struct srvparam, so a full queue never drops it. logfinish()
writes what is queued, 10 seconds at most, also as 3proxy exits on Unix.
Standalone services write as before, as each line comes.

LOGQUEUEMIN, LOGQUEUEMAX, DEFAULT_MAXCHILD, DEFAULT_POOLMAX,
DEFAULT_POOLTIMEOUT and POOLPERSERVICE (the automatic thread pool cap
for each service, which was 32 in the code) can be set with -D at build
time.

Tests: a log nobody reads (a FIFO) holds no client up, drops past its
queue and says so, and lines queued for a service a reload removed are
written as it formatted them; /dev/full says what it dropped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Vladimir DubrovinandClaude Opus 5.5 committed 2026-10-23 19:41:48 +03:00
1 parent a3c417c82a
commit 2052dc0a4f
13 files changed
+930 -158

No files matched your search

+25 -3
View File
@@ -349,12 +349,23 @@ log or by -l, and shared by every service using it; it is kept
open over a configuration reload while some service still uses
it, and closed once none does. stdout, stderr and syslog are
opened at startup and never closed. rotate and archiver apply
to the file of the last log command. A log which fails to be
written is reopened, and if it cannot be, its records go to
stderr while it is retried every minute. Errors and warnings
to the file of the last log command. Errors and warnings
with no connection go to stderr; after daemon (or as a Windows
service) nothing goes to stdout or stderr: logging to stdout is
none, and errors go to the last log configured. <br>
Once 3proxy runs, each log is written by a thread of its own
from a queue (see <b>minlogqueue</b> and <b>maxlogqueue</b>):
a client never waits for a log, a slow one (ODBC, RADIUS, a
full disk) included. A record which finds the queue full is
dropped. A log which fails to be written is reopened; if it
cannot be, its records are dropped while it is retried every
minute. Each time records are dropped, how many is said where
errors go: &quot;Log <i>name</i> has its queue full,
<i>N</i> records dropped&quot;, &quot;could not be written,
opened again&quot;, &quot;failed&quot;, &quot;is open
again&quot;. A service a reload removed is freed only once the
records logged for it are written. Standalone services write
their log as each record comes. <br>
log command supports same format specifications for filename
template as &quot;logformat&quot; (if filename contains
&acute;%&acute; sign it&acute;s believed to be template). As
@@ -367,6 +378,17 @@ specificators.</p>
<i>&lt;n&gt;</i> <br>
how many archived log files to keep</p>
<p style="margin-left:9%; margin-top: 1em"><b>minlogqueue</b>
<i>&lt;n&gt;</i> <br>
<b>maxlogqueue</b> <i>&lt;n&gt;</i> <br>
The records a log&acute;s queue keeps room for, allocated as
its thread starts (64 by default), and holds at most, records
past it being dropped (4096 by default). Room taken by a burst
beyond minlogqueue is freed as the queue empties. A record
takes about 2 KB. The values of the configuration in force
apply to every log. Other defaults can be given at build time
with -DLOGQUEUEMIN=<i>n</i> and -DLOGQUEUEMAX=<i>n</i>.</p>
<p style="margin-left:9%; margin-top: 1em"><b>logformat</b>
<i>&lt;format&gt;</i> <br>