Bug 1284246

Summary: EL 7: proftpd segfault - mod_delay/0.7: unable to open DelayTable '/run/proftpd/proftpd.delay'
Product: [Fedora] Fedora EPEL Reporter: Peter Bieringer <pb>
Component: proftpdAssignee: Paul Howarth <paul>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: epel7CC: itamar, matthias, paul, ruben
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-07-08 22:20:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Bieringer 2015-11-22 11:45:12 UTC
Description of problem:
proftpd crashed on CentOS 7 once mod_delay becomes active

Version-Release number of selected component (if applicable):
proftpd-1.3.5a-1.el7.x86_64

How reproducible: at least one time

Steps to Reproduce: don't know


Actual results:
Nov 22 07:40:28 *** proftpd[854]: 2015-11-22 07:40:28,011 *** proftpd[854] ***: ProFTPD killed (signal 15)
Nov 22 07:40:28 *** proftpd[854]: 2015-11-22 07:40:28,097 *** proftpd[854] ***: mod_delay/0.7: unable to open DelayTable '/run/proftpd/proftpd.delay': 그런 파일이나 디렉터리가 없습니다
Nov 22 07:40:28 *** proftpd[854]: 2015-11-22 07:40:28,097 *** proftpd[854] ***: ProFTPD 1.3.5a standalone mode SHUTDOWN


also happened in the past:
Sep 11 12:14:31 *** proftpd[774]: 2015-09-11 12:14:31,634 *** proftpd[774] ***: mod_delay/0.7: unable to open DelayTable '/run/proftpd/proftpd.delay': Няма такъв файл или директория



Expected results:
No crash


Additional info:
mod_delay is built-in in this release

# proftpd -v
ProFTPD Version 1.3.5a

# proftpd -l |grep mod_delay
  mod_delay.c

according to http://www.proftpd.org/docs/modules/mod_delay.html DelayEngine is also active by default.

Related directory is empty:

# ll /run/proftpd
total 0

but after start->stop the delay file is existing:

# LC_ALL=C ll /run/proftpd/
total 28
-rw-r--r-- 1 root root 25216 Nov 22 12:25 proftpd.delay


missing file can be reproduced by delete while proftpd is running, but this do not cause the crash.

Hopefully not a new security hole...

Comment 1 Paul Howarth 2016-01-07 11:26:32 UTC
Is this crash happening at start-up of proftpd, or after it's been running for a while?

Comment 2 Ruben Püttmann 2017-08-03 09:46:51 UTC
hi,

we have the same problem. It happend after start.:

JJul 10 22:51:11 XXXXXXX proftpd: 2017-07-10 22:51:11,466 XXXXX.stratoserver.net proftpd[339] XX.XXX.XXX.XX: ProFTPD killed (signal 15)
Jul 10 22:51:21 XXXXXXX proftpd: 2017-07-10 22:51:11,788 XXXXX.stratoserver.net proftpd[339] XX.XXX.XXX.XX: mod_delay/0.7: unable to open DelayTable '/run/proftpd/proftpd.delay': そのようなファイルやディレクトリはありません
Jul 10 22:51:21 XXXXXXX proftpd: 2017-07-10 22:51:11,788 XXXXX.stratoserver.net proftpd[339] XX.XXX.XXX.XX: ProFTPD 1.3.5e standalone mode SHUTDOWN

system locale is C. So this wired utf-8 char in log will be generated from 
proftpd

Base is:


[root@XXXXX log]# cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core) 
[root@XXXXX log]# rpm -qa |grep proft
proftpd-1.3.5e-2.el7.x86_64
proftpd-utils-1.3.5e-2.el7.x86_64
[root@XXXXX log]#

Comment 3 Paul Howarth 2017-08-03 10:04:47 UTC
Is this at all reproducible?

Comment 4 Ruben Püttmann 2017-08-04 09:48:14 UTC
It happend in the last month two times on my system. 
I think it is external triggered. I self have not found a way to manual reproduce

Comment 5 Fedora Admin user for bugzilla script actions 2021-02-17 00:08:01 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 6 Fedora Admin user for bugzilla script actions 2021-02-17 12:05:52 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 7 Paul Howarth 2023-11-26 10:18:47 UTC
It's possible that this issue may be triggered by ProFTPD not being able to resolve the IP address of a Virtual Host when it starts up. A fix for that issue may be to use the DefaultAddress directive to specify the address for the Virtual Host.

A similar issue was recently addressed in the upstream bug tracker:
https://github.com/proftpd/proftpd/issues/1746#issuecomment-1817922682

Comment 8 Peter Bieringer 2023-12-10 21:10:01 UTC
At least I haven't seen that issue after migration of the server to EL8 running

proftpd-1.3.6e-5.el8.x86_64

DefaultAddress is not set in the config and at least IPv6 addresses of virtual hosts are not resolvable back to name.

@Ruben: have you seen that issue since your last comment in 2017?

Comment 9 Troy Dawson 2024-07-08 22:20:30 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.

Comment 10 Red Hat Bugzilla 2024-11-06 04:25:03 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days