Starting an App using Admin Console - confusing message

Question

I tried starting my 'App' and the messages indicate success but say failure.
I am confused.
Here is a CUT/PASTE of the "Progress of Activation (Entire Domain)" window.
I also attach my config file for consideration...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
********CHECKING SYSTEM RESOURCES
Security=NONE
********ACTIVATING ADMINISTRATIVE SERVERS ON MASTER SITE
Could not Activate the Administrative Servers.
Domain=poc
Master=PACEMid1 [A.Central.poc.customs.gov.au]
State=INACTIVE
Options=LAN,MIGRATE
[Operation: SET T_DOMAIN STATE:ACTIVE]
[Message: Success]
The activation attempt has failed. Check
the information printed above for possible
reasons for the failure.
******END OF MESSAGES******
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[config.txt]

Answer 1

Lyall,
You are corect that you only need the compiled TUXCONFIG file on the
master machine, the boot process will propagate it to the other machines.
I am unclear as to what your problem is now, where is the boot failing?
Are there any errors in the ULOG file on the master machine, or the
other machine?
The tlisten process must be started manually (or via UNIX startup
scripts) the tmboot brings up application servers. This application
boot process that may require the tlisten to be running in advance.
There is no way that the boot process "thinks it is starting the tlisten"
Please post some more information about what your current problem is!
Regards,
Peter.
Got a Question? Ask BEA at http://askbea.bea.com
The views expressed in this posting are solely those of the author, and BEA
Systems, Inc. does not endorse any of these views.
BEA Systems, Inc. is not responsible for the accuracy or completeness of
the
information provided
and assumes no duty to correct, expand upon, delete or update any of the
information contained in this posting.
Lyall Pearce wrote:
Thankyou Peter for responding so quickly.
I am still having difficulty. (Linux unix in case you are wondering)
The admin console thinks it is ok starting the master (cos it thinks it is starting
the tlisten process when I know one is already running)
[tuxadm@PACEMid1 poc]$ ps -fae | grep tlisten
tuxadm 14653 1 0 18:10 pts/10 00:00:00 tlisten -l //PACEMid1:12344
tuxadm 14799 11238 0 18:29 pts/10 00:00:00 grep tlisten
[tuxadm@PACEMid1 poc]$
It also thinks that it is not running on the second machine and so, fails to start
up the second machine. I know the tlisten is running on the second machine.
[tuxadm@PACEMid2 poc]$ ps -afe | grep tlisten
tuxadm 2891 1 0 08:51 pts/8 00:00:00 tlisten -l //PACEMid2:12344
tuxadm 2954 1111 0 09:04 pts/8 00:00:00 grep tlisten
[tuxadm@PACEMid2 poc]$
The admin console shows the full configuration (wonderful stuff really)
My config file has been updated now that I understand the difference between NADDR
and NLSADDR (maybe some synonyms in these config files that are more intuitive
would be helpful!)
I have only shown what I understand to be the relevant networking entries here.
*MACHINES
"PACEMid1"
     LMID               = "Central.A.poc.customs.gov.au"
     TUXDIR               = "/opt/bea/tuxedo8.0"
     APPDIR               = "/home/tuxadm/poc"
     TUXCONFIG          = "/home/tuxadm/poc/tuxconfig.poc.customs.eds.au"
"PACEMid2"
     LMID               = "Adl.A.poc.customs.gov.au"
     TUXDIR               = "/opt/bea/tuxedo8.0"
     APPDIR               = "/home/tuxadm/poc"
     TUXCONFIG          = "/home/tuxadm/poc/tuxconfig.poc.customs.eds.au"
*NETWORK
"Central.A.poc.customs.gov.au"
     NADDR               = "//205.239.97.151:12345"
     NLSADDR               = "//205.239.97.151:12344"
"Adl.A.poc.customs.gov.au"
     NADDR               = "//205.239.97.198:12345"
     NLSADDR               = "//205.239.97.198:12344"
In summary:
I seem to be in control of the master machine by default since it gives the impression
it is starting it's own tlisten process (which I am unable to find).
I am not in control of the second machine.
I have compiled the Config file on the master machine only (it does not exist
on the second machine), I gather that it will be replicated to the second machine.
..Lyall