Kbase P147923: Database shutdown abnormally when a user process was terminated.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/15/2009 |
|
Status: Unverified
SYMPTOM(s):
Database shutdown abnormally when a user process was terminated.
User <num> died with <num> buffers locked. (2523)
(2523) User 346 died with 1 buffers locked.
There are no other messages for the USR 346 within the database other than a login into the database.
Broker process starts sending signals to all users attached to the database.
BROKER 0: (-----) Sending signal 12 to user 1
Background processes stop running.
Stopped. (2520)
BIW 8: (2520) Stopped.
All users start getting logged out of the database with 453 messages.
Logout by <user> on <ttyxxx>. (453)
FACT(s) (Environment):
Helpdesk was contacted to disconnect the user process.
Linux
OpenEdge 10.1A
CAUSE:
Process was terminated using a UNIX kill -9 command.
FIX:
Do not terminate a Progress/OpenEdge client using the UNIX kill -9 command. A UNIX kill -9 command cannot be trapped or handled. If this signal is used to terminate a process and the process is attached to shared memory and holding a resource, the database will shutdown to maintain database integrity. Terminate the process using promon or by sending signals to the process that the client can trap and handle. See solution: P67938, "How Progress interprets and handles kill signals" for additional information on signals and how Progress responds to them.