EPrints Technical Mailing List Archive

Message: #07781

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] ePrints server is freezing very often

Hi Francis,
I think the MariaDB errors might not be connected Ted to the EPrint exportview errors.

First, the MariaDB errors - this might be useful:
https://serverfault.com/questions/393862/mysql-warning-ip-address-could-not-be-resolved

Adjusting the MariaDB configuration and/or firewall setting on your server should help.

For the exportview errors, this can be a result of someone (or some machine) making a request, but not waiting for a response. This can happen because the export views can take a bit of time to generate. If they take too long, a browser might timeout - and the user might try again - increasing load on the server.

If possible, try and match up the entries in the Apache error log with entries in the Apache access log. You may be able to see the parameters that are being requested - and then be able to recreate the issue.

It may be that the exportview request contains many EPrints, with lots of authors (e.g. some physics papers might have thousands of authors), which will take time to generate.
If we can understand exactly what causes the slow response, we may be able to fix it!

There may even be robots visiting your repository that aren't behaving nicely - which you could block with firewall rules.

I hope some of that helps!
Cheers,
John
From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of Francis Jayakanth via Eprints-tech <eprints-tech@ecs.soton.ac.uk>
Sent: 05 April 2019 19:09:21
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] ePrints server is freezing very often
 
Hi Everyone, In the recent past, our eprints server,
eprints.iisc.ac.in, in becoming unresponsive very frequently - i would
say, once every 30 minutes. Restarting the httpd server brings back
the server, but in less than 30 minutes it freezes again! I had a look
at the httpd error log file, and was surprised to see that the log
file is full of entries similar to the ones indicated below:

[Fri Apr 05 22:44:43.717856 2019] [:error] [pid 114613] :Apache2 IO
write: (32) Broken pipe at /opt/eprints3/cgi/exportview line 108
[Fri Apr 05 22:44:52.392811 2019] [:error] [pid 114910] :Apache2 IO
write: (32) Broken pipe at /opt/eprints3/cgi/exportview line 108
[Fri Apr 05 22:44:58.314788 2019] [:error] [pid 114919] :Apache2 IO
write: (32) Broken pipe at /opt/eprints3/cgi/exportview line 108

I also had a look at the Mariadb log file, which is bombarded with
entries indicated below:

190405 23:23:59 [Warning] IP address '104.236.158.58' could not be
resolved: Name or service not known
190405 23:24:54 [Warning] IP address '104.248.56.116' could not be
resolved: Name or service not known
190405 23:25:25 [Warning] IP address '180.250.18.136' could not be
resolved: Name or service not known
190405 23:26:31 [Warning] IP address '157.230.33.59' could not be
resolved: Name or service not known
190405 23:26:59 [Warning] IP address '104.236.248.209' could not be
resolved: Name or service not known

All the IPs listed in the Mariadb log file have their origins in
China, South Korea, and other places.

Can someone help me to resolve the issue, please?.

We are running, eprints version: 3.3.15 eps on CentOS Linux release
7.4.1708 (Core)

Thanks and regards, Francis
*** 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/