[Tuxedo] LIBTUX_CAT:715 / LIBTUX_CAT:341 / LIBTUX_CAT:248 / TDM_CAT:2322 / CMDTUX_CAT:403

 

Questions/Symptoms

SYMPTOM:Getting memory fault coredump message when doing tmboot.
SYMPTOM:tmadmin fails and logs LIBTUX_CAT:715
SYMPTOM:LIBTUX_CAT:715: ERROR: Cannot attach bulletin board - magic number mismatch
SYMPTOM:LIBTUX_CAT:341: ERROR: Could not allocate bulletin board shared memory
SYMPTOM:LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr = TPESYSTEM - internal system error
SYMPTOM:TDM_CAT:2322: A BBL failed to start in an available CPU on <machine>. All admin processes will be stopped on that site.
SYMPTOM:CMDTUX_CAT:403: INFO: The DBBL is exiting system
...!tmboot...: WARN: No BBL available on site <machine>. Will not attempt to boot server processes on that site.

Cause

CAUSE:Customer coldload the system and didn't shutdown Tuxedo application. 
BB needed to be purged by the DBBL in the CPU reload case
(otherwise TS/MP 3.0 might start some servers before the BBL and they would fail). 
The system was brought down without shutting down the application so the BB didn't get purged. 
That might have caused a partial BB to be in the GSUBVOL so then when they attempted to restart the application the BBL detects a BB already exists and assumes 
it's restarting and detects a mismatch.

Answer/Solution

FIX:Make sure $T<IPCKEY> process does not exist.
Check the system for files in the ZZ<IPCKEY>nn in the configured GSUBVOL.
If they exist, purge them. Then tmboot the application.