Search Mailing List Archives


Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-owl] [protege-discussion] Access to Protégé's Server

Martin Malaquina martin.malaquina at active.com.uy
Thu Aug 13 07:02:05 PDT 2009


Timothy,
   
I did a test with two machines connected to the Internet, where one Protege server was running, and it worked without any problems. Thank you very much for everything. 

Now I will try to do it, so that the Protege server, run in NAT. 

Thank you

Martín.

-----Mensaje original-----
De: protege-owl-bounces at lists.stanford.edu [mailto:protege-owl-bounces at lists.stanford.edu] En nombre de Timothy Redmond
Enviado el: martes, 11 de agosto de 2009 07:46 p.m.
Para: User support for the Protege-OWL editor
Asunto: Re: [protege-owl] [protege-discussion] Access to Protégé's Server


> > What I see strange that the run_protege_server script has the following  
> > -Djava.rmi.server.hostname = 190.135.26.42, and when the client tries to connect appears in the log, the IP 190.135.26.120, which has no connection, why do that?. 

Yes the log file is suggesting  that the server is configured with

 -Djava.rmi.server.hostname=190.136.26.120

because this is the address held by the rmiregistry.  If the server is really configured with 

  -Djava.rmi.server.hostname = 190.135.26.42

then something is strangely wrong which is probably why the connection
failed.

My first guess is that maybe the rmiregistry is in a bad state and needs
to be killed and restarted.  What connection string did you use on the
Protege client?  It occurs to me that this would also be useful
information to put in the log and maybe I will do this for the next 3.4
patch release.

Another thing you could try, especially if you haven't succeeded in
getting a server to run right yet, would be to start a server without
changes from a fresh distribution.  run_protege_server.sh/bat should
work out of the box on a fresh installation and then you can modify the
running example to be closer to what you want.

-Timothy


On Tue, 2009-08-11 at 10:08 -0300, Martin Malaquina wrote:
> Forgive my error, a misunderstanding of your previous message and my terrible English.   Repair the error he had committed, but I still have problems. 
> 
> What I see strange that the run_protege_server script has the following  
> -Djava.rmi.server.hostname = 190.135.26.42, and when the client tries to connect appears in the log, the IP 190.135.26.120, which has no connection, why do that?. 
> 
> Greetings.
> 
> Martín.
> 
> -----Mensaje original-----
> De: protege-owl-bounces at lists.stanford.edu [mailto:protege-owl-bounces at lists.stanford.edu] En nombre de Timothy Redmond
> Enviado el: lunes, 10 de agosto de 2009 08:36 p.m.
> Para: User support for the Protege-OWL editor
> Asunto: Re: [protege-owl] [protege-discussion] Access to Protégé's Server
> 
> 
> Sorry for multiple messages.  Let me try again.  Here the problem is a
> typo in the run_protege_server script.  The script has
> 
>    -Djava.rmi.server.hostname=190,132.27.194
> 
> when it should have said
> 
>    -Djava.rmi.server.hostname=190.132.27.194
> 
> The difference between this and my previous diagnosis is that I should
> have realized from the exception that you had  already successfully
> talked to the rmiregistry.  This is the difference between the first
> two exceptions described in [1].  It also took me a moment  to realize
> that the first line in the log you sent was a different connection
> attempt that failed for some other reason.
> 
> -Timothy
> 
> [1]
> http://protegewiki.stanford.edu/index.php/Troubleshooting_Client_Server_Connections#Basics
> 
> On Mon, 2009-08-10 at 15:57 -0300, Martin Malaquina wrote:
> > Viewing the various mistakes that i have to use NAT, try to do it directly through two internet-connected computer. 
> > 
> > A machine run Protégé's Server and the other run Protégé's Client. 
> > 
> > It did not work and the logs of both attachments in this mail. 
> > 
> > Apparently, the error then it could be something else and not the router. 
> > 
> > Thank you. 
> > 
> > Martin.
> > 
> > -----Mensaje original-----
> > De: protege-owl-bounces at lists.stanford.edu [mailto:protege-owl-bounces at lists.stanford.edu] En nombre de Timothy Redmond
> > Enviado el: lunes, 10 de agosto de 2009 12:52 p.m.
> > Para: User support for the Protege-OWL editor
> > Asunto: Re: [protege-owl] [protege-discussion] Access to Protégé's Server
> > 
> > 
> > Hi - your diagram is nicely done.  I don't know what you did but it
> > answered many questions I could ask.
> > 
> > I wanted to ask you about the telnet.  When you said you could not use
> > telnet, did you mean that (1) you could not download or start telnet on
> > your machine or (2) you ran telnet and it was blocked?  If it was the
> > latter case then Protege is failing for the same reason that telnet
> > failed.  This would mean that you have a networking problem.
> > 
> > Also - everything looks right but I want to avoid confusion - when/if
> > you used telnet - were you running it inside the lan (on a 192.168.1.*
> > machine)?  Also another place to try  telnet would be on the
> > 192.168.1.69 machine itself.
> > 
> > Oh - and I noticed one more thing.  If you want the server to work
> > outside the lan then the hostname line needs to be
> > 
> >    -Djava.rmi.server.hostname=200.40.69.126
> > 
> > What this means is that the server registers itself as
> > 
> >     200.40.69.126:5200
> > 
> > and this will be how a protege client will reconnect back to the server.
> > Unfortunately this setting will probably not work inside the lan.
> > (Getting both to work involves some dns magic.)  The setting shown 
> > 
> >    -Djava.rmi.server.hostname=192.168.1.69
> > 
> > will mean that Protege will work inside  the lan but not outside.  The
> > server registers itself  as
> > 
> >      192.168.1.69:5200
> > 
> > which makes sense on the lan but not  on the intern et.
> > 
> > 
> > -Timothy
> > 
> > 
> > On Mon, 2009-08-10 at 11:33 -0300, Martin Malaquina wrote:
> > > I attach a diagram that describes what is happening. I tried what you said to me, but I have not been successful. 
> > > I think it can be a problem with the configuration of the router. Do you have any idea that problems can be what are causing this?.
> > > 
> > > 
> > > -----Mensaje original-----
> > > De: protege-owl-bounces at lists.stanford.edu [mailto:protege-owl-bounces at lists.stanford.edu] En nombre de Timothy Redmond
> > > Enviado el: jueves, 06 de agosto de 2009 06:35 p.m.
> > > Para: User support for the Protege-OWL editor
> > > Asunto: Re: [protege-owl] [protege-discussion] Access to Protégé's Server
> > > 
> > > 
> > > > Then configure the NAT to access ports 5200 and 5100. 
> > > 
> > > If you are in the NAT situation then this is a relatively advanced
> > > technique requiring a good understanding of networks.  I would recommend
> > > you try a server on a public ip address.
> > > 
> > > > > 
> > > > > Then I try to connecting through a machine with public ip and can't do this. (the logs I have attached, to this mail).
> > > 
> > > The logs are telling a very simple story - the client could not connect
> > > to the rmiregistry.  The most obvious possibility is that the
> > > rmiregistry program is not running.  You need to have the command 
> > > 
> > > 	rmiregistry 5200
> > > 
> > > (if I understand your port opts) running.  If the rmiregistry is not
> > > running you will probably also be seeing errors on the server console.
> > > 
> > > If the rmiregistry is running (in particular the server is successfully
> > > connecting to the rmiregistry without errors) then something on your
> > > network is either blocking the connection  or is not correctly
> > > forwarding the connection.  If  you can you should first check that you
> > > can access the rmiregistry on the LAN with telnet.  That is, on some
> > > machine on the lan but other than the protege server machine, you should
> > > run the command (see [1])
> > > 
> > > 	telnet [server ip address] 5200
> > > 
> > > and see if it connects.  If it does not connect then the problem might
> > > be a firewall on the protege server  machine.
> > > 
> > > If you can connect on the LAN and you are using NAT then it is quite
> > > possible that the problem is that the router is misconfigured.  But it
> > > is also possible that there is some other firewall between the protege
> > > server and the protege client  that is blocking the connection.  In any
> > > case, at this point we are talking about a network configuration
> > > problem.
> > > 
> > > There are a large number of variables to consider in this discussion. If
> > > you are still having trouble you might want to consider sending a
> > > diagram such as [2] and describing what you thing is happening in that
> > > context.
> > > 
> > > -Timothy
> > > 
> > > 
> > > 
> > > [1]
> > > http://protegewiki.stanford.edu/index.php/Protege_Client-Server_Tutorial#Troubleshooting
> > > [2] http://protegewiki.stanford.edu/images/7/7c/RMIProtocol04.png
> > > 
> > > On Thu, 2009-08-06 at 16:31 -0300, Martin Malaquina wrote:
> > > > In a machine with private ip , run the Protégé's server 
> > > > 
> > > > "PORTOPTS =- Dprotege.rmi.server.port = 5100 = 5200-Dprotege.rmi.registry.port. 
> > > >   HOSTNAME =- Djava.rmi.server.hostname = 200.40.69.126 
> > > > 
> > > > Then configure the NAT to access ports 5200 and 5100. 
> > > > 
> > > > Then I try to connecting through a machine with public ip and can't do this. (the logs I have attached, to this mail). 
> > > > 
> > > > Any help to solve this problem, it would be very helpful. 
> > > > 
> > > > Greetings, 
> > > > 
> > > > Martín
> > > > 
> > > > -----Mensaje original-----
> > > > De: protege-owl-bounces at lists.stanford.edu [mailto:protege-owl-bounces at lists.stanford.edu] En nombre de Timothy Redmond
> > > > Enviado el: martes, 04 de agosto de 2009 03:17 p.m.
> > > > Para: User support for Core Protege and the Protege-Frames editor
> > > > CC: 'User support for the Protege-OWL editor'
> > > > Asunto: Re: [protege-owl] [protege-discussion] Access to Protégé's Server
> > > > 
> > > > 
> > > > Are you  sure that  the rmiregistry process is  running and on the right
> > > > port?  We need more information like how  you started the server and the
> > > > logs on both the client and the server.
> > > > 
> > > > I added a page for  troubleshooting problems with the client-server [1].
> > > > It is very incomplete and currently  is just  a hodge-podge of things
> > > > that  we have seen happen.
> > > > 
> > > > -Timothy
> > > > 
> > > > [1]
> > > > http://protegewiki.stanford.edu/index.php/Troubleshooting_Client_Server_Connections
> > > > 
> > > > On Tue, 2009-08-04 at 11:39 -0300, Martin Malaquina wrote:
> > > > > Hello everybody, 
> > > > > 
> > > > > I have a big problem. I can not connect through a Protégé's client to
> > > > > Protégé's server ,the messsage  tells me "Unable to Connect to Server". 
> > > > > 
> > > > > To access the server, I use NAT, following the steps listed in the following
> > > > > link http://protegewiki.stanford.edu/index.php/Protege_Client_Server_RMI,
> > > > > but just keep happening the same problem. 
> > > > > 
> > > > > I Change the router configuration page as indicated. 
> > > > > 
> > > > > I Need help to solve this. Some help . . .
> > > > > 
> > > > > I am using Windows, Protege_3.4 build 537. 
> > > > > 
> > > > > Greetings.
> > > > > 
> > > > > _______________________________________________
> > > > > protege-discussion mailing list
> > > > > protege-discussion at lists.stanford.edu
> > > > > https://mailman.stanford.edu/mailman/listinfo/protege-discussion
> > > > > 
> > > > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> > > > 
> > > > _______________________________________________
> > > > protege-owl mailing list
> > > > protege-owl at lists.stanford.edu
> > > > https://mailman.stanford.edu/mailman/listinfo/protege-owl
> > > > 
> > > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> > > > _______________________________________________
> > > > protege-owl mailing list
> > > > protege-owl at lists.stanford.edu
> > > > https://mailman.stanford.edu/mailman/listinfo/protege-owl
> > > > 
> > > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> > > 
> > > _______________________________________________
> > > protege-owl mailing list
> > > protege-owl at lists.stanford.edu
> > > https://mailman.stanford.edu/mailman/listinfo/protege-owl
> > > 
> > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> > > _______________________________________________
> > > protege-owl mailing list
> > > protege-owl at lists.stanford.edu
> > > https://mailman.stanford.edu/mailman/listinfo/protege-owl
> > > 
> > > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> > 
> > _______________________________________________
> > protege-owl mailing list
> > protege-owl at lists.stanford.edu
> > https://mailman.stanford.edu/mailman/listinfo/protege-owl
> > 
> > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> > _______________________________________________
> > protege-owl mailing list
> > protege-owl at lists.stanford.edu
> > https://mailman.stanford.edu/mailman/listinfo/protege-owl
> > 
> > Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> 
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
> 
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
> _______________________________________________
> protege-owl mailing list
> protege-owl at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-owl
> 
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

_______________________________________________
protege-owl mailing list
protege-owl at lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/protege-owl

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03




More information about the protege-owl mailing list