vsftpd and the dreaded “500 OOPS: could not bind listening IPv4 socket”

During a server move from Slackware 13.0 to Slackware 64 13.0, I encountered the dreaded “500 OOPS: could not bind listening IPv4 socket” error from vsftpd.

As you may know, Slackware runs vsftpd (and some other services) from inetd: the internet “super-server.” After a bit of searching and some piddling around, I found a very simple solution: add the following to /etc/vsftpd.conf

listen=NO

FYI, I actually just uncommented the line listen=YES and changed YES to NO.

I post this in hopes that next time I encounter this issue, I’ll have the answer stored!

Happy ‘putering!
Stu…

4 thoughts on “vsftpd and the dreaded “500 OOPS: could not bind listening IPv4 socket””

Leave a Comment