My Oracle Support Banner

Tuxedo Freezes With LIBTUX_CAT:5005 (Doc ID 2304006.1)

Last updated on OCTOBER 18, 2018

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
IBM AIX on POWER Systems (64-bit)

Symptoms

Issue started happening after multiple application servers dies and restarted. Below messages are printed when the problem started. There are numerous 5005 errors in the logs. 

174342.almas!BBL.39780468.1.0: LIBTUX_CAT:541: WARN: Server TX1_GRPW/4350 terminated
174342.almas!BBL.39780468.1.0: LIBTUX_CAT:557: INFO: Server TX1_GRPW/4350 being restarted
174342.almas!TMSYSEVT.54723288.1.0: LIBTUX_CAT:1477: ERROR: .SysServerDied: wrEMS, group TX1_GRPW, id 4350 server died
174342.almas!TMSYSEVT.54723288.1.0: LIBTUX_CAT:1476: ERROR: .SysServerRestarting: wrEMS, group TX1_GRPW, id 4350 server restarting
174342.almas!wrEMS.9765612.1.0: 08-26-2017: Tuxedo Version 11.1.1.2.0, 64-bit
174342.almas!wrEMS.9765612.1.0: LIBTUX_CAT:262: INFO: Standard main starting
174342.almas!wrEMS.9765612.1.0: 96I0018
174342.almas!restartsrv.30802168.1.-2: 08-26-2017: Tuxedo Version 11.1.1.2.0, 64-bit
174342.almas!restartsrv.30802168.1.-2: server TX1_GRPW/4350: CMDTUX_CAT:580: INFO: A server process has restarted: 9765612
174357.almas!BBL.39780468.1.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=9765612
174407.almas!BBL.39780468.1.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=9765612
174417.almas!BBL.39780468.1.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=9765612
174427.almas!BBL.39780468.1.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=9765612
174437.almas!BBL.39780468.1.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=9765612


Later the logs are filled with these errors

184805.almas!TMS_ORA.52232882.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!wrATLYSFT.62915040.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.11469210.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!wrATLYSFT.38666952.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.17695014.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.16384354.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!TMS_QM.48890562.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!TMS_ORA.48300756.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!wrATLYSFT.30605700.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!TuxConnector.33685924.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!TuxConnector.9044306.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.16974242.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.16187716.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.12648736.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.20382182.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!WSL.50790910.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!TuxConnector.17957278.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!wrNGIN.30802280.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!srvproccad.25559648.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22
184805.almas!wrNGIN.58064986.1.0: LIBTUX_CAT:752: ERROR: semop system call failure for semaphore 14680096, errno 22

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.