RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1893636 - vsftpd service starts before network is UP
Summary: vsftpd service starts before network is UP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vsftpd
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.4
Assignee: aegorenk
QA Contact: Ondrej Mejzlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-02 09:07 UTC by Apurbita Mukherjee
Modified: 2021-05-18 15:49 UTC (History)
3 users (show)

Fixed In Version: vsftpd-3.0.3-33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:44:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:1826 0 None None None 2021-05-18 15:44:06 UTC

Description Apurbita Mukherjee 2020-11-02 09:07:57 UTC 
Description of problem:

When vsftpd is configured to listen on a specific ip address (instead of any address) by using the listen_address statement in vsftpd.conf, it fails to start at boot because the network is not yet configured when the service tries to start. The problem only occurs when using the listen_address (or listen_address6) statement.

Starting the service manually with "systemctl start vsftpd" after logging in via ssh works fine, since the at this point, the network is fully configured.

The root cause is that the systemd unit file (/usr/lib/systemd/system/vsftpd.service) has "After=network.target" instead of "After=network-online.target".


Version-Release number of selected component (if applicable):
vsftpd-3.0.3-31.el8

How reproducible:
Always

Steps to Reproduce:
1. cat /usr/lib/systemd/system/vsftpd.service
[Unit]
Description=Vsftpd ftp daemon
After=network.target

[Service]
Type=forking
ExecStart=/usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf

[Install]
WantedBy=multi-user.target

2. Restart vsftpd service. Due to above configuration, vsftpd service starts before network is up as explained above in description.


Actual results:
vsftpd service starts before network is up as explained above in description.


Expected results:
vsftpd service should start after the network is online.

Additional info:
Every time vsftpd starts at boot and trying to listen to only a specific address
Comment 10 errata-xmlrpc 2021-05-18 15:44:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (vsftpd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1826
Note You need to log in before you can comment on or make changes to this bug.