AIX 5.2 - problem after ML_01 applied

From: Marrek (ogniemi_at_poczta.onet.pl)
Date: 08/28/03 

Date: Thu, 28 Aug 2003 20:10:50 +0200

Hello,
I have a daemon listening on port tcp/2234. Before I upgraded aix 5.2 with
ML_01 it worked properly, but now when ML_01 is installed I get following
errors in daemon log:

somedaemon[33810]: Thu Aug 28 15:12:03 2003: TcpRead() failed: Interrupted
system call
somedaemon[33810]: Thu Aug 28 15:12:03 2003: TcpRead() failed: Not enough
space

I run "tcpdump" and it is the result of the connection to port 2234
(connection failed).
Could anyone please help to analyze the tcpdump output concerning connection
to the daemon:

15:09:47.168772784 10.10.30.12.2234 > 10.10.30.12.35303: S
3412943795:3412943795(0) ack 3637203492 win 16384 <mss 16856>
15:09:47.168788566 10.10.30.12.35303 > 10.10.30.12.2234: . ack 1 win 16384
15:09:47.169668988 10.10.30.12.35303 > 10.10.30.12.2234: P 1:5(4) ack 1 win
16384
15:09:47.193646275 10.10.30.12.2234 > 10.10.30.12.35303: . ack 5 win 16384
15:09:47.193657941 10.10.30.12.35303 > 10.10.30.12.2234: P 5:82(77) ack 1
win 16384
15:09:47.337483330 10.10.30.12.2234 > 10.10.30.12.35303: P 1:3(2) ack 82 win
16384
15:09:47.337657875 10.10.30.12.2234 > 10.10.30.12.35303: FP 3:5(2) ack 82
win 16384
15:09:47.337671453 10.10.30.12.35303 > 10.10.30.12.2234: . ack 6 win 16382
15:09:47.337722501 10.10.30.12.35303 > 10.10.30.12.2234: F 82:82(0) ack 6
win 16384
15:09:47.337737650 10.10.30.12.2234 > 10.10.30.12.35303: . ack 83 win 16384
15:09:47.343122770 10.10.30.12.35304 > 10.10.30.12.2234: S
1223508187:1223508187(0) win 16384 <mss 16856>
15:09:47.343157286 10.10.30.12.2234 > 10.10.30.12.35304: S
522667328:522667328(0) ack 1223508188 win 16384 <mss 16856>
15:09:47.343172399 10.10.30.12.35304 > 10.10.30.12.2234: . ack 1 win 16384
15:09:47.344005839 10.10.30.12.35304 > 10.10.30.12.2234: P 1:5(4) ack 1 win
16384
15:09:47.393670806 10.10.30.12.2234 > 10.10.30.12.35304: . ack 5 win 16384
15:09:47.393686864 10.10.30.12.35304 > 10.10.30.12.2234: P 5:204(199) ack 1
win 16384
15:09:47.393892901 10.10.30.12.2234 > 10.10.30.12.35304: F 1:1(0) ack 204
win 16384
15:09:47.393908697 10.10.30.12.35304 > 10.10.30.12.2234: . ack 2 win 16384

Relevant Pages

  • Re: Lightweight alternative MTA? [was: Re: Starting MTA:]
    ... listening daemon but nice to have queue daemon. ... exim works as both MTA and MDA depending on how it is used. ... rather fetchmail failed since there was no connection on port 25. ...
    (Debian-User)
  • Re: single daemon startup
    ... data for the connection on each end, ... on a particular port, it's getting the SAME daemon, not round-robin ... refer to the same machine. ... to the same port with the same IP address. ...
    (comp.unix.programmer)
  • Re: need a linux script
    ... what Jan's saying is that the problem is definitely with inetd; ... In the old days, before inetd, each port that accepted incoming ... but each daemon had to run just in case somebody tried to ... entries in /etc/inetd.conf), starts it, and passes the connection on. ...
    (alt.os.linux.suse)
  • Re: ssh_init: Network error: Connection refused
    ... > Is that the SSH server or is there a daemon missing? ... but it may not be the daemon -- they could be just left ... try connecting to port 22 from the same machine (e.g. ... otherwise you'd get a timeout instead of "connection refused"). ...
    (comp.security.ssh)
  • Re: monitoring traffic on a port?
    ... > application or daemon that's listening to the port. ... > You could also start looking at external network monitoring hardware to ...
    (comp.sys.sun.misc)