Awesome, thanks so much!

Deborah

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of helix84
Sent: Monday, 31 October 2016 10:30 p.m.
To: Fitchett, Deborah <[email protected]>
Cc: DSpace Technical Support <[email protected]>
Subject: Re: [dspace-tech] DSpace.log error message extravaganza

On Mon, Oct 31, 2016 at 1:29 AM, Fitchett, Deborah 
<[email protected]> wrote:
> 1.       “ERROR
> org.dspace.app.xmlui.cocoon.servlet.multipart.DSpaceMultipartFilter @ 
> Problem in multipart filter. Unable to create request” – we get a few 
> dozen of these some minutes after restarting the server

This one is harmless. It just says that a client request was interrupted due to 
the server restart. The next request should succeed.


> 2.       “ERROR org.dspace.core.PluginManager @ Name collision in named
> plugin, implementation 
> class="org.dspace.content.crosswalk.AIPDIMCrosswalk",
> name="DIM"” – about 160 of these, for various crosswalks and name 
> variations with some apparent repetition, shortly after the multipart 
> filter errors ie also on server restart

I've been getting those, too. Couldn't figure out why. But they seem harmless.


> 3.       “ERROR org.dspace.core.I18nUtil @ No language specified for EPerson
> #” – associated with the [dspace]/bin/dspace sub-daily job. I’m 
> presuming it’s what it says on the box: the eperson who’s subscribed 
> to something hasn’t specified a language and i18n is complaining about 
> it. Presumably also i18n then just sends them English by default 
> anyway, but is there a way we can actually go in somewhere and specify 
> ‘en’ just to keep this out of our logs? I can’t even see where this might be 
> stored in the database.

Until DSpace 4, you could specify language in the eperson table. Since DSpace 
5, most eperson attributes have moved into the metadatavalue table ("eperson" 
schema, element='language', qualifier = NULL). I wrote up an explanation of 
this change and how to access the
attributes:

https://wiki.duraspace.org/display/DSPACE/Metadata+for+all+DSpace+objects


> 4.       “ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL query
> updateQuery Error -
> org.postgresql.util.PSQLException: ERROR: update or delete on table 
> "bitstream" violates foreign key constraint 
> "bundle_primary_bitstream_id_fkey" on table "bundle"
>   Detail: Key (bitstream_id)=(#) is still referenced from table "bundle".”
> [followed by a SQL deleteByValue Error, a SQL delete Error, and a 
> “FATAL org.dspace.storage.bitstore.Cleanup @ Caught exception”, all 
> with the same cause] – this is associated with the [dspace]/bin/dspace 
> cleanup job. Just how fatal is FATAL in this context?

I've seen this before in an upgraded repository. The worst possible consequence 
is that the bitstream was not actually deleted.


> 5.       “ERROR org.apache.pdfbox.filter.FlateFilter @ FlateFilter: stop
> reading corrupt stream due to a DataFormatException” – associated with 
> the [dspace]/bin/dspace filter-media  (Note I haven’t seen this one 
> yet under
> v5.6 but as we only just upgraded from 5.5 this weekend I’m not sure 
> if the update’s fixed that or if it just hasn’t had an opportunity to 
> occur.)

There is a huge variety of PDFs created by many various tools. Not all tools 
comply to standards perfectly and the tool that extracts text from PDF may fail 
to read some formats. The only consequence is that the text is not extracted 
from the particular PDF. The process will skip it, report an error like this 
and continue processing the rest of PDFs.


> 6.       “WARN  org.dspace.app.xmlui.cocoon.DSpaceI18NTransformer @
> Translation not found for attribute title in element <img>” – clearly 
> what it says on the box but is there any way to figure out *which* 
> image attribute, in all of our installation, it could be complaining 
> about? (I realise this one may be a rhetorical question....)

Try grepping in the "themes" directory.

This may also help a bit:
http://cocoon.10839.n7.nabble.com/i18n-attr-translation-td6264.html



Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette 
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

________________________________
P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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.

Reply via email to