Wir haben vor einiger Zeit unseren Server komplett aufgesetzt und dabei auch ProFTPD verwendet. Nun nachdem die Techniker des Serverzentrums in dem unser Server steht dran waren waren alle Daemons beendet und proftpd lässt sich nicht mehr starten. Wir haben leider keine Ahnung was die da gemacht haben. Okay sie haben es geschafft einen E-Mail-Server zu installieren aber nun läuft proftpd nicht mehr.
Unser ProFTPD ist wie folgt kompiliert worden:
./configure \
--prefix=/usr/local/proftpd
make && make install
Und starten tue ich den über:
/usr/local/proftpd/sbin/proftpd start
Wenn ich das mache passiert nichts. Okay ich bekomme eine Meldung dass proftpd gestartet wurde aber wenn ich ps aux mache sehe ich den prozess nicht. Nun habe ich mal -d 9 gemacht und da kam auch nichts auffälliges:
rhein:/usr/local/proftpd/sbin# proftpd -d 9
- mod_tls/2.0.7: using OpenSSL 0.9.7g 11 Apr 2005
- parsing '/etc/proftpd.conf' configuration
- FS: using system open()
- FS: using system read()
- dispatching directive 'ServerName' to module mod_core
- dispatching directive 'ServerType' to module mod_core
- dispatching directive 'DefaultServer' to module mod_core
- dispatching directive 'ServerAdmin' to module mod_core
- dispatching directive 'ServerIdent' to module mod_core
- dispatching directive 'UseReverseDNS' to module mod_core
- dispatching directive 'IdentLookups' to module mod_core
- dispatching directive 'Port' to module mod_core
- dispatching directive 'Umask' to module mod_core
- FS: using system read()
- dispatching directive 'MaxInstances' to module mod_core
- dispatching directive 'User' to module mod_core
- dispatching auth request "getpwnam" to module mod_radius
- dispatching auth request "getpwnam" to module mod_sql
- dispatching auth request "getpwnam" to module mod_auth_file
- dispatching auth request "getpwnam" to module mod_auth_unix
- dispatching directive 'Group' to module mod_core
- dispatching auth request "getgrnam" to module mod_radius
- dispatching auth request "getgrnam" to module mod_sql
- dispatching auth request "getgrnam" to module mod_auth_file
- dispatching auth request "getgrnam" to module mod_auth_unix
- dispatching directive 'TransferLog' to module mod_core
- dispatching directive 'AllowOverwrite' to module mod_xfer
- dispatching directive 'DefaultRoot' to module mod_auth
- dispatching directive '<Limit>' to module mod_core
- dispatching directive '</Limit>' to module mod_core
- </Limit>: ignoring empty context
- FS: using system read()
- FS: using system close()
localhost.localdomain -
localhost.localdomain - Config for shining-network.com:
localhost.localdomain - DefaultServer
localhost.localdomain - ServerIdent
localhost.localdomain - IdentLookups
localhost.localdomain - Umask
localhost.localdomain - UserID
localhost.localdomain - UserName
localhost.localdomain - GroupID
localhost.localdomain - GroupName
localhost.localdomain - TransferLog
localhost.localdomain - AllowOverwrite
localhost.localdomain - DefaultRoot
localhost.localdomain - ROOT PRIVS at ../../../modules/mod_delay.c:295
localhost.localdomain - FS: using system open()
localhost.localdomain - RELINQUISH PRIVS at ../../../modules/mod_delay.c:297
localhost.localdomain - FS: using system fstat()
localhost.localdomain - FS: using system close()
localhost.localdomain - dispatching auth request "getgroups" to module mod_radius
localhost.localdomain - dispatching auth request "getgroups" to module mod_sql
localhost.localdomain - dispatching auth request "getgroups" to module mod_auth_file
localhost.localdomain - dispatching auth request "getgroups" to module mod_auth_unix
localhost.localdomain - SETUP PRIVS at ../../../src/main.c:2736
localhost.localdomain - ROOT PRIVS at ../../../src/main.c:1970
localhost.localdomain - RELINQUISH PRIVS at ../../../src/main.c:1977
Wenn ich nun auf den FTP zugreifen will (per Browser) bekomme ich ebenfalls keine Meldung. Es wird minutenlang versucht zu verbinden. Wenn ich per FTP-Progg drauf zugreifen will schlägt die Verbindung direkt fehl.
Unser /etc/proftpd.conf sieht wie folgt aus:
# This is a basic ProFTPD configuration file (rename it to
# 'proftpd.conf' for actual use. It establishes a single server
# and a single anonymous login. It assumes that you have a user/group
# "nobody" and "ftp" for normal operation and anon.
ServerName "Default FTD"
ServerType standalone
DefaultServer on
# Port 21 is the standard FTP port.
Port 21
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
Umask 022
# 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 under which the server will run.
User nobody
Group nogroup
# To cause every FTP user to be "jailed" (chrooted) into their home
# directory, uncomment this line.
DefaultRoot ~
# Normally, we want files to be overwriteable.
AllowOverwrite on
## Son Zeugs
UseReverseDNS off
IdentLookups off
# Bar use of SITE CHMOD by default
<Limit SITE_CHMOD>
DenyAll
</Limit>
# A basic anonymous configuration, no upload directories. If you do not
# want anonymous users, simply delete this entire <Anonymous> section.
<Anonymous ~ftp>
User ftp
Group ftp
# We want clients to be able to login with "anonymous" as well as "ftp"
UserAlias anonymous ftp
# Limit the maximum number of anonymous logins
MaxClients 10
# We want 'welcome.msg' displayed at login, and '.message' displayed
# in each newly chdired directory.
DisplayLogin welcome.msg
DisplayFirstChdir .message
# Limit WRITE everywhere in the anonymous chroot
<Limit WRITE>
DenyAll
</Limit>
</Anonymous>
