Your message dated Mon, 2 Mar 2009 10:05:49 +0100
with message-id <20090302090548.ga19...@mithrandir>
and subject line Re: Bug#517680: Proftpd-basic with proftpd-mod-pgsql : 
connection closed immediately: General Protection Rip
has caused the Debian Bug report #517680,
regarding Proftpd-basic with proftpd-mod-pgsql : connection closed immediately: 
General Protection Rip
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
517680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517680
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: proftpd-basic

Version:  1.3.1-17lenny1

 

Bug:

Proftpd is up and running. Connections are possible from remote and local,
but session is closed direct after connect (even before “Server ist ready”
message).

 

 

Syslog tells on connect:

jonathan kernel: proftpd[8904] general protection rip:2b1a87d33c98
rsp:ff17fdd575018919 error:0

 

 

strace tells (“strace proftpd -nd6”):

“

…
clone(jonathan.xxxxxx (yyy.yyy.yyy.yyy[zzz.zzz.zzz.zzz]) - FTP session
requested from unknown class
child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x2af5c1409200) = 9208
close(7)                                = 0
time([1235909534])                      = 1235909534
close(9)                                = 0
rt_sigprocmask(SIG_UNBLOCK, [USR1 USR2 TERM CHLD], NULL, 8) = 0
fcntl(1, F_GETFL)                       = 0x802 (flags O_RDWR|O_NONBLOCK)
fcntl(1, F_SETFL, O_RDWR)               = 0
lstat("/etc/shutmsg", 0x7fffea765640)   = -1 ENOENT (No such file or
directory)
select(9, [1 8], NULL, NULL, {30, 0})   = 1 (in [8], left {30, 0})
time(NULL)                              = 1235909534
close(8)                                = 0
lstat("/etc/shutmsg", 0x7fffea765640)   = -1 ENOENT (No such file or
directory)
select(2, [1], NULL, NULL, {30, 0})     = ? ERESTARTNOHAND (To be restarted)
--- SIGCHLD (Child exited) @ 0 (0) ---
rt_sigprocmask(SIG_BLOCK, [TERM CHLD], NULL, 8) = 0
wait4(-1, NULL, WNOHANG, NULL)          = 9208
wait4(-1, NULL, WNOHANG, NULL)          = -1 ECHILD (No child processes)
rt_sigprocmask(SIG_UNBLOCK, [TERM CHLD], NULL, 8) = 0
rt_sigaction(SIGCHLD, {0x40d700, [CHLD], SA_RESTORER|SA_RESTART,
0x2af5c10e6f60}, {0x40d700, [CHLD], SA_RESTORER|SA_RESTART, 0x2af5c10e6f60},
8) = 0
rt_sigreturn(0x11)                      = -1 EINTR (Interrupted system call)
rt_sigprocmask(SIG_BLOCK, [TERM CHLD], NULL, 8) = 0
wait4(-1, NULL, WNOHANG, NULL)          = -1 ECHILD (No child processes)
rt_sigprocmask(SIG_UNBLOCK, [TERM CHLD], NULL, 8) = 0
lstat("/etc/shutmsg", 0x7fffea765640)   = -1 ENOENT (No such file or
directory)
select(2, [1], NULL, NULL, {30, 0})     = ? ERESTARTNOHAND (To be restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---
rt_sigaction(SIGALRM, {0x414120, [], SA_RESTORER|SA_INTERRUPT,
0x2af5c10e6f60}, NULL, 8) = 0
rt_sigaction(SIGALRM, NULL, {0x414120, [], SA_RESTORER|SA_INTERRUPT,
0x2af5c10e6f60}, 8) = 0
rt_sigaction(SIGALRM, {0x414120, [], SA_RESTORER|SA_INTERRUPT,
0x2af5c10e6f60}, NULL, 8) = 0
time(NULL)                              = 1235909542
alarm(10)                               = 0
rt_sigreturn(0xa)                       = -1 EINTR (Interrupted system call)
alarm(0)                                = 10
time(NULL)                              = 1235909542
select(6, [4], NULL, NULL, {0, 500})    = 0 (Timeout)
time(NULL)                              = 1235909542
alarm(10)                               = 0
lstat("/etc/shutmsg", 0x7fffea765640)   = -1 ENOENT (No such file or
directory)
select(2, [1], NULL, NULL, {30, 0}

”

 

 

Proftpd-Log tells on connect:

“

Mär 01 13:13:03 mod_sql/4.2.2[9246]: defaulting to 'postgres' backend
Mär 01 13:13:03 mod_sql/4.2.2[9246]: backend module 'mod_sql_postgres/4.0.4'
Mär 01 13:13:03 mod_sql/4.2.2[9246]: backend api    'mod_sql_api_v1'
Mär 01 13:13:03 mod_sql/4.2.2[9246]: >>> sql_sess_init
Mär 01 13:13:03 mod_sql/4.2.2[9246]: entering   postgres
cmd_defineconnection
Mär 01 13:13:03 mod_sql/4.2.2[9246]:  name: 'default'
Mär 01 13:13:03 mod_sql/4.2.2[9246]:  user: 'proftpd'
Mär 01 13:13:03 mod_sql/4.2.2[9246]:  host: 'localhost'
Mär 01 13:13:03 mod_sql/4.2.2[9246]:    db: 'productive'
Mär 01 13:13:03 mod_sql/4.2.2[9246]:  port: '5432'
Mär 01 13:13:03 mod_sql/4.2.2[9246]:   ttl: '0'
Mär 01 13:13:03 mod_sql/4.2.2[9246]: exiting    postgres
cmd_defineconnection
Mär 01 13:13:03 mod_sql/4.2.2[9246]: entering   postgres cmd_open

“

 

Kernel:                                 2.6.18-6-xen-amd64

Shared Library:                 lrwxrwxrwx 1 root root 11 24. Feb 18:02
/lib/libc.so.6 -> libc-2.7.so

 

My Assumption: Child-Spawn on FTP-Connect failed, therefore session is
immediately closed. The main-process is running after such a connect
failure, so the general protection rip seem to happen in the child.

 

 


--- End Message ---
--- Begin Message ---
Package: proftpd-dfsg
Version: 1.3.1-17lenny2

That's fixed in the package version above, still pending in the security queue 
AFAIK.

-- 
Francesco P. Lovergine


--- End Message ---

Reply via email to