Eclipse Community Forums: DSDP - Target Management » Still having problems with rseserver

Help

Home

Home » Eclipse Projects » DSDP - Target Management » Still having problems with rseserver

Show: Today's Messages :: Show Polls :: Message Navigator

Still having problems with rseserver [message #24890]

Tue, 22 July 2008 19:36

Doug Abbott

Messages: 30
Registered: July 2009

Member

It's been about two months since I first posed this problem. Got
distracted by other issues and am just now getting back to DSDP and TM.

I'm trying to start a dstore server on a Linux box. When I run daemon.pl,
I get "Networking problem, can't resolve local host". server.pl starts
correctly on port 4033, but when I try to connect to it from Eclipse
(Ganymede) on another machine, I get

"A socket connection to 192.168.1.11 could not be established. If you are
connecting via the communications daemon make sure the daemon is running
on the remote system. If you are connecting directly to the
communications server make sure the server is started on the remote
system. If you are connecting using REXEC, make sure that the server is
installed on the remote system and that the REXEC service is running on
that system."

The Launcher property is set to Running. What else am I missing?

Thanks,

Doug

Report message to a moderator

Re: Still having problems with rseserver [message #24912 is a reply to message #24890]

Wed, 23 July 2008 14:49

David McKnight

Messages: 244
Registered: July 2009

Senior Member

When you try to connect, are there are messages in the console where you
started the server? Is there a firewall that could be preventing the
connect?

"Doug Abbott" <doug@intellimetrix.us> wrote in message
news:6df933883e1727b729abb786a3f614e5$1@www.eclipse.org...
> It's been about two months since I first posed this problem. Got
> distracted by other issues and am just now getting back to DSDP and TM.
>
> I'm trying to start a dstore server on a Linux box. When I run daemon.pl,
> I get "Networking problem, can't resolve local host". server.pl starts
> correctly on port 4033, but when I try to connect to it from Eclipse
> (Ganymede) on another machine, I get
> "A socket connection to 192.168.1.11 could not be established. If you are
> connecting via the communications daemon make sure the daemon is running
> on the remote system. If you are connecting directly to the
> communications server make sure the server is started on the remote
> system. If you are connecting using REXEC, make sure that the server is
> installed on the remote system and that the REXEC service is running on
> that system."
>
> The Launcher property is set to Running. What else am I missing?
>
> Thanks,
>
> Doug
>
>

Report message to a moderator

Re: Still having problems with rseserver [message #25105 is a reply to message #24912]

Fri, 25 July 2008 19:06

Doug Abbott

Messages: 30
Registered: July 2009

Member

Hi David,

Thanks for the clue. Turns out the firewall is disabled, but SE Linux was
enabled on the system running the server. Nevertheless, turning off SE
Linux didn't change anything. And no, I don't get any messages from the
server when I try to connect.

Doug

David McKnight wrote:

> When you try to connect, are there are messages in the console where you
> started the server? Is there a firewall that could be preventing the
> connect?

> "Doug Abbott" <doug@intellimetrix.us> wrote in message
> news:6df933883e1727b729abb786a3f614e5$1@www.eclipse.org...
>> It's been about two months since I first posed this problem. Got
>> distracted by other issues and am just now getting back to DSDP and TM.
>>
>> I'm trying to start a dstore server on a Linux box. When I run daemon.pl,
>> I get "Networking problem, can't resolve local host". server.pl starts
>> correctly on port 4033, but when I try to connect to it from Eclipse
>> (Ganymede) on another machine, I get
>> "A socket connection to 192.168.1.11 could not be established. If you are
>> connecting via the communications daemon make sure the daemon is running
>> on the remote system. If you are connecting directly to the
>> communications server make sure the server is started on the remote
>> system. If you are connecting using REXEC, make sure that the server is
>> installed on the remote system and that the REXEC service is running on
>> that system."
>>
>> The Launcher property is set to Running. What else am I missing?
>>
>> Thanks,
>>
>> Doug
>>
>>

Report message to a moderator

Re: Still having problems with rseserver [message #25312 is a reply to message #25105]

Thu, 31 July 2008 14:59

David McKnight

Messages: 244
Registered: July 2009

Senior Member

Hi Doug,

I don't know much about SELinux but to rule it out interference but it,
could you see if you can connect after you disable SELinux.

I think to disable it you need to edit /ect/selinux/config to have:

SELINUX=disabled

"Doug Abbott" <doug@intellimetrix.us> wrote in message
news:7bb3a6d30ca4cad81bd37f1d5b0ddf5f$1@www.eclipse.org...
> Hi David,
>
> Thanks for the clue. Turns out the firewall is disabled, but SE Linux was
> enabled on the system running the server. Nevertheless, turning off SE
> Linux didn't change anything. And no, I don't get any messages from the
> server when I try to connect.
>
> Doug
>
> David McKnight wrote:
>
>> When you try to connect, are there are messages in the console where you
>> started the server? Is there a firewall that could be preventing the
>> connect?
>
>
>> "Doug Abbott" <doug@intellimetrix.us> wrote in message
>> news:6df933883e1727b729abb786a3f614e5$1@www.eclipse.org...
>>> It's been about two months since I first posed this problem. Got
>>> distracted by other issues and am just now getting back to DSDP and TM.
>>>
>>> I'm trying to start a dstore server on a Linux box. When I run
>>> daemon.pl, I get "Networking problem, can't resolve local host".
>>> server.pl starts correctly on port 4033, but when I try to connect to it
>>> from Eclipse (Ganymede) on another machine, I get
>>> "A socket connection to 192.168.1.11 could not be established. If you
>>> are connecting via the communications daemon make sure the daemon is
>>> running on the remote system. If you are connecting directly to the
>>> communications server make sure the server is started on the remote
>>> system. If you are connecting using REXEC, make sure that the server is
>>> installed on the remote system and that the REXEC service is running on
>>> that system."
>>>
>>> The Launcher property is set to Running. What else am I missing?
>>>
>>> Thanks,
>>>
>>> Doug
>>>
>>>
>

Report message to a moderator

Re: Still having problems with rseserver [message #25635 is a reply to message #24890]

Wed, 06 August 2008 17:36

Martin Oberhuber

Messages: 1007
Registered: July 2009

Senior Member

Ok,

so you launched server.pl on the remote and set the Client's
launcher type to "Running". Have you also looked at the Subsystem
Properties (Right-click > Properties) and adjusted the Port
to be 4033 ? When that's also done, you just need to be quick
enough on the client, and connect to the server before it times
out. By default you have about 30 seconds before the server times
out (timeout value can be changed).

Your daemon.pl issue might be related to an invalid setting
in /etc/hosts, or invalid DNS configuration. Try commands
such as

hostname
uname -a
domainname
nslookup localhost
/usr/sbin/ifconfig

Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm

Doug Abbott wrote:
> It's been about two months since I first posed this problem. Got
> distracted by other issues and am just now getting back to DSDP and TM.
>
> I'm trying to start a dstore server on a Linux box. When I run
> daemon.pl, I get "Networking problem, can't resolve local host".
> server.pl starts correctly on port 4033, but when I try to connect to it
> from Eclipse (Ganymede) on another machine, I get
> "A socket connection to 192.168.1.11 could not be established. If you
> are connecting via the communications daemon make sure the daemon is
> running on the remote system. If you are connecting directly to the
> communications server make sure the server is started on the remote
> system. If you are connecting using REXEC, make sure that the server is
> installed on the remote system and that the REXEC service is running on
> that system."
>
> The Launcher property is set to Running. What else am I missing?
>
> Thanks,
>
> Doug
>
>

Report message to a moderator

Re: Still having problems with rseserver [message #532797 is a reply to message #25635]

Tue, 11 May 2010 09:23

No real name

Messages: 2
Registered: May 2010

Junior Member

Sorry to drag up an old topic, but....

I had the same problem as the OP - rseserver failing to start with the error message: "Networking problem, can't resolve local host".

In my case at least it was becase the hostname of the target was not in its /etc/hosts

-John

Report message to a moderator