Hi all,

I’ve been looking at our logs too much recently for various reasons and am keen 
to resolve underlying causes of the really common errors appearing in 
dspace.log.[datestamp] in order to a) reduce storage required but mostly b) 
make them slightly more navigable when a *real* error occurs. So below is a 
mishmash of common errors we’re getting which I’ve had no luck googling on. 
We’re on v.5.6 XMLUI/Mirage.


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



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


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.


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?



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



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


Any insight into what they are / whether they have dire consequences / how to 
avoid them would be highly appreciated for all/any of these!

Cheers,

Deborah Fitchett
Senior Advisor, Digital Access
Library, Teaching and Learning

p +64 3 423 0358
e [email protected]<mailto:[email protected]> | w 
ltl.lincoln.ac.nz<http://library.lincoln.ac.nz/>

Lincoln University, Te Whare Wānaka o Aoraki
New Zealand's specialist land-based university


________________________________
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