Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Cannot start server/region: CASCF0052S casstart: Error reading console daemon configuration data

Cannot start server/region: CASCF0052S casstart: Error reading console daemon configuration data

Problem:

On Linux/UNIX, a server/region in Enterprise Server (ES) would not start.  The error message was: CASCF0052S casstart: Error reading console daemon configuration data

Solution:

Here is a link into the documentation showing an explanation:

http://documentation.microfocus.com/help/index.jsp?topic=%2Fcom.microfocus.eclipse.infocenter.visualcobol.vs2012%2FGUID-6081411C-F6E2-42BC-8FD8-3C748C9C05A8.html

It is a permissions problem with the "system directory" of the server/region, caused by trying to start the server/region using a different Linux/UNIX user-id than the user-id used when the server/region was last started.

The system directory is where files such as the console.log, log-1.html, etc. are kept.  The directory is created and owned by the user-id that last started the server/region, and if you try to start the server/region with a different user-id, there will be a permissions problem on the system directory.

The quickest way to overcome this problem is to remove or re-name the existing system directory.  On disk the system directory has the same name as the server/region, and by default it is located in /var/mfcobol/es, though the location can be configured using the "casperm" command or by modifying the file $COBDIR/etc/cas/cas.cfg.  To reveal the current location, enter:

grep CASROOT $COBDIR/etc/cas/cas.cfg

Example:

$ grep CASROOT $COBDIR/etc/cas/cas.cfg
CASROOT=/var/mfcobol/es
$ cd /var/mfcobol/es
$ ls
ESDEMO
$ mv ESDEMO ESDEMO-old

After the existing system directory is removed or re-named, then when the server/region is next started, it will create a new system directory, and will start successfully.

If you start the server/region by clicking the "Start" button on the ES Admin page, then the user-id will be the "Default startup process user ID" that you see on the Start page.  But if you use "casstart" or "casstop" from the command line, you could possibly be logged in as a different user-id.  The long-term solution to this problem is to use the same user-id to start the server/region each time.  If you want to use "casstart" or "casstop", and sometimes you also want to use the "Start" and "Stop" buttons on the ES Admin page, then when you use "casstart" or "casstop", make sure you are logged in as the "Default startup process user ID" from the Start page.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2017-10-30 21:43
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.