Resolution:
Description:
= = = = = = =
“FATAL: failed to open log file ‘&ltlogfilename>’”

This issue could also cause the following errors:
“ERROR: Unable to open store file 'datastore/async-msgs.db', file may be locked.”
“ERROR: Unable to open store file 'datastore/meta.db', file may be locked.”
“ERROR: Unable to open store file 'datastore/sync-msgs.db', file may be locked”

Environment:
= = = = = = =
Unix


Check if the directory that the file is supposed to be located in is available first. If it is not then create it.

Be sure that the user who launches the EMS server has read+write permissions to the complete path provided for the location of the logfile, the storefile, as well as the config file.


When run as root, for security reasons, the tibemsd process drops the privilege to user nobody (uid = 65534). To run tibemsd as root you need to make the location for the logfile, config files, and the datastore file writable for this user.

Example:

The file location is given as /opt/tibco/ems/5.1/tibco/cfgmgmt/ems/data/tibemsd.conf. As a root user you are able to cd to the location of the tibemsd process. However, when the EMS server is started and the privilege is dropped to uid 65534, this user may not have read+execute rights on some or all of the directories in the path of the file being accessed and will fail.

A workaround would be to create a new user – e.g. "tibuser” and change the owner of all tib/ems related files to “tibuser” and launch the EMS server as “tibuser” instead of as root.


Keywords/Tags:
= = = = = = = = =
Locked, open

ERROR “FATAL: failed to open log file ‘logfilename’ ”