Please Do Needful

Mike

Moderator
No its not working same error

appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/proadsv -start
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>DLC=${DLC-/appln/prog91d/dlc};export DLC
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/proadsv -q
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004
AdminServer is alive. (8545)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i NS1 -stop
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)
Shut down NS1 (8277)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i NS1 -start
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)
Starting NS1. Check status. (8296)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i NS1 -q
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)

NameServer NS1 running on Host huldrtest Port 5162 Timeout 30 seconds.
There are no registered Application Services for this NameServer
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i devirishln -start
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for devirishln (8288)
Connecting to devirishln (8276)
Starting devirishln. Check status. (8296)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i devirishln -q
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for devirishln (8288)
Connecting to devirishln (8276)
Broker: devirishln not running (8313)
/appln/progress91d/dlc/webspeed>
 

TomBascom

Curmudgeon
Since you can ping the server properly the problem could also be that the port is being blocked by the firewall or that some other process is using that port.

If you can ping it it would seem like something has recently been fixed and you should no longer be seeing:
Unable to find host hultestdr in file HOSTS or HOSTS file not found in expected location. (5193)
[/quote
in the webspeed logs.

If those messages are still occurring in the webspeed logs even though you can ping it then I would be suspicious that you are the victim of that version of Progress using a very old networking component that has been recently replaced by something that is no longer compatible with Progress 9.1d. Or a Java upgrade.

If this worked previously and you changed nothing -- I would ask the sysadmin and networking people what they changed or upgraded on or around the date that this all stopped working. And I would show them these error messages as proof that it is a network related problem.

main>(Nov 4, 2016 16:04:45:741) Starting NameServer NS1 rmi://huldrtest:20931/NS1 Port = 5162 TimeOut = 30. (8196)
main>(Nov 4, 2016 16:04:45:750) Load Balancing Enabled For NameServer NS1. (8199)
main>(Nov 4, 2016 16:04:45:780) NameServer Port 5162 Invalid or In Use. (8212)
main>(Nov 4, 2016 16:04:45:780) Error Initialising NameServer. (8193)

If you were on a modern and supported release of Progress you could give tech support a call and see if they have any insight. You could give QAD a try too.
 

Mike

Moderator
butDear Tom still i getting this error:-

appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/proadsv -start
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>
/appln/progress91d/dlc/webspeed>DLC=${DLC-/appln/prog91d/dlc};export DLC
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/proadsv -q
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004
AdminServer is alive. (8545)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i NS1 -stop
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)
Shut down NS1 (8277)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i NS1 -start
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)
Starting NS1. Check status. (8296)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i NS1 -q
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for NS1 (8288)
Connecting to NS1 (8276)

NameServer NS1 running on Host huldrtest Port 5162 Timeout 30 seconds.
There are no registered Application Services for this NameServer
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i devirishln -start
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for devirishln (8288)
Connecting to devirishln (8276)
Starting devirishln. Check status. (8296)
/appln/progress91d/dlc/webspeed>/appln/prog91d/dlc/bin/wtbman -i devirishln -q
PROGRESS Version 9.1D09 as of Tue May 25 11:10:22 EDT 2004


Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Searching for devirishln (8288)
Connecting to devirishln (8276)
Broker: devirishln not running (8313)
/appln/progress91d/dlc/webspeed>
 

Cringer

ProgressTalk.com Moderator
Staff member
Again, that is not an error, it is a symptom. Please check all the logs as before.
 

TomBascom

Curmudgeon
There is no actual error anywhere in that output. There is a "not running" *status* but it is not an actual error nor does it tell you anything useful that would help in determining *why* it is not running.

(In a similar manner I can look out the window and see that my car is "not running".)

They *why* of the matter is being shown in the log file output.

(My car is a bit easier to debug -- the fact that I am not sitting in it is probably the main reason. But I suppose an analogy to your issue might be that I went out to start the car and discovered that my keys are not in the expected jacket pocket. I might then need to go ask my son where my keys have been moved to...)

There are two specific *error* messages in the log files which show you why Progress thinks that it cannot start a name server and webspeed -- both errors point to network configuration problems.
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
The issue is that you have the wrong host name. As RHD correctly said, this is a name-resolution issue.

Look at your error message again:
Unable to find host hultestdr in file HOSTS or HOSTS file not found in expected location. (5193)

Now look at the hosts file entry:
145.17.51.121 huldrtest

So if this application was working earlier, then either someone recently changed the hosts file contents, the Progress configuration, or both.
 

Mike

Moderator
Dear All.
Thank you very much now all is working fine. That was a host name mismatch.

Thanks with regards
Mike
 

TomBascom

Curmudgeon
It is important to do a root cause analysis -- the next question should be:

Who put the wrong name where?

and then:

Why was the wrong name used?

lastly:

How can we prevent a similar error from happening in the future?

along with:

What did you learn that will speed up future problem analysis?
 
It seems to show Mike has this "missing change control broken" problem in his department, where changes are made but actually not documented and no copies of /etc/hosts been made.:cool:
 
Top