Ja, eigentlich steht schon alles im Titel ...
Wenn ist den Dienst stoppe und neu starte bekomme ich die fehlermeldung could not bind listening IPv6 socket ...
wenn ich jetzt in der config-datei die Zeile listen=YES mit dem Attribut NO versehe erhalte ich die Fehlermeldung vsftpd: not configured for standalone, must be started from inetd und der Port auf dem vsftpd lauschen soll ist nicht von einem anderen Programm belegt ...
Hat jemand eine Idee?...
VSFTP startet nicht
Anmeldungsdatum: Beiträge: Zähle... |
|
(Themenstarter)
Anmeldungsdatum: Beiträge: Zähle... |
Bin ich der einzige mit dem Problem? 😮 |
Anmeldungsdatum: Beiträge: 12067 |
Hallo! Du betreibst offensichtlich einen Server. Dann sollte dir auch geläufig sein, wie man Fehler nachvollzieht, die das System ausgibt. Zeige doch die entsprechenden Auszüge, bzw. Stati hier, damit sich auch jemand damit befasst. Einem Informationen aus der Nase ziehen, die eigentlich im Eröffnungspost stehen sollten, machen nun mal wenig Spaß und bleibt Anfängern vorbehalten, die sich mit dem System neu befassen. tl;dr: Richtig Fragen |
(Themenstarter)
Anmeldungsdatum: Beiträge: 71 |
Sorry, ok hier also die vsftpd.conf datei ... # Example config file /etc/vsftpd.conf # # The default compiled in settings are fairly paranoid. This sample file # loosens things up a bit, to make the ftp daemon more usable. # Please see vsftpd.conf.5 for all compiled in defaults. # # READ THIS: This example file is NOT an exhaustive list of vsftpd options. # Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's # capabilities. # # # Run standalone? vsftpd can run either from an inetd or as a standalone # daemon started from an initscript. listen=YES # # This directive enables listening on IPv6 sockets. By default, listening # on the IPv6 "any" address (::) will accept connections from both IPv6 # and IPv4 clients. It is not necessary to listen on *both* IPv4 and IPv6 # sockets. If you want that (perhaps because you want to listen on specific # addresses) then you must run two copies of vsftpd with two configuration # files. listen_ipv6=YES # # Allow anonymous FTP? (Disabled by default). anonymous_enable=NO # # Uncomment this to allow local users to log in. local_enable=YES # # Uncomment this to enable any form of FTP write command. #write_enable=YES # # Default umask for local users is 077. You may wish to change this to 022, # if your users expect that (022 is used by most other ftpd's) #local_umask=0010 file_open_mode=0010 # # Uncomment this to allow the anonymous FTP user to upload files. This only # has an effect if the above global write enable is activated. Also, you will # obviously need to create a directory writable by the FTP user. #anon_upload_enable=YES # # Uncomment this if you want the anonymous FTP user to be able to create # new directories. #anon_mkdir_write_enable=YES # # Activate directory messages - messages given to remote users when they # go into a certain directory. #dirmessage_enable=YES # # If enabled, vsftpd will display directory listings with the time # in your local time zone. The default is to display GMT. The # times returned by the MDTM FTP command are also affected by this # option. use_localtime=YES # # Activate logging of uploads/downloads. xferlog_enable=YES # # Make sure PORT transfer connections originate from port 20 (ftp-data). connect_from_port_20=NO # # If you want, you can arrange for uploaded anonymous files to be owned by # a different user. Note! Using "root" for uploaded files is not # recommended! #chown_uploads=YES #chown_username=whoever # # You may override where the log file goes if you like. The default is shown # below. xferlog_file=/var/log/vsftpd.log #vsftpd_log_file=/var/log/vsftpd_sys.log # # If you want, you can have your log file in standard ftpd xferlog format. # Note that the default log file location is /var/log/xferlog in this case. #xferlog_std_format=YES # # You may change the default value for timing out an idle session. #idle_session_timeout=600 # # You may change the default value for timing out a data connection. #data_connection_timeout=120 # # It is recommended that you define on your system a unique user which the # ftp server can use as a totally isolated and unprivileged user. #nopriv_user=ftpsecure # # Enable this and the server will recognise asynchronous ABOR requests. Not # recommended for security (the code is non-trivial). Not enabling it, # however, may confuse older FTP clients. #async_abor_enable=YES # # By default the server will pretend to allow ASCII mode but in fact ignore # the request. Turn on the below options to have the server actually do ASCII # mangling on files when in ASCII mode. # Beware that on some FTP servers, ASCII support allows a denial of service # attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd # predicted this attack and has always been safe, reporting the size of the # raw file. # ASCII mangling is a horrible feature of the protocol. #ascii_upload_enable=YES #ascii_download_enable=YES # # You may fully customise the login banner string: ftpd_banner=Eigene Nachricht # # You may specify a file of disallowed anonymous e-mail addresses. Apparently # useful for combatting certain DoS attacks. #deny_email_enable=YES # (default follows) #banned_email_file=/etc/vsftpd.banned_emails # # You may restrict local users to their home directories. See the FAQ for # the possible risks in this before using chroot_local_user or # chroot_list_enable below. #chroot_local_user=YES # # You may specify an explicit list of local users to chroot() to their home # directory. If chroot_local_user is YES, then this list becomes a list of # users to NOT chroot(). # (Warning! chroot'ing can be very dangerous. If using chroot, make sure that # the user does not have write access to the top level directory within the # chroot) chroot_local_user=YES chroot_list_enable=YES # (default follows) chroot_list_file=/etc/vsftpd.chroot_list # # You may activate the "-R" option to the builtin ls. This is disabled by # default to avoid remote users being able to cause excessive I/O on large # sites. However, some broken FTP clients such as "ncftp" and "mirror" assume # the presence of the "-R" option, so there is a strong case for enabling it. #ls_recurse_enable=YES # # Customization # # Some of vsftpd's settings don't fit the filesystem layout by # default. # # This option should be the name of a directory which is empty. Also, the # directory should not be writable by the ftp user. This directory is used # as a secure chroot() jail at times vsftpd does not require filesystem # access. secure_chroot_dir=/var/run/vsftpd/empty # # This string is the name of the PAM service vsftpd will use. pam_service_name=vsftpd # # This option specifies the location of the RSA certificate to use for SSL # encrypted connections. rsa_cert_file=/etc/ssl/vsftpd.pem rsa_private_key_file=/etc/ssl/vsftpd.key ssl_enable=YES allow_anon_ssl=NO force_local_data_ssl=YES force_local_logins_ssl=YES require_ssl_reuse=NO max_clients=5 listen_port=2121 ftp_data_port=2122 pasv_min_port=2122 pasv_max_port=2126 # # Uncomment this to indicate that vsftpd use a utf8 filesystem. #utf8_filesystem=YES userlist_enable=YES userlist_file=/etc/vsftpd.user_list userlist_deny=NO
Die Fehlerbeschreibung habe ich Wort für Wort wiedergegeben ... |
Ehemalige
Anmeldungsdatum: Beiträge: 4403 Wohnort: Sachsen |
Was sagt netstat -tulpen|grep ":21" Wenn die Probleme exklusiv bei IPv6 auftreten, dann setze einfach |
(Themenstarter)
Anmeldungsdatum: Beiträge: 71 |
die Eingabe ergibt tcp6 0 0 :::21 :::* LISTEN 0 18358 1118/vsftpd und wenn ich das listen_ipv6=yes auf no ändere bekomme ich die fehlermeldung "could not bind listening IPv4 socket" Hier vielleicht noch die Ausgabe von netstat -tulpen: Aktive Internetverbindungen (Nur Server) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 1692/master tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1362/smbd tcp 0 0 0.0.0.0:2121 0.0.0.0:* LISTEN 7435/vsftpd tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1144/mysqld tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1362/smbd tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN 1097/sshd tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 1132/dovecot tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 1132/dovecot tcp6 0 0 ::1:25 :::* LISTEN 1692/master tcp6 0 0 :::443 :::* LISTEN 1295/apache2 tcp6 0 0 :::445 :::* LISTEN 1362/smbd tcp6 0 0 :::139 :::* LISTEN 1362/smbd tcp6 0 0 :::2222 :::* LISTEN 1097/sshd tcp6 0 0 :::110 :::* LISTEN 1132/dovecot tcp6 0 0 :::143 :::* LISTEN 1132/dovecot tcp6 0 0 :::80 :::* LISTEN 1295/apache2 udp 0 0 0.0.0.0:68 0.0.0.0:* 1410/dhclient udp 0 0 192.168.1.255:137 0.0.0.0:* 1360/nmbd udp 0 0 192.168.1.32:137 0.0.0.0:* 1360/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 1360/nmbd udp 0 0 192.168.1.255:138 0.0.0.0:* 1360/nmbd udp 0 0 192.168.1.32:138 0.0.0.0:* 1360/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 1360/nmbd |
Ehemalige
Anmeldungsdatum: Beiträge: 4403 Wohnort: Sachsen |
vsftp kann nicht gestartet werden, weil er bereits läuft, der Port also schon gebunden ist. |
(Themenstarter)
Anmeldungsdatum: Beiträge: 71 |
ja ... jetzt geht's auch aber ich hatte das Problem ja am Anfang schonmal beschrieben und ich hatte die services auch imer mit service --status-all überprüft ... naja 😉 |
Ehemalige
Anmeldungsdatum: Beiträge: 4403 Wohnort: Sachsen |