Vsftpd is dead but subsys is locked

VsftpdIs the most popular FTP server program in the Linux release. Features: small, light, secure, and easy to use. After a long time, I found a problem: vsftpd is dead, but subsys is locked. There are two answers for online search. See the following analysis!

Run after power-on today

# Service vsftpd start

# Service vsftpd status

Vsftpd is dead, but subsys is locked

After this error is found, the current configuration file is backed up to vsftpd. conf. bak20060401 to restore the previously backed up vsftpd. conf.

Restart vsftpd and run normally

Compare the current vsftpd. conf with the error vsftpd. conf. bak20060401

# Diff vsftpd. conf vsftpd. conf. bak20060401

32d31

48c47

---

> # Add chown_username and anon_umask to forbid downloading

60c59

---

> Idle_session_timeout = 600

Listen a107, 109

### Add chroot_local_user

> Max_clients = 5

> Max_per_ip = 2

2017a111

> Chroot_local_user

110c113

---

> # Userlist_enable = YES

The problem is found. The value of chroot_local_user is not defined.

Change to chroot_local_user = YES

# Mv vsftpd. conf. bak20060401 vsftpd. conf

Normal after restart

Previously, I searched for "vsftpd is dead, but subsys is locked" on the Internet"

There is only one result.

"There is a gssftp conflict with vsftpd in the super process. After gssftp is blocked, restart xinet and vsftpd ."

It seems that this sentence is not comprehensive.

Because there is no gssftp in my process, a low-level error occurs in vsftpd. conf.

I think most of the problems I encountered should be the same as I configured vsftp. conf, which has some negligence rather than the so-called gssftp.

Therefore, this statement is not completely credible if it is reproduced in large numbers on the Internet.

After reading this article, the key points of the problem have been found out. The solution is not that complicated!