Re: [Dspace-tech] Dspace 3.0 Upgrade/Server Migration

2013-01-30 Thread Chris King
Awesome. Thanks for the quick help. -Christopher King On Wed, Jan 30, 2013 at 12:24 PM, helix84 wrote: > Hi Chris, > > this is a common question, so I should probably write some > documentation about it. Meanwhile, here are the previous threads, they > apply to you, too: > > > http://dspace.22

[Dspace-tech] Dspace 3.0 Upgrade/Server Migration

2013-01-30 Thread Chris King
Hello, I do not have an actual issue currently I just wanted to see if my current plans to upgrade and migrate our dspace instance are actually feasible. Currently we are running dspace 1.8.2 which needs to be upgraded to 3.0 and moved to new server hardware. My plan currently is to get a new 3.0

Re: [Dspace-tech] Seemingly random file not found errors for bitstreams

2012-12-18 Thread Chris King
Hmmm. Well you are correct the file without the .gz extension does not exist. I had just assumed dspace was compressing the bitstream for whatever reason and I just didn't make the connection that the file shouldn't be compressed so I ignored that. The .gz is a valid gzipped file and if I uncompre

Re: [Dspace-tech] Seemingly random file not found errors for bitstreams

2012-12-18 Thread Chris King
Nope. We shouldn't be using SRB. I just checked dspace.cfg and all the SRB properties are commented out. Thanks for the quick reply, Chris On Tue, Dec 18, 2012 at 11:18 AM, helix84 wrote: > Hi Chris, > > are you using SRB [1]? According to the edu.sdsc.grid.io classes > appearing in the stackt

[Dspace-tech] Seemingly random file not found errors for bitstreams

2012-12-18 Thread Chris King
a stacktrace for the error. Also if you would like here is a link that reproduces the error: http://216.47.136.170/bitstream/id/173/preparationofzin00bent.pdf Thanks, Chris King Illinois Institute of Technology Galvin Library Technology Group org.apache.cocoon.ProcessingException: Failed to proce

[Dspace-tech] Dspace 1.7 upgrade to 1.8.2 Issues

2012-11-21 Thread Chris King
apparent on the website. Does anyone know of anything that might cause this? I can't think of what I might be doing wrong and its not really feasible to take our live server down long enough to "manually" iron out the bugs as they become apparent. Thanks for your help, -- Chris King