Neuinstallation auf Raspi2 mit dietpi

Einklappen
X
 
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge
  • whe
    Azubi
    • 04.02.2026
    • 6

    #1

    Neuinstallation auf Raspi2 mit dietpi

    Nach 3 Tagen Kampf mit der Neuinstallation, muss ich leider doch heute die Community in Anspruch nehmen.
    ich habe einen Raspi 2 B+ mit dem image von dietpi ausgestattet und die Installation lt. Wiki gestartet.
    leider bricht sie immer wieder an der gleichen Stelle ab:

    Klicke auf die Grafik für eine vergrößerte Ansicht

Name: image.png
Ansichten: 128
Größe: 47,2 KB
ID: 478721

    ich habe die Installation schon mehrfach wiederholt, es ist immer die gleiche Stelle.
    habe ich etwas falsch gemacht ?
  • Prof.Mobilux
    Supermoderator
    • 25.08.2015
    • 5359

    #2
    Das liegt am VSFTP Package. Er meckert beim Starten über irgendeine Option, die er nicht kennt. ("Status 2 / INVALIDARGUMENT"). KOmmt jetzt drauf an an welcher Stelle der Installation Du die Fehlermeldung bekommst, ob es an unserer Config liegt oder an der Distribution.

    Welche DietPi Version für den Raspberry2 ist das denn?

    Was sagt NACH dem Fehler folgender Befehl:

    Code:
    ls -l /etc/vsftpd.conf
    Da siehst Du, ob bereits unsere eigene Config aktiv ist oder noch die, die mit DietPi ausgeliefert wird.


    🇺🇦 Hilfe für die Menschen der Ukraine: https://www.loxforum.com/forum/proje...Cr-die-ukraine


    LoxBerry - Beyond the Limits

    Kommentar

    • whe
      Azubi
      • 04.02.2026
      • 6

      #3
      Ich benutze die bookworm version: DietPi_RPi2-ARMv7-Bookworm.img.xz mit der neuesten geht ja Loxberry nicht.
      hier der Inhalt von vsftpd.config; ist wohl schon die von der Installation, aber wohl identisch mit dem original: vsftpd.config.old
      Code:
      # 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=NO
      #
      # 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=022
      #
      # 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=YES
      #
      # 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
      #
      # 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=Welcome to blah FTP service.
      #
      # 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/certs/ssl-cert-snakeoil.pem
      rsa_private_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
      ssl_enable=NO
      
      #
      # Uncomment this to indicate that vsftpd use a utf8 filesystem.
      #utf8_filesystem=YES
      mir fällt aber folgendes im Journal log auf:
      Code:
      Feb 05 10:40:08 DietPi dbus-daemon[8480]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.2' (uid=0 pid=13351 comm="/usr/bin/python3 /usr/share/unattended-upgrades/un")
      Feb 05 10:40:08 DietPi dbus-daemon[8480]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.login1.service': Unit dbus-org.freedesktop.login1.service failed to load properly, please adjust/correct and reload service manager: File exists

      Kommentar

      • whe
        Azubi
        • 04.02.2026
        • 6

        #4
        vergessen:
        Code:
        root@DietPi:~# ls -l /etc/vsftpd.conf
        lrwxrwxrwx 1 root root 39 Feb  4 21:12 /etc/vsftpd.conf -> /opt/loxberry/system/vsftpd/vsftpd.conf

        Kommentar

        • whe
          Azubi
          • 04.02.2026
          • 6

          #5
          Habe jetzt mal vsftpd vorab aus der Dietpi Distribution installiert und warte mal ab, ob die Installation wieder da aussteigt.

          Hat leider nicht geholfen.
          Ich finde auch kein log und nirgendwo irgendwelche aussagefähigen Fehlermeldungen zu dem deamon.
          und er lässt sich auch nicht manuell starten und an der vsftpd.conf kann ich lt. Dokumentation auch keine Probleme finden.
          wie komme ich denn jetzt hier weiter ?
          Zuletzt geändert von whe; 06.02.2026, 20:51.

          Kommentar

          Lädt...