Slow Initial Connection Start up

[Bill Rambo]

We are experiencing an issue with our Cloverleaf Interface engine when we start a connection. It takes 4 to 5 minutes for the connection to go to an UP status. This happens on ALL connections across all sites.

Here is the messages i see in the log file:

[cmd :cmd :INFO/0: imo_xp_1_cmd:12/26/2012 13:29:19] Doing ‘pstart’ command on ‘imo_xp_1_raw’

[prod:prod:INFO/0: imo_xp_1_raw:12/26/2012 13:33:21] Applying EO config: ”

[icl :tcpi:ERR /0: imo_xp_1_cmd:12/26/2012 13:33:21] write failed: Broken pipe

[cmd :cmd :INFO/0: imo_xp_1_cmd:12/26/2012 13:33:21] Inrecoverable socket error.  Closing connection.

[cmd :cmd :INFO/0: imo_xp_1_cmd:12/26/2012 13:33:21] Receiving a command

[icl :tcpi:ERR /0: imo_xp_1_cmd:12/26/2012 13:33:21] write failed: Broken pipe

[cmd :cmd :INFO/0: imo_xp_1_cmd:12/26/2012 13:33:21] Since there are some error had occured while attempted to send an Ack back to client

[cmd :cmd :INFO/0: imo_xp_1_cmd:12/26/2012 13:33:21] We try to process the command anyway but no further Ack will be send back to Client

Cloverleaf ver 5.6 rel 2

OS  Linux 2.6.18-128

Bill Rambo

Self Regional Healthcare

Greenwood, SC

864-725-4732

Topic

[Peter Heggie]

Just some rough ideas; I’ve tried to get Linux working on a home PC, and a little knowledge is a dangerous thing..

1) Has this ever worked correctly or at least better in this environment / os release / patch level , Cloverleaf release / patch level?

2) If this behavior is consistent across all connections and sites, perhaps something has changed at the network level – have there been any changes to any software modules or configuration related to networking / ip / hostnames?

3) Is DNS or the equivalent functionality on Linux configured correctly? please forgive my incomplete knowledge, but could this be one of those problems relating to a timeout looking for a network definition?

4) is the Local Binding Addres correct and recognized by the network configuration?

Peter Heggie

[Bill Rambo]

Answer to your questions:

1) Has this ever worked correctly or at least better in this environment / os release / patch level , Cloverleaf release / patch level?  YES. It has been working correctly for years

2) If this behavior is consistent across all connections and sites, perhaps something has changed at the network level – have there been any changes to any software modules or configuration related to networking / ip / hostnames?  YES. All sites have the same issue with connectivity.

3) Is DNS or the equivalent functionality on Linux configured correctly? please forgive my incomplete knowledge, but could this be one of those problems relating to a timeout looking for a network definition? That is what i am having our network team looking into if i can get them to do it.

4) is the Local Binding Addres correct and recognized by the network configuration?  Not sure.

[Michael Hertel]

How many messages are in your recovery database?

[Bill Rambo]

Less than 100 total across ALL 7 sites.

[Ed Mastascusa]

I recollect we had a similar problem (3.8-5.5 on AIX) where the cause was the host server. As a result we always kill our host server on our prod box unless we need it running in order to use the GUI. maybe stop/start that (hciss -k h) and see what happens.

if you search for “inrecoverable socket error” there are different ways that the monitor daemons can get slowed down (i.e. 10s of thousands of messages in the recovery DB) and there are a reasonable number of posts on this topic.

[Michael Hertel]

I found this old post: https://usspvlclovertch2.infor.com/viewtopic.php?t=5232&highlight=slow+start

Maybe you can see if Jeff ever solved it. It was for CL5.6 and Linux just like your set up.

FWIW- I seem to remember having this problem a while back and it was related to DNS, but I’m on AIX.

Good luck

[Michael Hertel]

I have an idea. Try doing an nslookup on one of your interface host names from a command prompt and see how long it takes for the information to come back to you. Then check your dns server search order to see if the first server is still in operation.

[Bill Rambo]

When I do a nslookup, the response is immediate.  I get the server name of the IP I entered in the nslookup command. There is no delay.

[Author]

Replies