RE: [Proftpd-user] Problem with mod_ls while chrooted

[Rick C. <rc...@dw...>]

> -----Original Message-----
> From: pro...@li...
> [mailto:pro...@li...]On Behalf Of TJ Saunders
> Sent: Monday, November 29, 2004 3:35 AM
> To: pro...@li...
> Subject: RE: [Proftpd-user] Problem with mod_ls while chrooted
>
>
>
> > Attached is an strace of that process, as well as proftpd
> logging at debug
> > level 5. You will see the segfault happens at the point that
> the command is
> > handed off to mod_ls.
>
> To be accurate, the segfault occurs some time after proftpd prints that
> debug line about dispatching to mod_ls.
>
> Would it be possible to get a backtrace, as described here:
>
>   http://www.castaglia.org/proftpd/doc/devel-guide/devel/debugging.html
>
> Also, just an FYI, this issue is currently being tracked in Bugzilla:
>
>   http://bugs.proftpd.org/show_bug.cgi?id=2524
>

I had followed the old ref# referenced in the above bug and installed the
latest (development even) glibc and that did not help.

I just recompiled per the above instructions and ran the backtrace. The
relevant parts are:

ccfsrv01 - ProFTPD 1.2.10 (stable) (built Mon Nov 29 21:43:52 EST 2004)
standalone mode STARTUP
ccfsrv01 (srv2[192.168.1.1]) - FTP session requested from unknown class
ccfsrv01 (srv2[192.168.1.1]) - FTP session opened.
ccfsrv01 (srv2[192.168.1.1]) - USER ccfweb: Login successful.
ccfsrv01 (srv2[192.168.1.1]) - Preparing to chroot() the environment, path =
'/var/www/html/ccfweb'
ccfsrv01 (srv2[192.168.1.1]) - Environment successfully chroot()ed.
ccfsrv01 (srv2[192.168.1.1]) - mod_cap/1.0: capabilities '=
cap_net_bind_service+ep'
ccfsrv01 (srv2[192.168.1.1]) - Entering Passive Mode
(207,185,176,243,134,237).

Program received signal SIGSEGV, Segmentation fault.
0x00639b0c in open_path () from /lib/ld-linux.so.2
(gdb) backtrace
#0  0x00639b0c in open_path () from /lib/ld-linux.so.2
#1  0x0063a2b5 in _dl_map_object () from /lib/ld-linux.so.2
#2  0x00742e66 in dl_open_worker () from /lib/tls/libc.so.6
#3  0x00000000 in ?? ()
(gdb)

I am running this via an IpSec tunnel BTW. Just to be sure, I ran yum again
this evening and found and installed updates for glibc (and other glibc
related packages) and updated everything related to glibc, rebuild (make
clean, etc) proftpd and got the same results as above.

Rick




--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.