Sponsored Content
Operating Systems Linux 500 OOPS: vsftpd: cannot locate user specified in 'ftp_username':ftp Post 302325859 by thomn8r on Tuesday 16th of June 2009 10:17:57 AM
Old 06-16-2009
500 OOPS: vsftpd: cannot locate user specified in 'ftp_username':ftp

I've been fighting this for about a year: vsftp does not work on any of my RedHat Server 5.x systems - I keep getting a variation on 500 OOPS: vsftpd: cannot locate user specified in 'ftp_username':ftp or 500 OOPS: cannot locate user entry:nobody (different errors on different systems). I spent some time on google trying to find a solution, to no avail. I even tried to build from source but ran into other issues. The only way I've been able to get around this is to re-install with an older version of RedHat.

No matter what I change the ftp_username value to, I get the same result.

The ftp & nobody users exists in /etc/passwd
Code:
ftp:x:14:50:FTP User:/var/ftp:/sbin/nologin
nobody:x:99:99:Nobody:/:/sbin/nologin

Here's my vsftpd.conf file (comments removed for brevity)
Code:
anonymous_enable=YES
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
xferlog_std_format=YES
nopriv_user=ftp
listen=YES
pam_service_name=vsftpd
userlist_enable=NO
tcp_wrappers=YES
check_shell=NO
ftp_username=ftp

/etc/nsswitch.conf
Code:
passwd:       files [NOTFOUND=continue] nis
group:        files [NOTFOUND=continue] nis
hosts:        dns [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] nis [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] files
networks:     nis [NOTFOUND=return] files
protocols:    nis [NOTFOUND=return] files
rpc:          nis [NOTFOUND=return] files
publickey:    nis [NOTFOUND=return] files
netgroup:     nis [NOTFOUND=return] files
automount:    nis files
aliases:      nis files
services:     nis files

Code:
# ps -ef|grep vsftp
root     28607     1  0 Jul01 ?        00:00:00 /usr/sbin/vsftpd /etc/vsftpd/vsftpd.conf

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Locate a user by their IP address

We have a user that is sending rather large print jobs to a windows printer, we need to track them down and advise a sensible approach to printing. The only thing that shows up in the windows print manager is the IP address of the source. Is this achievable? :confused: (7 Replies)
Discussion started by: jagannatha
7 Replies

2. UNIX for Dummies Questions & Answers

Telnet Server FTP warning messages 500 'AUTH GSSAPI' how to resolve??

These are the warning messages I am getting but the FTP works fine.How do I get rid of these? 220 FTP server (SunOS 5.8) ready. 500 'AUTH GSSAPI': command not understood. 500 'AUTH KERBEROS_V4': command not understood. KERBEROS_V4 rejected as an authentication type (0 Replies)
Discussion started by: csviking
0 Replies

3. Ubuntu

500 OOPS: vsftpd: cannot locate user specified in 'ftp_username':ftp

I've been tearing my hair out over this: vsftp does not work on any of my RedHat Server 5.x systems - I keep getting a variation on 500 OOPS: vsftpd: cannot locate user specified in 'ftp_username':ftp or 500 OOPS: cannot locate user entry:nobody (different errors on different systems). I spent... (2 Replies)
Discussion started by: thomn8r
2 Replies

4. Red Hat

FTP problem in vsftpd & NcFTPd both

Hello Gurus, after installtion and configuration of vsftpd and NcFTPd, i could able to ftp from another Linux server but not from other windows cmd prompt. :mad: It show user/PASS need to be provided :( its not even prompting for username and password. :( Y it differs from windows and... (0 Replies)
Discussion started by: bullz26
0 Replies

5. Solaris

FTP problem in vsftpd & NcFTPd both

Hello Gurus, after installtion and configuration of vsftpd and NcFTPd, i could able to ftp from another Linux server but not from other windows cmd prompt. It show user/PASS need to be provided its not even prompting for username and password. Y it differs from windows and linux...? ... (1 Reply)
Discussion started by: bullz26
1 Replies

6. UNIX for Dummies Questions & Answers

VSFTPD - User or IP based SSL encryption?

Is there a way i can only force SSL encryption if they connect from outside our network OR allow certain IP's to connect without using encryption? (0 Replies)
Discussion started by: mokachoka
0 Replies

7. Ubuntu

vsftpd ftp server

Hi I am using the vsftpd ftp server. I am using it for the wordpress that I run. The folder /var/www/wordpress/wp-content has only root write permission. No one else has right permission to it. I want to give the vsftpd ftp also write permission for it. But no other user should have that... (1 Reply)
Discussion started by: programAngel
1 Replies

8. UNIX for Dummies Questions & Answers

Read Only user in Vsftpd

HI I have set up vsftp on my Red hat server. Chroot has been set up to control access to each user and folder directories. This all works fine. But i have one directory where i want to chroot but ensure that the ftp access is read only. Any help appreciated thanks Treds (1 Reply)
Discussion started by: treds
1 Replies

9. UNIX for Advanced & Expert Users

Does vsftpd support user access with client certificate with priv/pub key + vsftpd certificate?

:rolleyes:I am trying to setup all certificate based client-server environment in Linux using vsftpd and curl with openssl. I would like to make a user access with vsftpd certificate and user own client certificate (self-signed) with private/public key. I don't see google posts about the my plan... (4 Replies)
Discussion started by: gogogo
4 Replies

10. Red Hat

Does vsftpd support user subcommand?

I'm wondering if vsftpd supports user subcommand? I found I can't switch user after ftp login. Maybe someone can give me a certain answer. I always got the message as below, I enabled log_ftp_protocol=YES and checked the vsftpd.log, it didn't help much actually. The log file only... (6 Replies)
Discussion started by: bestard
6 Replies
NSSWITCH.CONF(5)					     Linux Programmer's Manual						  NSSWITCH.CONF(5)

NAME
nsswitch.conf - System Databases and Name Service Switch configuration file DESCRIPTION
Various functions in the C Library need to be configured to work correctly in the local environment. Traditionally, this was done by using files (e.g., /etc/passwd), but other nameservices (like the Network Information Service (NIS) and the Domain Name Service (DNS)) became popular, and were hacked into the C library, usually with a fixed search order. The Linux libc5 with NYS support and the GNU C Library 2.x (libc.so.6) contain a cleaner solution of this problem. It is designed after a method used by Sun Microsystems in the C library of Solaris 2. We follow their name and call this scheme "Name Service Switch" (NSS). The sources for the "databases" and their lookup order are specified in the /etc/nsswitch.conf file. The following databases are available in the NSS: aliases Mail aliases, used by sendmail(8). Presently ignored. ethers Ethernet numbers. group Groups of users, used by getgrent(3) functions. hosts Host names and numbers, used by gethostbyname(3) and similar functions. netgroup Network wide list of hosts and users, used for access rules. C libraries before glibc 2.1 only support netgroups over NIS. networks Network names and numbers, used by getnetent(3) functions. passwd User passwords, used by getpwent(3) functions. protocols Network protocols, used by getprotoent(3) functions. publickey Public and secret keys for Secure_RPC used by NFS and NIS+. rpc Remote procedure call names and numbers, used by getrpcbyname(3) and similar functions. services Network services, used by getservent(3) functions. shadow Shadow user passwords, used by getspnam(3). An example /etc/nsswitch.conf (namely, the default used when /etc/nsswitch.conf is missing): passwd: compat group: compat shadow: compat hosts: dns [!UNAVAIL=return] files networks: nis [NOTFOUND=return] files ethers: nis [NOTFOUND=return] files protocols: nis [NOTFOUND=return] files rpc: nis [NOTFOUND=return] files services: nis [NOTFOUND=return] files The first column is the database. The rest of the line specifies how the lookup process works. You can specify the way it works for each database individually. The configuration specification for each database can contain two different items: * The service specification like `files', `db', or `nis'. * The reaction on lookup result like `[NOTFOUND=return]'. For libc5 with NYS, the allowed service specifications are `files', `nis', and `nisplus'. For hosts, you could specify `dns' as extra ser- vice, for passwd and group `compat', but not for shadow. For glibc, you must have a file called /lib/libnss_SERVICE.so.X for every SERVICE you are using. On a standard installation, you could use `files', `db', `nis', and `nisplus'. For hosts, you could specify `dns' as extra service, for passwd, group, and shadow `compat'. These services will not be used by libc5 with NYS. The version number X is 1 for glibc 2.0 and 2 for glibc 2.1. The second item in the specification gives the user much finer control on the lookup process. Action items are placed between two service names and are written within brackets. The general form is `[' ( `!'? STATUS `=' ACTION )+ `]' where STATUS => success | notfound | unavail | tryagain ACTION => return | continue The case of the keywords is insignificant. The STATUS values are the results of a call to a lookup function of a specific service. They mean: success No error occurred and the wanted entry is returned. The default action for this is `return'. notfound The lookup process works ok but the needed value was not found. The default action is `continue'. unavail The service is permanently unavailable. This can either mean the needed file is not available, or, for DNS, the server is not available or does not allow queries. The default action is `continue'. tryagain The service is temporarily unavailable. This could mean a file is locked or a server currently cannot accept more connections. The default action is `continue'. Interaction with +/- syntax (compat mode) Linux libc5 without NYS does not have the name service switch but does allow the user some policy control. In /etc/passwd you could have entries of the form +user or +@netgroup (include the specified user from the NIS passwd map), -user or -@netgroup (exclude the specified user), and + (include every user, except the excluded ones, from the NIS passwd map). You can override certain passwd fields for a particular user from the NIS passwd map by using the extended form of +user:::::: in /etc/passwd. Non-empty fields override information in the NIS passwd map. Since most people only put a + at the end of /etc/passwd to include everything from NIS, the switch provides a faster alternative for this case (`passwd: files nis') which doesn't require the single + entry in /etc/passwd, /etc/group, and /etc/shadow. If this is not suffi- cient, the NSS `compat' service provides full +/- semantics. By default, the source is `nis', but this may be overridden by specifying `nisplus' as source for the pseudo-databases passwd_compat, group_compat and shadow_compat. These pseudo-databases are only available in GNU C Library. FILES
A service named SERVICE is implemented by a shared object library named libnss_SERVICE.so.X that resides in /lib. /etc/nsswitch.conf configuration file /lib/libnss_compat.so.X implements `compat' source for glibc2 /lib/libnss_db.so.X implements `db' source for glibc2 /lib/libnss_dns.so.X implements `dns' source for glibc2 /lib/libnss_files.so.X implements `files' source for glibc2 /lib/libnss_hesiod.so.X implements `hesiod' source for glibc2 /lib/libnss_nis.so.X implements `nis' source for glibc2 /lib/libnss_nisplus.so.2 implements `nisplus' source for glibc 2.1 NOTES
Within each process that uses nsswitch.conf, the entire file is read only once; if the file is later changed, the process will continue using the old configuration. With Solaris, it isn't possible to link programs using the NSS Service statically. With Linux, this is no problem. On a Debian system other mail transport agents may or may not ignore the aliases file. For example, unlike sendmail Exim does not ignore it. COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 1999-01-17 NSSWITCH.CONF(5)
All times are GMT -4. The time now is 05:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy