[EP-tech] Apache log getting a lot of errors and Mysql Going away

[Mathieu Perron]

Hi all,

Thank you for your advice.  I have noticed something in my error log.  The "connection abort" errors always happen at the same intervals...

Here's a look at a part of my log:

[Mon Mar 27 13:38:11 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:39:55 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:40:10 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:41:55 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:42:11 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:43:54 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:44:10 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:45:53 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n
[Mon Mar 27 13:46:10 2017] [error] Software caused connection abort at /eprints3/cgi/exportview line 108.\n

There's 2 recurring time gaps (1 min 45 secs then 15 secs then it starts over.)

I'm a little lost where I should look to pinpoint what is causing this...

I looked at my crons jobs and nothing there.

All help is appreciated!

Thank you again!


Mathieu Perron
Chargé de projet informatique et technologique

De : eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] De la part de Matthew Kerwin
Envoyé : 27 mars 2017 07:06
À : eprints-tech at ecs.soton.ac.uk
Objet : Re: [EP-tech] Apache log getting a lot of errors and Mysql Going away


Yeah, for what it's worth we've had a history of these sorts of errors. Eventually I resolved a lot of it by reducing the number of Apache processes and recycling them a little more aggressively.  In our case, it was a choice between: a few failed connects, or a lot of successful connects that don't go anywhere.



Your mileage may vary, of course.



Cheers
--
Matthew Kerwin  |  Senior Web Developer  |  Applications & Development <https://wiki.qut.edu.au/display/lib/Digital+Repository+Team>

________________________________
From: eprints-tech-bounces at ecs.soton.ac.uk<mailto:eprints-tech-bounces at ecs.soton.ac.uk> <eprints-tech-bounces at ecs.soton.ac.uk<mailto:eprints-tech-bounces at ecs.soton.ac.uk>> on behalf of Yuri <yurj at alfa.it<mailto:yurj at alfa.it>>
Sent: 27 March 2017 17:03
To: eprints-tech at ecs.soton.ac.uk<mailto:eprints-tech at ecs.soton.ac.uk>
Subject: Re: [EP-tech] Apache log getting a lot of errors and Mysql Going away

I think it happens when you've a lot of connections on mysql. Rise up
the number of connection in mysql and use some script in a cronjob to
check if mysql has gone away and notify you.

The problem can go even worse when you've a lot of Apache threads and it
eats al the RAM available, you've to rise or lower the apache threads
according to the load.


Il 24/03/2017 19:26, Mathieu Perron ha scritto:
>
> Hi,
>
> We are using ePrints v3.3.13 and lately we have been experiencing some
> crashes due to MySQL going away.  I looked in the Apache log and I see
> a lot of the following errors:
>
> "[error] Software caused connection abort at /eprints3/cgi/exportview
> line 108.\n"
>
> I looked at the cgi script and searched in the files and this script
> has something to do with the Views.pm module.  I can't seem to make
> the error happen on demand and I'm wondering if anyone could help me
> with this.  I don't know if the MySQL server going away is related to
> these errors or not.
>
> Thank you for your time!
>
> *Mathieu Perron*
> Chargé de projet informatique et technologique
>
>
> Service des technologies de l'information
> Université du Québec à Chicoutimi
> 555, boul. de l'Université
> Chicoutimi (Québec) G7H 2B1
>
> *Mathieu_Perron at uqac.ca*<mailto:*Mathieu_Perron at uqac.ca*> <mailto:Mathieu_Perron at uqac.ca>
>
>
>
> *logo uqac* <http://www.uqac.ca/>
>
> Le présent document (y compris les pièces qui y sont annexées, le cas
> échéant) s'adresse au destinataire indiqué et peut contenir des
> renseignements de caractère privé ou confidentiel. Si vous n'êtes pas
> le destinataire de ce document, nous vous signalons qu'il est
> strictement interdit de le diffuser, de le distribuer ou de le
> reproduire. Si ce message vous a été transmis par erreur, veuillez en
> informer l'expéditeur et le supprimer immédiatement. Avant d'imprimer,
> pensez à l'environnement!
>
>
>
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/


*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20170327/2bad36c6/attachment-0001.html