This has got to be one of the weirder errors I've recently encountered.  I've had weirder but not recently. ;-)

We are trying to start up a new installation of release IDS-14.10 on a host and have set up the onconfig similar to onconfig files where it has been successful.  One error message complains when we try to come up:

ERROR: The requested log staging directory is not secure or does not exist.

To display the path name here might be a confidence breach.  However, looking at the onconfig of a 12.10 instance on the same host, we are specifying the same full path. (No, they're NOT both up at the same time.) Ownership is informix:informix and permissions are 770, just as they are on all other hosts in our environment.

This sounds like a red-herring error message - the problem lies elsewhere.  After all, we do have a running (test) server with the identical setting ad permissions and no complaints there.

We got the server up by commenting out LOG_STAGE_DIR but we need to be able to use it; this server is intended as part of an RSS pair.

Hey, I'm open to ideas, as usual.

Thanks! Спасибо! Köszönöm, even!

Jacob:

Check the permissions on the oninit executable.

Art

This has got to be one of the weirder errors I've recently encountered.  I've had weirder but not recently. ;-)

We are trying to start up a new installation of release IDS-14.10 on a host and have set up the onconfig similar to onconfig files where it has been successful.  One error message complains when we try to come up:

ERROR: The requested log staging directory is not secure or does not exist.

To display the path name here might be a confidence breach.  However, looking at the onconfig of a 12.10 instance on the same host, we are specifying the same full path. (No, they're NOT both up at the same time.) Ownership is informix:informix and permissions are 770, just as they are on all other hosts in our environment.

This sounds like a red-herring error message - the problem lies elsewhere.  After all, we do have a running (test) server with the identical setting ad permissions and no complaints there.

We got the server up by commenting out LOG_STAGE_DIR but we need to be able to use it; this server is intended as part of an RSS pair.

Hey, I'm open to ideas, as usual.

Thanks! Спасибо! Köszönöm, even!

This has got to be one of the weirder errors I've recently encountered.  I've had weirder but not recently. ;-)

We are trying to start up a new installation of release IDS-14.10 on a host and have set up the onconfig similar to onconfig files where it has been successful.  One error message complains when we try to come up:

ERROR: The requested log staging directory is not secure or does not exist.

To display the path name here might be a confidence breach.  However, looking at the onconfig of a 12.10 instance on the same host, we are specifying the same full path. (No, they're NOT both up at the same time.) Ownership is informix:informix and permissions are 770, just as they are on all other hosts in our environment.

This sounds like a red-herring error message - the problem lies elsewhere.  After all, we do have a running (test) server with the identical setting ad permissions and no complaints there.

We got the server up by commenting out LOG_STAGE_DIR but we need to be able to use it; this server is intended as part of an RSS pair.

Hey, I'm open to ideas, as usual.

Thanks! Спасибо! Köszönöm, even!

LOG_STAGING_DIR should have 700 permission and owned by informix:informix.

If you run onstat -g cfg full LOG_STAGING_DIR, you will get below which can explain:

     Description:

     Use the LOG_STAGING_DIR configuration parameter to specify the

     location of log files received from the primary server when

     configuring delayed application of log files on RS secondary servers.

     The directory specified by the LOG_STAGING_DIR configuration

     parameter is used to store logs sent from the primary server when

     using the DELAY_APPLY configuration parameter to delay application

     of log files on an RS secondary server. Delaying the application

     of log files allows you to recover quickly from erroneous database

     modifications by restoring the data from the RS secondary server.

     The directory specified by the LOG_STAGING_DIR configuration

     parameter must be secure. The directory must be owned by user

     informix, must belong to group informix, and must not have public

     read, write, or execute permission.

Please make sure no typo in the parameter name, it is 

LOG_STAGING_DIR,

not LOG_STAGE_DIR

(not sure if this is the reason why your other servers did not complain).

This has got to be one of the weirder errors I've recently encountered.  I've had weirder but not recently. ;-)

We are trying to start up a new installation of release IDS-14.10 on a host and have set up the onconfig similar to onconfig files where it has been successful.  One error message complains when we try to come up:

ERROR: The requested log staging directory is not secure or does not exist.

To display the path name here might be a confidence breach.  However, looking at the onconfig of a 12.10 instance on the same host, we are specifying the same full path. (No, they're NOT both up at the same time.) Ownership is informix:informix and permissions are 770, just as they are on all other hosts in our environment.

This sounds like a red-herring error message - the problem lies elsewhere.  After all, we do have a running (test) server with the identical setting ad permissions and no complaints there.

We got the server up by commenting out LOG_STAGE_DIR but we need to be able to use it; this server is intended as part of an RSS pair.

Hey, I'm open to ideas, as usual.

Thanks! Спасибо! Köszönöm, even!

LOG_STAGING_DIR should have 700 permission and owned by informix:informix.

If you run onstat -g cfg full LOG_STAGING_DIR, you will get below which can explain:

     Description:

     Use the LOG_STAGING_DIR configuration parameter to specify the

     location of log files received from the primary server when

     configuring delayed application of log files on RS secondary servers.

     The directory specified by the LOG_STAGING_DIR configuration

     parameter is used to store logs sent from the primary server when

     using the DELAY_APPLY configuration parameter to delay application

     of log files on an RS secondary server. Delaying the application

     of log files allows you to recover quickly from erroneous database

     modifications by restoring the data from the RS secondary server.

     The directory specified by the LOG_STAGING_DIR configuration

     parameter must be secure. The directory must be owned by user

     informix, must belong to group informix, and must not have public

     read, write, or execute permission.

Please make sure no typo in the parameter name, it is 

LOG_STAGING_DIR,

not LOG_STAGE_DIR

(not sure if this is the reason why your other servers did not complain).

This has got to be one of the weirder errors I've recently encountered.  I've had weirder but not recently. ;-)

We are trying to start up a new installation of release IDS-14.10 on a host and have set up the onconfig similar to onconfig files where it has been successful.  One error message complains when we try to come up:

ERROR: The requested log staging directory is not secure or does not exist.

To display the path name here might be a confidence breach.  However, looking at the onconfig of a 12.10 instance on the same host, we are specifying the same full path. (No, they're NOT both up at the same time.) Ownership is informix:informix and permissions are 770, just as they are on all other hosts in our environment.

This sounds like a red-herring error message - the problem lies elsewhere.  After all, we do have a running (test) server with the identical setting ad permissions and no complaints there.

We got the server up by commenting out LOG_STAGE_DIR but we need to be able to use it; this server is intended as part of an RSS pair.

Hey, I'm open to ideas, as usual.

Thanks! Спасибо! Köszönöm, even!

This has got to be one of the weirder errors I've recently encountered.  I've had weirder but not recently. ;-)

We are trying to start up a new installation of release IDS-14.10 on a host and have set up the onconfig similar to onconfig files where it has been successful.  One error message complains when we try to come up:

ERROR: The requested log staging directory is not secure or does not exist.

To display the path name here might be a confidence breach.  However, looking at the onconfig of a 12.10 instance on the same host, we are specifying the same full path. (No, they're NOT both up at the same time.) Ownership is informix:informix and permissions are 770, just as they are on all other hosts in our environment.

This sounds like a red-herring error message - the problem lies elsewhere.  After all, we do have a running (test) server with the identical setting ad permissions and no complaints there.

We got the server up by commenting out LOG_STAGE_DIR but we need to be able to use it; this server is intended as part of an RSS pair.

Hey, I'm open to ideas, as usual.

Thanks! Спасибо! Köszönöm, even!

Hi,

LOG_STAGING_DIR can be change in memory only - https://www.ibm.com/docs/en/informix-servers/14.10.0?topic=parameters-log-staging-dir-configuration-parameter

onstat -g cfg full LOG_STAGING_DIR and get the current value

Use onsecurity with -d and the current value of LOG_STAGING_DIR to check permissions.

As per the link above 

"The directory must be owned by user informix, must belong to group informix, and must not have public read, write, or execute permission."

Permission 770 works with 14.10  last time I checked.

Regards,

David.

This has got to be one of the weirder errors I've recently encountered.  I've had weirder but not recently. ;-)

We are trying to start up a new installation of release IDS-14.10 on a host and have set up the onconfig similar to onconfig files where it has been successful.  One error message complains when we try to come up:

ERROR: The requested log staging directory is not secure or does not exist.

To display the path name here might be a confidence breach.  However, looking at the onconfig of a 12.10 instance on the same host, we are specifying the same full path. (No, they're NOT both up at the same time.) Ownership is informix:informix and permissions are 770, just as they are on all other hosts in our environment.

This sounds like a red-herring error message - the problem lies elsewhere.  After all, we do have a running (test) server with the identical setting ad permissions and no complaints there.

We got the server up by commenting out LOG_STAGE_DIR but we need to be able to use it; this server is intended as part of an RSS pair.

Hey, I'm open to ideas, as usual.

Thanks! Спасибо! Köszönöm, even!