Virtualise is a good idea.
You avoid the very tricky hardware upgrades.
See: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Upgrading/Hardware
On 12 October 2012 11:57, Sean Carte <[email protected]> wrote:
> On 12 October 2012 11:40, Hilton Gibson <[email protected]> wrote:
> > If it's REAL RAM, then I would suspect faulty RAM.
> > This can happen.
> > Reducing the memory need may bypass the faulty RAM.
>
> My guess was that the server didn't have enough RAM to accommodate
> giving 2GB to tomcat as it's only got 4G in total:
>
> root@ir:~# free
> total used free shared buffers cached
> Mem: 4121136 1438008 2683128 0 24360 269764
> -/+ buffers/cache: 1143884 2977252
> Swap: 5853176 0 5853176
>
> But my collectd graphs seem to dispute that (see attached).
>
> Can RAM go bad? This server has been in daily use since 2008. I
> suppose I'm going to have to prioritise my plans to virtualise it
> elsewhere.
>
> Sean
> --
> Sean Carte
> DUT E-Repository Administrator
> +27 72 898 8775
> +27 31 373 5761
> fax: +27 86 674 1254
> http://ir.dut.ac.za
>
--
*Hilton Gibson*
Systems Administrator
JS Gericke Library
Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
http://library.sun.ac.za
http://scholar.sun.ac.za
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
