Re: [Proftpd-user] mod_sql backend error: could not lookup local user ID

> Below are the relevant configuration fragments we use. 

Thanks!

Does your configuration use "DefaultRoot ~" or somesuch for your logins
as well?

The "could not look up local user ID" error string is coming from libpq,
the Postgres client library.  There are only a few places where this
string is used in their source code, e.g.:

  https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/interfaces/libpq/fe-auth.c;h=f4397afc64901bd30bdfafb7489e544e4d078def;hb=HEAD#l1055

In all the cases I found, the libpq code is attempting to resolve the
UID using the system files (such as /etc/passwd) to a name.  If this
happens _after_ the initial authentication has succeeded, AND a
chroot(2) has occurred, then those attempts to resolve the UID will
fail.  (And perhaps that is where the SIGSEGV ("signal 11") happens as
well; many libraries do not react well to operating in a chroot.)

Thus if you *are* using "DefaultRoot ~", as an experiment, you might
disable that and see if it helps/changes your use case.

In the mean time, I'll be trying to reproduce this behavior locally;
there may be _other_ issues involved that lead to the problematic
behavior.

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