Hi

Hello,

I have confirmed that ports 2641 and 8000 had been opened.. Telnet is
off on my Linux system but I can connect to the system using ssh and a
program called putty. I'm assuming the ports are therefore not an issue.
Tried running the handle update prefix script also, even though the
prefix was already correct and we hadn't made any entries prior to
setting up handle server(I had edited the config file in advance with
our pre existing prefix from our test server).

Any more insight will be greatly appreciated

Thanks for your input

Nigel

-----Original Message-----
From: Graham Triggs [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 24, 2007 1:16 PM
To: Nigel Pegus
Cc: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Handle Server fails to connect on dspace
1.4.1

Hi,

Can you telnet to that machine / ports - both from the machine itself, 
from the wider network, and from the even wider internet?

Then you'll know if there is a firewall / port binding issue, which 
would be the most obvious / easiest to resolve problem.

Next, check that you actually have handles with the correct prefix in 
the database - if you've got old items prior to receiving a prefix, you 
have to ensure that they are migrated to the prefix 
(/dspace/bin/update-handle-prefix).

G

Nigel Pegus wrote:
>
> Hello all,
>
> I am running dspace 1.4.1 on Linux Enterprise AS v3 update6
>
> I originally had a problem setting up the handle server with the 
> provided script, having gotten around that (I ran command 
> /dspace/bin/dsrun net.handle.server.Main /dspace/handle-server instead

> of /dspace/bin/make-handle-config) I am unable to resolve any handles.

> I have updated my config.dct with the required entries (see contents 
> below). I noted that I had to create the storage_type and 
> storage_class entries as opposed to just filling in the appropriate 
> vals after the "=" sign and wandered if that is a sign of a setup 
> problem on my end... To the best of my knowledge ports 2641 and 8000
are 
> opened to the wider internet. Is there something I have overlooked?
>
> "num_threads" = "15"
>
> "bind_port" = "2641"
>
> "backlog" = "5"
>
> "log_accesses" = "yes"
>
> }
>
> "log_save_config" = {
>
> "log_save_weekday" = "N/A"
>
> "log_save_time" = "02:00:00"
>
> "log_save_directory" = "/dspace/handle-server/logs"
>
> "log_save_interval" = "Monthly"
>
> }
>
> "no_udp_resolution" = "y"
>
> "interfaces" = (
>
> "hdl_udp"
>
> "hdl_tcp"
>
> "hdl_http"
>
> )
>
> "server_config" = {
>
> "server_admins" = (
>
> "300:0.NA/2139"
>
> )
>
> "replication_admins" = (
>
> "300:0.NA/2139"
>
> )
>
> "max_session_time" = "86400000"
>
> "this_server_id" = "1"
>
> "max_auth_time" = "60000"
>
> "backup_admins" = (
>
> "300:0.NA/2139"
>
> )
>
> "case_sensitive" = "no"
>
> "storage_type" = "CUSTOM"
>
> "storage_class" = "org.dspace.handle.HandlePlugin"
>
> }
>
> }
>
> Thanks for any input,
>
> **/Nigel Pegus/**
>
> **/Main Library, Systems Unit/**
>
> **/The University of the West Indies/**
>
> **/ext: 2241/**
>
>
------------------------------------------------------------------------
>
>
------------------------------------------------------------------------
-
> 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
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>   

This email has been scanned by Postini.
For more information please visit http://www.postini.com


-------------------------------------------------------------------------
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
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to