Kbase P66822: User logged out but still shows in Promon
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/19/2004 |
|
Status: Unverified
SYMPTOM(s):
One user hanging and can't disconnect
SYSTEM ERROR: strent request for more than 64K. (9874)
Server crashed
SYSTEM ERROR: Memory violation. (49)
PROSHUT option 1 (disconnect a user).
Repeating PROSHUT 1 for same user gives message "User XXX is not logged on (6799)"
Same user still seen by PROMON option 1 (User control)
CAUSE:
We can not know exactly what caused this confusion between PROSHUT and PROMON, but it could be due to the following scenario:
- The Remote Server crashed because of 9874.
- While trying to clean up after itself it crashed again with error 49.
- This second crash was a serious crash, meaning that no cleanup of the remote clients was done. This must have left shared memory in a "confused" state not knowing who is logged in and who is logged out.
All the users connect to the same remote Server still appeared as logged in.
Another consequence of error 49 is that the Watchdog did not pick up that the server had died, which confirms that at that point in time the log in and log outs really were "confused".
- When trying to disconnect the hanging user the remote server who is responsible for this user is actually dead, so this disconnection request cannot really be processed. This causes the inconsistency between proshut and promon.
FIX:
Shut down database by PROSHUT option 3 (Emergency shutdown (Kill all))