Hi all
I have a strange problem I am hoping someone has come across before. I
have 4 clients and one server all running Centos 6 Rivendell appliance
with all the updates. They are all setup exactly the same nfs etc...
Only one of the four clients if it is left unused for approx 15 minutes
or
On Mon, Nov 9, 2015 at 6:48 AM, Stan Fotinos wrote:
> I have a strange problem I am hoping someone has come across before. I have
> 4 clients and one server all running Centos 6 Rivendell appliance with all
> the updates. They are all setup exactly the same nfs etc...
>
> Only one of the four clie
Hi,
A few things.
First, in your Mysql configuration file (my.cnf) for the Mysql server
make sure you've turned off the DNS lookup of clients. I've seen this
cause pauses and slowdowns.
[mysqld]
# Skip reverse DNS lookup of clients
skip-name-resolve
Second, in the rd.conf file make sure you
On 11/09/2015 11:10 PM, Lorne Tyndale wrote:
Also if you are just
using a locally installed MySQL (stand alone machine) then don't point
to 127.0.0.1 - this can cause problems. Use a static IP address and
point to that IP in your rd.conf file
All of what he said
Certain apps, notably
Hi Sherrod
Answers bellow:
On 10/11/2015 2:18 am, Sherrod Munday wrote:
On Mon, Nov 9, 2015 at 6:48 AM, Stan Fotinos wrote:
I have a strange problem I am hoping someone has come across before. I have
4 clients and one server all running Centos 6 Rivendell appliance with all
the updates. They
Hi Lorne
Answers bellow:
On 10/11/2015 12:10 pm, Lorne Tyndale wrote:
Hi,
A few things.
First, in your Mysql configuration file (my.cnf) for the Mysql server
make sure you've turned off the DNS lookup of clients. I've seen this
cause pauses and slowdowns.
[mysqld]
# Skip reverse DNS lookup
Thanks Cowboy
On 10/11/2015 8:56 pm, Cowboy wrote:
On 11/09/2015 11:10 PM, Lorne Tyndale wrote:
Also if you are just
using a locally installed MySQL (stand alone machine) then don't point
to 127.0.0.1 - this can cause problems. Use a static IP address and
point to that IP in your rd.conf fil
On 11/18/2015 06:46 AM, Stan Fotinos wrote:
* Wireshark traffic (a.k.a. packet capture) (on both ends of the wire)
various systems looking for responsiveness/delay in the transport/IP
layer (2/3), the TCP layer (4), or the OS/Rivendell client (7) layer
Working on this at the moment, I hope this
