RW Cronacle : OS Account and requested OS Account

[Former Member]

Hello everyone,

I would like to know how the parameter OS Account is set in the "Scheduling behavior" ?

Actually we have a job that fails and the error log tells this :

JCS-00579: we tried to use the OS user given by the credentials (cronconf)

JCS-00590: we cannot switch to user cronconf

JCS-00586: no fallback allowed when explicit credentials are specified

JCS-00270: master agent is not able to start this job

Actually we have declared cronconf as an "enabled_os_users" in the init file but the script still fails, how can we fix that ?

Thanks for your help.

Regards.

[gmblom]

Hello,

1) Does OS user cronconf exist on the machine of the Scheduler where the job is executed?

2) Is the scheduler installed to enable user switching (is the set-uid bit set on the RS executable of this scheduler)? Check ls -l $JCS_HOME/bin/rs

Regards Gerben

[Former Member]

Hello Gerben,

1) Does OS user cronconf exist on the machine of the Scheduler where the job is executed? >> Actually, the user does exists on the target scheduler.

2) Is the scheduler installed to enable user switching (is the set-uid bit set on the RS executable of this scheduler)? Check ls -l $JCS_HOME/bin/rs >> The set-uid bit is not set, but we never had needed to set it.

Here is the result of ls command :

-rwxxx 2 root dba 3152080 May 21 15:09 /distrib/cronacle/704/bin/rs

This error never happened until Cronacle has been upgraded to 7.0.4, the script always used the OS account when it's specified in the script (i.e. here cronconf), otherwise the script used cronacle as the default OS account.

Here are all Redwood software components :

JCS Redwood Reports Module 7.0.2 Production Cronacle Reports Module

JCS Redwood Mail Module 7.0.2 Production Cronacle Mail Module

JCS PM4W 7.0.2 Production Cronacle Process Manager for Web

JCS RSI 7.0.4 SP3 production Cronacle for SAP solutions

JCS CATREM 7.0.3 Production Cronacle for catrem

JCS Object Database 7.0.4.51 SP4 Production Cronacle Repository

JCS Modules 7.0.4 SP4 Production Cronacle Module Installer

Thanks a lot.

Regards

Scheduling team

[Former Member]

Gerben,

Maybe there was a mistake during the installation of the upgrade, at the phase of setuid, the option 2 may had been selected.

Do you know if we have to reinstall the process server from the start or do we have a solution to workaround this ?

Product:   Redwood Cronacle Version 7.0.3 Production build 20071113
Copyright: (C) Copyright 1993-2007 Redwood Technology B.V., Houten, The Netherlands
Phase:     setuid
Platform:  linux-i686-2.3
Logfile:   /home/masalan/Cronacle_install/cr703-setup.log
--------------------------------------------------------------------------------
* Decide which Unix account the Redwood Cronacle jobs will use

        1. Run jobs using an Unix account derived from the
           Redwood Cronacle User's Oracle account.
           (needs root password to make rs setuid-root) (recommended)

        2. Run jobs using the Unix account that started the scheduler

        Answer: [12](1)

Thank you a lot.

Regards

Scheduling team.

[gmblom]

Hello,

Yes you can run the installer again, or you can manually chmod the rs executable to the same settings (I think 4711 if I remember correctly) as on a machine where all is ok.

Regards Gerben

[Former Member]

Hello Gerben,

Thanks for your answer, we have modified the settings for the /distrib/cronacle/704/bin/rs file, set the setuid right for the owner and the group.

The switch between users defined in Cronacle repository is OK.

Thanks for your help.

Regards,

Scheduling team.