search for: 428e

...and it gives me: setfacl: Option -m: Invalid argument near character 3 I've spent hours googling trying to find some indication as to what is going on but I can't seem to figure out what is happening. My filesystem is mounted with the necessary options: UUID=f45e8060-3a37-428e-9e6c-680012a87009 /home/shares ext4 user_xattr,acl,barrier=1,rw 1 1 I also did the acl test from this wiki article: https://wiki.samba.org/index.php/OS_Requirements#Testing_Your_Filesystem and it was successful. I'm missing some piece of information but I can't figure out wh...

...alert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from getattr access on the directory /proc/<pid>. For complete SELinux messages. run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from search access on the directory /proc/<pid>/stat. For complete SELinux messages. run sealert -l 2448a46d-5089-4f85-aae8-e9013341471f Dec 2 10:04:05 server setroubleshoot: last message repeated 2 times...

...> > Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times > > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > > getattr access on the directory /proc/<pid>. For complete SELinux > messages. > > run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc > > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > > search access on the directory /proc/<pid>/stat. For complete SELinux > > messages. run sealert -l 2448a46d-5089-4f85-aae8-e9013341471f > > Dec 2 10:04:05 server setrou...

...oubleshoot: last message repeated 2 times > >>> Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps > from > >>> getattr access on the directory /proc/<pid>. For complete SELinux > >> messages. > >>> run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc > >>> Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps > from > >>> search access on the directory /proc/<pid>/stat. For complete SELinux > >>> messages. run sealert -l 2448a46d-5089-4f85-aae8-e9013341471f > >&...

...b2-433a-aaa2-361cc95b6069 > Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > getattr access on the directory /proc/<pid>. For complete SELinux messages. > run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > search access on the directory /proc/<pid>/stat. For complete SELinux > messages. run sealert -l 2448a46d-5089-4f85-aae8-e9013341471f > Dec 2 10:04:05 server setroubleshoot: last messa...

...c 2 10:04:04 server setroubleshoot: last message repeated 2 times >>> Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from >>> getattr access on the directory /proc/<pid>. For complete SELinux >> messages. >>> run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc >>> Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from >>> search access on the directory /proc/<pid>/stat. For complete SELinux >>> messages. run sealert -l 2448a46d-5089-4f85-aae8-e9013341471f >>> Dec 2 10:04:05 s...

We are currently running libxml2-2.7.6-14.el6_5.2.x86_64 How far back would you suggest we go? would libxml2-2.7.6-14.el6_5.1.x86_64 be sufficient -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Daniel J Walsh Sent: 01 December 2014 15:10 To: CentOS mailing list Subject: Re: [CentOS] SEtroubleshootd Crashing I am not sure. I was