Hello All,

Actually, We have a problem in our server (RHEL 7.1), 1st server is used for payment apps like switch card payment (passthru only), and 2nd server is used for Database transaction.
When high transaction there is different connection between Apps Server and DB server, Apps Server sends connection to DB Server, but sometimes that’s connection not ESTABLISHED like low traffic (I checked thru netstat in 2 servers). I have changed value Local_port range, and fin_timeout but it wasn’t solve this problem, and I think my current kernel needs to update kernel to latest or stable version to solve this.
current kernel : 3.10.0-229.e17.x86_64

Please give me suggest about our this connection problem.

Thank you
Regards

Thoughts:
#1 why have you not asked RHEL support about how to address this issue?

#2 Why do you suspect the kernel is somehow to blame? Have you evidence to suggest this may be the case?

#3 what is the nature of your connection? ODBC is notorious for connection inefficiencies in some combinations of database, client, OS, and networking environment.

#4 have you considered a network/hardware solution? What other traffic is on this network? If this connection on line dedicated to this connection?

#5 in my experience, the database itself is often the bottleneck. What is the nature or base of your database?

Hi Wpeckham,

Thanks for your reply.
Currently my subscription was expired, and I'm still processing to renewal, that's why I created to this forum.

Actually I don't understand about bottleneck, and this connection through firewall.
Like this : Firewall >> Apps Server >> firewall >> DB server.

This connection just like payment switch passthru. And another network engineer is still checking from his environments as well. And I should to make sure from server has no bug or problem.

And my colleague suggests to check kernel OS. But I don't know exactly this problem.

Did you ever get issue like this connection before?

Thanks. Appreciate your response.
Regards

I understand, but until you are licensed and registerd as licensed with the RHN you will not be able to update the kernel properly. Once you can, I recommend bringing ALL of your packages current, including the kernel.
Well this tells us a LOT that you left out earlier. There is a (still undefined) database involved, that we connect to with a (still undefined) connection protocol through (If I understand correctly) at least one and possibly two firewalls.

Question, is this over controlled wire or over the internet? If part of your connection depends upon public carriers that brings in a TON of additional possible factors!
This description tells me almost nothing. There must be around 700 different kinds of payment switch pass through techniques in the history of IT.Excellent. I am glad he is checking the network devices. A good network diagnostic run when the problem exhibits might be very instructive even if the network is not implicated.
Neither does he, thus the shotgun approach of "check everything", which I do approve of by the way.

Did this problem come up when you are first establishing this system, or has this been around for some time and only started having this problem recently? Our approach in the two cases should be quite different.

I do hope that neither application nor kernel version issues are involved, since resolving those properly cannot be properly and legally addressed until your registration is current. That should not take long, but please keep us informed.


Only dozens of times and involving a dozen kinds of network configuration, perhaps a dozen database engines, MANY kinds of database client applications or code, and many kinds of servers. Your original description of the problem was so generic it could have been almost anything.
I think we are slowely drilling down to enough detail to define the problem, and that is the first requirement to investigation.
IT has rarely been the OS at fault as long as the DB was not hosted on Windows.

You are very welcome. I am only surprised that several other good people here have not added their $0.02 USD by now, as we have some VERY good people around.

Hi wpeckham,

Thanks for your explanation.
And so far you tell me about this, we're still checking network peripheral.
Maybe we will change topology, and make P2P method between Apps Server to DB server, because we suspect in Fortinet network miss config.

Once again, thanks for your suggested.

Thank you
Regards,
I Made Dwi