Monday, May 3, 2021

R12.2 adautocfg.sh fails with AC-00444: Unable to write to file

Suddenly, R12.2 autoconfig failed with below message in log file $INST_TOP/admin/log/0X131006/adconfig.log:

   [INSTANTIATE PHASE]

  AutoConfig could not successfully instantiate the following files:
    Directory: $INST_TOP/admin/install
          adadmprf.sh             INSTE8_PRF
          adapperms.sh           INSTE8_APPLY
          adgendbc.sh             INSTE8_SETUP
  adgenjky.sh              INSTE8_SETUP
  admkpltfrm.sh          INSTE8_PRF
  admkxdir.sh             INSTE8_SETUP
  adsvcm.sh                INSTE8_APPLY
  afadmprf.sh             INSTE8_PRF
  afcpctx.sh                INSTE8_PRF
  afcpgsm.sh              INSTE8_PRF
  afcpnode.sh             INSTE8_SETUP
  afgcsreg.sh              INSTE8_SETUP
  ibywebprf.sh           INSTE8_PRF
  igccmprf.sh             INSTE8_PRF
  java.sh                    INSTE8
  jtfictx.sh                  INSTE8_PRF
  jtfsvfm.sh                INSTE8_APPLY
  okladmprf.sh           INSTE8_PRF
  shttimezone.sh        INSTE8_SETUP
  txkJavaMailerCfg.sh     INSTE8_PRF
  txkWebServicescfg.sh    INSTE8_PRF
    Directory: $INST_TOP/admin/scripts/msc
          mscmatlab.sh            INSTE8_PRF  

Seems those .sh files are randomly picked up. Log file has also message:

AC-00444: Unable to write to file: java.io.FileNotFoundException: $INST_TOP/admin/install/adadmprf.sh (Text file busy)
Raised by oracle.apps.ad.autoconfig.InstantiateProcess

After trying different ways to troubleshoot it, I suspected it is caused by something on the OS level. 

Finally, Linux Admin found it is CrowdStrike falcon-sensor, a security tool for monitoring.

$ ps -ef | grep falcon
root      1027        1  0 May1 ?        00:00:00 /opt/CrowdStrike/falcond
root      1028  1027  0 May1 ?        00:00:17 falcon-sensor

After disabled it and rebooted the server, adautocfg.sh worked successfully. 

We found it also made EBS Rapid Install for R12.2 upgrade fail with strange errors. I was told the bug in CrowdStrike was fixed later.

No comments: