Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My name's Todd and I'm having some trouble with ProFTPd. Also that the moment, my server won't run Postfix correctly saying "Relay access denied." I'm wondering if ProFTPd's problem is the same as Postfix's. I'll explain what happens.
I try logging in and nothing happens. I run netstat and nothing turns up for ProFTPd. I look at the logs and ProFTPd didn't log anything except for the syslogger in the syslog: "proftpd[10180]: xetaspace.net - socket() failed in connection initialization: Address family not supported by protocol".
I'm somewhat experienced but still inexperienced in all areas of Linux and Debian (which I'm running). So I'm not sure how to fix it. I tried all old ProFTPd configs which worked before all this but now do nothing. I am trying to figure out what's causing this. Does anyone know what I can do? I tried removing and purging ProFTPd and then reinstalling it again but still nothing.
However, when I removed ProFTPd with apt-get, it told me that contents were left in "/var/run/proftpd" and so it wasn't removed which is ironic since I looked and it was removed by apt-get during removal or purging. Could this be part of the problem to ProFTPd not starting?
Probably there's a line in your configuration file (/etc/proftpd/proftpd.conf) which enables the IPV6 protocol. Normally you don't use this so you must modify the configuration file and change UseIPv6 on to UseIPv6 off.
Now you can start ProFTPD using /etc/init.d/proftpd start.
I tried that but it doesn't seem to work. It's ProFTPd 1.2.16 (I believe) and I tried the UseIPv6 directive but it says,
Code:
Starting ProFTPD ftp daemon: - Fatal: unknown configuration directive 'UseIPv6' on line 20 of '/etc/proftpd.conf'.
.
Here's my proftpd.conf file:
Code:
#
# ispCP OMEGA ProFTPd config file
#
#
#
# Includes required DSO modules. This is mandatory in proftpd 1.3
#
#Include /etc/proftpd/modules.conf
ServerName "xetaspace.net"
ServerType standalone
DeferWelcome off
ShowSymlinks on
MultilineRFC2228 on
DefaultServer on
ShowSymlinks on
AllowOverwrite on
UseReverseDNS off
IdentLookups off
AllowStoreRestart on
AllowForeignAddress on
LogFormat traff "%b %u"
TimeoutNoTransfer 600
TimeoutStalled 600
TimeoutIdle 1200
DisplayLogin welcome.msg
DisplayFirstChdir message
#LsDefaultOptions "-l"
DenyFilter \*.*/
DefaultRoot ~
# Uncomment this if you are using NIS or LDAP to retrieve passwords:
#PersistentPasswd off
# Port 21 is the standard FTP port.
Port 21
# To prevent DoS attacks, set the maximum number of child processes
# to 30. If you need to allow more than 30 concurrent connections
# at once, simply increase this value. Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
MaxInstances 30
# Set the user and group that the server normally runs at.
User nobody
Group nogroup
# Normally, we want files to be overwriteable.
<Directory /*>
# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask 022 022
AllowOverwrite on
HideNoAccess on
</Directory>
<Limit ALL>
IgnoreHidden on
</Limit>
<Global>
RootLogin off
TransferLog /var/log/proftpd/xferlog
ExtendedLog /var/log/proftpd/ftp_traff.log read,write traff
PathDenyFilter "\.quota$"
</Global>
<IfModule mod_delay.c>
DelayEngine off
</IfModule>
#
# ISPCP Managment;
#
#SQLBackend mysql # enable for proFTPd >= 1.3
SQLAuthTypes Crypt
SQLAuthenticate on
SQLConnectInfo ispcp@localhost root *********
SQLUserInfo ftp_users userid passwd uid gid homedir shell
SQLGroupInfo ftp_group groupname gid members
SQLMinID 2000
#
# ISPCP Quota management;
#
QuotaEngine on
QuotaShowQuotas on
QuotaDisplayUnits Mb
SQLNamedQuery get-quota-limit SELECT "name, quota_type, per_session, limit_type, bytes_in_avail, bytes_out_avail, bytes_xfer_avail, files_in_avail, files_out_avail, files_xfer_avail FROM quotalimits WHERE name = '%{0}' AND quota_type = '%{1}'"
SQLNamedQuery get-quota-tally SELECT "name, quota_type, bytes_in_used, bytes_out_used, bytes_xfer_used, files_in_used, files_out_used, files_xfer_used FROM quotatallies WHERE name = '%{0}' AND quota_type = '%{1}'"
SQLNamedQuery update-quota-tally UPDATE "bytes_in_used = bytes_in_used + %{0}, bytes_out_used = bytes_out_used + %{1}, bytes_xfer_used = bytes_xfer_used + %{2}, files_in_used = files_in_used + %{3}, files_out_used = files_out_used + %{4}, files_xfer_used = files_xfer_used + %{5} WHERE name = '%{6}' AND quota_type = '%{7}'" quotatallies
SQLNamedQuery insert-quota-tally INSERT "%{0}, %{1}, %{2}, %{3}, %{4}, %{5}, %{6}, %{7}" quotatallies
QuotaLock /var/run/proftpd/tally.lock
QuotaLimitTable sql:/get-quota-limit
QuotaTallyTable sql:/get-quota-tally/update-quota-tally/insert-quota-tally
#
# SSL via TLS
#
#<IfModule mod_tls.c>
# TLSEngine off # on for use of TLS
# TLSLog /var/log/proftpd/ftp_ssl.log # where to log to
# TLSProtocol SSLv23 # SSLv23 or TLSv1
# TLSOptions NoCertRequest # either to request the certificate or not
# TLSRSACertificateFile /etc/proftpd/ssl.crt # SSL certfile
# TLSRSACertificateKeyFile /etc/proftpd/ssl.key # SSL keyfile
# TLSVerifyClient off # client verification
#</IfModule>
Not to sound condescending, but I don't think it's a config problem. I even had the default config installed when ProFTPd is installed fresh and it still wouldn't start.
Personally I think it might be a problem with either another program or a port or socket is being blocked.
Maybe you can upgrade to the new version of ProFTPd. It seems like your total configuration is corrupt. Have you installed some weird stuff on your server which has caused these errors?
That's just really strange. I only installed ispCP (a VHCS fork) which is a web hosting control panel but it still has compatibility with ProFTPd. And ProFTPd was working about a couple days ago. I would upgrade but I'd need to either build it myself (from ProFTP sources) or upgrade from Sarge (which isn't very likely since my data center controls OS upgrades and such). I'd like to stick to keeping as much preserved as possible.
I know what you mean. The advise allways is to use a clean install of you Linux distribution and than install such software as VHCS.
The warn you about allreay configured packages etc. because VHCS etc. installs own versions of things.
You can use netstat -tap to see which ports are being used. U can also try to find out which firewall rules
are set. I think it's in /etc/iptables.up.rules. Maybe you can install Webmin, it's a handy Administrators tool
for Linux.
Now I can't get ProFTPd to start or log anything. So now I'm like a blind man trying to find different colored items. I'm just about ready to re-install everything. It's driving me insane.
I was messing around and I tried running ProFTPd as a program and not a daemon and so I set the debug level to 9 and it told me about the invalid socket error, and so I did some Googling and then thought, "What about /etc/hosts?" So I looked at it and remove a few unnecessary lines and low and behold, it worked! I figured it out from another forum post and that's why ProFTPd couldn't start!
Thanks for all your help and advice. This is a really great forum because I have a much quicker response than on other tech support sites.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.