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: | proftpd | Assignee: | Paul Howarth <paul> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | 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
Is this crash happening at start-up of proftpd, or after it's been running for a while? 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]# Is this at all reproducible? 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 This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. 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 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? 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. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |