2012/6/13 Johan De Meersman <vegiv...@tuxera.be> > > ----- Original Message ----- > > From: "Claudio Nanni" <claudio.na...@gmail.com> > > > > @Johan, you say "I'm having trouble with clients aborting, but for > > some reason they don't get logged." > > Ah, it *did* start logging, now, and they come from multiple applications, > too. > > 120612 12:19:09 [Warning] Aborted connection 13019149 to db: 'music' user: > 'music' host: 'viaprod1' (Got an error reading communication packets) > 120612 13:13:52 [Warning] Aborted connection 13020111 to db: 'epg' user: > 'epg' host: 'viaprod1' (Got timeout reading communication packets) > 120612 14:21:10 [Warning] Aborted connection 13021624 to db: 'music' user: > 'music' host: 'viaprod1' (Got an error reading communication packets) > > Am I wrong in thinking this looks more like a hardware/network problem? > > > Not at all. Just to close completely the code 'option', are you sure the codebase is completely different? since they still come from the same host. In this way so we can totally exclude code 'bad' habit.
Then network can be a problem for sure, usually when there are firewalls in between, also when I had similar problems a network change took place, like changing switches or some configuration. Can you count the hops between MySQL and the app server? Dank Je Wel ;) Claudio > -- > Bier met grenadyn > Is als mosterd by den wyn > Sy die't drinkt, is eene kwezel > Hy die't drinkt, is ras een ezel > -- Claudio
