Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-25 Thread Ricardo Borillo
. - Original Message - From: Tonny Hjelmberg Laursen thl@cbs.dk To: keith gilbertson keith.gilbert...@library.gatech.edu Cc: dspace-tech@lists.sourceforge.net Sent: Monday, May 24, 2010 10:38:06 AM GMT -05:00 US/Canada Eastern Subject: Re: [Dspace-tech] Handle server problems after update

Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-25 Thread Gilbertson, Keith R
. UU./Canadá Asunto: Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2 Hi all, I have followed your indications, but i still get this error message and my handle-server didn't start ... I have replaced my 1.6.1 dsrun file with the one in the 1.6.0 tag and i get the same

[Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-24 Thread Tonny Hjelmberg Laursen
Hey, Im in the middle of updating a DSpace installation and everything seems fine. But im having a problem with starting the handle server. When I execute bin/start-handle-server im getting this error in the handle-server logfile: Error in launcher.xml: Invalid class name:

Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-24 Thread Gilbertson, Keith R
to the list so that experts on the dspace launcher command can research more. --keith - Original Message - From: Tonny Hjelmberg Laursen thl@cbs.dk To: dspace-tech@lists.sourceforge.net Sent: Monday, May 24, 2010 7:55:29 AM GMT -05:00 US/Canada Eastern Subject: [Dspace-tech] Handle server

Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-24 Thread Tonny Hjelmberg Laursen
research more. --keith - Original Message - From: Tonny Hjelmberg Laursenthl@cbs.dk To: dspace-tech@lists.sourceforge.net Sent: Monday, May 24, 2010 7:55:29 AM GMT -05:00 US/Canada Eastern Subject: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2 Hey, Im

Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-24 Thread keith . gilbertson
: dspace-tech@lists.sourceforge.net Sent: Monday, May 24, 2010 9:38:51 AM GMT -05:00 US/Canada Eastern Subject: Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2 Thanks, The error is gone now, but now I got another error in the log file (The handle server is still not running

Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-24 Thread Tonny Hjelmberg Laursen
Eastern Subject: Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2 Thanks, The error is gone now, but now I got another error in the log file (The handle server is still not running.) Usage:program-name config-directory The bin/start-handle-server line looks

Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2

2010-05-24 Thread Gilbertson, Keith R
, 2010 10:38:06 AM GMT -05:00 US/Canada Eastern Subject: Re: [Dspace-tech] Handle server problems after update to 1.6.1 from 1.5.2 One of the things that I didn't test on the test server (1.6.0) was the handle-server. I have now replaced dsrun with the one from the 1.6.0 source package

[Dspace-tech] Handle Server Problems

2010-03-11 Thread Cameron, Jacob
Our handle server has stopped responding. I've killed and restarted the process several times and had it working again this morning. But it has died again this afternoon and I'm unable to resurrect it. We just renewed our handle server so I know it's not shutdown. I have even tried

Re: [Dspace-tech] Handle Server Problems

2010-03-11 Thread Graham Triggs
Sounds like you need to remove the lock file from the txns directory. Regards, G On 11 March 2010 22:32, Cameron, Jacob jacob.came...@uleth.ca wrote: Our handle server has stopped responding. I’ve killed and restarted the process several times and had it working again this morning. But

[Dspace-tech] handle server problems

2008-04-28 Thread Marc Goovaerts
Every Monday our Handle server is running 'wild'. From 0.00 until 24.00, it uses all the free CPU capacity, freeing it if another application needs it. I linked the problem to the creation of the log files, which are created on Monday, 0.00hr. I looked at the configuration and properties files,