PJ wrote: > On Fri, Mar 11, 2011 at 2:33 PM, <m.r...@5-cent.us> wrote: >> PJ wrote: >>> On Fri, Mar 11, 2011 at 11:05 AM, Steve Thompson <s...@vgersoft.com> >>> wrote: >>>> >>>>> PJ wrote: >>>>>> Mar 8 03:33:18 web1 kernel: INFO: task wget:13608 blocked for more >> than 120 seconds. >> <snip> >>> Great replies from everyone, I really appreciate the feedback. >>> >>> Interesting entries in /var/log/cron: >> <snip> >>> Mar 11 03:01:01 web1 crond[13613]: (root) CMD (run-parts >> /etc/cron.hourly) Mar 11 03:07:20 web1 crond[13727]: (webuser) error: >> Job execution of per-minute job scheduled for 03:05 delayed into >> subsequent minute 03:07. Skipping job run. >>> Mar 11 03:07:20 web1 crond[13727]: CRON (webuser) ERROR: cannot set >> security context >> <snip> >> SELINUX! Look at /var/log/messages for an selinux error: if you don't >> have sealert, install the package, then use it on /var/log/audit. >> >> Or put selinux in permissive mode. > > I thought about that :) > > [root@web1 ~]# sestatus > SELinux status: disabled > > It's already disabled and always has been.
acl's? mark _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
