Location 2710 Problem.

[sicnet.suporte]

I have a Location 2710, with a 3.0.37.0 release.

I tried to stop the appliance (like Cisco says in the documentation, “locserverd stop”) and the appliance doesn't stops.

I tried to see the “man” information of the command “locserverd” and the appliance saes that that command does not exist.

What can I do?

Do you have any solution?

Some one can help me?

Thanks in advance,

Rui Capao

[ericgarnel]

I am assuming that you are ssh'd into the location server.

The full command is /etc/init.d/locserverd stop

or if you are in the /etc/init.d dir, ./locserverd stop

You could also simply type service locserverd stop as well

The loc app is basically a Redhat Linux ES 3 box, so most of the same commands are there.

[sicnet.suporte]

Eric,

I'm using the console port to (for now) to configure the appliance.

Your advice solved the problem.

I was doing “locserverd stop” in the “/etc/init.d/” directory.

If I type “/etc/init.d/ locserverd stop”, it works.

But, if I type “locserverd stop” in the “/etc/init.d/” directory, it don't work. ~

Do you know why?

By the way, in the WCS I was trying to associate the Location 2710 with “ssh” instead of the standard port 8001.

The WCS could not succeed in doing that. Can you tell me why?

Thanks in advance,

Rui Capao

[ericgarnel · Accepted solution]

You have to add "./" (without quotes) in front of the command when you are in the same directory AND the directory is not in your path environment; /etc and below are typically not.

Here is a typical path:

PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/mis/bin

the port is already in use by ssh daemon on the location server

[sicnet.suporte]

Eric,

I tried and it worked, thanks.

In the case of the ssh… I was referring associating the Location appliance with the WCS.

In the WCS you have to define the location server (name of the server, Ip address, etc…).

One field that we can select, if we what to have access to the appliance using http or https, is unchecking HTTPS and using port 8001 or checking HTTP and I think that we have to put the port 443…

I type the button SAVE and the WCS says that the Server is not responding. Or it may be unreachable, or connectivity credentials are incorrect.

But, if I leave the HTTPS option unchecked, with the standard port 8001, the WCS succeeds in associating with the Location Appliance.

Can you help me?

Thanks in advance,

Rui Capao

[ericgarnel]

You do not have to put 443, that is just the standard port for ssl for browser encryption, but you can have ssl listen on other ports as well. The location server is running a java app and not apache even though it has it installed:

[root@loc-server conf]# rpm -qa|grep httpd

redhat-config-httpd-1.1.0-4

httpd-2.0.46-38.ent

[root@loc-server conf]# pgrep httpd

[root@loc-server conf]#

Here are the ports it is listening on:

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

tcp 0 0 *:8001 *:* LISTEN 903/java

tcp 0 0 *:8002 *:* LISTEN 903/java

tcp 0 0 *:7555 *:* LISTEN 903/java

tcp 0 0 localhost.localdom:2315 *:* LISTEN 903/java

tcp 0 0 *:6100 *:* LISTEN 901/Xvfb

tcp 0 0 *:ssh *:* LISTEN 833/sshd

Also, it uses the certs located in /opt/locserver/ssl for the ssl

[ericgarnel]

I did some poking around and did not see where in the location server install/upgrade process that the port could be changed from 8001, which, is curious that you can change it in WCS. Perhaps for port redirects, etc...

[rcapao]

Yes, it's like that.

Thanks.