Diagnosing Failed Cron job via server logs

-
  1. Open your preferred your ssh client. If you need an ssh client, we recommend PuTTY. You can download it here.
  2. Log into your server via your ssh client.
  3. Once logged in as the root user, use the following command to check the log for the cron script. The command will use the following format: grep "script.php" /path/file.ext. For instance, the code below is looking for the script cronscript.php in the cron.log file, which is in the /var/log folder.

    grep "cronscript.php" /var/log/cron
  4. Hit Enter after that and the results, if any, will display like below:

    Feb 24 02:33:02 ecbiz108 crond[9772]: (userna5) CMD (php -q /home/userna5/public_html/cronscript.php)
    Feb 25 02:33:01 ecbiz108 crond[16587]: (userna5) CMD (php -q /home/userna5/public_html/cronscript.php)
    Feb 25 11:45:01 ecbiz108 crond[21887]: (userna5) CMD (php -q /home/userna5/public_html/cronscript.php)
  5. Looking at the output, you will see the date and time the cron job has run. This is followed by the server name, cron ID, the cpanel username, and the command that ran. At the end of the command, you will see the name of the script.

ref: http://www.inmotionhosting.com/support/website/cron-jobs/did-cron-job-run




Comments

Post a Comment

Popular posts from this blog

RMAN backup Status (Remaining Time and Percentage)

-
On Running a huge database backup we often need to know the status of backup. 1) How much backup is taken. 2) How much is remain. 3) Estimate time to complete the backup. After lot of search i find out this amazing query below. col dbsize_mbytes for 99,999,990.00 justify right head "DBSIZE_MB" col input_mbytes for 99,999,990.00 justify right head "READ_MB" col output_mbytes for 99,999,990.00 justify right head "WRITTEN_MB" col output_device_type for a10 justify left head "DEVICE" col complete for 990.00 justify right head "COMPLETE %" col compression for 990.00 justify right head "COMPRESS|% ORIG" col est_complete for a20 head "ESTIMATED COMPLETION" col recid for 9999999 head "ID" select recid , output_device_type , dbsize_mbytes , input_bytes/1024/1024 input_mbytes , output_bytes/1024/1
Read more

EBS R12.2 Autoconfig Failed. Resolved

-
Hi, Please do the following and retest the issue: Due to the method required for "cleaning out" / "re-synchronizing" the following tables, it is EXPECTED / REQUIRED that the Applications have been shutdown. The only thing running should be the Database Tier. Note: A full backup should also be taken before any testing begins. Test the following steps in a development instance, and then migrate accordingly once the desired result is confirmed: 1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables in the EBS env: sqlplus applsys/pwd create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files; create table fnd_nodes_bk as select * from fnd_nodes; create table adop_valid_nodes_bk as select * from adop_valid_nodes; 2. Truncate the following tables: truncate table fnd_oam_context_files; truncate table fnd_nodes; truncate table adop_valid_nodes; 3. Run AutoConfig on the DB tier
Read more

Cleaning nodes in EBS databae.

-
Cleaning EBS nodes with EXEC FND_CONC_CLONE.SETUP_CLEAN; . EBSapps.env run   $ sqlplus apps/<PASSWORD> SQL> create table fnd_nodes_22ep14 as select * from fnd_nodes; SQL> exec fnd_conc_clone.setup_clean; PL/SQL procedure successfully completed. SQL> commit; Commit complete. After that run autoconfig in below order to populate the FND TABLES properly. 1) Stop application services ( optional but  recommended )  2) Run autoconfig on dbTier 3) Run autoconfig on appTier
Read more