I have a zombied EXPORT session that refuses to die, even after bouncing
the server.
I was running an export from a 5.5.3 server to my 6.1.2 server. Of
course, the 6.1.2 server crashed (any reasonable activity seems to kill
6.1.x - very fragile), thus hanging the export.
The "Q EXPORT" shows:
3:02:10 PM GALAXY : q export
Export identifier Start date Status Process Command
number
-------------------- ---------- ------------- -------
-------------------------
ACIPENSER_WIND 09/29/2009 Running 1,350 exp node
ACIPENSER.VCU.E-
14:06:10 DU filed=All
tos=WIND
enc=AES
exportid='ACIPE-
NSER_WIND'
Yet there are no processes nor sessions running on the source server,
especially since I bounced it due to a previous export that hung and
causes a log-pinned situation.
CANCEL EXPORT says it isn't in a "suspend" state. Doing a SUSPEND EXPORT
causes a server dump/error:
3:04:26 PM GALAXY : suspend export ACIPENSER_WIND
ANR2032E SUSPEND EXPORT: Command failed - internal server error detected.
ANR9999D Thread<373> issued message 2032 from:
ANR9999D Thread<373> 0x0000000000b85f8a outTextf+0x0xba
ANR9999D Thread<373> 0x0000000000ba3c0f xiSuspendExport+0x0x2df
ANR9999D Thread<373> 0x000000000048d318 AdmCommandLocal+0x0x3b8
ANR9999D Thread<373> 0x000000000048e12f admCommand+0x0x92f
ANR9999D Thread<373> 0x0000000000a816ca SmAdminCommandThread+0x0x1a
ANR9999D Thread<373> 0x0000000000bf53e6 StartThread+0x0x76
ANR9999D Thread<373> 0x0000003a32006137 *UNKNOWN*
ANR9999D Thread<373> 0x0000003a315c7113 *UNKNOWN*
ANS8001I Return code 4.
The 5.5.3 readme shows a lot of problems with the export process being
addressed but I am at the 5.5.3.0 level and I don't see any newer patches.
Suggestions?
