Not sure what happened last night, but our Dspace instance went down.
We got bombarded by a whole bunch of these errors in the mail:
Exception:
java.lang.ArrayIndexOutOfBoundsException: -2147483648
at
java.text.SimpleDateFormat.subFormat(SimpleDateFormat.java:1049)
at java.text.SimpleDateFormat.format(SimpleDateFormat.java:882)
at java.text.SimpleDateFormat.format(SimpleDateFormat.java:852)
at java.text.DateFormat.format(DateFormat.java:316)
Unfortunately all the dspace.log files got owned by root, so I have no
information from the Dspace application. Once in a while we get a few
dsapce.log files that get owned by root, but not all for one day, that I
have noticed. What could be causing the dspace.log file to get owned by
root?
Our sys admin guy rebooted our server and our Dspace instance came back
up. But dspace.log file was owned by root again, so I deleted it and
restarted tomcat, which changes the ownership to dspace. Everything is
running fine now.
But why would this have happened? In looking at the tomcat log files.
I don't see much more than crawlers accessing our site at what appears
to be a normal rate. I do see a few access to images at our site like:
76.107.55.179 - - [13/Sep/2007:00:01:05 -0500] "GET /styles.css.jsp
HTTP/1.1" 200 13754
76.107.55.179 - - [13/Sep/2007:00:01:05 -0500] "GET /favicon.ico
HTTP/1.1" 200 3978
76.107.55.179 - - [13/Sep/2007:00:01:05 -0500] "GET /utils.js HTTP/1.1"
200 9537
76.107.55.179 - - [13/Sep/2007:00:01:07 -0500] "GET
/image/deepbluetype1.gif HTTP/1.1" 200 849
76.107.55.179 - - [13/Sep/2007:00:01:07 -0500] "GET /image/drop1.gif
HTTP/1.1" 200 7912
76.107.55.179 - - [13/Sep/2007:00:01:07 -0500] "GET
/image/searchbtbl.gif HTTP/1.1" 200 932
76.107.55.179 - - [13/Sep/2007:00:01:07 -0500] "GET /image/arrow.gif
HTTP/1.1" 200 61
76.107.55.179 - - [13/Sep/2007:00:01:07 -0500] "GET /image/spacer.gif
HTTP/1.1" 200 49
Which I guess is OK behavior for crawlers, no? Most or the access are
to items, bitstreams, or browse-title.
Over the weekend we also had an IP that was crawling us, and we got a
whole bunch of SQL connection errors where the connection pool was
exhausted. I'm pretty certain that this IP was the cause because when
we denied it access, the error went away. I looked at the log files,
both dspace and tomcat, and did not see anything that looked suspicious.
The IP was crawling us at a slow rate, and was basically doing a search
and then harvesting the results. If any one has any thoughts on why this
IP would have been causing the SQL connection errors while others
aren't, please let me know.
Many thanks!
Jose
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
