12-09-2016, 02:02 AM
Hi
Adiditonaly to CSF RESTRICT_SYSLOG, once changed the option, you may have to change the permissio to 666 for /dev/log.
Reply from one of the cpanel techs
===========================
Non-default Perms: /dev/log [mode 0660] (default 0666) - CSF RESTRICT_SYSLOG can change this. Non-root users may not be able to log to syslog, including user cron jobs to /var/log/cron.
This may possibly be the cause of the crons to fail to properly load. I changed the permissions for the /dev/log file to 666 now so lets check to see if crons now run
[01:40:13 server101 root@7878233 /dev]cPs# stat log
File: `log'
Size: 0 Blocks: 0 IO Block: 4096 socket
Device: 5h/5d Inode: 9592 Links: 1
Access: (0660/srw-rw----) Uid: ( 0/ root) Gid: ( 494/mysyslog)
Access: 2016-11-03 01:59:01.741000037 -0400
Modify: 2016-11-02 01:58:43.860755866 -0400
Change: 2016-11-02 01:58:46.211755864 -0400
[01:40:15 server101 root@7878233 /dev]cPs# chmod 666 log
[01:40:23 server101 root@7878233 /dev]cPs#
Adiditonaly to CSF RESTRICT_SYSLOG, once changed the option, you may have to change the permissio to 666 for /dev/log.
Reply from one of the cpanel techs
===========================
Non-default Perms: /dev/log [mode 0660] (default 0666) - CSF RESTRICT_SYSLOG can change this. Non-root users may not be able to log to syslog, including user cron jobs to /var/log/cron.
This may possibly be the cause of the crons to fail to properly load. I changed the permissions for the /dev/log file to 666 now so lets check to see if crons now run
[01:40:13 server101 root@7878233 /dev]cPs# stat log
File: `log'
Size: 0 Blocks: 0 IO Block: 4096 socket
Device: 5h/5d Inode: 9592 Links: 1
Access: (0660/srw-rw----) Uid: ( 0/ root) Gid: ( 494/mysyslog)
Access: 2016-11-03 01:59:01.741000037 -0400
Modify: 2016-11-02 01:58:43.860755866 -0400
Change: 2016-11-02 01:58:46.211755864 -0400
[01:40:15 server101 root@7878233 /dev]cPs# chmod 666 log
[01:40:23 server101 root@7878233 /dev]cPs#