Welcome login

Home Communities

Enterprise Message Service

Up to Conversations in Enterprise Message Service

This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)

Unable to start EMS

Created on: Feb 8, 2010 8:40 AM

Created by: Manoranjan Reddy

Hi all

I was trying to start EMS, im very new to TIBCO EMS.

Faced a problem in starting EMS.

======================================================

TIBCO Enterprise Message Service.
Copyright 2003-2009 by TIBCO Software Inc.
All rights reserved.

Version 5.1.4 V5 11/14/2009

2010-02-08 07:21:24.231 Process started from './tibemsd'.
2010-02-08 07:21:24.231 Process Id: 639048
2010-02-08 07:21:24.231 Hostname: vcsax022
2010-02-08 07:21:24.232 Hostname IP address: 10.209.60.54
2010-02-08 07:21:24.232 Detected IP interface: 10.209.60.54 (en0)
2010-02-08 07:21:24.232 Detected IP interface: 10.209.60.225 (en0)
2010-02-08 07:21:24.232 Detected IP interface: 127.0.0.1 (lo0)
2010-02-08 07:21:24.233 Reading configuration from '/tibco/cfgmgmt/ems/data/tibemsd.conf'.
2010-02-08 07:21:24.536 FATAL: failed to open log file '/tibco/cfgmgmt/ems/data/datastore/logfile'.
2010-02-08 07:21:24.544 FATAL: Exception in startup, exiting.

======================================================

Machine Details

AIX

EMS : 5.1

In guide found it might be because of some file access problems, but in this case im able to able to read/write logfile.

Can anyone help me..

Tags: tibco, ems, ems_server_logs

Yeshodhan Kulkarni

149 posts since
May 21, 2009

1. Feb 8, 2010 9:32 PM

in response to: Manoranjan Reddy

Re: Unable to start EMS

Some other process has acquired a lock on the file and the EMS server is trying to gain access to the file when the lock hasn't been released by the earlier process.

Its quite possible that the same log file is configured within multiple EMS servers you may have configured on the server.

Regards ~ Yeshodhan Kulkarni

Manoranjan Reddy

4 posts since
Feb 8, 2010

2. Feb 11, 2010 3:31 AM

in response to: Yeshodhan Kulkarni

Re: Unable to start EMS

Hi yeshodhan

I tried removing the directories likeTIBCO_HOME, CONFIG Directory

And tried installing again, but facing the same issue.

when i try installing 4.4 on same system, it works.

I'm i missing anything?

Let me know, help is appreciated..

==========================================================

TIBCO Enterprise Message Service.
Copyright 2003-2008 by TIBCO Software Inc.
All rights reserved.

Version 5.0.0 V28 4/29/2008

2010-02-11 14:46:37.368 Process started from './tibemsd'.
2010-02-11 14:46:37.368 Process Id: 20474
2010-02-11 14:46:37.369 Hostname: vcssx208
2010-02-11 14:46:37.369 Hostname IP address: 10.209.60.167
2010-02-11 14:46:37.369 Detected IP interface: 127.0.0.1 (lo0)
2010-02-11 14:46:37.369 Detected IP interface: 10.209.60.167 (bge0)
2010-02-11 14:46:37.369 Detected IP interface: 10.209.62.237 (bge0:1)
2010-02-11 14:46:37.369 Reading configuration from 'tibemsd.conf'.
2010-02-11 14:46:37.375 Server name: 'EMS-SERVER'.
2010-02-11 14:46:37.376 Storage Location: 'datastore'.
2010-02-11 14:46:37.376 Routing is disabled.
2010-02-11 14:46:37.376 Authorization is disabled.
2010-02-11 14:46:37.381 Accepting connections on tcp://vcssx208:7222.
2010-02-11 14:46:37.381 Recovering state, please wait.
2010-02-11 14:46:37.381 Creating store '$sys.nonfailsafe' file 'datastore/async-msgs.db' ...
2010-02-11 14:46:37.382 Creating store '$sys.failsafe' file 'datastore/sync-msgs.db' ...
2010-02-11 14:46:37.382 ERROR: Unable to open store file 'datastore/async-msgs.db', file may be locked.
2010-02-11 14:46:37.382 ERROR: Unable to open store file 'datastore/sync-msgs.db', file may be locked.
2010-02-11 14:46:37.383 Creating store '$sys.meta' file 'datastore/meta.db' ...
2010-02-11 14:46:37.383 ERROR: Unable to open store file 'datastore/meta.db', file may be locked.
2010-02-11 14:46:37.383 FATAL: Exception in startup, exiting.

================================================

Thanks

Manoranjan

Yeshodhan Kulkarni

149 posts since
May 21, 2009

3. Feb 11, 2010 6:34 AM

in response to: Manoranjan Reddy

Re: Unable to start EMS

Could you try flock -u ../datastore/async-msgs.db and flock -u ../datastore/sync-msgs.db?

This should release all the locks on the file. If this doesn't work perhaps you could consider a machine restart, but off-course this depends upon your environment if you could afford downtime.

You could also take some advice from some linux guru.

Regards ~ Yeshodhan Kulkarni

Manoranjan Reddy

4 posts since
Feb 8, 2010

4. Feb 18, 2010 11:40 PM

in response to: Yeshodhan Kulkarni

Re: Unable to start EMS

Hi Yeshodhan

Thanks for the timely responses.

One thing i observed is, when i try to run EMS from root user, its giving errors like

1)Creating store '$sys.nonfailsafe' file 'datastore/async-msgs.db' ...
Creating store '$sys.failsafe' file 'datastore/sync-msgs.db' ...
ERROR: Unable to open store file 'datastore/async-msgs.db', file may be locked.
ERROR: Unable to open store file 'datastore/sync-msgs.db', file may be locked.
Creating store '$sys.meta' file 'datastore/meta.db' ...
ERROR: Unable to open store file 'datastore/meta.db', file may be locked.
FATAL: Exception in startup, exiting.

2)Reading configuration from '/tibco/cfgmgmt/ems/data/tibemsd.conf'.
FATAL: failed to open log file '/tibco/cfgmgmt/ems/data/datastore/logfile'.
FATAL: Exception in startup, exiting.

I observed these errors in all unix platforms AIX, RHEL, SOL SPARC, HP,

And when i tried doing the same with non-root user, it works fine.

In documentation its given that, both root/non-root user should work.

Any other recommendations?

Thanks

Manoranjan

Konstantin Kersch

2 posts since
Oct 24, 2008

5. Feb 19, 2010 1:22 AM

in response to: Manoranjan Reddy

Re: Unable to start EMS

Hi Manoranjan,

on unix-platforms you have filemasks on the created datastore-files and logfiles. Please check this at first.

The first user who starts ems get this files writeable. My datastore-files have 644 (rw-r--r--) and belongs to non-root user.

Therefore the root-user fail with starting EMS, because tibemsd wants to open these files and have the writeable right.

Regards

Konstantin

Go to original post