Dear all, I'm trying to find the cause for why my DSpace crashed last Thursday when I ran "filter-media" command.
(I always run "index-discovery -b" before running "filter-media") This morning when I looked at the dspace.log file I saw following errors: 2017-08-24 12:59:15,016 ERROR org.dspace.discovery.SolrServiceImpl @ Error while writing item to discovery index: 2900/617 message:Expected mime type application/octet-stream but got application/xml. <?xml version="1.0" encoding="UTF-8"?> <response> <lst name="error"><str name="msg">Processing of multipart/form-data request failed. /var/cache/tomcat/temp/upload_64764935_15d611d7cd8__7fff _00051158.tmp (No space left on device)</str><str name="trace">org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processin g of multipart/form-data request failed. /var/cache/tomcat/temp/upload_64764935_15d611d7cd8__7fff_00051158.tmp (No space left on device) I don't know whether it's "index-discovery" caused the above error, or "filter-media" did it? I noticed that the "No space left on device" message on /var/cache/tomcat/temp... Then when I did "df -k", I saw: /dev/mapper/sys_vg-VAR01 4184064 4182476 1588 100% /var At this moment my guess for the reason of failed "filter-media" process or "index-discovery -b" process is that the /var device is full. My question is: Should I delete the content of /var/cache/tomcat/temp/ to make more space on /var? Is it safe to do that? the /var/cache/tomcat/temp/ contains a bunch of folders like the following: ... drwxr-xr-x 2 dspace dspace 4.0K Aug 24 13:19 ehcache_auto_created_1503595149877 drwxr-xr-x 2 dspace dspace 4.0K Aug 24 13:19 ehcache_auto_created_1503595150125 drwxr-xr-x 2 dspace dspace 4.0K Aug 24 13:19 ehcache_auto_created_1503595184821 drwxr-xr-x 2 dspace dspace 4.0K Aug 24 13:19 ehcache_auto_created_1503595185332 drwxr-xr-x 2 dspace dspace 4.0K Aug 24 13:19 ehcache_auto_created_1503595186445 drwxrwx--- 94 dspace dspace 8.0K Aug 24 13:19 . drwxr-xr-x 2 dspace dspace 4.0K Aug 24 13:19 ehcache_auto_created_1503595186623 However, when I took a peek inside the above folders, I only saw several zero size files: -rw-r--r-- 1 dspace dspace 0 Aug 24 13:19 org.hibernate.cache.spi.UpdateTimestampsCache.data -rw-r--r-- 1 dspace dspace 0 Aug 24 13:19 org.hibernate.cache.internal.StandardQueryCache.data -rw-r--r-- 1 dspace dspace 0 Aug 24 13:19 org.dspace.content.MetadataSchema.data -rw-r--r-- 1 dspace dspace 0 Aug 24 13:19 org.dspace.content.MetadataField.data So I'm not sure that deleting all ehcache_auto_created_ folders will make more space for /var. Any advice will be greatly appreciated! Yongming On Thu, Aug 24, 2017 at 3:55 PM, Wang, Yongming <[email protected]> wrote: > Dear all, > > We are on DSpace 6.0 (RHEL) and it's a new installation. We are about to > launch it in a couple of weeks. > > Today when I ran the ./dspace filter-media command, I got the following > error after it ran for a while, and the DSpace crashed after the error > occurred. > > "ERROR filtering, skipping bitstream: > > Item Handle: 2900/1283" > > I ran multiple times, and each time the Item Handle is different. > > I've increased the DSpace command line java memory to 1024 M in the > /dspace/bin/dspace file. My java heap memory is 4G. > > What could be the cause for this error? Did this error cause the crash? > How can I troubleshoot it? > > > Thanks so much in advance for any help! > > > > Yongming > > -- > Yongming Wang > Systems Librarian/Associate Professor > The College of New Jersey > tel: 609-771-3337 <(609)%20771-3337> > email: [email protected] > -- Yongming Wang Systems Librarian/Associate Professor The College of New Jersey tel: 609-771-3337 email: [email protected] -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
