vsftpd (w/ Fedora Core 4) File Write Problems
 

Hello.

I recently installed Fedora Core 4 with its server packages. I'm using vsftpd (which was installed with the FC4 distro) in attempt to set up a properly working FTP server. Here's what I've done:

(1) configured /etc/vsftpd/vsftpd.conf to denyi anonymous access, but allow local users to log in
(2) created a user "michaelgubbels" with home dir /home/michaelgubbels
(3) restarted vsftpd

I can log in successfully but when trying to create a directory or upload files I get an error message stating "550 Create directory operation failed."

Any ideas? I would appreciate help greatly on this issue.

Thanks.

More details are needed.
What client are you using?
What logging mode is enabled?
Post your vsftpd.conf

When you first load the directory, do you start in /home/michaelgubbels?
or more like / or somewhere else? You might be trying to write to a directory other than michaelgubbels's which would cause permission issues.

If you can see the whole server when you should only see the users directory (when logged in as the user), you might want to check into the chroot options in the conf. file as well.

I've got exactly the same problem with vsftpd on Fedora Core 4

I've opened a Terminal window on the ftp server itself so there can't be any firewall issues

the user I'm using is oracle and his home is /home/oracle - I've set vstpd.conf to write_enable=YES and local_enable=YES

when I ftp and log in as oracle my path becomes "/home/oracle" as expected. I can "ls" and "get" successfully but as soon as I try to do a "put" or "mput" I get a 553 error. If I try to do a "mkdir" then I get a 550 error

I have set /home/oracle permissions to rwx for user group and other

I have no idea what else to try - can anyone please help!!

thanks very much

Check your log files. Also post your vsftpd.conf

snoek-
check who owns the files that are in that home directory..

ls-la /home/oracle in a terminal window

example would be:

[root@LDC1 ~]# ls -la /home/admin
total 48
drwxr-xr-x 6 admin admin 4096 Aug 8 08:38 .
drwxr-xr-x 10 root root 4096 Aug 8 18:10 ..
-rw-r--r-- 1 admin admin 24 Aug 8 08:38 .bash_logout
-rw-r--r-- 1 admin admin 191 Aug 8 08:38 .bash_profile
-rw-r--r-- 1 admin admin 124 Aug 8 08:38 .bashrc
drwxr-xr-x 2 admin admin 4096 Aug 8 08:38 cgi-bin
-rw-r--r-- 1 admin admin 120 Aug 8 08:38 .gtkrc
drwxr-xr-x 2 admin admin 4096 Aug 8 08:38 homes
drwxr-xr-x 2 admin admin 4096 Aug 8 08:38 logs
drwxr-xr-x 3 admin admin 4096 Aug 8 08:38 public_html
-rw-r--r-- 1 admin admin 658 Aug 8 08:38 .zshrc

Make sure the owners match for user/group.
In my example admin is owner and also group

IF these aren't Oracle in your case, you will want to
chmod <files> oracle
chgrp <files> oracle

Could be way off but thats what I would check out!~

I've got exactly the same problem here...

Since I've upgraded to FC4 nothing but problems

A. My tty's wont do it anymore
B. Samba is working against me
C. VSFTPD is totally out of control

D. I think I'm gooing to downgrad to FC3

Same problem here, vsftpd worked in FC3, but not in FC4 ('550 errors' when uploading files).
Has anyone got it working in FC4?

Thanks.

PS going to look bug reports about vsftpd in FC4.

i've also been having the same 550 and 553 error messages when uploading files and folders to my FC4 system. I'm using the default settings/vsftpd.conf file. strange cuz the default settings in FC3 worked from jumped.

any ideas???

Since Fedora uses a kind of 'tripwire' system to prevent some files from beeing changed, this is enabled by default in FC4.
You need to disable this security setting, and everything should work. (At least it dit overhere, but now I'm running on SuSe9.3).
I believe it's somwhere with the firewall settings. (During installation you'll be prompted for this setting)

I got my vsftpd working by:
1) disabled selinux (from system tools -> security level)
2) restored the default vsftpd.conf (asked from a friend)

Now all uploads and features work as expected.

worked like a charm. thanx

Wouldn't a better solution be to edit the SELinux settings so the specific users, groups, etc. have permissions to the specific areas they need to access. By disabling SELinux, you've (potentially) opened the door to your system fairly wide.

Found a solution that does not require disabling the whole selinux:
http://www.fedoraforum.org/forum/sho...316#post321485

Has anyone found a solution to the SELinux VSFTPd context problem?