Return to Question

• syslog-ng was running and logging (installed, not a default).
• crond was confirmed running (by rc-service crond status).
• crontab entry was valid and present for root.
• crond was NOT sending any CRON messages to syslog-ng, even after explicit restarts
• Installed and reinstalled Cornie, Deleted the .Pid files (/run/cronie.pid ; /var/run/cronie.pid)

• syslog-ng was running and logging (installed, not a default).
• crond was confirmed running (by rc-service crond status).
• crontab entry was valid and present for root.
• Ownership (chown), Mode (chmod) and UID, GID all are in favour of root in the Script, log and cron (cornie-service / crond)
• crond was NOT sending any CRON messages to syslog-ng, even after explicit restarts
• Installed and reinstalled Cornie, Deleted the .Pid files (/run/cronie.pid ; /var/run/cronie.pid)

Here I am providing the script, as there is a suspicion regarding this--- This is under root cron so privileges are not an issue.

Here I am providing the script, as there is a suspicion regarding this

This is under root cron so privileges are not an issue.

Synopsis:
syslog-ng is running and logging (installed, not a default). crond is confirmed running (by rc-service crond status). crontab entry is valid and present for root. But crond was NOT sending any CRON messages to syslog-ng, even after explicit restarts, and your job is not executing. Installed and reinstalled Cornie, Deleted the .Pid files (/run/cronie.pid ; /var/run/cronie.pid)

Synopsis:

• syslog-ng was running and logging (installed, not a default).
• crond was confirmed running (by rc-service crond status).
• crontab entry was valid and present for root.
• crond was NOT sending any CRON messages to syslog-ng, even after explicit restarts
• Installed and reinstalled Cornie, Deleted the .Pid files (/run/cronie.pid ; /var/run/cronie.pid)