NameServer Issues - Forum - Community Groups - Progress Community

NameServer Issues

 Forum

NameServer Issues

  • Hi guys,

    We have some webservices configured that until recently have been working fine. However about 2 weeks ago the nameserver stopped starting up on port 5162 due to a port conflict error. We have since tried to change the port that the NameServer starts on through both the Explorer Tool and ubroker.properties file without result. The nameserver does start up as seen in the logs:

    File NS1.ns.log:

    ======================================================================
    [09/06/10@12:31:03.928+1000] P-001688 T-main 1 --- --- C:\Progress\WRK\NS1.ns.log opened.[09/06/10@12:12:40.501+1000] P-008964 T-main 1 --- --- C:\Progress\WRK\NS1.ns.log opened.
    [09/06/10@12:12:40.501+1000] P-008964 T-main 1 --- --- Logging level set to = 2
    [09/06/10@12:12:40.501+1000] P-008964 T-main 1 --- --- Log entry types activated: NSPlumbing,
    [09/06/10@12:12:40.532+1000] P-008964 T-main 2 NS NSPlumbing Starting NameServer NS1 rmi://kingdc:20931/NS1 Port = 30450 TimeOut = 30. (8196)
    [09/06/10@12:12:40.532+1000] P-008964 T-main 2 NS NSPlumbing Load Balancing Disabled For NameServer NS1. (8200)

    Which tells me that the NameServer started. The broker does also register with the name server as well, but not with the example i provided above. But i do normally get the following as well:

    File NS1.ns.log:

    [09/06/10@12:35:07.830+1000] P-001688 T-Thread-2 2 NS NSPlumbing Registering Broker 92781e7a51a92348:cdedfd:11ddd6fd284:-2f95 AS.mwservices kingdc 30400. (8205)
    [09/06/10@12:35:07.830+1000] P-001688 T-Thread-2 2 NS NSPlumbing Broker 92781e7a51a92348:cdedfd:11ddd6fd284:-2f95 Registered For Application Service AS.mwservices. (8207)

    Which all looks fine, and a java.exe process starts on port 30450. But in the other files i get this:

    File admserv.log:

    [10/06/09 12:12:40] [3] [AdminServer]           SvcControlCmd.connectToService() failure: Unable to connect to the service process at rmi://kingdc:20931/NS1(after 2 retries) (8171)

    File cmdplugin.log:

    Plug-in of type: com.progress.ubroker.tools.UBCommandPlugin>(10/06/2009 12:13:08:064) NS1 is not responding to a ping (8307)

    Now if i check the status of the NS1 through the Explorer Tool i get all the correct information regarding the connected brokers, but at the command line when i run the command "c:\progress\openedge\bin\nsman -i ns1 -query" i get:

    Connecting to Progress AdminServer using rmi://localhost:20931/Chimera

    Searching for ns1 (8288)

    Unable to connect to ns1 (8289)

    Unable to find ns1 (8281)

    And just to be sure i ran the command "c:\progress\openedge\bin\nsman -i ns1 -r kingdc -query" with the same result.

    Everything is running on the same server, and everything was working until a windows update for dns.exe started using thousands of ports including 5162. All databases are running fine in the same port range and most things are set to localhost, so i'm ruling out a firewall issue. The questions i have are:

    1) Is there a known issue with changing the port of NS1?

    2) Are there other locations to specify the port of NS1 other than ubroker.properties?

    3) What other debug avenues can i try?

    I would appreciate any further debug ideas or insight on the problem.

    Thanks,

    Andrew

  • drew_sav wrote:

    Hi guys,

    We have some webservices configured that until recently have been working fine. However about 2 weeks ago the nameserver stopped starting up on port 5162 due to a port conflict error. We have since tried to change the port that the NameServer starts on through both the Explorer Tool and ubroker.properties file without result. The nameserver does start up as seen in the logs:

    File NS1.ns.log:

    ======================================================================
    [09/06/10@12:31:03.928+1000] P-001688 T-main 1 --- --- C:\Progress\WRK\NS1.ns.log opened.[09/06/10@12:12:40.501+1000] P-008964 T-main 1 --- --- C:\Progress\WRK\NS1.ns.log opened.
    [09/06/10@12:12:40.501+1000] P-008964 T-main 1 --- --- Logging level set to = 2
    [09/06/10@12:12:40.501+1000] P-008964 T-main 1 --- --- Log entry types activated: NSPlumbing,
    [09/06/10@12:12:40.532+1000] P-008964 T-main 2 NS NSPlumbing Starting NameServer NS1 rmi://kingdc:20931/NS1 Port = 30450 TimeOut = 30. (8196)
    [09/06/10@12:12:40.532+1000] P-008964 T-main 2 NS NSPlumbing Load Balancing Disabled For NameServer NS1. (8200)

    Which tells me that the NameServer started. The broker does also register with the name server as well, but not with the example i provided above. But i do normally get the following as well:

    File NS1.ns.log:

    [09/06/10@12:35:07.830+1000] P-001688 T-Thread-2 2 NS NSPlumbing Registering Broker 92781e7a51a92348:cdedfd:11ddd6fd284:-2f95 AS.mwservices kingdc 30400. (8205)
    [09/06/10@12:35:07.830+1000] P-001688 T-Thread-2 2 NS NSPlumbing Broker 92781e7a51a92348:cdedfd:11ddd6fd284:-2f95 Registered For Application Service AS.mwservices. (8207)

    Which all looks fine, and a java.exe process starts on port 30450. But in the other files i get this:

    File admserv.log:

    [10/06/09 12:12:40] [3] [AdminServer]           SvcControlCmd.connectToService() failure: Unable to connect to the service process at rmi://kingdc:20931/NS1(after 2 retries) (8171)

    File cmdplugin.log:

    Plug-in of type: com.progress.ubroker.tools.UBCommandPlugin>(10/06/2009 12:13:08:064) NS1 is not responding to a ping (8307)

    Now if i check the status of the NS1 through the Explorer Tool i get all the correct information regarding the connected brokers, but at the command line when i run the command "c:\progress\openedge\bin\nsman -i ns1 -query" i get:

    Connecting to Progress AdminServer using rmi://localhost:20931/Chimera

    Searching for ns1 (8288)

    Unable to connect to ns1 (8289)

    Unable to find ns1 (8281)

    And just to be sure i ran the command "c:\progress\openedge\bin\nsman -i ns1 -r kingdc -query" with the same result.

    Everything is running on the same server, and everything was working until a windows update for dns.exe started using thousands of ports including 5162. All databases are running fine in the same port range and most things are set to localhost, so i'm ruling out a firewall issue. The questions i have are:

    1) Is there a known issue with changing the port of NS1?

    2) Are there other locations to specify the port of NS1 other than ubroker.properties?

    3) What other debug avenues can i try?

    I would appreciate any further debug ideas or insight on the problem.

    Thanks,

    Andrew

    Hi Andrew.

    I am assuming you copied the command directly so I think the issue is that your using lower case characters for the nameserver name. The name is case sensitive so try NS1 (capitals).

    HTH
    Molly

  • Hi Molly,

    Thanks for the reply. I don't think the name is case sensitive as the query commands did work previously before having to modify the port number. Unfortunately i will not get the chance to test this, as we have isolated the process using the port 5162 and removed it. As soon as the name server could use 5162 it was happy again.

    Thanks for your efforts,

    Andrew