abnormal shutdown code 2

[gerie]

On the OTA enviroment de database shutted down without me knowing why. Maybe you can help me finding out why it happened. A simulair situation happend some months ago on production aswell, so I'm a bit worried.

OS VM windows 2003.
Openedge 10.1B

Admserv.log:
[16-2-11 17:35:47] [2] [AdminServer] Tool added: com.progress.ubroker.tools.adapter.AdapterRemoteObject@97d01f (7415)
[16-2-11 17:35:47] [2] [AdminServer] Tool added: com.progress.ubroker.tools.NSRemoteObject@1ce784b (7415)
[16-2-11 17:35:47] [2] [AdminServer] Tool added: com.progress.juniper.admin.JAPlugIn@d56b37 (7415)
[16-2-11 17:35:47] [2] [AdminServer] Tool added: com.progress.ubroker.tools.aia.AiaRemoteObject@11756a4 (7415)
[24-2-11 10:06:51] [2] [ConnectionManager] Error detected in config: exactcs.defaultconfiguration(13); attempting graceful shutdown. (8468)
[24-2-11 10:06:52] [3] [ConnectionManager] Abnormal communication failure for config: exactcs.defaultconfiguration (8490)
[24-2-11 10:06:52] [2] [ConnectionManager] In crash handler for config com.progress.juniper.admin.MProservJuniper@13043d2. (8486)
[24-2-11 10:06:52] [1] [ConnectionManager] Configuration is exiting: exactcs.defaultconfiguration (7394)

Database log:

[2011/02/23@16:35:24.137+0100] P-3788 T-4960 I SRV 2: (7129) Usr 446 set name to sysprogress.
[2011/02/23@16:43:16.787+0100] P-3788 T-4960 I SRV 2: (453) Logout by sysprogress on .
[2011/02/24@10:06:50.914+0100] P-3788 T-7776 I SRV 2: (9437) CTRL_LOGOFF_EVENT console event received.
Thu Feb 24 10:06:51 2011
[2011/02/24@10:06:51.070+0100] P-6380 T-5328 I SRV 5: (2520) Stopped.
[2011/02/24@10:06:51.085+0100] P-2764 T-7600 I SRV 4: (2520) Stopped.
[2011/02/24@10:06:51.085+0100] P-5900 T-1228 I APW 49: (2520) Stopped.
[2011/02/24@10:06:51.101+0100] P-1492 T-3208 I SRV 3: (2520) Stopped.
[2011/02/24@10:06:51.101+0100] P-1896 T-3908 I BIW 47: (2520) Stopped.
[2011/02/24@10:06:51.976+0100] P-3788 T-7652 I SRV 2: (9437) CTRL_LOGOFF_EVENT console event received.
[2011/02/24@10:06:52.554+0100] P-4180 T-3612 I BROKER 0: (2249) Begin ABNORMAL shutdown code 2
[2011/02/24@10:06:57.054+0100] P-2188 T-4432 I WDOG 48: (2520) Stopped.
[2011/02/24@10:06:58.914+0100] P-4180 T-3612 I BROKER : (334) Multi-user session end.

 

[cj_brandt]

Databases started from a user session will terminate when the user logs off.

Databases on windows can be started with the admin server to avoid this issue.

 

[gerie]

The database is not started form a user session.

 

[Casper]

It looks like you encountered a bug: Maybe take it up with TS?

KB: P127558:

Status: Verified
SYMPTOM(s):
User logs off console and database shuts down with CTRL_LOGOFF_EVENT
in database log file
Database shuts down abnormally
database log file shows error:
CTRL_LOGOFF_EVENT console event received
admserv.log file shows error:
Error detected in config: (); attempting graceful shutdown. (8468)
FACT(s) (Environment):
Database started with Adminserver
Second broker started for SQL connections
User logs off from Windows Remote Desktop connection or Windows Server
Console
Windows
OpenEdge 10.1C
OpenEdge 10.1B
CAUSE:
Bug# OE00162393
FIX:
Upgrade to 10.1C01 or later.

HTH,

Casper.

 

[gerie]

I found that one already. But I was hoping for other solutions. :-(
Well it is a good topic to discuss monday. Pffffffff

 

[Casper]

I found that one already. But I was hoping for other solutions. :-(
Well it is a good topic to discuss monday. Pffffffff

You could try to find out if this bug was also resolved in a later sp for 10.1B. So imight think it is good to contact TS on this one (or go throught the release notes to see if this bug number was released in SP from 10.1B).
An upgrade would mean upgrade to 10.2B which takes more time then installing a SP.

Regards,
Casper.

 

[gerie]

I will call them. Thnx.