LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 01-14-2006, 07:34 AM   #1
ozric
LQ Newbie
 
Registered: Jan 2005
Location: Örebro, Sweden
Distribution: SUSE 9.2
Posts: 23

Rep: Reputation: 15
Question SuSE 9.2 exits xinetd after malfuntion in mail?


Yet again I seek help with something that I can't get my head around. I've got two servers on a remote location running suse 9.2. One serves as FTP, the other one is connected directly to the first one via a crossed tp-cable, and serving the FTP box with an NFS share.

A while ago, I took the servers down for some hardware upgrades, and evaluated the stability of the machines at the same time by running them for a week without any interuption. It worked fine. 2 days ago I moved them back to their original location and after approx. 30 hrs uptime the system went down. It was manually restarted, and I took a look at /var/log/warn. The last output is as follows:

Quote:
Jan 13 22:13:41 c-6fe471d5 kernel: ip_conntrack version 2.1 (3839 buckets, 30712 max) - 336 bytes per conntrack
Jan 13 22:13:41 c-6fe471d5 kernel: ip6_conntrack version 0.1 (3839 buckets, 30712 max) - 208 bytes per conntrack
Jan 13 22:13:47 c-6fe471d5 ifup: No configuration found for sit0
Jan 13 22:13:54 c-6fe471d5 sshd[5627]: error: getnameinfo failed
Jan 13 22:13:54 c-6fe471d5 sshd[5627]: error: Bind to port 6669 on 0.0.0.0 failed: Address already in use.
Jan 13 22:18:02 c-6fe471d5 kernel: ip6_tables: (C) 2000-2002 Netfilter core team
Jan 13 22:18:02 c-6fe471d5 kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 13 22:18:02 c-6fe471d5 kernel: ip_conntrack version 2.1 (3839 buckets, 30712 max) - 336 bytes per conntrack
Jan 13 22:18:02 c-6fe471d5 kernel: ip6_conntrack version 0.1 (3839 buckets, 30712 max) - 208 bytes per conntrack
Jan 13 22:18:09 c-6fe471d5 ifup: No configuration found for sit0
Jan 13 22:18:14 c-6fe471d5 sshd[5628]: error: getnameinfo failed
Jan 13 22:18:14 c-6fe471d5 sshd[5628]: error: Bind to port 6669 on 0.0.0.0 failed: Address already in use.
Jan 13 22:18:19 c-6fe471d5 kernel: mtrr: 0xe0000000,0x2000000 overlaps existing 0xe0000000,0x1000000
Jan 13 22:18:21 c-6fe471d5 postfix/master[5922]: fatal: getaddrinfo: Servname not supported for ai_socktype
Jan 13 22:18:29 c-6fe471d5 kernel: SFW2-OUT-ERROR IN= OUT=eth1 SRC=xxx.xxx.xxx.xxx DST=xxx.xxx.xx.xx LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=3$
Jan 13 22:18:32 c-6fe471d5 kernel: SFW2-OUT-ERROR IN= OUT=eth1 SRC=xxx.xxx.xxx.xxx DST=xxx.xxx.xx.xx LEN=48 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=3$
Jan 13 21:19:23 c-6fe471d5 postfix/postqueue[6603]: fatal: Cannot flush mail queue - mail system is down
Jan 13 22:18:44 c-6fe471d5 last message repeated 3 times
Jan 13 22:25:53 c-6fe471d5 xinetd[5823]: Exiting...
Obviously the machine got unreachable after the last entry. As I don't have the knowledge to intepret this log fully, the only thing I can really say for sure is that the firewall had problem passing a packet, and that something happened with the mail system just before it shutdown the inet daemon.

I don't expect anyone here to fully read the log and come up with a defenitive answer on what has gone wrong, but I would gladly appreciate any ideas on how to fix this.

Since this happened, I have removed the postfix component after googling a bit on the subject. The error has not occured since, but the system halted 30 hrs after I put it online, and has only been up 20 hrs after the restart.

System spec's (FTP): SuSE 9.2, firewalled, 512mb ram
 
Old 01-14-2006, 08:06 AM   #2
micxz
Senior Member
 
Registered: Sep 2002
Location: CA
Distribution: openSuSE, Cent OS, Slackware
Posts: 1,131

Rep: Reputation: 75
Jan 13 22:13:47 c-6fe471d5 ifup: No configuration found for sit0
Jan 13 22:13:54 c-6fe471d5 sshd[5627]: error: getnameinfo failed
Jan 13 22:13:54 c-6fe471d5 sshd[5627]: error: Bind to port 6669 on 0.0.0.0 failed: Address already in use.

Looks like you need an IP. Is you network card (sit0) up? That would start this chain of errors.
 
Old 01-14-2006, 08:51 AM   #3
ozric
LQ Newbie
 
Registered: Jan 2005
Location: Örebro, Sweden
Distribution: SUSE 9.2
Posts: 23

Original Poster
Rep: Reputation: 15
Thanks for your reply micxz,

In the FTP box (which went down) I have 2 nic's installed, one for wan and the other at 192.168.0.2 - The NFS server box is at 192.168.0.1.

Both cards on the FTP box are configured, but as eth0 and 1. I wasn't aware of anything called sit(0). Where would I configure this?
 
Old 01-14-2006, 09:26 AM   #4
micxz
Senior Member
 
Registered: Sep 2002
Location: CA
Distribution: openSuSE, Cent OS, Slackware
Posts: 1,131

Rep: Reputation: 75
try the command as root:

Code:
ifconfig
You will see all configured network devices and loopback.
 
Old 01-14-2006, 10:08 AM   #5
ozric
LQ Newbie
 
Registered: Jan 2005
Location: Örebro, Sweden
Distribution: SUSE 9.2
Posts: 23

Original Poster
Rep: Reputation: 15
Quote:
c-6fe471d5:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:BF:E2:63:7D
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::250:bfff:fee2:637d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22186500 errors:0 dropped:0 overruns:0 frame:0
TX packets:27252322 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4040061030 (3852.9 Mb) TX bytes:2858181330 (2725.7 Mb)
Interrupt:10

eth1 Link encap:Ethernet HWaddr 00:50:707:34:61
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:xxx.xxx.xxx.xxx
inet6 addr: fe80::250:70ff:fed7:3461/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29804883 errors:0 dropped:0 overruns:0 frame:0
TX packets:22635449 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2098989451 (2001.7 Mb) TX bytes:1794100291 (1710.9 Mb)
Interrupt:12 Base address:0xec00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:46 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3324 (3.2 Kb) TX bytes:3324 (3.2 Kb)
These two (and only) nic's are configured and shown as "already configured devices" in yast. I don't understand why the logfile refers to a device named sit(0).
 
Old 01-14-2006, 07:04 PM   #6
ozric
LQ Newbie
 
Registered: Jan 2005
Location: Örebro, Sweden
Distribution: SUSE 9.2
Posts: 23

Original Poster
Rep: Reputation: 15
The same problem occured once again, just about exactly after 30 hrs of uptime. I'm grateful for any kind of advice how to solve this matter. It seems strange that the machine worked flawless duing my test-trial of one week, and then suddenly behaves like this.
 
Old 01-14-2006, 07:49 PM   #7
micxz
Senior Member
 
Registered: Sep 2002
Location: CA
Distribution: openSuSE, Cent OS, Slackware
Posts: 1,131

Rep: Reputation: 75
consistantly 30 hrs everytime? There is definately something fishy. I'm not sure what to reply with. If that's the warn log what's messages contain about the crash time?
 
Old 01-14-2006, 07:51 PM   #8
ozric
LQ Newbie
 
Registered: Jan 2005
Location: Örebro, Sweden
Distribution: SUSE 9.2
Posts: 23

Original Poster
Rep: Reputation: 15
I'll be psysically at the box location tomorrow and will paste all the output i can get. Thanks for the support mate.
 
Old 01-17-2006, 04:42 PM   #9
ozric
LQ Newbie
 
Registered: Jan 2005
Location: Örebro, Sweden
Distribution: SUSE 9.2
Posts: 23

Original Poster
Rep: Reputation: 15
Well I have now removed unwanted things such as X server, print service and the power management server, and it now seems to be rolling fine. I don't think I mentioned that the box is running on a Celeron 2GHz with 512 MB ram, and that the system might have been stalled due to lack of resources. I'm not sure that I found the real sollution to the problem, but the server has now been up for about 60 hrs, and no dodgy things appear in the logs.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
firefox just exits bloodiestmarry Linux - Software 6 01-12-2006 11:04 AM
How to make xinetd run at startup on SuSE ??? cwolf78 Linux - Software 2 04-22-2005 05:13 PM
SuSE 9.1 inetd or xinetd ??? cwolf78 Linux - Software 1 04-22-2005 05:10 PM
Postfix not sending mail, exits without error kevlarboxers Linux - Software 0 11-28-2004 02:09 PM
LIRC Exits.... Aeiri Linux - Hardware 0 06-13-2004 07:55 PM


All times are GMT -5. The time now is 04:52 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration