vsftpd Fehler. Login nicht möglich.

Backup, Restore und Transfer von Daten
Post Reply
taker
Posts: 71
Joined: 2004-01-25 14:08
 

vsftpd Fehler. Login nicht möglich.

Post by taker »

Hi Leute..

Also gestern hab ich nen Yast Update gemacht und da ging wohl was schief.. Ich hab irgendwie nen Update von xinetd gemacht.. So jetzt geht der FTP Zugang gar nicht mehr..

Fehlermeldung aus meinem Client:

Code: Select all

Continue to login attempt 11...
    Connecting to (p15149767.pureserver.info) ->  IP: 217.160.207.65 PORT: 21
    Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte.
    Connection closed.

So, ich hab dann natürlich hier gesucht und bin darauf gestoßen das ich aus der xinetd.conf das "RECORD" Entfernen soll. OK gemacht Getan..

Hier meine xinetd.conf

Code: Select all

# 
# xinetd.conf 
# 
# Copyright (c) 1998-2001 SuSE GmbH Nuernberg, Germany. 
# Copyright (c) 2002 SuSE Linux AG, Nuernberg, Germany. 
# 

defaults 
{ 
        log_type        = FILE /var/log/xinetd.log 
        log_on_success  = HOST EXIT DURATION 
        log_on_failure  = HOST ATTEMPT 
#        only_from       = localhost 
        instances       = 10 
} 

service ftp 
{ 
        socket_type     = stream 
        protocol        = tcp 
        wait            = no 
        user            = root 
        server          = /usr/sbin/vsftpd 
#       server_args     = -a 
        log_on_success  = HOST PID EXIT DURATION 
        log_on_failure  = HOST ATTEMPT 
} 


service pop3 
{ 
        socket_type = stream 
        protocol = tcp 
        wait = no 
        user = root 
        server = /usr/sbin/popper 
        server_args = qpopper -s 
        log_on_success  = HOST PID EXIT DURATION 
#       log_on_failure  = HOST ATTEMPT 
} 

# *grrr* SuSE-8.1: qpopper.rpm compiled without ssl/tls-support 
service pop3s 
{ 
        socket_type = stream 
        protocol = tcp 
        wait = no 
        user = root 
        server = /usr/sbin/stunnel 
        server_args = qpopper -l /usr/sbin/popper -- -R -s 
        log_on_success  = HOST PID EXIT DURATION 
#       log_on_failure  = HOST ATTEMPT 
} 

#service ident 
#{ 
#       socket_type     = stream 
#       protocol        = tcp 
#       wait            = no 
#       user            = nobody 
#       server          = /usr/sbin/in.identd 
#       server_args     = -w -t120 
#} 

# includedir /etc/xinetd.d
So, aber trotzdem kann ich mich nicht einloggen. Wenn ich gucke ob der Service läuft kann ich nix finden..

Code: Select all

p15149767:/ # ps -axu
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root         1  3.1  0.0   448  236 ?        S    18:02   0:05 init
root         2  0.0  0.0     0    0 ?        SW   18:02   0:00 [keventd]
root         3  0.0  0.0     0    0 ?        SWN  18:02   0:00 [ksoftirqd_CPU0]
root         4  0.0  0.0     0    0 ?        SW   18:02   0:00 [kswapd]
root         5  0.0  0.0     0    0 ?        SW   18:02   0:00 [bdflush]
root         6  0.0  0.0     0    0 ?        SW   18:02   0:00 [kupdated]
root         8  0.0  0.0     0    0 ?        DW   18:02   0:00 [kjournald]
root        56  0.0  0.0     0    0 ?        SW   18:03   0:00 [kjournald]
root       303  0.0  0.2  1300  548 ?        S    18:03   0:00 /sbin/dhcpcd -d -
root       319  0.0  0.2  1340  596 ?        S    18:03   0:00 /sbin/syslogd
root       322  0.0  0.5  2076 1252 ?        S    18:03   0:00 /sbin/klogd -c 1
bin        354  0.0  0.1  1292  396 ?        S    18:03   0:00 /sbin/portmap
root       368  0.0  0.4  2256 1152 ?        S    18:03   0:00 /bin/sh /usr/bin/
root       393  0.0  0.6  4144 1572 ?        S    18:03   0:00 /usr/sbin/sshd
mysql      400  0.0  1.3 21176 3312 ?        S    18:03   0:00 /usr/sbin/mysqld
mysql      402  0.0  1.3 21176 3312 ?        S    18:03   0:00 /usr/sbin/mysqld
mysql      403  0.0  1.3 21176 3312 ?        S    18:03   0:00 /usr/sbin/mysqld
root       404  0.0  0.9  7308 2280 ?        S    18:03   0:00 /usr/sbin/sshd
root       417  0.0  0.4  3796 1120 ?        S    18:03   0:00 /usr/lib/ssh/sftp
ntp        439  0.0  0.7  1920 1912 ?        SL   18:03   0:00 /usr/sbin/ntpd -U
root       493  0.0  0.5  4424 1452 ?        S    18:03   0:00 /usr/lib/postfix/
postfix    507  0.0  0.5  4388 1392 ?        S    18:03   0:00 pickup -l -t fifo
postfix    508  0.0  0.6  7024 1720 ?        S    18:03   0:00 qmgr -l -t fifo -
root       515  0.1  0.9  7392 2312 ?        S    18:03   0:00 /usr/sbin/sshd
root       522  0.0  0.6  2780 1704 pts/0    S    18:03   0:00 -bash
root       544  0.6  4.6 86072 11504 ?       S    18:03   0:00 /usr/sbin/httpd -
at         551  0.0  0.2  1400  548 ?        S    18:03   0:00 /usr/sbin/atd
root       566  0.0  0.2  1416  624 ?        S    18:03   0:00 /usr/sbin/cron
root       586  0.0  0.2 11740  716 ?        S    18:03   0:00 /usr/sbin/nscd
root       587  0.0  0.1  1260  496 tty1     S    18:03   0:00 /sbin/mingetty --
root       588  0.0  0.1  1260  496 tty2     S    18:03   0:00 /sbin/mingetty tt
root       589  0.0  0.1  1260  496 tty3     S    18:03   0:00 /sbin/mingetty tt
root       590  0.0  0.1  1260  496 tty4     S    18:03   0:00 /sbin/mingetty tt
root       591  0.0  0.1  1260  496 tty5     S    18:03   0:00 /sbin/mingetty tt
root       592  0.0  0.1  1260  496 tty6     S    18:03   0:00 /sbin/mingetty tt
root       593  0.0  0.2 11740  716 ?        S    18:03   0:00 /usr/sbin/nscd
root       594  0.0  0.2 11740  716 ?        S    18:03   0:00 /usr/sbin/nscd
root       595  0.0  0.2 11740  716 ?        S    18:03   0:00 /usr/sbin/nscd
root       596  0.0  0.2 11740  716 ?        S    18:03   0:00 /usr/sbin/nscd
root       597  0.0  0.2 11740  716 ?        S    18:03   0:00 /usr/sbin/nscd
root       598  0.0  0.2 11740  716 ?        S    18:03   0:00 /usr/sbin/nscd
root       599  0.0  0.5  3024 1344 ?        S    18:03   0:00 /usr/bin/perl /ro
wwwrun     600  0.1  5.2 87156 13132 ?       S    18:03   0:00 /usr/sbin/httpd -
wwwrun     601  0.1  5.3 87340 13320 ?       S    18:03   0:00 /usr/sbin/httpd -
wwwrun     602  0.0  4.6 86252 11604 ?       S    18:03   0:00 /usr/sbin/httpd -
wwwrun     603  0.1  5.4 87648 13636 ?       S    18:03   0:00 /usr/sbin/httpd -
wwwrun     604  0.3  5.5 87776 13788 ?       S    18:03   0:00 /usr/sbin/httpd -
wwwrun     608  0.1  5.4 87628 13620 ?       S    18:03   0:00 /usr/sbin/httpd -
wwwrun     609  0.0  4.6 86084 11592 ?       S    18:03   0:00 /usr/sbin/httpd -
wwwrun     610  0.0  4.6 86084 11596 ?       S    18:03   0:00 /usr/sbin/httpd -
root       710  0.0  0.5  2444 1488 pts/0    R    18:06   0:00 ps -axu

So.. Ich hab echt keine Ahnung mehr woran das liegen kannn.. Hab doch sonst nix mehr geändert.. In der xinetd.log finde ich nichts von heute.. Nur noch Sachen von Gestern



Code: Select all

04/4/25@03:17:34: START: ftp pid=8661 from=211.22.72.136
04/4/25@03:17:34: EXIT: ftp status=1 pid=8661 duration=0(sec)
04/4/25@08:24:32: START: pop3 pid=10595 from=217.84.225.74
04/4/25@08:24:32: EXIT: pop3 status=0 pid=10595 duration=0(sec)
04/4/25@08:55:24: START: pop3 pid=10823 from=127.0.0.1
04/4/25@08:55:24: EXIT: pop3 status=0 pid=10823 duration=0(sec)
04/4/25@08:55:28: START: pop3 pid=10826 from=127.0.0.1
04/4/25@08:55:28: EXIT: pop3 status=0 pid=10826 duration=0(sec)
04/4/25@08:55:30: START: pop3 pid=10829 from=127.0.0.1
04/4/25@08:55:30: EXIT: pop3 status=0 pid=10829 duration=0(sec)
04/4/25@08:55:40: START: pop3 pid=10833 from=127.0.0.1
04/4/25@08:55:40: EXIT: pop3 status=0 pid=10833 duration=0(sec)
04/4/25@08:55:42: START: pop3 pid=10836 from=127.0.0.1
04/4/25@08:55:42: EXIT: pop3 status=0 pid=10836 duration=0(sec)
04/4/25@08:55:44: START: pop3 pid=10839 from=127.0.0.1
04/4/25@08:55:44: EXIT: pop3 status=0 pid=10839 duration=0(sec)
04/4/25@08:56:03: START: pop3 pid=10855 from=127.0.0.1
04/4/25@08:56:03: EXIT: pop3 status=0 pid=10855 duration=0(sec)
04/4/25@08:56:06: START: pop3 pid=10858 from=127.0.0.1
04/4/25@08:56:06: EXIT: pop3 status=0 pid=10858 duration=0(sec)
04/4/25@08:56:51: START: pop3 pid=10862 from=127.0.0.1
04/4/25@08:56:51: EXIT: pop3 status=0 pid=10862 duration=0(sec)
04/4/25@08:56:58: START: pop3 pid=10869 from=127.0.0.1
04/4/25@08:56:58: EXIT: pop3 status=0 pid=10869 duration=0(sec)
04/4/25@08:57:00: START: pop3 pid=10872 from=127.0.0.1
04/4/25@08:57:00: EXIT: pop3 status=0 pid=10872 duration=0(sec)
04/4/25@08:57:02: START: pop3 pid=10879 from=127.0.0.1
04/4/25@08:57:02: EXIT: pop3 status=0 pid=10879 duration=0(sec)
04/4/25@08:57:04: START: pop3 pid=10882 from=127.0.0.1
04/4/25@08:57:04: EXIT: pop3 status=0 pid=10882 duration=0(sec)
04/4/25@08:58:53: START: pop3 pid=10891 from=127.0.0.1
04/4/25@08:58:53: EXIT: pop3 status=0 pid=10891 duration=0(sec)
04/4/25@08:58:55: START: pop3 pid=10894 from=127.0.0.1
04/4/25@08:58:55: EXIT: pop3 status=0 pid=10894 duration=0(sec)
04/4/25@09:52:02: START: ftp pid=11245 from=80.130.79.13
04/4/25@09:58:18: START: pop3 pid=11281 from=127.0.0.1
04/4/25@09:58:18: EXIT: pop3 status=0 pid=11281 duration=0(sec)
04/4/25@09:58:21: START: pop3 pid=11284 from=127.0.0.1
04/4/25@09:58:21: EXIT: pop3 status=0 pid=11284 duration=0(sec)
04/4/25@09:58:22: EXIT: ftp status=0 pid=11245 duration=380(sec)
04/4/25@10:03:47: START: ftp pid=11348 from=217.229.67.74
04/4/25@10:11:56: START: pop3 pid=11424 from=127.0.0.1
04/4/25@10:11:56: EXIT: pop3 status=0 pid=11424 duration=0(sec)

Also wie gesagt, "RECORDS" ist schon raus.. Server ist neu gestartet und trotzdem nix.. wenn ich

Code: Select all

p15149767:~ # /etc/init.d/xinetd status
-bash: /etc/init.d/xinetd: No such file or directory

Das Steht in der "warn.log"


eingebe bekomme ich die oben genannte Ausgabe.. Also woran kanns dann noch liegen?! Ich hab echt alle Beiträge durch die es behandelt hatten...

Grüße

Taker


EDIT: Also "etc/init.d/xinetd status" funzt jetzt.. Er sagt dann "unused"

WEnn ich es mit rcxinetd start Starte sagt er "done" aber wenn ich dann nachfrage mit "etc/init.d/xinetd status" sagt er "unused"



Nochmal Grüße

Taker

Code: Select all

Apr 26 17:07:43 p15149767 postfix/smtpd[8990]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:07:44 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 8990 exit status 1
Apr 26 17:07:44 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:08:44 p15149767 postfix/smtpd[8998]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:08:45 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 8998 exit status 1
Apr 26 17:08:45 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:09:45 p15149767 postfix/smtpd[9003]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:09:46 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9003 exit status 1
Apr 26 17:09:46 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:10:46 p15149767 postfix/smtpd[9008]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:10:47 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9008 exit status 1
Apr 26 17:10:47 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:11:47 p15149767 postfix/smtpd[9017]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:11:48 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9017 exit status 1
Apr 26 17:11:48 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:12:48 p15149767 postfix/smtpd[9042]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:12:49 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9042 exit status 1
Apr 26 17:12:49 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:13:49 p15149767 postfix/smtpd[9097]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:13:50 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9097 exit status 1
Apr 26 17:13:50 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:14:50 p15149767 postfix/smtpd[9126]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:14:51 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9126 exit status 1
Apr 26 17:14:51 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:15:51 p15149767 postfix/smtpd[9184]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:15:52 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9184 exit status 1
Apr 26 17:15:52 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:16:52 p15149767 postfix/smtpd[9197]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:16:53 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9197 exit status 1
Apr 26 17:16:53 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:17:53 p15149767 postfix/smtpd[9218]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:17:54 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9218 exit status 1
Apr 26 17:17:54 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:18:54 p15149767 postfix/smtpd[9228]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:18:55 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9228 exit status 1
Apr 26 17:18:55 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:19:55 p15149767 postfix/smtpd[9241]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:19:56 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9241 exit status 1
Apr 26 17:19:56 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:20:56 p15149767 postfix/smtpd[9248]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:20:57 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9248 exit status 1
Apr 26 17:20:57 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:21:57 p15149767 postfix/smtpd[9272]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:21:58 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9272 exit status 1
Apr 26 17:21:58 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:22:58 p15149767 postfix/smtpd[9351]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:22:59 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9351 exit status 1
Apr 26 17:22:59 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:23:59 p15149767 postfix/smtpd[9369]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:24:00 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9369 exit status 1
Apr 26 17:24:00 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:25:00 p15149767 postfix/smtpd[9411]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:25:01 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9411 exit status 1
Apr 26 17:25:01 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:26:01 p15149767 postfix/smtpd[9420]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:26:02 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9420 exit status 1
Apr 26 17:26:02 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:27:02 p15149767 postfix/smtpd[9439]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:27:03 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9439 exit status 1
Apr 26 17:27:03 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:28:04 p15149767 postfix/smtpd[9444]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:28:05 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 9444 exit status 1
Apr 26 17:28:05 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:29:32 p15149767 xinetd[502]: missing service keyword [line=8]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad socket type: stream^M [line=19]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute socket_type - DISABLING SERVICE [line=19]
Apr 26 17:29:32 p15149767 xinetd[502]: Protocol tcp^M not in /etc/protocols [line=20]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute protocol - DISABLING SERVICE [line=20]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad value for wait: no^M [line=21]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute wait - DISABLING SERVICE [line=21]
Apr 26 17:29:32 p15149767 xinetd[502]: Unknown user: root^M [line=22]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute user - DISABLING SERVICE [line=22]
Apr 26 17:29:32 p15149767 xinetd[502]: Server /usr/sbin/vsftpd^M is not executable [line=23]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute server - DISABLING SERVICE [line=23]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad log_on_success flag: DURATION^M [line=25]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute log_on_success - DISABLING SERVICE [line=25]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad socket type: stream^M [line=32]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute socket_type - DISABLING SERVICE [line=32]
Apr 26 17:29:32 p15149767 xinetd[502]: Protocol tcp^M not in /etc/protocols [line=33]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute protocol - DISABLING SERVICE [line=33]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad value for wait: no^M [line=34]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute wait - DISABLING SERVICE [line=34]
Apr 26 17:29:32 p15149767 xinetd[502]: Unknown user: root^M [line=35]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute user - DISABLING SERVICE [line=35]
Apr 26 17:29:32 p15149767 xinetd[502]: Server /usr/sbin/popper^M is not executable [line=36]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute server - DISABLING SERVICE [line=36]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad log_on_success flag: DURATION^M [line=38]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute log_on_success - DISABLING SERVICE [line=38]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad socket type: stream^M [line=45]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute socket_type - DISABLING SERVICE [line=45]
Apr 26 17:29:32 p15149767 xinetd[502]: Protocol tcp^M not in /etc/protocols [line=46]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute protocol - DISABLING SERVICE [line=46]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad value for wait: no^M [line=47]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute wait - DISABLING SERVICE [line=47]
Apr 26 17:29:32 p15149767 xinetd[502]: Unknown user: root^M [line=48]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute user - DISABLING SERVICE [line=48]
Apr 26 17:29:32 p15149767 xinetd[502]: Server /usr/sbin/stunnel^M is not executable [line=49]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute server - DISABLING SERVICE [line=49]
Apr 26 17:29:32 p15149767 xinetd[502]: Bad log_on_success flag: DURATION^M [line=51]
Apr 26 17:29:32 p15149767 xinetd[502]: Error parsing attribute log_on_success - DISABLING SERVICE [line=51]
Apr 26 17:29:32 p15149767 xinetd[502]: 502 {init_services} no services. Exiting...
Apr 26 17:43:37 p15149767 xinetd[765]: missing service keyword [line=8]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad socket type: stream^M [line=19]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute socket_type - DISABLING SERVICE [line=19]
Apr 26 17:43:37 p15149767 xinetd[765]: Protocol tcp^M not in /etc/protocols [line=20]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute protocol - DISABLING SERVICE [line=20]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad value for wait: no^M [line=21]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute wait - DISABLING SERVICE [line=21]
Apr 26 17:43:37 p15149767 xinetd[765]: Unknown user: root^M [line=22]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute user - DISABLING SERVICE [line=22]
Apr 26 17:43:37 p15149767 xinetd[765]: Server /usr/sbin/vsftpd^M is not executable [line=23]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute server - DISABLING SERVICE [line=23]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad log_on_success flag: DURATION^M [line=25]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute log_on_success - DISABLING SERVICE [line=25]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad socket type: stream^M [line=32]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute socket_type - DISABLING SERVICE [line=32]
Apr 26 17:43:37 p15149767 xinetd[765]: Protocol tcp^M not in /etc/protocols [line=33]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute protocol - DISABLING SERVICE [line=33]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad value for wait: no^M [line=34]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute wait - DISABLING SERVICE [line=34]
Apr 26 17:43:37 p15149767 xinetd[765]: Unknown user: root^M [line=35]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute user - DISABLING SERVICE [line=35]
Apr 26 17:43:37 p15149767 xinetd[765]: Server /usr/sbin/popper^M is not executable [line=36]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute server - DISABLING SERVICE [line=36]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad log_on_success flag: DURATION^M [line=38]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute log_on_success - DISABLING SERVICE [line=38]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad socket type: stream^M [line=45]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute socket_type - DISABLING SERVICE [line=45]
Apr 26 17:43:37 p15149767 xinetd[765]: Protocol tcp^M not in /etc/protocols [line=46]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute protocol - DISABLING SERVICE [line=46]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad value for wait: no^M [line=47]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute wait - DISABLING SERVICE [line=47]
Apr 26 17:43:37 p15149767 xinetd[765]: Unknown user: root^M [line=48]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute user - DISABLING SERVICE [line=48]
Apr 26 17:43:37 p15149767 xinetd[765]: Server /usr/sbin/stunnel^M is not executable [line=49]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute server - DISABLING SERVICE [line=49]
Apr 26 17:43:37 p15149767 xinetd[765]: Bad log_on_success flag: DURATION^M [line=51]
Apr 26 17:43:37 p15149767 xinetd[765]: Error parsing attribute log_on_success - DISABLING SERVICE [line=51]
Apr 26 17:43:37 p15149767 xinetd[765]: 765 {init_services} no services. Exiting...
Apr 26 17:50:38 p15149767 xinetd[502]: missing service keyword [line=8]
Apr 26 17:50:38 p15149767 xinetd[502]: Bad socket type: stream^M [line=19]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute socket_type - DISABLING SERVICE [line=19]
Apr 26 17:50:38 p15149767 xinetd[502]: Protocol tcp^M not in /etc/protocols [line=20]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute protocol - DISABLING SERVICE [line=20]
Apr 26 17:50:38 p15149767 xinetd[502]: Bad value for wait: no^M [line=21]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute wait - DISABLING SERVICE [line=21]
Apr 26 17:50:38 p15149767 xinetd[502]: Unknown user: root^M [line=22]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute user - DISABLING SERVICE [line=22]
Apr 26 17:50:38 p15149767 xinetd[502]: Server /usr/sbin/vsftpd^M is not executable [line=23]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute server - DISABLING SERVICE [line=23]
Apr 26 17:50:38 p15149767 xinetd[502]: Bad log_on_success flag: DURATION^M [line=25]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute log_on_success - DISABLING SERVICE [line=25]
Apr 26 17:50:38 p15149767 xinetd[502]: Bad log_on_failure flag: ATTEMPT^M [line=26]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute log_on_failure - DISABLING SERVICE [line=26]
Apr 26 17:50:38 p15149767 xinetd[502]: Bad socket type: stream^M [line=32]
Apr 26 17:50:38 p15149767 xinetd[502]: Error parsing attribute socket_type - DISABLING SERVICE [line=32]
Apr 26 17:50:39 p15149767 xinetd[502]: Protocol tcp^M not in /etc/protocols [line=33]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute protocol - DISABLING SERVICE [line=33]
Apr 26 17:50:39 p15149767 xinetd[502]: Bad value for wait: no^M [line=34]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute wait - DISABLING SERVICE [line=34]
Apr 26 17:50:39 p15149767 xinetd[502]: Unknown user: root^M [line=35]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute user - DISABLING SERVICE [line=35]
Apr 26 17:50:39 p15149767 xinetd[502]: Server /usr/sbin/popper^M is not executable [line=36]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute server - DISABLING SERVICE [line=36]
Apr 26 17:50:39 p15149767 xinetd[502]: Bad log_on_success flag: DURATION^M [line=38]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute log_on_success - DISABLING SERVICE [line=38]
Apr 26 17:50:39 p15149767 xinetd[502]: Bad log_on_failure flag: RECORD^M [line=39]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute log_on_failure - DISABLING SERVICE [line=39]
Apr 26 17:50:39 p15149767 xinetd[502]: Bad socket type: stream^M [line=45]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute socket_type - DISABLING SERVICE [line=45]
Apr 26 17:50:39 p15149767 xinetd[502]: Protocol tcp^M not in /etc/protocols [line=46]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute protocol - DISABLING SERVICE [line=46]
Apr 26 17:50:39 p15149767 xinetd[502]: Bad value for wait: no^M [line=47]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute wait - DISABLING SERVICE [line=47]
Apr 26 17:50:39 p15149767 xinetd[502]: Unknown user: root^M [line=48]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute user - DISABLING SERVICE [line=48]
Apr 26 17:50:39 p15149767 xinetd[502]: Server /usr/sbin/stunnel^M is not executable [line=49]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute server - DISABLING SERVICE [line=49]
Apr 26 17:50:39 p15149767 xinetd[502]: Bad log_on_success flag: DURATION^M [line=51]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute log_on_success - DISABLING SERVICE [line=51]
Apr 26 17:50:39 p15149767 xinetd[502]: Bad log_on_failure flag: RECORD^M [line=52]
Apr 26 17:50:39 p15149767 xinetd[502]: Error parsing attribute log_on_failure - DISABLING SERVICE [line=52]
Apr 26 17:50:39 p15149767 xinetd[502]: 502 {init_services} no services. Exiting...
Apr 26 17:54:18 p15149767 xinetd[647]: Bad log_on_success flag: ^M [line=11]
Apr 26 17:54:18 p15149767 xinetd[647]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 17:54:18 p15149767 xinetd[647]: Exiting...
Apr 26 17:54:24 p15149767 xinetd[669]: Bad log_on_success flag: ^M [line=11]
Apr 26 17:54:24 p15149767 xinetd[669]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 17:54:24 p15149767 xinetd[669]: Exiting...
Apr 26 17:55:59 p15149767 postfix/smtpd[693]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:56:00 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 693 exit status 1
Apr 26 17:56:00 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:57:00 p15149767 postfix/smtpd[701]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:57:01 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 701 exit status 1
Apr 26 17:57:01 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:58:01 p15149767 postfix/smtpd[710]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:58:02 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 710 exit status 1
Apr 26 17:58:02 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 17:59:02 p15149767 postfix/smtpd[927]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 17:59:03 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 927 exit status 1
Apr 26 17:59:03 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 18:00:03 p15149767 postfix/smtpd[965]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 18:00:04 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 965 exit status 1
Apr 26 18:00:04 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 18:01:04 p15149767 postfix/smtpd[973]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 18:01:05 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 973 exit status 1
Apr 26 18:01:05 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 18:02:05 p15149767 postfix/smtpd[1794]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 18:02:06 p15149767 postfix/master[468]: warning: process /usr/lib/postfix/smtpd pid 1794 exit status 1
Apr 26 18:02:06 p15149767 postfix/master[468]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 26 18:28:08 p15149767 kernel: eth0: MII status changed: Autonegotiation advertising 05e1  partner 41e1.
Apr 26 18:29:49 p15149767 postfix/smtp[1706]: warning: mailer loop: best MX host for garfield0815.de is local
Apr 26 18:29:49 p15149767 postfix/smtp[1706]: warning: mailer loop: best MX host for garfield0815.de is local
Apr 26 18:30:20 p15149767 xinetd[1765]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:30:20 p15149767 xinetd[1765]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:30:20 p15149767 xinetd[1765]: Exiting...
Apr 26 18:30:25 p15149767 xinetd[1787]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:30:25 p15149767 xinetd[1787]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:30:25 p15149767 xinetd[1787]: Exiting...
Apr 26 18:30:27 p15149767 xinetd[1809]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:30:27 p15149767 xinetd[1809]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:30:27 p15149767 xinetd[1809]: Exiting...
Apr 26 18:30:29 p15149767 xinetd[1831]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:30:29 p15149767 xinetd[1831]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:30:29 p15149767 xinetd[1831]: Exiting...
Apr 26 18:33:09 p15149767 xinetd[649]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:33:09 p15149767 xinetd[649]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:33:09 p15149767 xinetd[649]: Exiting...
Apr 26 18:33:12 p15149767 xinetd[672]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:33:12 p15149767 xinetd[672]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:33:12 p15149767 xinetd[672]: Exiting...
Apr 26 18:34:18 p15149767 xinetd[719]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:34:18 p15149767 xinetd[719]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:34:18 p15149767 xinetd[719]: Exiting...
Apr 26 18:34:21 p15149767 xinetd[741]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:34:21 p15149767 xinetd[741]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:34:21 p15149767 xinetd[741]: Exiting...
Apr 26 18:34:30 p15149767 xinetd[762]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:34:30 p15149767 xinetd[762]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:34:30 p15149767 xinetd[762]: Exiting...
Apr 26 18:37:34 p15149767 xinetd[796]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:37:34 p15149767 xinetd[796]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:37:34 p15149767 xinetd[796]: Exiting...
Apr 26 18:37:36 p15149767 xinetd[807]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:37:36 p15149767 xinetd[807]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:37:36 p15149767 xinetd[807]: Exiting...
Apr 26 18:37:40 p15149767 xinetd[827]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:37:40 p15149767 xinetd[827]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:37:40 p15149767 xinetd[827]: Exiting...
Apr 26 18:37:42 p15149767 xinetd[838]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:37:42 p15149767 xinetd[838]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:37:42 p15149767 xinetd[838]: Exiting...
Apr 26 18:40:29 p15149767 xinetd[623]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:40:29 p15149767 xinetd[623]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:40:29 p15149767 xinetd[623]: Exiting...
Apr 26 18:40:40 p15149767 xinetd[652]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:40:40 p15149767 xinetd[652]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:40:41 p15149767 xinetd[652]: Exiting...
Apr 26 18:40:42 p15149767 xinetd[663]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:40:42 p15149767 xinetd[663]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:40:42 p15149767 xinetd[663]: Exiting...
Apr 26 18:50:11 p15149767 xinetd[824]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:50:11 p15149767 xinetd[824]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:50:11 p15149767 xinetd[824]: Exiting...
Apr 26 18:50:14 p15149767 xinetd[846]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:50:14 p15149767 xinetd[846]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:50:14 p15149767 xinetd[846]: Exiting...
Top
darkspirit
Posts: 553
Joined: 2002-10-05 16:39
Location: D'dorf
Contact:
Contact darkspirit
 

Re: vsftpd Fehler. Login nicht möglich.

Post by darkspirit »

Du solltest deine Configs nicht per Windows editieren oder zumindest wenigstens dafür sorgen, dass sie anständig konvertiert werden..
Top
taker
Posts: 71
Joined: 2004-01-25 14:08
 

Re: vsftpd Fehler. Login nicht möglich.

Post by taker »

Apr 26 18:50:11 p15149767 xinetd[824]: Exiting...
Apr 26 18:50:14 p15149767 xinetd[846]: Bad log-on-success flag: ^M [line=11]
Apr 26 18:50:14 p15149767 xinetd[846]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 26 18:50:14 p15149767 xinetd[846]: Exiting...

Ich hab schon alles mögliche Versucht in Zeile 11 , da wo die Defaults sind..

Also ich habs heute mal mit Dreamweaver geöffnet, geht sogar*lol* Nee Geht sogar sehr gut..Alles übersichtlich etc.

Kannst du mir denn helfen?

Taker
Top
chris76
Posts: 1878
Joined: 2003-06-27 14:37
Location: Germering
 

Re: vsftpd Fehler. Login nicht möglich.

Post by chris76 »

Du hast um die Zeile 11 herum was stehen das nur von einem Windowseditor her stammen kann :)

Schau das du das ^M wegbringst, dann sollte es wieder klappen.

vi ist dein Freund :wink:
Gruß Christian

BofH excuses: YOU HAVE AN I/O ERROR -> Incompetent Operator error
Top
taker
Posts: 71
Joined: 2004-01-25 14:08
 

Re: vsftpd Fehler. Login nicht möglich.

Post by taker »

HI, also ja da hätt ich meinen Besten Freund bald vergessen*lol*

ALso Im Ernst, habs in Vi geöffnet aber da stehts auch nur so drin, hier Ein Auszug:

Code: Select all


#
# xinetd.conf
#
# Copyright (c) 1998-2001 SuSE GmbH Nuernberg, Germany.
# Copyright (c) 2002 SuSE Linux AG, Nuernberg, Germany.
#

defaults
{
        log_type        = FILE /var/log/xinetd.log
        log_on_success  = HOST EXIT DURATION
        log_on_failure  = HOST ATTEMPT
#       only_from       = localhost
        instances       = 10
}

service ftp
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = root
        server          = /usr/sbin/vsftpd
#       server_args     = -a
        log_on_success  = HOST PID EXIT DURATION
#       log_on_failure  = HOST ATTEMPT
}


service pop3
{
        socket_type = stream
        protocol = tcp
        wait = no
        user = root
        server = /usr/sbin/popper
        server_args = qpopper -s
        log_on_success  = HOST PID EXIT DURATION
#       log_on_failure  = HOST ATTEMPT
}

# *grrr* SuSE-8.1: qpopper.rpm compiled without ssl/tls-support
service pop3s
{
        socket_type = stream
        protocol = tcp
        wait = no
        user = root
        server = /usr/sbin/stunnel
        server_args = qpopper -l /usr/sbin/popper -- -R -s
        log_on_success  = HOST PID EXIT DURATION
#       log_on_failure  = HOST ATTEMPT
}

Also da steht nix mit ^M oder so.. Ich versteh das einfach nich...

Taker
Top
captaincrunch
Userprojekt
Userprojekt
Posts: 7066
Joined: 2002-10-09 14:30
Location: Dorsten
Contact:
Contact captaincrunch
 

Re: vsftpd Fehler. Login nicht möglich.

Post by captaincrunch »

Code: Select all

dos2unix /etc/xinetd.conf
Wann lernen die Leute es endlich, dass es keine gute Idee ist, Windows-Editoren zu nutzen?
DebianHowTo
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc
Top
taker
Posts: 71
Joined: 2004-01-25 14:08
 

Re: vsftpd Fehler. Login nicht möglich.

Post by taker »

Danke Leute aber ich habs jetzt gelöst! Ich hab mich mit "Syro" in Verbindung gesetzt und der hat mir dann per ICQ geholfen. Nach ein paar weiteren Kleinen Probs hats dann endlich funktioniert! SYRO DANKE DIR!!! Und natürlich auch danke an alle anderen!

Grüße

Taker

PS: Ich werds mir merken wegen den "Editoren"
Top
taker
Posts: 71
Joined: 2004-01-25 14:08
 

Re: vsftpd Fehler. Login nicht möglich.

Post by taker »

Hallo Leute, also eigentlich hat alles funktioniert aber das "lustige" ist das ich jetzt immer einmal am Tag die xinetd.cf neu einspielen muss damit es funzt! Irgendwie macht mir da was einen Strich durch die Rechnung! Es scheint so als ob irgendetwas die conf umschreiben würde! Ich denke da an Confixx oder sowas.. WEil immer nach den "CronJobs" gings nicht mehr. Also das vermute ich jedenfalls weil die letzte "warn" die ich hatte war die das Confixx die CronsJobs jetzt ausführt. Und heute mittag bemerke ich das mein FTP net mehr geht..
Könnte da ein Zusammenhang bestehen? Reicht es aus wenn ich die xinetd.cf schreibscütze oder was kann ich dagegen tun? Oder kann ich die Daten in den "cron Ordnern" bedenkenlos löschen?! Dann würd ich einfach die ganzen ordner leer machen.. (die "cron Ordner")

Hoffe mir hilft nochmals jemand, aber krass für mich wirds immer Klarer, langsam aber sicher versteh ich so manche Zusammenhänge besser!

Grüße

Taker

EDIT: Ich hab jetzt mal alle Logs angeguckt aber nichts gefunden.. Nur "xinetd exiting" Toll.. Das merk ich auch so^^ Also der Dienst beendet sich einfach automatisch.. HEUL Ich versteh die Welt nicht mehr
Top
Post Reply

Return to “Datentransfer”