Displaying 13 results from an estimated 13 matches for "4fd5".
Did you mean:
4fd3
2018 Sep 20
2
Re: Which objects does dynamic_ownership apply to?
...host devices such as USB and PCI devices? For example
<hostdev managed="no" mode="subsystem" type="usb">
<source>
<address bus="3" device="2" />
</source>
<alias name="ua-3773b389-54be-4fd5-ae8b-2f954470b1a9" />
<address bus="0" port="1" type="usb" />
</hostdev>
doesn't change the owner of /dev/bus/usb/003/002 (the same for
managed="yes"). Similarly for a PCI hostdev device /dev/vfio/* owners
are not changed. D...
2018 Sep 20
0
Re: Which objects does dynamic_ownership apply to?
...PCI devices? For example
>
> <hostdev managed="no" mode="subsystem" type="usb">
> <source>
> <address bus="3" device="2" />
> </source>
> <alias name="ua-3773b389-54be-4fd5-ae8b-2f954470b1a9" />
> <address bus="0" port="1" type="usb" />
> </hostdev>
>
> doesn't change the owner of /dev/bus/usb/003/002 (the same for
> managed="yes").
Are you perhaps using namespaces and looking in...
2018 Sep 19
2
Which objects does dynamic_ownership apply to?
Hi, I'm playing with dynamic ownership and not all objects have their
owners changed.
Is dynamic_ownership and its scope documented somewhere, besides the
comment in qemu.conf?
And what kinds of objects are handled by dynamic ownership? While some
objects seem to be handled, other objects are apparently unaffected.
For instance /dev/hwrng or a USB host device keep their root owners and
are
2014 Dec 02
2
SEtroubleshootd Crashing
...irectory /proc/<pid>. For complete SELinux messages.
run sealert -l f935416b-54fe-4bbd-b66c-2e1b2e6724be
Dec 2 10:04:06 server setroubleshoot: SELinux is preventing /bin/ps from
search access on the directory /proc/<pid>/stat. For complete SELinux
messages. run sealert -l d8dbf973-7bc2-4fd5-9540-18c4040be03c
Dec 2 10:04:06 server setroubleshoot: last message repeated 2 times
Dec 2 10:04:06 server sedispatch: AVC Message for setroubleshoot, dropping
message
Dec 2 10:04:06 server sedispatch: last message repeated 3 times
Cheers,
John
On 1 December 2014 at 17:19, Daniel J Walsh <...
2014 Dec 03
2
SEtroubleshootd Crashing
...nux
> messages.
> > run sealert -l f935416b-54fe-4bbd-b66c-2e1b2e6724be
> > Dec 2 10:04:06 server setroubleshoot: SELinux is preventing /bin/ps from
> > search access on the directory /proc/<pid>/stat. For complete SELinux
> > messages. run sealert -l d8dbf973-7bc2-4fd5-9540-18c4040be03c
> > Dec 2 10:04:06 server setroubleshoot: last message repeated 2 times
> > Dec 2 10:04:06 server sedispatch: AVC Message for setroubleshoot,
> dropping
> > message
> > Dec 2 10:04:06 server sedispatch: last message repeated 3 times
> >
> >...
2014 Dec 03
1
SEtroubleshootd Crashing
...run sealert -l f935416b-54fe-4bbd-b66c-2e1b2e6724be
> >>> Dec 2 10:04:06 server setroubleshoot: SELinux is preventing /bin/ps
> from
> >>> search access on the directory /proc/<pid>/stat. For complete SELinux
> >>> messages. run sealert -l d8dbf973-7bc2-4fd5-9540-18c4040be03c
> >>> Dec 2 10:04:06 server setroubleshoot: last message repeated 2 times
> >>> Dec 2 10:04:06 server sedispatch: AVC Message for setroubleshoot,
> >> dropping
> >>> message
> >>> Dec 2 10:04:06 server sedispatch: last me...
2014 Dec 02
0
SEtroubleshootd Crashing
...id>. For complete SELinux messages.
> run sealert -l f935416b-54fe-4bbd-b66c-2e1b2e6724be
> Dec 2 10:04:06 server setroubleshoot: SELinux is preventing /bin/ps from
> search access on the directory /proc/<pid>/stat. For complete SELinux
> messages. run sealert -l d8dbf973-7bc2-4fd5-9540-18c4040be03c
> Dec 2 10:04:06 server setroubleshoot: last message repeated 2 times
> Dec 2 10:04:06 server sedispatch: AVC Message for setroubleshoot, dropping
> message
> Dec 2 10:04:06 server sedispatch: last message repeated 3 times
>
> Cheers,
>
> John
>
>...
2014 Dec 03
0
SEtroubleshootd Crashing
...sages.
>>> run sealert -l f935416b-54fe-4bbd-b66c-2e1b2e6724be
>>> Dec 2 10:04:06 server setroubleshoot: SELinux is preventing /bin/ps from
>>> search access on the directory /proc/<pid>/stat. For complete SELinux
>>> messages. run sealert -l d8dbf973-7bc2-4fd5-9540-18c4040be03c
>>> Dec 2 10:04:06 server setroubleshoot: last message repeated 2 times
>>> Dec 2 10:04:06 server sedispatch: AVC Message for setroubleshoot,
>> dropping
>>> message
>>> Dec 2 10:04:06 server sedispatch: last message repeated 3 times
&g...
2014 Dec 01
2
SEtroubleshootd Crashing
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
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...7031FC449608F7E (e581de1f-3254-417c-bf62-4b4cfd7f4746) on home-client-2
[2017-10-25 10:14:11.568964] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/BA952A77E94CC1360FCBCCB5DC77E8A71F460D57 (d8271097-d983-4fd5-b86b-9db8378fadde) on home-client-2
[2017-10-25 10:14:11.587953] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/7AFA8E17B0BC31500A79EE306166CDF6AFD25758 (00cfccc5-4834-4b14-ad0c-24cca34455cc) on home-cli...
2012 May 08
6
registry vulnerabilities in R
...rotocol=6|Profile=Public|RPort=445|RA4=LocalSubnet|RA6=LocalSubnet|App=System|Name=@FirewallAPI.dll,-28515|Desc=@FirewallAPI.dll,-28518|EmbedCtxt @FirewallAPI.dll,-28502|"
HKEY_LOCAL_MACHINE\System\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules "{316BC912-86CD-4FD5-82DA-92A56D189306}"="v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Public|LPort=445|RA4=LocalSubnet|RA6=LocalSubnet|App=System|Name=@FirewallAPI.dll,-28511|Desc=@FirewallAPI.dll,-28514|EmbedCtxt @FirewallAPI.dll,-28502|"
HKEY_LOCAL_MACHINE\System\ControlSet001\services\Sha...