Broker not starting after crash

, , ,
1

Hi,

I currently have a problem with our QA Broker:

I failed somewhere in the last weeks and now it is not starting any longer.

Here is the message I got from the server_qsck:

BRC.300.1031] Phase 1: ERROR: Cannot open QS Configuration file "/opt/webma/wm65/BrokerData/Broker10406/BrokerConfig.qs", QS Error: LOCKED(QS-2) source:qs.cc line:181 
[BRC.300.1026] Phase 1: ERROR: Configuration QS instance "qs:///opt/webma/wm65/BrokerData/Broker10406/BrokerConfig.qs" fails. 
[BRC.300.1031] Phase 1: ERROR: Cannot open QS Configuration file "/opt/webma/wm65/BrokerData/Broker10406/BrokerData.qs", QS Error: LOCKED(QS-2) source:qs.cc line:181 
[BRC.300.1029] Phase 1: ERROR: Runtime Data QS instance "qs:///opt/webma/wm65/BrokerData/Broker10406/BrokerData.qs" fails. 
[BRC.300.1030] Phase 1: QS FAILURE 
[Aborting]

Broker Version: Version 6.5.2.0.1098 061907 FIX5

Any ideas, what is going on here and how to recover it?

Regards,
Holger

2

It appears that something has corrupted one of the data store files, possibly the Broker crash. I would suggest contacting wM tech support to see if they can help you recover without losing config info–although it may be lost. Hopefully you have backups?

3

Hi,

Did you resolved your problem, I have a similar problem

Unlinking expired file “/opt/webMethods/awbrokers71/default/diag.log.29946” from Mon May 11 13:55:01 2009
Locale character type is C.
Using builtin major message catalog.
CORRUPT(QS-14) source:qs.cc line:5342

Thanks

4

As far as I can remember the resolution was to re-create the Broker and its storage.

Luckily this was a QA-Environment and not the production environment.