xinetd + Record, sorry aber es will einfach nicht

Backup, Restore und Transfer von Daten
Post Reply
syro
Posts: 26
Joined: 2003-10-23 22:10
 

xinetd + Record, sorry aber es will einfach nicht

Post by syro »

Hi,
vorab ich habe sogut wie jeden thread hier im Forum darüber gelesen, doch nichts wollte helfen.


Was habe ich gemacht ?
YAST Update + Kernel Update auf 2.4.20.

Server neugestartet und nur http funktioniert. FTP + POP3 nicht.

Nun habe ich die Beiträge hier gelesen und das RECORD in der file xinetd.conf entfernt. hier:

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
Server neugestartet und wieder läuft es nicht.

Nun habe ich folgendes versucht:

/etc/init.d/xinetd restart
es sagt mir dann auch das es erfolgreich gestartet wurde.

mache ich
/etc/init.d/xinetd status

kommt:

Code: Select all

p15135513:~ # /etc/init.d/xinetd status
Checking for service xinetd:                                                                                       unused
Nun war ich schon am verzweifeln und habe xinetd upgedatet auf Version 2.3.13.

Server wieder neugestartet und es will imemr noch nicht.

hier noch ein paar Auszüge:

Code: Select all

p15135513:~ # netstat -pletu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 *:mysql                 *:*                     LISTEN      root       1304       402/mysqld
tcp        0      0 *:sunrpc                *:*                     LISTEN      root       1220       353/portmap
tcp        0      0 *:www-http              *:*                     LISTEN      root       2795       532/httpd
tcp        0      0 *:smtps                 *:*                     LISTEN      root       1920       499/master
tcp        0      0 *:ident                 *:*                     LISTEN      root       401        181/oidentd
tcp        0      0 *:ssh                   *:*                     LISTEN      root       1280       369/sshd
tcp        0      0 *:smtp                  *:*                     LISTEN      root       1917       499/master
tcp        0      0 *:https                 *:*                     LISTEN      root       2794       532/httpd
udp        0      0 *:bootpc                *:*                                 root       521        313/dhcpcd
udp        0      0 *:sunrpc                *:*                                 root       1166       353/portmap
udp        0      0 bse-zone.com:ntp        *:*                                 root       1744       445/ntpd
udp        0      0 localhost.localdoma:ntp *:*                                 root       1743       445/ntpd
udp        0      0 *:ntp                   *:*                                 root       1742       445/ntpd

Code: Select all

p15135513:~ # ps -aux
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root         1  1.4  0.0   448  236 ?        S    12:45   0:05 init
root         2  0.0  0.0     0    0 ?        SW   12:45   0:00 [keventd]
root         3  0.0  0.0     0    0 ?        SWN  12:45   0:00 [ksoftirqd_CPU0]
root         4  0.0  0.0     0    0 ?        SW   12:45   0:00 [kswapd]
root         5  0.0  0.0     0    0 ?        SW   12:45   0:00 [bdflush]
root         6  0.0  0.0     0    0 ?        SW   12:45   0:00 [kupdated]
root         8  0.0  0.0     0    0 ?        SW   12:45   0:00 [kjournald]
root        55  0.0  0.0     0    0 ?        SW   12:45   0:00 [kjournald]
nobody     181  0.0  0.2  1472  632 ?        S    12:45   0:00 /usr/sbin/oidentd -u nobody -g nobody
root       313  0.0  0.2  1300  548 ?        S    12:45   0:00 /sbin/dhcpcd -d -N -Y -t 999999 eth0
root       329  0.0  0.2  1340  596 ?        S    12:45   0:00 /sbin/syslogd
root       332  0.0  0.5  2076 1252 ?        S    12:45   0:00 /sbin/klogd -c 1 -2
bin        353  0.0  0.1  1292  396 ?        S    12:45   0:00 /sbin/portmap
root       367  0.0  0.4  2256 1152 ?        S    12:45   0:00 /bin/sh /usr/bin/safe_mysqld --user=mysql --pid-file=/var/lib/m
root       369  0.0  0.6  4144 1636 ?        S    12:45   0:00 /usr/sbin/sshd
mysql      402  0.0  1.4 21908 3672 ?        S    12:45   0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user
mysql      404  0.0  1.4 21908 3672 ?        S    12:45   0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user
mysql      405  0.0  1.4 21908 3672 ?        S    12:45   0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user
ntp        445  0.0  0.7  1920 1912 ?        SL   12:45   0:00 /usr/sbin/ntpd -U ntp
root       499  0.0  0.5  4424 1452 ?        S    12:45   0:00 /usr/lib/postfix/master
postfix    513  0.0  0.5  4388 1392 ?        S    12:45   0:00 pickup -l -t fifo -u
postfix    514  0.0  0.7  9644 1872 ?        S    12:45   0:00 qmgr -l -t fifo -u
root       532  0.0  3.2 82988 7996 ?        S    12:45   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
root       545  0.0  0.5  3028 1348 ?        S    12:45   0:00 /usr/bin/perl /root/confixx/pipelog.pl
wwwrun     546  0.1  3.7 83916 9404 ?        S    12:45   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     547  0.0  3.4 83204 8672 ?        S    12:45   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
at         548  0.0  0.2  1400  548 ?        S    12:45   0:00 /usr/sbin/atd
wwwrun     549  0.0  3.3 83080 8436 ?        S    12:45   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     550  0.0  3.2 83000 8072 ?        S    12:45   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     551  0.0  3.6 83696 9152 ?        S    12:45   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
root       566  0.0  0.2  1416  624 ?        S    12:45   0:00 /usr/sbin/cron
root       582  0.0  0.2 11744  720 ?        S    12:45   0:00 /usr/sbin/nscd
root       587  0.0  0.1  1260  496 tty1     S    12:45   0:00 /sbin/mingetty --noclear tty1
root       588  0.0  0.1  1260  496 tty2     S    12:45   0:00 /sbin/mingetty tty2
root       589  0.0  0.1  1260  496 tty3     S    12:45   0:00 /sbin/mingetty tty3
root       590  0.0  0.1  1260  496 tty4     S    12:45   0:00 /sbin/mingetty tty4
root       591  0.0  0.1  1260  496 tty5     S    12:45   0:00 /sbin/mingetty tty5
root       592  0.0  0.2 11744  720 ?        S    12:45   0:00 /usr/sbin/nscd
root       593  0.0  0.2 11744  720 ?        S    12:45   0:00 /usr/sbin/nscd
root       594  0.0  0.1  1260  496 tty6     S    12:45   0:00 /sbin/mingetty tty6
root       595  0.0  0.2 11744  720 ?        S    12:45   0:00 /usr/sbin/nscd
root       596  0.0  0.2 11744  720 ?        S    12:45   0:00 /usr/sbin/nscd
root       597  0.0  0.2 11744  720 ?        S    12:45   0:00 /usr/sbin/nscd
root       598  0.0  0.2 11744  720 ?        S    12:45   0:00 /usr/sbin/nscd
wwwrun     604  0.0  4.0 84488 10000 ?       S    12:46   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     607  0.5  3.7 83724 9268 ?        S    12:46   0:01 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     608  0.1  3.4 83100 8548 ?        S    12:46   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     609  0.3  4.0 84536 10072 ?       S    12:46   0:01 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     614  0.0  3.7 83948 9344 ?        S    12:46   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
root       654  0.0  0.8  7304 2236 ?        S    12:48   0:00 /usr/sbin/sshd
root       659  0.0  0.6  2820 1696 pts/0    S    12:48   0:00 -bash
wwwrun     762  0.0  3.2 83000 8076 ?        S    12:50   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     763  0.3  3.7 83948 9348 ?        S    12:50   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
wwwrun     764  0.0  3.2 83000 8080 ?        S    12:50   0:00 /usr/sbin/httpd -f /etc/httpd/httpd.conf -D SSL
postfix    789  0.2  1.0 13804 2696 ?        S    12:51   0:00 smtpd -n smtp -t inet -u
postfix    791  0.2  0.7 10940 1884 ?        S    12:51   0:00 cleanup -t unix -u
postfix    792  0.1  0.6  5704 1692 ?        S    12:51   0:00 trivial-rewrite -n rewrite -t unix -u
postfix    793  0.0  0.7  5744 1772 ?        S    12:51   0:00 local -t unix
root       797  0.0  0.6  2448 1492 pts/0    R    12:51   0:00 ps -aux
Ich hoffe ihr könnt mir helfen, und bitte schreibt nciht ich soll hier die Suchfunktion benutzten, das habe nämlich schon gemacht ! Es will alles nichts helfen.

Ich hoffe auf Antworten.

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

Re: xinetd + Record, sorry aber es will einfach nicht

Post by chris76 »

steht dazu was in den logs?
Top
syro
Posts: 26
Joined: 2003-10-23 22:10
 

re

Post by syro »

seit gestern 20.00 (da wo server restarted wurde) schreibt er nichts mehr in die xinetd.log rein.

hier ein auszug bis zum restart (update):

Code: Select all

04/4/17@20:01:11: START: ftp pid=15796 from=80.131.100.142
04/4/17@20:02:20: START: ftp pid=15837 from=80.131.100.142
04/4/17@20:02:31: EXIT: ftp status=0 pid=15837 duration=11(sec)
04/4/17@20:02:58: START: pop3 pid=15888 from=212.184.156.74
04/4/17@20:03:00: EXIT: pop3 status=0 pid=15888 duration=2(sec)
04/4/17@20:03:00: START: pop3 pid=15894 from=212.184.156.74
04/4/17@20:03:01: EXIT: pop3 status=0 pid=15894 duration=1(sec)
04/4/17@20:03:32: START: ftp pid=15918 from=80.131.100.142
04/4/17@20:04:32: EXIT: ftp status=1 pid=15918 duration=60(sec)
04/4/17@20:04:49: EXIT: ftp status=1 pid=15796 duration=218(sec)
04/4/17@20:06:47: START: ftp pid=16075 from=80.131.100.142
04/4/17@20:07:06: START: ftp pid=16086 from=80.131.100.142
04/4/17@20:07:17: EXIT: ftp status=0 pid=16086 duration=11(sec)
04/4/17@20:07:39: EXIT: ftp status=0 pid=15531 duration=892(sec)
04/4/17@20:07:40: EXIT: ftp status=1 pid=16075 duration=53(sec)
04/4/17@20:07:43: START: ftp pid=16102 from=217.85.148.107
04/4/17@20:13:59: EXIT: ftp status=0 pid=15569 duration=1161(sec)
04/4/17@20:15:04: START: ftp pid=16374 from=217.229.149.129
04/4/17@20:15:08: START: ftp pid=16377 from=217.235.16.24
04/4/17@20:15:20: EXIT: ftp status=0 pid=13759 duration=4936(sec)
04/4/17@20:15:20: EXIT: ftp status=0 pid=16374 duration=16(sec)
04/4/17@20:17:55: START: pop3 pid=16426 from=212.184.155.72
04/4/17@20:18:00: EXIT: pop3 status=0 pid=16426 duration=5(sec)
04/4/17@20:18:00: START: pop3 pid=16432 from=212.184.155.72
04/4/17@20:18:01: EXIT: pop3 status=0 pid=16432 duration=1(sec)
04/4/17@20:20:26: EXIT: ftp status=0 pid=16377 duration=318(sec)
04/4/17@20:21:24: EXIT: ftp status=0 pid=16102 duration=821(sec)
Top
chris76
Posts: 1878
Joined: 2003-06-27 14:37
Location: Germering
 

Re: xinetd + Record, sorry aber es will einfach nicht

Post by chris76 »

Ich meinte eher ob da Informationen drin stehen im message oder warn log, ob der xinetd überhaupt startet. Oder warum net!
Gruß Christian

BofH excuses: YOU HAVE AN I/O ERROR -> Incompetent Operator error
Top
syro
Posts: 26
Joined: 2003-10-23 22:10
 

re

Post by syro »

jo da steht was drinnen, nur werde ich daraus schlau:

Code: Select all

Apr 18 12:40:33 p15135513 xinetd[5111]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:40:33 p15135513 xinetd[5111]: Exiting...
Apr 18 12:40:34 p15135513 xinetd[5133]: Bad log_on_success flag: ^M [line=11]
Apr 18 12:40:34 p15135513 xinetd[5133]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:40:34 p15135513 xinetd[5133]: Exiting...
Apr 18 12:45:31 p15135513 xinetd[428]: Bad log_on_success flag: ^M [line=11]
Apr 18 12:45:31 p15135513 xinetd[428]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:45:31 p15135513 xinetd[428]: Exiting...
Apr 18 12:49:18 p15135513 xinetd[699]: Bad log_on_success flag: ^M [line=11]
Apr 18 12:49:18 p15135513 xinetd[699]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:49:18 p15135513 xinetd[699]: Exiting...
Apr 18 12:49:20 p15135513 xinetd[710]: Bad log_on_success flag: ^M [line=11]
Apr 18 12:49:20 p15135513 xinetd[710]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:49:20 p15135513 xinetd[710]: Exiting...
Apr 18 12:49:21 p15135513 xinetd[721]: Bad log_on_success flag: ^M [line=11]
Apr 18 12:49:21 p15135513 xinetd[721]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:49:21 p15135513 xinetd[721]: Exiting...
Apr 18 12:49:21 p15135513 xinetd[732]: Bad log_on_success flag: ^M [line=11]
Apr 18 12:49:21 p15135513 xinetd[732]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:49:21 p15135513 xinetd[732]: Exiting...
Apr 18 12:49:21 p15135513 xinetd[743]: Bad log_on_success flag: ^M [line=11]
Apr 18 12:49:21 p15135513 xinetd[743]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 12:49:21 p15135513 xinetd[743]: Exiting...
Apr 18 13:55:15 p15135513 xinetd[2253]: Bad log_on_success flag: ^M [line=11]
Apr 18 13:55:15 p15135513 xinetd[2253]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 13:55:15 p15135513 xinetd[2253]: Exiting...
Apr 18 13:55:58 p15135513 xinetd[2279]: Bad log_on_success flag: ^M [line=11]
Apr 18 13:55:58 p15135513 xinetd[2279]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 13:55:58 p15135513 xinetd[2279]: Exiting...
Apr 18 13:55:58 p15135513 xinetd[2290]: Bad log_on_success flag: ^M [line=11]
Apr 18 13:55:58 p15135513 xinetd[2290]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 13:55:58 p15135513 xinetd[2290]: Exiting...
Apr 18 13:55:59 p15135513 xinetd[2301]: Bad log_on_success flag: ^M [line=11]
Apr 18 13:55:59 p15135513 xinetd[2301]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 13:55:59 p15135513 xinetd[2301]: Exiting...
Apr 18 13:56:00 p15135513 xinetd[2312]: Bad log_on_success flag: ^M [line=11]
Apr 18 13:56:00 p15135513 xinetd[2312]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 13:56:00 p15135513 xinetd[2312]: Exiting...
Apr 18 13:56:35 p15135513 xinetd[2351]: Bad log_on_success flag: ^M [line=11]
Apr 18 13:56:35 p15135513 xinetd[2351]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 13:56:35 p15135513 xinetd[2351]: Exiting...
Apr 18 13:56:54 p15135513 xinetd[2359]: Bad log_on_success flag: ^M [line=11]
Apr 18 13:56:54 p15135513 xinetd[2359]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 13:56:54 p15135513 xinetd[2359]: Exiting...
Apr 18 14:05:28 p15135513 xinetd[2669]: Bad log_on_success flag: ^M [line=11]
Apr 18 14:05:28 p15135513 xinetd[2669]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 14:05:28 p15135513 xinetd[2669]: Exiting...
Apr 18 14:11:47 p15135513 xinetd[428]: Bad log-on-success flag: ^M [line=11]
Apr 18 14:11:47 p15135513 xinetd[428]: A fatal error was encountered while parsing the default section. xinetd will exit.
Apr 18 14:11:47 p15135513 xinetd[428]: Exiting...
meint es, die elfte zeile in der conf file ? oder was ganz anderes ?
Top
captaincrunch
Userprojekt
Userprojekt
Posts: 7066
Joined: 2002-10-09 14:30
Location: Dorsten
Contact:
Contact captaincrunch
 

Re: xinetd + Record, sorry aber es will einfach nicht

Post by captaincrunch »

Sofern du das File mit einem vernünftigen Editor (und nicht unter Windows) bearbeitet hättest, hättest du das Problem erst gar nicht.
DebianHowTo
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc
Top
syro
Posts: 26
Joined: 2003-10-23 22:10
 

re

Post by syro »

alles klar, an alle anderen newbies draußen, niemals dateien mit dem wordpad editieren..

vielen dank für die antworten.

mfg syro
Top
compositiv
Posts: 193
Joined: 2003-01-22 14:58
Location: Hamburg
Contact:
Contact compositiv
 

Re: xinetd + Record, sorry aber es will einfach nicht

Post by compositiv »

Vielleicht erleichtert der Editor joe den Umstieg aufs editieren in der Linuxshell, ist IMHO nicht ganz so kryptisch zu bedienen wie vi oder ed.
Top
Post Reply

Return to “Datentransfer”