Results 1 to 4 of 4
  1. #1
    Join Date
    Jul 2015
    Posts
    3

    Unanswered: Need help with listener-thread: err = -25580: & -25582:

    Hello,

    I have been tasked to help our Application Team with intermittent slowness reported with our EHDS ver 6.1 Informix application. The Database folks continue to provide output from logs (see below example). When this happened about a month or so ago, it was related to ip addresses that the Informix instance could not “verify”, and it takes a while to run this verification. You and others found 1 ip address that was not in the DNS “list” and the application team added it to the .rhosts file. This resolved the problem until now. Can someone tell me why this error is showing up for other clients? I am not seeing any network errors on the wire for these clients. Thank you

    13:17:11 listener-thread: err = -25580: oserr = 104: errstr = : System error occurred in network function.
    14:07:44 listener-thread: err = -25582: oserr = 0: errstr = from 10.57.76.134 to server ifmxlog1_tcp : Network connection is broken.
    14:51:17 listener-thread: err = -25580: oserr = 104: errstr = : System error occurred in network function.
    14:54:15 listener-thread: err = -25580: oserr = 104: errstr = : System error occurred in network function.
    14:54:16 listener-thread: err = -25582: oserr = 0: errstr = from 10.59.225.92 to server ifmxlog1_tcp : Network connection is broken.
    14:55:35 listener-thread: err = -25580: oserr = 104: errstr = : System error occurred in network function.
    14:55:57 listener-thread: err = -25582: oserr = 0: errstr = from 206.24.53.1 to server ifmxlog1_tcp : Network connection is broken.
    15:28:49 listener-thread: err = -25582: oserr = 0: errstr = from 206.24.53.1 to server ifmxlog1_tcp : Network connection is broken.
    15:33:15 listener-thread: err = -25582: oserr = 0: errstr = from 10.59.96.14 to server ifmxlog1_tcp : Network connection is broken.
    15:33:15 listener-thread: err = -25582: oserr = 0: errstr = from 10.59.241.88 to server ifmxlog1_tcp : Network connection is broken.
    15:33:22 listener-thread: err = -25582: oserr = 0: errstr = from 10.59.100.209 to server ifmxlog1_tcp : Network connection is broken.
    15:33:25 listener-thread: err = -25582: oserr = 0: errstr = from 206.24.53.1 to server ifmxlog1_tcp : Network connection is broken.
    15:33:29 listener-thread: err = -25582: oserr = 0: errstr = from 206.24.53.1 to server ifmxlog1_tcp : Network connection is broken.
    15:33:32 listener-thread: err = -25582: oserr = 0: errstr = from 206.24.53.1 to server ifmxlog1_tcp : Network connection is broken.
    15:33:33 listener-thread: err = -25582: oserr = 0: errstr = from 206.24.53.1 to server ifmxlog1_tcp : Network connection is broken.
    15:33:36 listener-thread: err = -25582: oserr = 0: errstr = from 206.24.53.1 to server ifmxlog1_tcp : Network connection is broken.
    20:39:05 listener-thread: err = -25582: oserr = 0: errstr = from mdo08814ag1213m.kih.kmart.com to server ifmxlog1_tcp : Network connection is broken.

  2. #2
    Join Date
    May 2008
    Posts
    19
    Hi,

    can you specify the exact Informix and OS versions?
    Old
    Error 104 means: ISAM error: too many files open.

    Some older versions required Linux to raise the system limits.
    Please check
    ulimit -n
    and verify that it is set to the value specified in the Machine Specific Notes in $INFORMIXDIR/release/en_us/0333/*machine_notes*, if applicable

  3. #3
    Join Date
    Jul 2015
    Posts
    3

    follow-up

    I believe the Informix database version is 12.10. I'm not that familar with the database but, from what folks are telling me is that these oserr=104 (which I thought were connections reset by peer) are happening when the database tries to do a dns query against an IP address that is NATed. They put the IP in the rhosts file so it wouldn't use DNS but it's still occurring. They are trying something with one of the two userid's used by the clients to resolve this issues as well (not sure what that is). All I know is that the query by the server holds up several other queries behind it which prevent others from connecting and eventually timing out. I know the server was recently migrated to a VM host but, the problems still surfaced when it was running on a standalone AIX box. Thx

  4. #4
    Join Date
    Jul 2015
    Posts
    3

    temp fix

    We added a reverse lookup for one of the IP's that is NAT'ed and now we get a DNS error but, the good news is that the DNS query releases automatically when the error occurrs allowing other Clients to access the database without delays. Any info on how this is possible would be appreciated. Thx

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •