Re: [RDD] Slow Start trigger

[Stan Fotinos]

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 are all setup exactly the same nfs etc...

Only one of the four clients if it is left unused for approx 15 minutes or
more, when you press start to play a cart it takes up to 3 seconds to start
the cart. After the first start it works perfectly, triggering instantly.


Couple of ideas, in no particular order:

* Audio storage location (NFS server) hard drive spin-down (power
saving in BIOS) enabled?  Might it be that the other three clients
would exhibit the same behavior if no client were doing anything for
15 minutes too?
As far as I can see no power saving setting are enabled in the BIOS, no 
other client behaves this way after 15 minutes.


* SELinux settings different on various machines?

  New installations of CentOS come with SELinux enabled by default, but
I don't recall if Rivendell Appliance CentOS has it disabled or not
I cant see this enabled in Centos Appliance and I have turn all firewall 
stuff off.


* 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 can show me what is happening...


* Check system logs for NFS timeout errors -- on both ends of the wire

* Check caed logs for errors, etc.

Will look into these too.



You might try to capture some snippets of logs from different systems
when you replicate the same steps on each, and just pore through them
for any differences.
Good idea thank you, I hope to get to the bottom of this and I will post 
my solution.


--Sherrod


Thank you

Stan

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev



___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Slow Start trigger

[Stan Fotinos]

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 file


 All of what he said

 Certain apps, notably Talk and MySQL are brain-dead when it comes to
 addressing localhost.
 As well documented on this very list over many years, the IP 127.0.0.1
 is problematic. Why that one only out of the entire 127.x.x.x block,
 who knows ?
 Since the entire 127.x.x.x block refers to localhost and the lo network
 interface, it therefore is prudent to use any 127.x.x.x EXCEPT 127.0.0.1
 when referring to the local machine.
 Typically, I use 127.0.0.2 but 127.234.145.178 would work just as well.



___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Slow Start trigger

[Cowboy]

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 can show me what is happening...


 Wireshark has some features, but the program tcpdump is typically part
 of any *nix worth a d%$# out there, including MacOS and about every
 OS running on Linux that I've played with.

 You wouldn't need to dump both ends of the wire that way, as tcpdump
 will/can ( depending on command options ) show you everything on that
 wire, regardless of origination, destination, formatting, etc.
 Typically, it'll show you way more than you ever wanted.

--
Cowboy

http://cowboy.cwf1.com

Don't abandon hope: your Tom Mix decoder ring arrives tomorrow.
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Slow Start trigger

[Cowboy]

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 Talk and MySQL are brain-dead when it comes to
 addressing localhost.
 As well documented on this very list over many years, the IP 127.0.0.1
 is problematic. Why that one only out of the entire 127.x.x.x block,
 who knows ?
 Since the entire 127.x.x.x block refers to localhost and the lo network
 interface, it therefore is prudent to use any 127.x.x.x EXCEPT 127.0.0.1
 when referring to the local machine.
 Typically, I use 127.0.0.2 but 127.234.145.178 would work just as well.

--
Cowboy

http://cowboy.cwf1.com

Sooner or later you must pay for your sins.  (Those who have already
paid may disregard this fortune).
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Slow Start trigger

[Lorne Tyndale]

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're pointing to the IP address
of your Mysql server, don't use the DNS name.  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

Also I find it helpful to make sure the machine names and (static) IP
addresses are properly listed in the /etc/hosts file

Don't use DHCP for your Rivendell workstations - you'll just be inviting
problems.

Double check things like power saving options, hard disk spin down
options, screen savers, etc - anything that might start up after 15
minutes, and turn them off.  

If you happen to have one of those "green" drives in that computer, that
might be part of the problem.  I gave up with those several years back
because they seem to like to randomly spin down at the most
inappropriate times in the name of saving a miniscule amount of
electricity (or something like that).  The 3 to 5 second pause they took
to spin back up was enough make me replace them all.

Of course as also mentioned, check things like your network cable, etc.

Lorne Tyndale


> 
> 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 more, when you press start to play a cart it takes up to 3 seconds to 
> start the cart. After the first start it works perfectly, triggering 
> instantly.
> 
> I have change check the nfs mount settings, changed the network cable, 
> rebuilt the OS and changed the hard drive, still the same result.
> 
> Has anyone come across this before or does any have any ideas where to 
> look next?
> 
> Kind Regards
> 
> Stan
> 
> ___
> Rivendell-dev mailing list
> Rivendell-dev@lists.rivendellaudio.org
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Slow Start trigger

[Sherrod Munday]

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 clients if it is left unused for approx 15 minutes or
> more, when you press start to play a cart it takes up to 3 seconds to start
> the cart. After the first start it works perfectly, triggering instantly.


Couple of ideas, in no particular order:

* Audio storage location (NFS server) hard drive spin-down (power
saving in BIOS) enabled?  Might it be that the other three clients
would exhibit the same behavior if no client were doing anything for
15 minutes too?

* SELinux settings different on various machines?

 New installations of CentOS come with SELinux enabled by default, but
I don't recall if Rivendell Appliance CentOS has it disabled or not

* 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

* Check system logs for NFS timeout errors -- on both ends of the wire

* Check caed logs for errors, etc.


You might try to capture some snippets of logs from different systems
when you replicate the same steps on each, and just pore through them
for any differences.

--Sherrod
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Slow Start trigger

[Stan Fotinos]

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 more, when you press start to play a cart it takes up to 3 seconds to 
start the cart. After the first start it works perfectly, triggering 
instantly.


I have change check the nfs mount settings, changed the network cable, 
rebuilt the OS and changed the hard drive, still the same result.


Has anyone come across this before or does any have any ideas where to 
look next?


Kind Regards

Stan

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev