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

[Hilmar Preuße]

# in v1.3.6
tags 839880 + fixed-upstream
stop

Hi,

OK, I mark that bug as fixed in upstream.

Hilmar

Am 12.01.2018 um 01:56 teilte Олег Мороз mit:

I have installed version 1.3.6 from [1], it's works fine with mod_sftp.

11.01.2018 15:32, Hilmar Preuße пишет:

Am 09.01.2018 um 17:45 teilte Hilmar Preuße mit:

Hi,

I've escalated the bug to here [1]. Feel to subscribe to the bug to 
get informed about news.


Hilmar

[1] http://bugs.proftpd.org/4334

I've got a response from upstream. They told me to test latest 
upstream 1.3.6. So, I've packaged 1.3.6 for you, it is here [1]. I did 
a very basic test: I can transfer files using it, but I did not use 
ssl. So, please don't put it on a prod system, if possible.


Please be so kind to return results, i.e. if it sill crashes.

@Frankie: the source tree I have here. It's not perfect at all: I had 
to drop some patches b/c they did not apply. I still have to sort out 
if they are surplus or if they need to be adapted.


Hilmar

[1] https://freeshell.de/~hille42/proftpd/1.3.6/


___
Pkg-proftpd-maintainers mailing list
pkg-proftpd-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-proftpd-maintainers



--
#206401 http://counter.li.org

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

[Олег Мороз]

I have installed version 1.3.6 from [1], it's works fine with mod_sftp.

11.01.2018 15:32, Hilmar Preuße пишет:

Am 09.01.2018 um 17:45 teilte Hilmar Preuße mit:

Hi,

I've escalated the bug to here [1]. Feel to subscribe to the bug to 
get informed about news.


Hilmar

[1] http://bugs.proftpd.org/4334

I've got a response from upstream. They told me to test latest 
upstream 1.3.6. So, I've packaged 1.3.6 for you, it is here [1]. I did 
a very basic test: I can transfer files using it, but I did not use 
ssl. So, please don't put it on a prod system, if possible.


Please be so kind to return results, i.e. if it sill crashes.

@Frankie: the source tree I have here. It's not perfect at all: I had 
to drop some patches b/c they did not apply. I still have to sort out 
if they are surplus or if they need to be adapted.


Hilmar

[1] https://freeshell.de/~hille42/proftpd/1.3.6/

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

[Hilmar Preuße]

Am 09.01.2018 um 17:45 teilte Hilmar Preuße mit:

Hi,

I've escalated the bug to here [1]. Feel to subscribe to the bug to get 
informed about news.


Hilmar

[1] http://bugs.proftpd.org/4334

I've got a response from upstream. They told me to test latest upstream 
1.3.6. So, I've packaged 1.3.6 for you, it is here [1]. I did a very 
basic test: I can transfer files using it, but I did not use ssl. So, 
please don't put it on a prod system, if possible.


Please be so kind to return results, i.e. if it sill crashes.

@Frankie: the source tree I have here. It's not perfect at all: I had to 
drop some patches b/c they did not apply. I still have to sort out if 
they are surplus or if they need to be adapted.


Hilmar

[1] https://freeshell.de/~hille42/proftpd/1.3.6/
--
#206401 http://counter.li.org

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

[Олег Мороз]

Thank a lot. Will subscribe.

09.01.2018 19:45, Hilmar Preuße пишет:

forwarded 839880 http://bugs.proftpd.org/4334
stop

Am 09.01.2018 um 09:24 teilte Олег Мороз mit:

Hi Олег,

I've escalated the bug to here [1]. Feel to subscribe to the bug to 
get informed about news.


Hilmar

[1] http://bugs.proftpd.org/4334


Have tried

root@sim-ng-data:/home/vniiem# cat /var/log/proftpd/proftpd.log
...
...
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): -BEGIN STACK TRACE-
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [0] /usr/sbin/proftpd(+0x1f3b0) 
[0x563c3354f3b0]
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [1] /usr/sbin/proftpd(+0x1f3b0) 
[0x563c3354f3b0]



root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 0x1f3b0
./src/pool.c:546

but () gives error

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
0x563c3354f3b0()

bash: syntax error near unexpected token `('

and

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
(0x563c3354f3b0)

bash: syntax error near unexpected token `('


03.01.2018 15:47, Hilmar Preuße пишет:

Am 03.01.2018 um 09:39 teilte Олег Мороз mit:

Hi Oleg,

Happy new year!

according to my knowledge the most top line of the stack trace is 
the relevant one.


Your first addr2line command leads me to line 1312 in 
./contrib/mod_sftp/auth.c. This line just contains a call to 
function pr_cmd_dispatch_phase(). This function however is 
implemented in ./src/main.c . So to learn in which part of the 
function the crash happens one has to go one line up in the stack 
trace.


So please repeat the command for the most upper line in your stack 
trace and send me the output. Please use the addresses in the (), 
I've no clue why the 64bit addresses can't be used.


Many thanks!
  Hilmar


So sorry for delay, i'm on vacation.

I believe that problem is in mod_sftp.so

part of proftpd.log stack trace
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] 
/usr/lib/proftpd/mod_sftp.so(+0x3c7ef) [0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) 
[0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]



# addr2line -e /usr/lib/proftpd/mod_sftp.so 0x3c7ef
./contrib/mod_sftp/auth.c:1312


# addr2line -e /usr/lib/proftpd/mod_sftp.so +0xfa07
./contrib/mod_sftp/mod_sftp.c:247


unfortunatelly i cant use 64 bit addresses like 0x7f5e93b9d7ef , 
because in that case addr2line gives ??:0




Log Files snipped.

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

[Hilmar Preuße]

forwarded 839880 http://bugs.proftpd.org/4334
stop

Am 09.01.2018 um 09:24 teilte Олег Мороз mit:

Hi Олег,

I've escalated the bug to here [1]. Feel to subscribe to the bug to get 
informed about news.


Hilmar

[1] http://bugs.proftpd.org/4334


Have tried

root@sim-ng-data:/home/vniiem# cat /var/log/proftpd/proftpd.log
...
...
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): -BEGIN STACK TRACE-
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [0] /usr/sbin/proftpd(+0x1f3b0) [0x563c3354f3b0]
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [1] /usr/sbin/proftpd(+0x1f3b0) [0x563c3354f3b0]



root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 0x1f3b0
./src/pool.c:546

but () gives error

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
0x563c3354f3b0()

bash: syntax error near unexpected token `('

and

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
(0x563c3354f3b0)

bash: syntax error near unexpected token `('


03.01.2018 15:47, Hilmar Preuße пишет:

Am 03.01.2018 um 09:39 teilte Олег Мороз mit:

Hi Oleg,

Happy new year!

according to my knowledge the most top line of the stack trace is the 
relevant one.


Your first addr2line command leads me to line 1312 in 
./contrib/mod_sftp/auth.c. This line just contains a call to function 
pr_cmd_dispatch_phase(). This function however is implemented in 
./src/main.c . So to learn in which part of the function the crash 
happens one has to go one line up in the stack trace.


So please repeat the command for the most upper line in your stack 
trace and send me the output. Please use the addresses in the (), I've 
no clue why the 64bit addresses can't be used.


Many thanks!
  Hilmar


So sorry for delay, i'm on vacation.

I believe that problem is in mod_sftp.so

part of proftpd.log stack trace
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) 
[0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]



# addr2line -e /usr/lib/proftpd/mod_sftp.so 0x3c7ef
./contrib/mod_sftp/auth.c:1312


# addr2line -e /usr/lib/proftpd/mod_sftp.so +0xfa07
./contrib/mod_sftp/mod_sftp.c:247


unfortunatelly i cant use 64 bit addresses like 0x7f5e93b9d7ef , 
because in that case addr2line gives ??:0




Log Files snipped.






--
#206401 http://counter.li.org

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

[Hilmar Preuße]

Am 09.01.2018 um 09:24 teilte Олег Мороз mit:

Hi Олег,


root@sim-ng-data:/home/vniiem# cat /var/log/proftpd/proftpd.log
...
...
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): -BEGIN STACK TRACE-
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [0] /usr/sbin/proftpd(+0x1f3b0) [0x563c3354f3b0]
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [1] /usr/sbin/proftpd(+0x1f3b0) [0x563c3354f3b0]



root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 0x1f3b0
./src/pool.c:546


This(!) is the output I need. Many thanks!

Hilmar



but () gives error

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
0x563c3354f3b0()

bash: syntax error near unexpected token `('

and

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
(0x563c3354f3b0)

bash: syntax error near unexpected token `('


03.01.2018 15:47, Hilmar Preuße пишет:

Am 03.01.2018 um 09:39 teilte Олег Мороз mit:

Hi Oleg,

Happy new year!

according to my knowledge the most top line of the stack trace is the 
relevant one.


Your first addr2line command leads me to line 1312 in 
./contrib/mod_sftp/auth.c. This line just contains a call to function 
pr_cmd_dispatch_phase(). This function however is implemented in 
./src/main.c . So to learn in which part of the function the crash 
happens one has to go one line up in the stack trace.


So please repeat the command for the most upper line in your stack 
trace and send me the output. Please use the addresses in the (), I've 
no clue why the 64bit addresses can't be used.


Many thanks!
  Hilmar


So sorry for delay, i'm on vacation.

I believe that problem is in mod_sftp.so

part of proftpd.log stack trace
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) 
[0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]



# addr2line -e /usr/lib/proftpd/mod_sftp.so 0x3c7ef
./contrib/mod_sftp/auth.c:1312


# addr2line -e /usr/lib/proftpd/mod_sftp.so +0xfa07
./contrib/mod_sftp/mod_sftp.c:247


unfortunatelly i cant use 64 bit addresses like 0x7f5e93b9d7ef , 
because in that case addr2line gives ??:0




Log Files snipped.






--
#206401 http://counter.li.org

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

[Олег Мороз]

Have tried

root@sim-ng-data:/home/vniiem# cat /var/log/proftpd/proftpd.log
...
...
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): -BEGIN STACK TRACE-
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [0] /usr/sbin/proftpd(+0x1f3b0) [0x563c3354f3b0]
2018-01-09 08:16:37,030 sim-ng-data proftpd[24660] sim-ng-data 
(OpenWrt[192.168.3.180]): [1] /usr/sbin/proftpd(+0x1f3b0) [0x563c3354f3b0]



root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 0x1f3b0
./src/pool.c:546

but () gives error

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
0x563c3354f3b0()

bash: syntax error near unexpected token `('

and

root@sim-ng-data:/home/vniiem# addr2line -e /usr/sbin/proftpd 
(0x563c3354f3b0)

bash: syntax error near unexpected token `('


03.01.2018 15:47, Hilmar Preuße пишет:

Am 03.01.2018 um 09:39 teilte Олег Мороз mit:

Hi Oleg,

Happy new year!

according to my knowledge the most top line of the stack trace is the 
relevant one.


Your first addr2line command leads me to line 1312 in 
./contrib/mod_sftp/auth.c. This line just contains a call to function 
pr_cmd_dispatch_phase(). This function however is implemented in 
./src/main.c . So to learn in which part of the function the crash 
happens one has to go one line up in the stack trace.


So please repeat the command for the most upper line in your stack 
trace and send me the output. Please use the addresses in the (), I've 
no clue why the 64bit addresses can't be used.


Many thanks!
  Hilmar


So sorry for delay, i'm on vacation.

I believe that problem is in mod_sftp.so

part of proftpd.log stack trace
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) 
[0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]



# addr2line -e /usr/lib/proftpd/mod_sftp.so 0x3c7ef
./contrib/mod_sftp/auth.c:1312


# addr2line -e /usr/lib/proftpd/mod_sftp.so +0xfa07
./contrib/mod_sftp/mod_sftp.c:247


unfortunatelly i cant use 64 bit addresses like 0x7f5e93b9d7ef , 
because in that case addr2line gives ??:0




Log Files snipped.

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

[Hilmar Preuße]

Am 03.01.2018 um 09:39 teilte Олег Мороз mit:

Hi Oleg,

Happy new year!

according to my knowledge the most top line of the stack trace is the 
relevant one.


Your first addr2line command leads me to line 1312 in 
./contrib/mod_sftp/auth.c. This line just contains a call to function 
pr_cmd_dispatch_phase(). This function however is implemented in 
./src/main.c . So to learn in which part of the function the crash 
happens one has to go one line up in the stack trace.


So please repeat the command for the most upper line in your stack trace 
and send me the output. Please use the addresses in the (), I've no clue 
why the 64bit addresses can't be used.


Many thanks!
  Hilmar


So sorry for delay, i'm on vacation.

I believe that problem is in mod_sftp.so

part of proftpd.log stack trace
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) 
[0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]



# addr2line -e /usr/lib/proftpd/mod_sftp.so 0x3c7ef
./contrib/mod_sftp/auth.c:1312


# addr2line -e /usr/lib/proftpd/mod_sftp.so +0xfa07
./contrib/mod_sftp/mod_sftp.c:247


unfortunatelly i cant use 64 bit addresses like 0x7f5e93b9d7ef , because 
in that case addr2line gives ??:0




Log Files snipped.

--
#206401 http://counter.li.org

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

[Олег Мороз]

So sorry for delay, i'm on vacation.

I believe that problem is in mod_sftp.so

part of proftpd.log stack trace
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) [0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]



# addr2line -e /usr/lib/proftpd/mod_sftp.so 0x3c7ef
./contrib/mod_sftp/auth.c:1312


# addr2line -e /usr/lib/proftpd/mod_sftp.so +0xfa07
./contrib/mod_sftp/mod_sftp.c:247


unfortunatelly i cant use 64 bit addresses like 0x7f5e93b9d7ef , because 
in that case addr2line gives ??:0





--- logs ---

cat proftpd.log
2018-01-03 11:29:00,728 sim-ng-data proftpd[29204] sim-ng-data: ProFTPD 
1.3.5e (maint) (built Fri Jul 7 2017 10:06:53 UTC) standalone mode STARTUP
2018-01-03 11:29:26,276 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2018-01-03 08:29:28,666 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2018-01-03 08:29:28,667 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2018-01-03 08:29:28,667 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.
2018-01-03 08:29:28,667 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): -BEGIN STACK TRACE-
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [0] /usr/sbin/proftpd(+0x1f3b0) [0x558dcafec3b0]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [1] /usr/sbin/proftpd(+0x1f3b0) [0x558dcafec3b0]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [2] /usr/sbin/proftpd(palloc+0x37) 
[0x558dcafec4b2]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [3] /usr/sbin/proftpd(pcalloc+0x32) 
[0x558dcafec547]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [4] /usr/sbin/proftpd(pr_response_add+0xee) 
[0x558dcb016e25]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f5e93b9d7ef]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f5e93b9dc31]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) [0x7f5e93b7c9ad]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f5e93b70a07]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [9] /usr/sbin/proftpd(+0x19ee3) [0x558dcafe6ee3]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [10] /usr/sbin/proftpd(+0x1a706) [0x558dcafe7706]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [11] /usr/sbin/proftpd(+0x1bf2f) [0x558dcafe8f2f]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [12] /usr/sbin/proftpd(main+0x94b) 
[0x558dcafe9ce3]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [13] 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f5e974a1561]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): [14] /usr/sbin/proftpd(_start+0x2a) 
[0x558dcafe3daa]
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): -END STACK TRACE-
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2018-01-03 08:29:28,674 sim-ng-data proftpd[29225] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.




cat sftp.log
2018-01-03 11:29:26,276 mod_sftp/0.9.9[29225]: error using DisplayLogin 
'welcome.msg': No such file or directory
2018-01-03 11:29:26,277 mod_sftp/0.9.9[29225]: sent server version 
'SSH-2.0-mod_sftp/0.9.9'
2018-01-03 11:29:26,277 mod_sftp/0.9.9[29225]: received client version 
'SSH-2.0-FileZilla_3.29.0'
2018-01-03 11:29:26,277 mod_sftp/0.9.9[29225]: handling connection from 
SSH2 client 'FileZilla_3.29.0'
2018-01-03 11:29:26,360 mod_sftp/0.9.9[29225]:  + Session key exchange: 
ecdh-sha2-nistp256
2018-01-03 11:29:26,360 mod_sftp/0.9.9[29225]:  + Session server 
hostkey: ssh-rsa
2018-01-03 11:29:26,360

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

[Hilmar Preuße]

On 29.12.2017 23:04, Hilmar Preuße wrote:

Hi Олег,

could you please attach both log files proftpd.log & sftp.log showing
the crashes.

Hilmar

> On 28.12.2017 14:53, Hilmar Preuße wrote:
> 
> Добры бечер Олег,
> 
> On my system the addr2line command gives only useful results if I use
> the numbers in (), like this. At least output below makes sense to me.
> What does your addr2line returns?
> 
> hille@amd64-sid:~$ addr2line -e /usr/sbin/proftpd 0x55e39fd633b0
> ??:0
> hille@amd64-sid:~$ addr2line -e /usr/sbin/proftpd 0x1f3b0
> ./src/pool.c:546
> 
> Hilmar
> 
>> Hi Олег,
>>
>> did to try to run addr2line as described on [1]? Does is print something
>> useful. The command is provided by package binutils.
>>
>> Hilmar
>>
>> [1] http://www.proftpd.org/docs/howto/Compiling.html
>>
>>> Got some positive results
>>>
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): -BEGIN STACK TRACE-
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [0] /usr/sbin/proftpd(+0x1f3b0)
>>> [0x55e39fd633b0]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [1] /usr/sbin/proftpd(+0x1f3b0)
>>> [0x55e39fd633b0]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [2] /usr/sbin/proftpd(palloc+0x37)
>>> [0x55e39fd634b2]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [3] /usr/sbin/proftpd(pcalloc+0x32)
>>> [0x55e39fd63547]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [4]
>>> /usr/sbin/proftpd(pr_response_add+0xee) [0x55e39fd8de25]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef)
>>> [0x7f04249dd7ef]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [6]
>>> /usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f04249ddc31]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [7]
>>> /usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363)
>>> [0x7f04249bc9ad]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07)
>>> [0x7f04249b0a07]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [9] /usr/sbin/proftpd(+0x19ee3)
>>> [0x55e39fd5dee3]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [10] /usr/sbin/proftpd(+0x1a706)
>>> [0x55e39fd5e706]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [11] /usr/sbin/proftpd(+0x1bf2f)
>>> [0x55e39fd5ff2f]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [12] /usr/sbin/proftpd(main+0x94b)
>>> [0x55e39fd60ce3]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [13]
>>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f04282e1561]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): [14] /usr/sbin/proftpd(_start+0x2a)
>>> [0x55e39fd5adaa]
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): -END STACK TRACE-
>>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): ProFTPD terminating (signal 11)
>>> 2017-12-28 07:32:21,762 sim-ng-data proftpd[26614] sim-ng-data
>>> (PG10.local[192.168.3.17]): SSH2 session closed.
>>>
>>>
>>> 28.12.2017 0:09, 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@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) [0x7fd99e1c3cc

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

[Hilmar Preuße]

On 28.12.2017 14:53, Hilmar Preuße wrote:

Добры бечер Олег,

On my system the addr2line command gives only useful results if I use
the numbers in (), like this. At least output below makes sense to me.
What does your addr2line returns?

hille@amd64-sid:~$ addr2line -e /usr/sbin/proftpd 0x55e39fd633b0
??:0
hille@amd64-sid:~$ addr2line -e /usr/sbin/proftpd 0x1f3b0
./src/pool.c:546

Hilmar

> Hi Олег,
> 
> did to try to run addr2line as described on [1]? Does is print something
> useful. The command is provided by package binutils.
> 
> Hilmar
> 
> [1] http://www.proftpd.org/docs/howto/Compiling.html
> 
>> Got some positive results
>>
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): -BEGIN STACK TRACE-
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [0] /usr/sbin/proftpd(+0x1f3b0)
>> [0x55e39fd633b0]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [1] /usr/sbin/proftpd(+0x1f3b0)
>> [0x55e39fd633b0]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [2] /usr/sbin/proftpd(palloc+0x37)
>> [0x55e39fd634b2]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [3] /usr/sbin/proftpd(pcalloc+0x32)
>> [0x55e39fd63547]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [4]
>> /usr/sbin/proftpd(pr_response_add+0xee) [0x55e39fd8de25]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef)
>> [0x7f04249dd7ef]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [6]
>> /usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f04249ddc31]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [7]
>> /usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363)
>> [0x7f04249bc9ad]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07)
>> [0x7f04249b0a07]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [9] /usr/sbin/proftpd(+0x19ee3)
>> [0x55e39fd5dee3]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [10] /usr/sbin/proftpd(+0x1a706)
>> [0x55e39fd5e706]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [11] /usr/sbin/proftpd(+0x1bf2f)
>> [0x55e39fd5ff2f]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [12] /usr/sbin/proftpd(main+0x94b)
>> [0x55e39fd60ce3]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [13]
>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f04282e1561]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): [14] /usr/sbin/proftpd(_start+0x2a)
>> [0x55e39fd5adaa]
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): -END STACK TRACE-
>> 2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): ProFTPD terminating (signal 11)
>> 2017-12-28 07:32:21,762 sim-ng-data proftpd[26614] sim-ng-data
>> (PG10.local[192.168.3.17]): SSH2 session closed.
>>
>>
>> 28.12.2017 0:09, 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@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 amd6

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

[Hilmar Preuße]

Am 28.12.2017 um 08:34 teilte Мороз Олег mit:

Hi Олег,

did to try to run addr2line as described on [1]? Does is print something 
useful. The command is provided by package binutils.


Hilmar

[1] http://www.proftpd.org/docs/howto/Compiling.html


Got some positive results

2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): -BEGIN STACK TRACE-
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [0] /usr/sbin/proftpd(+0x1f3b0) 
[0x55e39fd633b0]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [1] /usr/sbin/proftpd(+0x1f3b0) 
[0x55e39fd633b0]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [2] /usr/sbin/proftpd(palloc+0x37) 
[0x55e39fd634b2]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [3] /usr/sbin/proftpd(pcalloc+0x32) 
[0x55e39fd63547]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [4] /usr/sbin/proftpd(pr_response_add+0xee) 
[0x55e39fd8de25]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f04249dd7ef]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f04249ddc31]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) 
[0x7f04249bc9ad]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f04249b0a07]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [9] /usr/sbin/proftpd(+0x19ee3) 
[0x55e39fd5dee3]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [10] /usr/sbin/proftpd(+0x1a706) 
[0x55e39fd5e706]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [11] /usr/sbin/proftpd(+0x1bf2f) 
[0x55e39fd5ff2f]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [12] /usr/sbin/proftpd(main+0x94b) 
[0x55e39fd60ce3]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [13] 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f04282e1561]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [14] /usr/sbin/proftpd(_start+0x2a) 
[0x55e39fd5adaa]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): -END STACK TRACE-
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): ProFTPD terminating (signal 11)
2017-12-28 07:32:21,762 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): SSH2 session closed.



28.12.2017 0:09, 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@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 shou

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

[Мороз Олег]

Got some positive results

2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): -BEGIN STACK TRACE-
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [0] /usr/sbin/proftpd(+0x1f3b0) [0x55e39fd633b0]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [1] /usr/sbin/proftpd(+0x1f3b0) [0x55e39fd633b0]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [2] /usr/sbin/proftpd(palloc+0x37) 
[0x55e39fd634b2]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [3] /usr/sbin/proftpd(pcalloc+0x32) 
[0x55e39fd63547]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [4] /usr/sbin/proftpd(pr_response_add+0xee) 
[0x55e39fd8de25]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [5] /usr/lib/proftpd/mod_sftp.so(+0x3c7ef) 
[0x7f04249dd7ef]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [6] 
/usr/lib/proftpd/mod_sftp.so(sftp_auth_handle+0x62) [0x7f04249ddc31]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [7] 
/usr/lib/proftpd/mod_sftp.so(sftp_ssh2_packet_handle+0x363) [0x7f04249bc9ad]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [8] /usr/lib/proftpd/mod_sftp.so(+0xfa07) 
[0x7f04249b0a07]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [9] /usr/sbin/proftpd(+0x19ee3) [0x55e39fd5dee3]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [10] /usr/sbin/proftpd(+0x1a706) 
[0x55e39fd5e706]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [11] /usr/sbin/proftpd(+0x1bf2f) 
[0x55e39fd5ff2f]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [12] /usr/sbin/proftpd(main+0x94b) 
[0x55e39fd60ce3]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [13] 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f04282e1561]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): [14] /usr/sbin/proftpd(_start+0x2a) 
[0x55e39fd5adaa]
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): -END STACK TRACE-
2017-12-28 07:32:21,761 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): ProFTPD terminating (signal 11)
2017-12-28 07:32:21,762 sim-ng-data proftpd[26614] sim-ng-data 
(PG10.local[192.168.3.17]): SSH2 session closed.



28.12.2017 0:09, 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@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/


--
Олег Мороз
Заместитель начальника отдела АО "Корпорация ВНИИЭМ"
+7-96

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@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



signature.asc
Description: OpenPGP digital signature

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

[Мороз Олег]

Hi,


Have made changes in

/etc/security/limits.d/core_dump.conf

then set path to save code dumps into /tmp

vniiem@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




25.12.2017 17:09, Hilmar Preuße пишет:

On 24.12.2017 11:32, Олег Мороз wrote:

Hi,

no, we did not package any version between b-4 and d-1. However I doubt
to learn a lot by simply knowing in which version the issue was introduced.

Regarding your core dumps: Please make sure the core dumps are created
in the context of every user:

hille@haka:~$ less -X /etc/security/limits.d/core_dump.conf
# Each line describes a limit for a user in the form:
#
#
#
*  hard  core  unlimited
*  soft  core  unlimited

...or set it directly in the limits.conf. Settings are effective upon
next login.

If your system is configured to write core dumps to a specific location:

hille@haka:~$ /sbin/sysctl -a -r kernel.core
kernel.core_pattern = /var/crash/core.%e.%p.%h.%t
kernel.core_pipe_limit = 0
kernel.core_uses_pid = 0
hille@haka:~$

...make sure it is writable for the specific user: proftp runs as user
proftpd . Make it world writable for now.

Hilmar


I'm not checked any version except 1.3.5b-4 and 1.3.5d-1. If it possible
to download .deb packages for any other version within that interval,
i'll be happy to test it.

24.12.2017 12:21, Hilmar Preuße пишет:

Am 24.12.2017 um 08:33 teilte Олег Мороз mit:

Hi Олег,

so, your problem was introduced anywhere between 1.3.5b & 1.3.5d?

You can have a look at the files in /usr/share/doc/proftpd-basic/ here
are the upstream logs (changelog.gz) and the Debian Log. However I
don't think that they are useful to debug your problem.

Hilmar


  >does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually
describe your problem?
Don't think so. Have tried to disable pam, but with no effect. Anyway
i've reinstall proftpd-basic 1.3.5b-4 from stretch - looks to be work.

Where can i find information about changes from 1.3.5b-4 up to 1.3.5d-1?



--
Олег Мороз
Заместитель начальника отдела АО "Корпорация ВНИИЭМ"
+7-963-760-70-15

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

[Hilmar Preuße]

On 24.12.2017 11:32, Олег Мороз wrote:

Hi,

no, we did not package any version between b-4 and d-1. However I doubt
to learn a lot by simply knowing in which version the issue was introduced.

Regarding your core dumps: Please make sure the core dumps are created
in the context of every user:

hille@haka:~$ less -X /etc/security/limits.d/core_dump.conf
# Each line describes a limit for a user in the form:
#
#
#
*  hard  core  unlimited
*  soft  core  unlimited

...or set it directly in the limits.conf. Settings are effective upon
next login.

If your system is configured to write core dumps to a specific location:

hille@haka:~$ /sbin/sysctl -a -r kernel.core
kernel.core_pattern = /var/crash/core.%e.%p.%h.%t
kernel.core_pipe_limit = 0
kernel.core_uses_pid = 0
hille@haka:~$

...make sure it is writable for the specific user: proftp runs as user
proftpd . Make it world writable for now.

Hilmar

> I'm not checked any version except 1.3.5b-4 and 1.3.5d-1. If it possible
> to download .deb packages for any other version within that interval,
> i'll be happy to test it.
> 
> 24.12.2017 12:21, Hilmar Preuße пишет:
>> Am 24.12.2017 um 08:33 teilte Олег Мороз mit:
>>
>> Hi Олег,
>>
>> so, your problem was introduced anywhere between 1.3.5b & 1.3.5d?
>>
>> You can have a look at the files in /usr/share/doc/proftpd-basic/ here
>> are the upstream logs (changelog.gz) and the Debian Log. However I
>> don't think that they are useful to debug your problem.
>>
>> Hilmar
>>
>>>  >does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually
>>> describe your problem?
>>> Don't think so. Have tried to disable pam, but with no effect. Anyway
>>> i've reinstall proftpd-basic 1.3.5b-4 from stretch - looks to be work.
>>>
>>> Where can i find information about changes from 1.3.5b-4 up to 1.3.5d-1?
>>>

-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

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

[Олег Мороз]

I'm not checked any version except 1.3.5b-4 and 1.3.5d-1. If it possible 
to download .deb packages for any other version within that interval, 
i'll be happy to test it.


24.12.2017 12:21, Hilmar Preuße пишет:

Am 24.12.2017 um 08:33 teilte Олег Мороз mit:

Hi Олег,

so, your problem was introduced anywhere between 1.3.5b & 1.3.5d?

You can have a look at the files in /usr/share/doc/proftpd-basic/ here 
are the upstream logs (changelog.gz) and the Debian Log. However I 
don't think that they are useful to debug your problem.


Hilmar

 >does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually 
describe your problem?
Don't think so. Have tried to disable pam, but with no effect. Anyway 
i've reinstall proftpd-basic 1.3.5b-4 from stretch - looks to be work.


Where can i find information about changes from 1.3.5b-4 up to 1.3.5d-1?

24.12.2017 2:02, Hilmar Preuße пишет:

Am 23.12.2017 um 11:25 teilte Олег Мороз mit:

Hi,

does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually 
describe your problem?


Hilmar


Have installed 1.3.5e, but problem not solved


2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: 
ProFTPD 1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) 
standalone mode STARTUP
2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.
2017-12-23 13:24:24,428 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.


22.12.2017 0:51, Hilmar Preuße пишет:

On 21.12.2017 05:00, Мороз Олег wrote:

Hi Олег,

you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should 
contain
both fixes) and uploaded the full suite here [1]. Please be so 
kind to

report back.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/


Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,

proftpd started successfully in my jessie system.  However 
after some

day
(it may be after a system-wide upgrade) the client failed to 
login.



For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused 
by null

pointer dereference.

Could you apply the two related patches [1] and [2] and test if 
they
solve the problem? Eventually I can build custom packages for 
you; in

this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch 



[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch

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

[Hilmar Preuße]

Am 24.12.2017 um 08:33 teilte Олег Мороз mit:

Hi Олег,

so, your problem was introduced anywhere between 1.3.5b & 1.3.5d?

You can have a look at the files in /usr/share/doc/proftpd-basic/ here 
are the upstream logs (changelog.gz) and the Debian Log. However I don't 
think that they are useful to debug your problem.


Hilmar

 >does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually describe 
your problem?
Don't think so. Have tried to disable pam, but with no effect. Anyway 
i've reinstall proftpd-basic 1.3.5b-4 from stretch - looks to be work.


Where can i find information about changes from 1.3.5b-4 up to 1.3.5d-1?

24.12.2017 2:02, Hilmar Preuße пишет:

Am 23.12.2017 um 11:25 teilte Олег Мороз mit:

Hi,

does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually describe 
your problem?


Hilmar


Have installed 1.3.5e, but problem not solved


2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: 
ProFTPD 1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone 
mode STARTUP
2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.
2017-12-23 13:24:24,428 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.


22.12.2017 0:51, Hilmar Preuße пишет:

On 21.12.2017 05:00, Мороз Олег wrote:

Hi Олег,

you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should contain
both fixes) and uploaded the full suite here [1]. Please be so kind to
report back.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/


Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,

proftpd started successfully in my jessie system.  However after 
some

day
(it may be after a system-wide upgrade) the client failed to login.


For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by 
null

    pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch 



[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch












--
#206401 http://counter.li.org

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

[Олег Мороз]

>does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually describe 
your problem?
Don't think so. Have tried to disable pam, but with no effect. Anyway 
i've reinstall proftpd-basic 1.3.5b-4 from stretch - looks to be work.


Where can i find information about changes from 1.3.5b-4 up to 1.3.5d-1?

24.12.2017 2:02, Hilmar Preuße пишет:

Am 23.12.2017 um 11:25 teilte Олег Мороз mit:

Hi,

does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually describe 
your problem?


Hilmar


Have installed 1.3.5e, but problem not solved


2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: 
ProFTPD 1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone 
mode STARTUP
2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.
2017-12-23 13:24:24,428 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.


22.12.2017 0:51, Hilmar Preuße пишет:

On 21.12.2017 05:00, Мороз Олег wrote:

Hi Олег,

you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should contain
both fixes) and uploaded the full suite here [1]. Please be so kind to
report back.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/


Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,

proftpd started successfully in my jessie system.  However after 
some

day
(it may be after a system-wide upgrade) the client failed to login.


For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by 
null

pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch 



[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch

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

[Hilmar Preuße]

Am 23.12.2017 um 11:25 teilte Олег Мороз mit:

Hi,

does http://bugs.proftpd.org/show_bug.cgi?id=4321 eventually describe 
your problem?


Hilmar


Have installed 1.3.5e, but problem not solved


2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: ProFTPD 
1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode STARTUP
2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.
2017-12-23 13:24:24,428 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.


22.12.2017 0:51, Hilmar Preuße пишет:

On 21.12.2017 05:00, Мороз Олег wrote:

Hi Олег,

you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should contain
both fixes) and uploaded the full suite here [1]. Please be so kind to
report back.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/


Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,


proftpd started successfully in my jessie system.  However after some
day
(it may be after a system-wide upgrade) the client failed to login.


For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
    pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch 



[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch







--
#206401 http://counter.li.org

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

[Hilmar Preuße]

Am 23.12.2017 um 16:58 teilte Олег Мороз mit:

Hi,

did you set the limits in correct user context (see 
/etc/security/limits.conf)? No sorry, I'm not an expert in this.


Regarding the crash: I do see the sig 11 below. Did you try to hit 
CTRL-C (as described) and generate a backtrace then?


Thanks!

Hilmar


coredump did not generated. Have tried to use:

|ulimit -c unlimited|

with no effects (have checked / and  /root directories to find coredump)

Then have installed proftpd debug symbols and gdb and start proftpd 
debugging



root@sim-ng-data /run # gdb proftpd
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from proftpd...Reading symbols from 
/usr/lib/debug/.build-id/c9/5250b18658db39aa4692b37f01f3549f2181a5.debug...done. 


done.

(gdb) run -n
Starting program: /usr/sbin/proftpd -n
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2017-12-23 18:56:12,032 sim-ng-data proftpd[11874]: processing 
configuration directory '/etc/proftpd/conf.d/'
2017-12-23 18:56:12,041 sim-ng-data proftpd[11874] sim-ng-data: ProFTPD 
1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode STARTUP
2017-12-23 18:56:17,915 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.



program is not crushed (still working and running) because of that i 
have no posibility to collect backtrace of error




23.12.2017 17:53, Hilmar Preuße пишет:

On 23.12.2017 11:25, Олег Мороз wrote:

Hi Олег,


2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: ProFTPD
1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode 
STARTUP

2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session closed.


Is a core dump generated for the crash? If not, don't care for now.

The URL [1] describes some basic steps how to generated a back trace for
debugging. Please follow them as far as possible, in case of questions
please call back. The section "Installing the debugging symbols" won't
work as described; our debug symbols are not in archive yet. However
I've uploaded the appropriate dbgsym packages to the location where you
got the proftpd package, please install them from there.

Hilmar

[1] https://wiki.debian.org/HowToGetABacktrace





--
#206401 http://counter.li.org

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

[Олег Мороз]

coredump did not generated. Have tried to use:

|ulimit -c unlimited|

with no effects (have checked / and  /root directories to find coredump)


Then have installed proftpd debug symbols and gdb and start proftpd 
debugging



root@sim-ng-data /run # gdb proftpd
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from proftpd...Reading symbols from 
/usr/lib/debug/.build-id/c9/5250b18658db39aa4692b37f01f3549f2181a5.debug...done.

done.

(gdb) run -n
Starting program: /usr/sbin/proftpd -n
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2017-12-23 18:56:12,032 sim-ng-data proftpd[11874]: processing 
configuration directory '/etc/proftpd/conf.d/'
2017-12-23 18:56:12,041 sim-ng-data proftpd[11874] sim-ng-data: ProFTPD 
1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode STARTUP
2017-12-23 18:56:17,915 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 15:56:18,046 sim-ng-data proftpd[11912] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.



program is not crushed (still working and running) because of that i 
have no posibility to collect backtrace of error




23.12.2017 17:53, Hilmar Preuße пишет:

On 23.12.2017 11:25, Олег Мороз wrote:

Hi Олег,


2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: ProFTPD
1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode STARTUP
2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
(OpenWrt[192.168.3.180]): SSH2 session closed.


Is a core dump generated for the crash? If not, don't care for now.

The URL [1] describes some basic steps how to generated a back trace for
debugging. Please follow them as far as possible, in case of questions
please call back. The section "Installing the debugging symbols" won't
work as described; our debug symbols are not in archive yet. However
I've uploaded the appropriate dbgsym packages to the location where you
got the proftpd package, please install them from there.

Hilmar

[1] https://wiki.debian.org/HowToGetABacktrace

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

[Hilmar Preuße]

On 23.12.2017 11:25, Олег Мороз wrote:

Hi Олег,

> 2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: ProFTPD
> 1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode STARTUP
> 2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data
> (OpenWrt[192.168.3.180]): SSH2 session opened.
> 2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
> (OpenWrt[192.168.3.180]): USER ftp: Login successful
> 2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
> (OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
> 2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data
> (OpenWrt[192.168.3.180]): SSH2 session closed.
> 
Is a core dump generated for the crash? If not, don't care for now.

The URL [1] describes some basic steps how to generated a back trace for
debugging. Please follow them as far as possible, in case of questions
please call back. The section "Installing the debugging symbols" won't
work as described; our debug symbols are not in archive yet. However
I've uploaded the appropriate dbgsym packages to the location where you
got the proftpd package, please install them from there.

Hilmar

[1] https://wiki.debian.org/HowToGetABacktrace
-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

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

[Олег Мороз]

Have installed 1.3.5e, but problem not solved


2017-12-23 13:24:15,773 sim-ng-data proftpd[25418] sim-ng-data: ProFTPD 
1.3.5e (maint) (built Di Dez 19 2017 07:53:15 CET) standalone mode STARTUP
2017-12-23 13:24:19,256 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:19,381 sim-ng-data proftpd[25446] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.
2017-12-23 13:24:24,428 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session opened.
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): USER ftp: Login successful
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): ProFTPD terminating (signal 11)
2017-12-23 10:24:24,561 sim-ng-data proftpd[25461] sim-ng-data 
(OpenWrt[192.168.3.180]): SSH2 session closed.


22.12.2017 0:51, Hilmar Preuße пишет:

On 21.12.2017 05:00, Мороз Олег wrote:

Hi Олег,

you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should contain
both fixes) and uploaded the full suite here [1]. Please be so kind to
report back.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/


Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,


proftpd started successfully in my jessie system.  However after some
day
(it may be after a system-wide upgrade) the client failed to login.


For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch

[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch

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

[Олег Мороз]

I'm using debian testing

$apt show proftpd-basic
Package: proftpd-basic
Version: 1.3.5d-1


Will try to install yours 1.3.5e

22.12.2017 0:51, Hilmar Preuße пишет:

On 21.12.2017 05:00, Мороз Олег wrote:

Hi Олег,

you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should contain
both fixes) and uploaded the full suite here [1]. Please be so kind to
report back.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/


Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,


proftpd started successfully in my jessie system.  However after some
day
(it may be after a system-wide upgrade) the client failed to login.


For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch

[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch

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

[Hilmar Preuße]

On 21.12.2017 05:00, Мороз Олег wrote:

Hi Олег,

you did not tell, if you run stable or unstable. As you use 1.3.5d I
assume you run sid. I've packaged the 1.3.5e for sid (it should contain
both fixes) and uploaded the full suite here [1]. Please be so kind to
report back.

Hilmar

[1] https://freeshell.de/~hille42/proftpd/

> Can you please build for x86_64 ?
> 
> 
> 21.12.2017 1:07, Hilmar Preuße пишет:
>> On 06.10.2016 05:52, Franklin Weng wrote:
>>
>> Hi all,
>>
>>> proftpd started successfully in my jessie system.  However after some
>>> day
>>> (it may be after a system-wide upgrade) the client failed to login.
>>>
>> For 1.3.5e I see only two crash bugs fixed:
>>
>> - Bug 4287 - SFTP clients using umac...@openssh.com digest fail to
>> connect.
>> - Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
>>    pointer dereference.
>>
>> Could you apply the two related patches [1] and [2] and test if they
>> solve the problem? Eventually I can build custom packages for you; in
>> this case I need your CPU architecture.
>>
>> Hilmar
>>
>> [1]
>> https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch
>>
>> [2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
>> /pull/431.patch
> 


-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

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

[Мороз Олег]

Can you please build for x86_64 ?


21.12.2017 1:07, Hilmar Preuße пишет:

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,


proftpd started successfully in my jessie system.  However after some day
(it may be after a system-wide upgrade) the client failed to login.


For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
   pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch
[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch


--
Олег Мороз
Заместитель начальника отдела АО "Корпорация ВНИИЭМ"
+7-963-760-70-15

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

[Hilmar Preuße]

On 06.10.2016 05:52, Franklin Weng wrote:

Hi all,

> proftpd started successfully in my jessie system.  However after some day
> (it may be after a system-wide upgrade) the client failed to login.
> 
For 1.3.5e I see only two crash bugs fixed:

- Bug 4287 - SFTP clients using umac...@openssh.com digest fail to connect.
- Bug 4288 - SFTP rekeying failure with ProFTPD 1.3.5d, caused by null
  pointer dereference.

Could you apply the two related patches [1] and [2] and test if they
solve the problem? Eventually I can build custom packages for you; in
this case I need your CPU architecture.

Hilmar

[1]
https://patch-diff.githubusercontent.com/raw/proftpd/proftpd/pull/411.patch
[2] https://patch-diff.githubusercontent.com/raw/proftpd/proftpd
/pull/431.patch
-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

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

[Hilmar Preuße]

severity 839880 important
tags 839880 + moreinfo
stop

Am 06.10.2016 um 05:52 schrieb Franklin Weng:

Hi Franklin,


Package: proftpd-basic
Version: 1.3.5-1.1+deb8u1
Severity: grave
Justification: renders package unusable

proftpd started successfully in my jessie system.  However after some day
(it may be after a system-wide upgrade) the client failed to login.

I gave it a short test on my system and it worked (see bottom of 
E-mail). My system is similar to your one (8.6 on i386), so it can't be 
a general problem. No, I did not let my system run for a few days.


I'm setting this bug to important for now and tag it moreinfo, although 
I don't know, which informations to collect. As the server crashed: do 
you have a core dump one could analyse? If not could you generate one?


Thanks,
  Hilmar

hille@sid:~ $ ncftp
NcFTP 3.2.5 (Feb 02, 2011) by Mike Gleason (http://www.NcFTP.com/contact/).
ncftp> open -u 192.168.1.131
Username at 192.168.1.131: *
Connecting to 192.168.1.131...
ProFTPD 1.3.5 Server (Debian) [:::192.168.1.131]
Logging in...
Password requested by 192.168.1.131 for user "hille".

Password required for hille

Password: 

User hille logged in
Logged in to 192.168.1.131.
ncftp /home/hille > get -r nouveau/
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
nouveau/xserver-xorg-video-nouveau_1.0.1.orig.tar.gz:  671.45 kB6.79 
MB/s
nouveau/libdrm-nouveau2-dbg_2.4.52-1_i386.deb:  33.87 kB   25.04 
MB/s
.../xserver-xorg-video-nouveau-dbg_1.0.10-1_i386.deb:  852.65 kB3.72 
MB/s
nouveau/libdrm-intel1-dbg_2.4.52-1_i386.deb:   102.79 kB  930.80 
kB/s
nouveau/xserver-xorg-video-nouveau_1.0.10-1.diff.gz:36.14 kB2.05 
MB/s
nouveau/xserver-xorg-video-nouveau_1.0.1-5.dsc:  2.47 kB  228.96 
kB/s
nouveau/libdrm_2.4.52.orig.tar.gz: 733.19 kB5.79 
MB/s
nouveau/libdrm2-dbg_2.4.52-1_i386.deb:  55.63 kB2.08 
MB/s
nouveau/xserver-xorg-video-nouveau_1.0.10-1.dsc: 2.46 kB2.99 
MB/s
nouveau/xserver-xorg-video-nouveau_1.0.1-5.diff.gz: 54.44 kB   27.20 
MB/s
nouveau/libdrm-radeon1-dbg_2.4.52-1_i386.deb:   54.74 kB  804.91 
kB/s
nouveau/libdrm_2.4.52-1.diff.gz:18.47 kB   14.48 
MB/s
nouveau/libdrm_2.4.52-1.dsc: 2.48 kB3.72 
MB/s
nouveau/libdrm-dev_2.4.52-1_i386.deb:  211.77 kB8.81 
MB/s
nouveau/libdrm-nouveau2_2.4.52-1_i386.deb:  23.73 kB  288.38 
kB/s
nouveau/xserver-xorg-video-nouveau_1.0.10-1_i386.deb:  304.73 kB   46.31 
MB/s
nouveau/libdrm-intel1_2.4.52-1_i386.deb:72.40 kB   25.08 
MB/s
nouveau/libdrm-radeon1_2.4.52-1_i386.deb:   36.10 kB   29.40 
MB/s
nouveau/libdrm2_2.4.52-1_i386.deb:  33.87 kB  608.97 
kB/s
...eau/xserver-xorg-video-nouveau_1.0.10.orig.tar.gz:  696.00 kB6.21 
MB/s
nouveau/libdrm2-udeb_2.4.52-1_i386.udeb:19.02 kB  321.88 
kB/s

ncftp /home/hille >



You have not saved a bookmark for this site.

Would you like to save a bookmark to:
ftp://hille:PASSWORD@192.168.1.131

Save? (yes/no) no
Not saved.  (If you don't want to be asked this, "set confirm-close no")


hille@sid:~ $


--
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

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

[Franklin Weng]

Package: proftpd-basic
Version: 1.3.5-1.1+deb8u1
Severity: grave
Justification: renders package unusable

proftpd started successfully in my jessie system.  However after some day
(it may be after a system-wide upgrade) the client failed to login.

The client part shows:

Connected to goodhorse.idv.tw.
220 ProFTPD 1.3.5 Server (Debian) [:::218.161.78.26]
Name (goodhorse.idv.tw:franklin): ftp
331 允許匿名登入，請用您完整的信箱位址做為登入密碼
Password:
421 Service not available, remote server has closed connection
Login failed.
No control connection for command: No such file or directory
ftp>


The server part (running with `proftpd -n -d 10`) shows

2016-10-06 11:47:43,524 teabbs proftpd[18292] teabbs.goodhorse.idv.tw
(223-137-143-82.EMOME-IP.hinet.net[223.137.143.82]): retrieved group ID:
65534
2016-10-06 11:47:43,524 teabbs proftpd[18292] teabbs.goodhorse.idv.tw
(223-137-143-82.EMOME-IP.hinet.net[223.137.143.82]): retrieved group name:
nogroup
2016-10-06 11:47:43,524 teabbs proftpd[18292] teabbs.goodhorse.idv.tw
(223-137-143-82.EMOME-IP.hinet.net[223.137.143.82]): dispatching PRE_CMD
command 'PASS (hidden)' to mod_shaper
2016-10-06 11:47:43,524 teabbs proftpd[18292] teabbs.goodhorse.idv.tw
(223-137-143-82.EMOME-IP.hinet.net[223.137.143.82]): ROOT PRIVS at
mod_shaper.c:2026
2016-10-06 11:47:43,524 teabbs proftpd[18292] teabbs.goodhorse.idv.tw
(223-137-143-82.EMOME-IP.hinet.net[223.137.143.82]): ProFTPD terminating
(signal 11)
2016-10-06 11:47:43,524 teabbs proftpd[18292] teabbs.goodhorse.idv.tw
(223-137-143-82.EMOME-IP.hinet.net[223.137.143.82]): ProFTPD terminating
(signal 11)
2016-10-06 11:47:43,524 teabbs proftpd[18292] teabbs.goodhorse.idv.tw
(223-137-143-82.EMOME-IP.hinet.net[223.137.143.82]): FTP session closed.
2016-10-06 11:47:46,046 teabbs proftpd[18278] teabbs.goodhorse.idv.tw:
scrubbing scoreboard



-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (501, 'stable'), (500, 'stable-updates'), (50, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages proftpd-basic depends on:
ii  adduser3.113+nmu3
ii  debconf1.5.56
ii  debianutils4.4+b1
ii  libacl12.2.52-2
ii  libc6  2.19-18+deb8u6
ii  libcap21:2.24-8
ii  libmemcached11 1.0.18-4
ii  libmemcachedutil2  1.0.18-4
ii  libncurses55.9+20140913-1+b1
ii  libpam-runtime 1.1.8-3.1+deb8u1
ii  libpam0g   1.1.8-3.1+deb8u1+b1
ii  libpcre3   2:8.35-3.3+deb8u4
ii  libssl1.0.01.0.1t-1+deb8u3
ii  libtinfo5  5.9+20140913-1+b1
ii  libwrap0   7.6.q-25
ii  netbase5.3
ii  sed4.2.2-4+b1
ii  ucf3.0030
ii  zlib1g 1:1.2.8.dfsg-2+b1

proftpd-basic recommends no packages.

Versions of packages proftpd-basic suggests:
pn  openbsd-inetd | inet-superserver  
ii  openssl   1.0.1t-1+deb8u3
pn  proftpd-doc   
pn  proftpd-mod-geoip 
pn  proftpd-mod-ldap  
pn  proftpd-mod-mysql 
pn  proftpd-mod-odbc  
pn  proftpd-mod-pgsql 
pn  proftpd-mod-sqlite

-- debconf information:
* shared/proftpd/inetd_or_standalone: standalone