Re: [Proftpd-user] Every transfer logged with: "error adding 'XXX' to config ID table: No space left on device

TJ Saunders <[email protected]>
Newsgroups gmane.network.proftpd.user
Message-ID <1481903209.2031585.821278041.385C6ED7@webmail.messagingengine.com>
> If I am barking in the wrong place just yell at me, but I am having a
> problem with a stock Debian Proftpd server
> 
> Every transfer is logged in proftpd.log with "error adding 'XXX' to
> config ID table: No space left on device" (XXX being the file
> transferred)
> 
> Any idea where I find information about the 'config ID table' mentioned
> in the error? I have checked the source files and the config ID table is
> only mentioned when it can't be emptied or removed (in dirtree.c)

This error is somewhat misleading, and has nothing to do with disk
space.

Internally, ProFTPD maintains an in-memory table of configuration
directives.
For comparison purposes when merging bits of configuration together
(e.g.
when handing .ftpaccess files), each entry in that table is assigned a
numeric
ID.This table is that "config ID table" mentioned in the log message.

The in-memory table implementation that ProFTPD uses sets a limit on the
maximum
number of entries in the table, to prevent memory leaks/undue memory
usage.  The
default max number of entries in a table is 8192.  And when that limit
is reached,
attempting to add more entries to the table fails with the ENOSPC errno
value
("No spaceleft on device").

There a couple of different things that, to me, the logging behavior you
encounter suggest that we should do.  First, that particular error
message, while
logged at the DEBUG0 log level, should probably be made even less
verbose, such as
DEBUG9 (or maybe even just a TraceLog message). The error in question is
more
benign than anything else; it will not cause the file transfer to fail. 
In addition,
the maximum number of entries for that config ID table should be made
higher, to
decrease the chance of the error being logged.

I'll make the above tweaks in the master branch today.

All that said, I would be curious to hear more about your particular
setup, that
would lead to the log message in the first place.  Are you using
.ftpaccess files?
Do you only see this message for particularly long-running sessions
(i.e. only
after a certain number of file transfers)?

Cheers,
TJ

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.