In wie fern wirkt sich das aus.Jede Verbindung scheitert
Probier mal
Code:/etc/init.d/inetd restart
-bash: /etc/init.d/inetd: No such file or directory
Status: Auflösen der IP-Adresse für xxx.de
Status: Verbinde mit xx.xxx.xxx:21...
Status: Verbindung hergestellt, warte auf Willkommensnachricht...
Fehler: Herstellen der Verbindung zum Server fehlgeschlagen
Status: Nächsten Versuch abwarten...
Status: Auflösen der IP-Adresse für xxx.de
Status: Verbinde mit xx.xxx.xxx:21...
Status: Verbindung hergestellt, warte auf Willkommensnachricht...
Fehler: Herstellen der Verbindung zum Server fehlgeschlagen
dan schau dir mal die Logs an, scheinbar ist eine Einstellung vorhanden, welche den Zugriff verhindert.
/etc/init.d/xinetd restart
??
plesk:/etc/init.d # ls
.depend.boot boot.local mailman rc2.d
.depend.halt boot.localfs mdadmd rc3.d
.depend.start boot.localnet microcode.ctl rc4.d
.depend.stop boot.lvm multipathd rc5.d
README boot.md mysql rc6.d
SuSEfirewall2_init boot.multipath named rcS.d
SuSEfirewall2_setup boot.proc network reboot
acpid boot.rootfsck network-remotefs rpasswdd
after.local boot.sched nfs rpcbind
apache2 boot.scpm nmb rpmconfigcheck
atd boot.swap nscd rsyncd
autofs boot.sysctl ntp setserial
autoyast boot.udev openct single
aveserver boot.udev_retry pcscd skeleton
boot courier-imap pm-profiler skeleton.compat
boot.blktrace cron postfix smartd
boot.cleanup dbus postgresql smb
boot.clock drwebd powerd smbfs
boot.crypto earlysyslog powerfail spamd
boot.crypto-early earlyxdm psa sshd
boot.cycle fbset psa-firewall stopblktrace
boot.d gpm psa-firewall-forward sw-cp-server
boot.device-mapper haldaemon psa-spamassassin syslog
boot.dmraid halt psa-vpn tomcat6
boot.fuse halt.local random uuidd
boot.ipconfig irq_balancer raw waitfornm
boot.klog java.binfmt_misc rc xinetd
boot.ldconfig kbd rc0.d ypbind
boot.loadmodules kexec rc1.d
Dein FTP-Server wird über den xinetd gestartet. Die Konfigurationsdatei dürfte in /etc/xinetd.d/proftpd liegen.
Diese Datei sowie die zugehörige /etc/proftpd.conf könnten uns da evtl. weiterhelfen.
#
# To have more informations about Proftpd configuration
# look at : http://www.proftpd.org/
#
# 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 "ProFTPD"
#ServerType standalone
ServerType inetd
DefaultServer on
<Global>
DefaultRoot ~ psacln
AllowOverwrite on
</Global>
DefaultTransferMode binary
UseFtpUsers on
TimesGMT off
SetEnv TZ :/etc/localtime
# 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
#Following part of this config file were generate by PSA automatically
#Any changes in this part will be overwritten by next manipulation
#with Anonymous FTP feature in PSA control panel.
#Include directive should point to place where FTP Virtual Hosts configurations
#preserved
ScoreboardFile /var/run/proftpd/scoreboard
# Primary log file mest be outside of system logrotate province
TransferLog /usr/local/psa/var/log/xferlog
#Change default group for new files and directories in vhosts dir to psacln
<Directory /srv/www/vhosts>
GroupOwner psacln
</Directory>
# Enable PAM authentication
AuthPAM on
AuthPAMConfig proftpd
IdentLookups off
UseReverseDNS off
AuthGroupFile /etc/group
Include /etc/proftpd.include
Dann schau mal, was Du in /etc/xinetd.d/ liegen hast, was auf FTP hindeutet und poste bitte auch mal die Ausgabe vonCode:iptables -L -n
plesk:~ # iptables -L -n
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp flags:!0x17/0x02 reject-with tcp-reset
DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8443
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8880
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:21
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:587
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:25
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:465
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:110
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:995
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:143
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:993
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:106
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:3306
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5432
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:9008
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:9080
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:137
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:138
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:139
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:445
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:1194
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 8 code 0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp flags:!0x17/0x02 reject-with tcp-reset
DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
DROP all -- 0.0.0.0/0 0.0.0.0/0
Chain OUTPUT (policy DROP)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp flags:!0x17/0x02 reject-with tcp-reset
DROP all -- 0.0.0.0/0 0.0.0.0/0 state INVALID
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
was steht in der
/var/log/xinetd.log
??
10/1/4@13:33:14: START: ftp from=77.180.xx.xxx
10/1/4@13:33:14: EXIT: ftp status=1 duration=0(sec)
10/1/4@13:33:16: START: ftp from=77.180.xx.xxx
10/1/4@13:33:16: EXIT: ftp status=1 duration=0(sec)
Deine Firewall ist etwas strange aufgebaut. Mach mal testweise und versuch dann nochmal die Verbindung.Code:iptables-save; for i in INPUT OUTPUT FORWARD; do iptables -P $i ACCEPT; done; iptables -F
iptables-save; for i in INPUT OUTPUT FORWARD; do iptables -P $i ACCEPT; done; iptables -F
# Generated by iptables-save v1.4.2-rc1 on Mon Jan 4 14:33:49 2010
*nat
:PREROUTING ACCEPT [138708:7946143]
:POSTROUTING ACCEPT [275408:19748523]
:OUTPUT ACCEPT [275396:19778890]
COMMIT
# Completed on Mon Jan 4 14:33:49 2010
# Generated by iptables-save v1.4.2-rc1 on Mon Jan 4 14:33:49 2010
*mangle
:PREROUTING ACCEPT [4659294:583394756]
:INPUT ACCEPT [4659208:583389960]
:FORWARD ACCEPT [86:4796]
:OUTPUT ACCEPT [7445565:8236149053]
:POSTROUTING ACCEPT [7442280:8235976608]
COMMIT
# Completed on Mon Jan 4 14:33:49 2010
# Generated by iptables-save v1.4.2-rc1 on Mon Jan 4 14:33:49 2010
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT DROP [0:0]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -j REJECT --reject-with tcp-reset
-A INPUT -m state --state INVALID -j DROP
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8880 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 21 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 587 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 25 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 465 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 110 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 995 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 143 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 993 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 106 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 3306 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 5432 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9008 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9080 -j ACCEPT
-A INPUT -p udp -m udp --dport 137 -j ACCEPT
-A INPUT -p udp -m udp --dport 138 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 139 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 445 -j ACCEPT
-A INPUT -p udp -m udp --dport 1194 -j ACCEPT
-A INPUT -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 8/0 -j ACCEPT
-A INPUT -j ACCEPT
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -j REJECT --reject-with tcp-reset
-A FORWARD -m state --state INVALID -j DROP
-A FORWARD -i lo -o lo -j ACCEPT
-A FORWARD -j DROP
-A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -j REJECT --reject-with tcp-reset
-A OUTPUT -m state --state INVALID -j DROP
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -j ACCEPT
COMMIT
# Completed on Mon Jan 4 14:33:49 2010
Hier müsste nämlich der Grund zu finden sein, warum der FTP-Server nicht läuft, denn das ist anscheinend so!/var/log/proftpd/proftpd.log
und schau danach in die oben genannte Logdatei. Bei einem erfolgreichen FTP-Serverstart müsste da etwas so in der Art am Ende der Logdatei drinstehen:/etc/init.d/proftpd restart
Falls der Server nicht neugestartet werden konnte (Fehler in den Konfigurationsdateien?) dann steht das auch in der Logdatei!Jan 04 14:50:18 example.com proftpd[4388] srv110: ProFTPD 1.x.x (stable) (built xxx xxx xx 23:xx:xx UTC 20xx) standalone mode STARTUP