R
Richard Shulman
Guest
Hello James, A quick way to search for the dead user. Identify the wdog message. Example: [2016/06/03@09:24:38.070+0100] P-8156 T-6724 I WDOG 25: (2527) Disconnecting dead user 33. Then search up from there for the user number followed by a colon. Example: [2016/06/03@08:08:26.572+0100] P-10144 T-10412 I ABL 33: (452) Login by WH5 on CON:. [2016/06/03@08:08:26.579+0100] P-10144 T-10412 I ABL 33: (12699) Database pws Options: Though this doesn't answer why it died it gives you something to search for. You now know that WH5 which is a shared memory connection (confirmed two ways one WDOG caught it and two it shows up as ABL in this listing as opposed to SRV). You could search to see if a batch job is scheduled to connect at this time or if that is a true user you could ask them what they can remember from that login session (if you are close enough in time for them to recall). Look for protraces that are between the login and the wdog detection as dead in case it died but was able to leave a protrace. (I admit since it died in a fashion that didn't give it time to say it generated a core in the log the chances are slim.) Hope this helps.
Continue reading...
Continue reading...
