Yes I have.  The problem is we have multiple filesystems and none show Use% 
above 88% and I’m not sure where it’s trying to get temporary space from.



Sue Walker-Thornton
Software Developer/Database Administrator
NASA Langley Research Center|LITES Contract
(757) 224-4074


From: Debashree Pati [mailto:[email protected]]
Sent: Wednesday, April 06, 2011 2:45 PM
To: Thornton, Susan M. (LARC-B702)[LITES]; [email protected]
Subject: RE: [Dspace-tech] FW: [larc-ldr-errors-and-alerts] Langley Digital 
Repository (LDR) Internal Server Error


Have you typed the command to check disk space availability (linux):



df -h



Something like the following will show up:



Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3             7.8G  2.8G  4.6G  38% /
/dev/sda6              20G   15G  3.9G  79% /local
/dev/sda5             3.9G  616M  3.1G  17% /var

See if Use% shows 100% on any dev mount point.



Debashree

________________________________
From: Thornton, Susan M. (LARC-B702)[LITES] [[email protected]]
Sent: Monday, April 04, 2011 11:03 AM
To: [email protected]
Subject: [Dspace-tech] FW: [larc-ldr-errors-and-alerts] Langley Digital 
Repository (LDR) Internal Server Error

Good morning,

I’ve been seeing this error recently in our filter-media cron.  I see it’s 
complaining about space, but I don’t know where the space problem is.  Does 
anyone know where exactly this would be?  I don’t think it’s on /assetstore or 
in our DSpace installation directory.  Is it possible it’s in a temporary 
directory it’s using to filter documents?

Thanks in advance,

Sue Walker-Thornton







Sue Walker-Thornton

Software Developer/Database Administrator

NASA Langley Research Center|LITES Contract

(757) 224-4074





-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of LDR - 
Langley Digital Repository (1.5.1)
Sent: Saturday, April 02, 2011 9:28 PM
To: LDR - Langley Digital Repository Admin (Odyssey)
Subject: [larc-ldr-errors-and-alerts] Langley Digital Repository (LDR) Internal 
Server Error





An internal server error occurred on http://ldr.larc.nasa.gov:



Date......: 4/2/11 9:27 PM

Session ID: java.io.IOException: background merge hit exception: _tye0:c163542 
_tyg9:c73 _tyga:c1 _tygb:c1 _tygc:c1 _tygd:c1 _tyge:c1 into _tygf [optimize]

      at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:1749)

      at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:1689)

      at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:1669)

      at org.dspace.search.DSIndexer.optimizeIndex(DSIndexer.java:498)

      at org.dspace.search.DSIndexer.updateIndex(DSIndexer.java:663)

      at org.dspace.search.DSIndexer.updateIndex(DSIndexer.java:613)

      at 
org.dspace.app.mediafilter.MediaFilterManager.main(MediaFilterManager.java:396)

Caused by: java.io.IOException: No space left on device

      at java.io.RandomAccessFile.writeBytes(Native Method)

      at java.io.RandomAccessFile.write(RandomAccessFile.java:466)

      at 
org.apache.lucene.store.FSDirectory$FSIndexOutput.flushBuffer(FSDirectory.java:599)

      at 
org.apache.lucene.store.BufferedIndexOutput.flushBuffer(BufferedIndexOutput.java:96)

      at 
org.apache.lucene.store.BufferedIndexOutput.flush(BufferedIndexOutput.java:85)

      at 
org.apache.lucene.store.BufferedIndexOutput.writeBytes(BufferedIndexOutput.java:75)

      at org.apache.lucene.store.IndexOutput.writeBytes(IndexOutput.java:40)

      at 
org.apache.lucene.index.CompoundFileWriter.copyFile(CompoundFileWriter.java:216)

      at 
org.apache.lucene.index.CompoundFileWriter.close(CompoundFileWriter.java:173)

      at 
org.apache.lucene.index.SegmentMerger.createCompoundFile(SegmentMerger.java:194)

      at org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3137)

      at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)

      at 
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:240)





{3}



***************

* Exception.: *

***************

{4}





**Note......:  This error occurs due to one or more Java errors/exceptions in 
LDR and

is a "catch-all" for non-specific application errors.  Stack traces should be 
analyzed

to determine likely causes.  In addition, DSpace, PostgreSQL, and server logs 
can be examined

for specific error mesasges that may help with error diagnosis and resolution.





LDR Administration


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to