Bug#839880: proftpd-basic: proftpd server instance crashed with signal 11

[Hilmar Preuße]

On 26.12.2017 09:41, Мороз Олег wrote:

Hi Олег,

> Have made changes in
> 
> /etc/security/limits.d/core_dump.conf
> 
> then set path to save code dumps into /tmp
> 
> vniiem at sim-ng-data /tmp % /sbin/sysctl -a -r kernel.core
> kernel.core_pattern = /tmp/core.%e.%p.%t
> kernel.core_pipe_limit = 0
> kernel.core_uses_pid = 0
> 
> Then relogin and reinstall proftpd, tried to login to ftp , but no
> core.dump was generated
> 
So, proftpd seems to trap the SIGSEGV (sig11) and performs a grace
shutdown upon SIG11. I've found [1] giving some hints to debug crash
problems. I've put debug binaries using --enable-devel=stacktrace on
[2]. I've crashed the binaries using a SIGSEGV and found a stack trace
in /var/log/proftpd/proftpd.log:

2017-12-27 21:51:07,528 amd64-sid proftpd[23112] amd64-sid: -----BEGIN
STACK TRACE-----
2017-12-27 21:51:07,528 amd64-sid proftpd[23112] amd64-sid: [0]
/lib/x86_64-linux-gnu/libc.so.6(__select+0x13) [0x7fd99e1c3cc3]
2017-12-27 21:51:07,529 amd64-sid proftpd[23112] amd64-sid: [1]
/lib/x86_64-linux-gnu/libc.so.6(__select+0x13) [0x7fd99e1c3cc3]
2017-12-27 21:51:07,529 amd64-sid proftpd[23112] amd64-sid: [2]
/usr/sbin/proftpd(+0x1a2d0) [0x5559bc50c2d0]
2017-12-27 21:51:07,529 amd64-sid proftpd[23112] amd64-sid: [3]
/usr/sbin/proftpd(+0x1bf2f) [0x5559bc50df2f]
2017-12-27 21:51:07,529 amd64-sid proftpd[23112] amd64-sid: [4]
/usr/sbin/proftpd(main+0x94b) [0x5559bc50ece3]
2017-12-27 21:51:07,529 amd64-sid proftpd[23112] amd64-sid: [5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fd99e0ff561]
2017-12-27 21:51:07,529 amd64-sid proftpd[23112] amd64-sid: [6]
/usr/sbin/proftpd(_start+0x2a) [0x5559bc508daa]
2017-12-27 21:51:07,529 amd64-sid proftpd[23112] amd64-sid: -----END
STACK TRACE-----

Please install the binary, the stack trace should at least show us if
the problematic code is in proftp or anywhere else.
The addr2line directions in [1] did not help me, I always got "??:0". At
least the stack trace should be a basis to issue a bug @upstream.

Many thanks for help!

Hilmar

[1] http://www.proftpd.org/docs/howto/Compiling.html
[2] https://freeshell.de/~hille42/proftpd/stacktrace/
-- 
#206401 http://counter.li.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-proftpd-maintainers/attachments/20171227/882c9d34/attachment.sig>