Ryszard Musielak
Member
Hello,
I encountered a problem today. We've made a copy of our Progress server, changing the obvious things like IP address, etc.
Normally we would be able to start the server, start the DB and Apps server and would be able to use it for testing.
One thing to point out, is that the copy server would be on a different network, so for example the live one would be 172.18.201.32
The copy/test one would be 172.18.200.32. They are normally in physically different locations.
The new copy server is on 172.18.16.32. THis machine is in the same physical location as the Live one.
I know, it's probably odd that I think this may be a conflict. But... I managed to start the Admin Server "proadsv -start".
I managed to start the database:
proserve package -pf broker.pf # Serve the database
probiw package # Enterprise Progress
proapw package # Enterprise Progress
proapw package # Enterprise Progress
proserve package -pf sqlbroker.pf # SQL - Unixware problem
prowdog package # Enterprise Progress
However, when trying to start the Apps server broker:
asbman -i AccordTest -start # App server
It would throw these messages:
OpenEdge Release 11.6.1 as of Fri Feb 19 18:20:45 EST 2016
Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Unable to connect to Progress AdminServer at rmi://localhost:20931/Chimera (8287)
Unable to find AccordTest (8281)
One very peculiar thing occurred - the Live Apps server also was affected, basically it went down on 172.18.201.32 .
My question is - is it possible there is a conflict on the side of the port numbers the brokers are using?
It may just be coincidence that the Live server went down as I started the copy one for testing.
Is there any way I can find how to change the port number and change it? For the Application server I found this article:
I have *.pf files and the port number 20931 is not in any of them. I found the folder /bcp/dlc/properties which looks like the installation
where the Progress sits. I have not found this number in any of the files. So where it the file that would have to be changed?
More bizarrely, here are the date and times of my database being started:
Yet my attempt to start the brokers wasn't even logged:
I hope this makes sense.
Thanks,
Richard
I encountered a problem today. We've made a copy of our Progress server, changing the obvious things like IP address, etc.
Normally we would be able to start the server, start the DB and Apps server and would be able to use it for testing.
One thing to point out, is that the copy server would be on a different network, so for example the live one would be 172.18.201.32
The copy/test one would be 172.18.200.32. They are normally in physically different locations.
The new copy server is on 172.18.16.32. THis machine is in the same physical location as the Live one.
I know, it's probably odd that I think this may be a conflict. But... I managed to start the Admin Server "proadsv -start".
I managed to start the database:
proserve package -pf broker.pf # Serve the database
probiw package # Enterprise Progress
proapw package # Enterprise Progress
proapw package # Enterprise Progress
proserve package -pf sqlbroker.pf # SQL - Unixware problem
prowdog package # Enterprise Progress
However, when trying to start the Apps server broker:
asbman -i AccordTest -start # App server
It would throw these messages:
OpenEdge Release 11.6.1 as of Fri Feb 19 18:20:45 EST 2016
Connecting to Progress AdminServer using rmi://localhost:20931/Chimera (8280)
Unable to connect to Progress AdminServer at rmi://localhost:20931/Chimera (8287)
Unable to find AccordTest (8281)
One very peculiar thing occurred - the Live Apps server also was affected, basically it went down on 172.18.201.32 .
My question is - is it possible there is a conflict on the side of the port numbers the brokers are using?
It may just be coincidence that the Live server went down as I started the copy one for testing.
Is there any way I can find how to change the port number and change it? For the Application server I found this article:
Progress Customer Community
community.progress.com
AdminServer
- AdminServer Listening Port: -port 20931
I have *.pf files and the port number 20931 is not in any of them. I found the folder /bcp/dlc/properties which looks like the installation
where the Progress sits. I have not found this number in any of the files. So where it the file that would have to be changed?
More bizarrely, here are the date and times of my database being started:
[root@accordvwell test]# ls -ltr package*
-rw-rw-rw-. 1 root root 202 Jan 5 2018 package.st
-rw-r--r--. 1 root root 655360 Feb 14 10:54 package.db
-rw-r--r--. 1 root root 10619977728 Feb 14 10:54 package_7.d1
-r--r--r--. 1 root root 1420768 Feb 14 11:00 package.lic
-rw-r--r--. 1 root root 610402304 Feb 14 11:43 package.b1
-rw-r--r--. 1 root root 11381768192 Feb 14 11:43 package_9.d1
-rw-r--r--. 1 root root 45386563584 Feb 14 11:43 package_8.d1
-rw-r--r--. 1 root root 16252928 Feb 14 11:43 package.d1
-rw-r--r--. 1 root root 16329956 Feb 14 11:43 package.lg
Yet my attempt to start the brokers wasn't even logged:
-rw-rw-rw-. 1 root root 1024021 Feb 3 16:50 AccordLive.broker.019973.log
-rw-rw-rw-. 1 root root 1258040 Feb 3 16:52 AccordLive.server.052239.log
-rw-rw-rw-. 1 root root 2651961 Feb 4 08:58 AccordTest.broker.log
-rw-rw-rw-. 1 root root 5236581 Feb 4 08:58 AccordTest.server.log
-rw-rw-rw-. 1 root root 104571 Feb 4 09:04 AccordLive.broker.019974.log
-rw-rw-rw-. 1 root root 259060 Feb 4 09:04 AccordLive.server.052240.log
I hope this makes sense.
Thanks,
Richard
Last edited: