Proftpd lässt sich nicht starten [GELÖST]

[Dennisda]

STOP - Bitte lesen Sie die nächsten Zeilen aufmerksam!

1) Bitte füllen Sie die unten stehende Beitragsvorlage vollständig aus!
2) Die Mitglieder dieses Forum stellen ihre wertvolle Zeit zur Verfügung, um zu helfen! Bitte stellen Sie im Gegenzug soviel Informationen wie möglich zur Verfügung und seien Sie in der Fehlerbeschreibung konkret. Beiträge die geringe Eigeninitiative zeigen werden wahrscheinlich keine guten Antworten erhalten!

Sie können diesen oberen Teil der Beitragsvorlage entfernen.
Die folgende Beitragsvorlage darf jedoch in keinem Fall entfernt werden.
---------------------------------------------------------------------------


Ich bin sicher, dass die Ursache des Problems bei KeyHelp liegt
(Probleme ohne KeyHelp-Bezug gehören ins Offtopic-Forum)

Es ist davon auszugehen

Server-Betriebssystem + Version
(z.B. Ubuntu 20.04)
Debian 12

Eingesetzte Server-Virtualisierung-Technologie
(z.B. keine, OpenVZ, KVM, XEN, etc.)

keine

KeyHelp-Version + Build-Nummer
(z.B. 22.0 - Build 2366)
24.2 (Build 3326)

Problembeschreibung / Fehlermeldungen

Der FTP Server ist nicht gestartet, wenn ich Ihn über dem UI starten möchte erhalte ich nur folgende Meldung:

Der Vorgang konnte nicht korrekt ausgeführt werden. (Berechtigungen korrekt?)

Der Status auf der Konsole sagt:

Code: Select all

 systemctl status proftpd.service
× proftpd.service - ProFTPD FTP Server
     Loaded: loaded (/lib/systemd/system/proftpd.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2024-11-17 16:20:37 CET; 37s ago
       Docs: man:proftpd(8)
    Process: 21456 ExecStartPre=/usr/sbin/proftpd --configtest -c $CONFIG_FILE $OPTIONS (code=exited, status=1/FAILURE)
        CPU: 9ms

Nov 17 16:20:37 srv.***.de systemd[1]: Starting proftpd.service - ProFTPD FTP Server...
Nov 17 16:20:37 srv..de proftpd[21456]: Checking syntax of configuration file
Nov 17 16:20:37 srv.pov.de proftpd[21456]: 2024-11-17 16:20:37,461 srv.p****.de proftpd[21456]: warning: unable to determine IP address of 'srv.p>
Nov 17 16:20:37 srv.po.de proftpd[21456]: 2024-11-17 16:20:37,461 srv.p****.de proftpd[21456]: error: no valid servers configured
Nov 17 16:20:37 srv.po.de proftpd[21456]: 2024-11-17 16:20:37,461 srv.*****.de proftpd[21456]: fatal: error processing configuration file '/etc/>
Nov 17 16:20:37 srv.po.de systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE
Nov 17 16:20:37 srv.po.de systemd[1]: proftpd.service: Failed with result 'exit-code'.
Nov 17 16:20:37 srv.po.de systemd[1]: Failed to start proftpd.service - ProFTPD FTP Server.

Wenn ich Starte erhalte ich auf der Konsole folgende Meldung

Job for proftpd.service failed because the control process exited with error code.
See "systemctl status proftpd.service" and "journalctl -xeu proftpd.service" for details.

Logs sind leer. Eine Neuinstallation vom FTP brachte auch kein Erfolg...
Bin ratlos, was meint Ihr ?

[Jolinar]

Was sagt ein:

Code: Select all

journalctl -u proftpd.service

[Dennisda]

Code: Select all

Nov 17 16:24:03 srv..de systemd[1]: Starting proftpd.service - ProFTPD FTP Server...
Nov 17 16:24:03 srv..de proftpd[22001]: Checking syntax of configuration file
Nov 17 16:24:03 srv.de proftpd[22001]: 2024-11-17 16:24:03,688 srv.pohleserv.de proftpd[22001]: warning: unable to determine IP address of 'srv.p>
Nov 17 16:24:03 srv.de proftpd[22001]: 2024-11-17 16:24:03,688 srv.pohleserv.de proftpd[22001]: error: no valid servers configured
Nov 17 16:24:03 srv.p proftpd[22001]: 2024-11-17 16:24:03,688 srv.pohleserv.de proftpd[22001]: fatal: error processing configuration file '/etc/>
Nov 17 16:24:03 srv.pde systemd[1]: proftpd.service: Control process exited, code=exited, status=1/FAILURE
Nov 17 16:24:03 srv.v.de systemd[1]: proftpd.service: Failed with result 'exit-code'.
Nov 17 16:24:03 srvrv.de systemd[1]: Failed to start proftpd.service - ProFTPD FTP Server.

Hier der abgeschnittene Teil:

ohleserv.de proftpd[22001]: warning: unable to determine IP address of 'srv.pohleserv.de'
ohleserv.de proftpd[22001]: error: no valid servers configured
ohleserv.de proftpd[22001]: fatal: error processing configuration file '/etc/proftpd/proftpd.conf'
exited, code=exited, status=1/FAILURE

und hier die Config:

Code: Select all

#
# /etc/proftpd/proftpd.conf -- This is a basic ProFTPD configuration file.
# To really apply changes, reload proftpd after modifications, if
# it runs in daemon mode. It is not required in inetd/xinetd mode.
#

# Includes DSO modules
Include /etc/proftpd/modules.conf

# Set off to disable IPv6 support which is annoying on IPv4 only boxes.
UseIPv6 on
# If set on you can experience a longer connection delay in many cases.
<IfModule mod_ident.c>
  IdentLookups off
</IfModule>

ServerName "srv*****.de"
# Set to inetd only if you would run proftpd by inetd/xinetd/socket.
# Read README.Debian for more information on proper configuration.
ServerType standalone
DeferWelcome off

# Disable MultilineRFC2228 per https://github.com/proftpd/proftpd/issues/1085
# MultilineRFC2228on
DefaultServer on
ShowSymlinks on

TimeoutNoTransfer 600
TimeoutStalled 600
TimeoutIdle 1200

DisplayLogin welcome.msg
DisplayChdir .message true
ListOptions "-l"

DenyFilter \*.*/

# Use this to jail all users in their homes
# DefaultRoot ~

# Users require a valid shell listed in /etc/shells to login.
# Use this directive to release that constrain.
# RequireValidShell off

# Port 21 is the standard FTP port.
Port 21

# In some cases you have to specify passive ports range to by-pass
# firewall limitations. Ephemeral ports can be used for that, but
# feel free to use a more narrow range.
# PassivePorts 49152 65534

# If your host was NATted, this option is useful in order to
# allow passive tranfers to work. You have to use your public
# address and opening the passive ports used on your firewall as well.
# MasqueradeAddress 1.2.3.4

# This is useful for masquerading address with dynamic IPs:
# refresh any configured MasqueradeAddress directives every 8 hours
<IfModule mod_dynmasq.c>
# DynMasqRefresh 28800
</IfModule>

# 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 proftpd
Group nogroup

# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask 022 022
# Normally, we want files to be overwriteable.
AllowOverwrite on

# Uncomment this if you are using NIS or LDAP via NSS to retrieve passwords:
# PersistentPasswd off

# This is required to use both PAM-based authentication and local passwords
# AuthOrder mod_auth_pam.c* mod_auth_unix.c

# Be warned: use of this directive impacts CPU average load!
# Uncomment this if you like to see progress and transfer rate with ftpwho
# in downloads. That is not needed for uploads rates.
#
# UseSendFile off

TransferLog /var/log/proftpd/xferlog
SystemLog /var/log/proftpd/proftpd.log

# Logging onto /var/log/lastlog is enabled but set to off by default
#UseLastlog on

# In order to keep log file dates consistent after chroot, use timezone info
# from /etc/localtime.  If this is not set, and proftpd is configured to
# chroot (e.g. DefaultRoot or <Anonymous>), it will use the non-daylight
# savings timezone regardless of whether DST is in effect.
#SetEnv TZ :/etc/localtime

<IfModule mod_quotatab.c>
QuotaEngine off
</IfModule>

<IfModule mod_ratio.c>
Ratios off
</IfModule>


# Delay engine reduces impact of the so-called Timing Attack described in
# http://www.securityfocus.com/bid/11430/discuss
# It is on by default.
<IfModule mod_delay.c>
DelayEngine on
</IfModule>

<IfModule mod_ctrls.c>
ControlsEngine off
ControlsMaxClients 2
ControlsLog /var/log/proftpd/controls.log
ControlsInterval 5
ControlsSocket /var/run/proftpd/proftpd.sock
</IfModule>

<IfModule mod_ctrls_admin.c>
AdminControlsEngine off
</IfModule>

#
# Alternative authentication frameworks
#
#Include /etc/proftpd/ldap.conf
#Include /etc/proftpd/sql.conf

#
# This is used for FTPS connections
#
#Include /etc/proftpd/tls.conf

#
# This is used for SFTP connections
#
#Include /etc/proftpd/sftp.conf

#
# This is used for other add-on modules
#
#Include /etc/proftpd/dnsbl.conf
#Include /etc/proftpd/geoip.conf
#Include /etc/proftpd/snmp.conf

#
# Useful to keep VirtualHost/VirtualRoot directives separated
#
#Include /etc/proftpd/virtuals.conf

# A basic anonymous configuration, no upload directories.

# <Anonymous ~ftp>
#   User ftp
#   Group nogroup
#   # We want clients to be able to login with "anonymous" as well as "ftp"
#   UserAlias anonymous ftp
#   # Cosmetic changes, all files belongs to ftp user
#   DirFakeUser on ftp
#   DirFakeGroup on ftp
#
#   RequireValidShell off
#
#   # 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
#   DisplayChdir .message
#
#   # Limit WRITE everywhere in the anonymous chroot
#   <Directory *>
#     <Limit WRITE>
#       DenyAll
#     </Limit>
#   </Directory>
#
#   # Uncomment this if you're brave.
#   # <Directory incoming>
#   #   # Umask 022 is a good standard umask to prevent new files and dirs
#   #   # (second parm) from being group and world writable.
#   #   Umask 022  022
#   #   <Limit READ WRITE>
#   #     DenyAll
#   #     </Limit>
#   #       <Limit STOR>
#   #         AllowAll
#   #     </Limit>
#   # </Directory>
#
# </Anonymous>

# Include other custom configuration files
# !! Please note, that this statement will read /all/ file from this subdir,
# i.e. backup files created by your editor, too !!!
# Eventually create file patterns like this: /etc/proftpd/conf.d/*.conf
#
Include /etc/proftpd/conf.d/

[Dennisda]

Danke habe es hinbekommen.
Die " bei Servername waren der Grund Oo

[Jolinar]

Die " bei Servername waren der Grund

Jupp, meistens sind es nur solche Kleinigkeiten...Aber schön, daß du dein Problem lösen konntest.