EPrints Technical Mailing List Archive

Message: #08201

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

Re: [EP-tech] Error cannot allocate memory

Sorry for the double email.
 To debug, use free and the apache utility "ab" (with cookies for a logged user test) to see how much load your server can handle.
 In my experience, a small/medium eprints installation need 8GB of RAM and a good disk speed. 

Il 16/06/20 10:10, Budiwijaya via Eprints-tech ha scritto:

Hi Lists,

Our repository sometimes having this error on the browser:

*"Error calling df: Cannot allocate memory"*

And checking on the log of the apache, I got this:
================
[Tue Jun 16 03:58:30.265596 2020] [:error] [pid 6987:tid 139987773269760] Apache2::RequestIO::read: (70008) Partial results are valid but processing is incomplete at 
 (eval 685) line 5
------------------------------------------------------------------
---------------- EPrints System Error ----------------------------
------------------------------------------------------------------
Error calling df: Cannot allocate memory
------------------------------------------------------------------
 at /opt/eprints3/perl_lib/EPrints/System.pm line 349.
EPrints::System::free_space('EPrints::System::linux=HASH(0x559787596f18)', '/opt/eprints3/archives/wiraraja/documents/disk0') called at /opt/eprints3/perl_li 
b/EPrints/BackCompatibility.pm line 467
EPrints::Platform::free_space('/opt/eprints3/archives/wiraraja/documents/disk0') called at /opt/eprints3/perl_lib/EPrints/Repository.pm line 1851 EPrints::Repository::get_store_dir('EPrints::Repository=HASH(0x5597864b7c78)') called at /opt/eprints3/perl_lib/EPrints/DataObj/EPrint.pm line 597 EPrints::DataObj::EPrint::get_defaults('EPrints::DataObj::EPrint', 'EPrints::Repository=HASH(0x5597864b7c78)', 'HASH(0x5597831a9800)', 'EPrints::DataSet=HASH (0x55978814e1b0)') called at /opt/eprints3/perl_lib/EPrints/DataObj.pm line 259 EPrints::DataObj::create_from_data('EPrints::DataObj::EPrint', 'EPrints::Repository=HASH(0x5597864b7c78)', 'HASH(0x559783197000)', 'EPrints::DataSet=HASH(0x5 5978814e1b0)') called at /opt/eprints3/perl_lib/EPrints/DataObj/EPrint.pm line 495 EPrints::DataObj::EPrint::create_from_data('EPrints::DataObj::EPrint', 'EPrints::Repository=HASH(0x5597864b7c78)', 'HASH(0x559783197000)', 'EPrints::DataSet= HASH(0x55978814e1b0)') called at /opt/eprints3/perl_lib/EPrints/DataSet.pm line 1013 EPrints::DataSet::create_dataobj('EPrints::DataSet=HASH(0x55978814e1b0)', 'HASH(0x559783197000)') called at /opt/eprints3/perl_lib/EPrints/DataSet.pm line 10 
07
EPrints::DataSet::create_object('EPrints::DataSet=HASH(0x55978814e1b0)', 'EPrints::Repository=HASH(0x5597864b7c78)', 'HASH(0x559783197000)') called at /opt/e 
prints3/perl_lib/EPrints/Plugin/Screen/NewEPrint.pm line 50
EPrints::Plugin::Screen::NewEPrint::action_create('EPrints::Plugin::Screen::NewEPrint=HASH(0x559788872308)') called at /opt/eprints3/perl_lib/EPrints/Plugin/ 
Screen.pm line 240
EPrints::Plugin::Screen::from('EPrints::Plugin::Screen::NewEPrint=HASH(0x559788872308)') called at /opt/eprints3/perl_lib/EPrints/ScreenProcessor.pm line 310 EPrints::ScreenProcessor::process('EPrints::ScreenProcessor', 'session', 'EPrints::Repository=HASH(0x5597864b7c78)', 'template', undef, 'url', '/cgi/users/ho 
me') called at /opt/eprints3/cgi/users/home line 25
ModPerl::ROOT::ModPerl::Registry::opt_eprints3_cgi_users_home::handler('Apache2::RequestRec=SCALAR(0x5597832db168)') called at /usr/lib/perl5/ModPerl/Registr 
yCooker.pm line 206
        eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 206 ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x559783196fd0)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 172 ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x559783196fd0)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31         ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x5597832db168)') called at -e line 0 
        eval {...} called at -e line 0
================
At the time of the error, tried to `df` using cli of eprints user, can give the disk free of the linux. Is there any way to debug more? Or the solution is just throw more RAM on the VM? 

Eprints version: 3.3.15
OS: Linux Ubuntu 14.04
RAM: 1GB

Cheers,
Budiwijaya

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C185d1dedaba641dd8d1808d811e6c2a2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=rFyGGp2kA60VwG4tyt0cKas9WpWWqmozFZ5yYNMfMuA%3D&amp;reserved=0
*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&amp;data=01%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7C185d1dedaba641dd8d1808d811e6c2a2%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&amp;sdata=C6HqARqJ7LRCHfKdDCkqDGVUCxeqOIsmLeLwCFCAQwY%3D&amp;reserved=0