Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: 220 (vsFTPd 2.0.3) USER someuser 331 Please specify the password. PASS somepass 530 Login incorrect. 500 OOPS: vsf_sysutil_recv_peek: no data 500 OOPS: child died grep someuser /etc/passwd: someuser:x:556:556:guest acct:/var/www/html/someuser/./:/etc/ftponly The shell /etc/ftponly is not in /etc/shells Version-Release number of selected component (if applicable): vsftpd-2.0.3-pre2, vsftpd-2.0.1-5 How reproducible: Always Steps to Reproduce: 1. Create a user with a password and a shell that doesn't exist in /etc/shells 2. Try to log in. 3. Actual Results: 530 Login incorrect. 500 OOPS: vsf_sysutil_recv_peek: no data 500 OOPS: child died Expected Results: Successful login. Additional info: It's a mystery to me why a bad shell should cause such a hiccup. I'd expect a nice (or mysterious) error message for the user and a clear error message to syslog.
Can't reproduce any vsftpd problem. 500 OOPS: vsf_sysutil_recv_peek: no data usually means that the FTP client just disconnects suddenly. What FTP client is in use here?
Initially I discovered the problem using Mozilla. Then I tried the regular 'ftp' command. I wound up using 'telnet' to demonstrate the problem to myself. It's been a while, and I've reformatted that system since then, but I'm thinking it might have been a problem with selinux. Try adding a user to the password and shadow files with 'vi', don't tell selinux about the user, and see if that causes it. If not, then I guess this bug has vanished. Sorry for the long delay!
The problem will go away as soon as you disable selinx. I would like the work around for selinux enabled. :)
If it's a selinux issue, can you post the vsftpd related lines from /var/log/audit.log and /var/log/messages here?
Ouchie. I reformatted that system in July of last year and haven't experienced the problem since. I just tried recreating it on my current system (FC4), and couldn't. I guess this bug is now close-able; sorry!
No problem, it took me quite a long time to get back to this bug :) I'm closing it as CURRENTRELEASE.