similar to: TDM400p Loaded only once

Hello, I received the below SELinux message today and I am trying to figure out what caused it. I see what it says under Allow Access but I am not sure this is what I really want to do without know why it happened in the first place. What should I be looking at to understand what or why this has happened? Any help I would be most grateful for. Here is the output form SELinux SUMMARY:

All of a sudden, Virtual Machine Manager (VMM) on a CentOS 5.7 load will no longer run any VMs. The VM worked A-OK on the morning of 23 Feb, when I brought it up, applied the Microsoft updates, rebooted it, installed an application, rebooted again and ran several tests. Later that day, it wouldn't run. I didn't have time to diagnose, so I did some investigation a few minutes ago. Working

Daniel P. Berrangé <berrange@redhat.com> writes: > On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >> Hi, >> > >> I've met two situations with NVDIMM support in libvirt where I'm not >> sure all the parties (libvirt & I) do the things correctly. >> >> The first problem is with memory alignment and size changes. In

Milan Zamazal <mzamazal@redhat.com> writes: > Daniel P. Berrangé <berrange@redhat.com> writes: > >> On Thu, Jul 02, 2020 at 01:21:15PM +0200, Milan Zamazal wrote: >>> The second problem is that a VM fails to start with a backing NVDIMM in >>> devdax mode due to SELinux preventing access to the /dev/dax* device (it >>> doesn't happen with any

I run a sshd host solely to allow employees to tunnel secure connections to our internal hosts. Some of which do not support encrypted protocols. These connections are chroot'ed via the following in /etc/ssh/sshd_config Match Group !wheel,!xxxxxx,yyyyy AllowTcpForwarding yes ChrootDirectory /home/yyyyy X11Forwarding yes Where external users belong to group yyyyy (primary). We

This is probably a known issue, but just in case. On my Desktop, I am running SELinux in Permissive mode. When I restart the system, or shut it down, I notice this message: "Stopping setroubleshootd failed". Notice at the end of the dmseg output below, regarding SELinux, there are three (3) identical lines. I don't know if that is normal or not. [lanny at dell2400 ~]$ dmesg |more

This happened a few times now, I (soft) reboot and do the fsck thing and all is fine until it happens again. Any ideas? [root at test-dhcp ~]# yum remove bluez-libs bluez-utils Loaded plugins: fastestmirror Setting up Remove Process Resolving Dependencies <snip/> Finished Transaction Test Transaction Test Succeeded Running Transaction Erasing : bluez-utils 1/3 Erasing :

I have a simple manifest that I''m using to keep unwanted services from running on an array of Linux systems. On my test host, I see these two services repeatedly come up in the puppet.log, even tho they are not running and are chkconfig set to off: service { "cups": enable => false, ensure => stopped, } service {

2011/6/27 Frederic BOHE <fbohe-guest at alioth.debian.org> > Author: fbohe-guest > Date: Mon Jun 27 13:56:51 2011 > New Revision: 3060 > URL: http://trac.networkupstools.org/projects/nut/changeset/3060 > > Log: > Add NUT server scan. > > (...) > device_t * scan_snmp(char * start_ip, char * stop_ip,long usec_timeout, > snmp_security_t * sec); > >

Hi, I haven't tried the code yet. Is there a way to parse this data using R and create bar plots so that each program's 'RAM used' figures are grouped together. So 'uuidd' bars will be together. The data will have about 50 sets. So if there are 100 processes each will have about 50 bars. What is the recommended way to graph these big barplots ? I am looking

As an update it states the following when booting either rhel4, fc3 or fc4 under xen? Not sure if the "unable to open an initial console" is the real issue, this doesn''t happen under fc1, or rhel 3. Can anyone help please Freeing unused kernel memory: 152k freed Warning: unable to open an initial console. ***************************************************************

At the risk of angering the crash Gods, my sustem has NOT crashed again since I downgraded the kernel from 2.6.18-1.2239.fc5 to 2.6.18-1.2200.fc5. Given that newfound stability, and my lack of time, I'm going to put on hold any further diagnostics, until the next kernel revision is released. I have submitted a report at bugzilla.redhat.com (bug 218128). (Ah, nuts; accidentally created a

Hi all, I installed Performance Co-Pilot 3 days ago, and installed the nVidia PMDA according to the instructions at https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Performance_Tuning_Guide/ch03s03s02.html and was able to view metrics about my video card using pmchart. I then played around a little with the lmsensors PMDA (but it doesn't look too useful to me -

I have a Windows Server 2003 system I'm trying to back up to a Linux host. when I access the share with smbclient, I can "see" the files (`ls` returns a list of files, etc) smbclient -U shareuser //server/sharename password But, when I try to actually mount the drive, I get "permission denied" errors trying to access the drive. (EG: using `df`) Running the following

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot

I am wondering what is the interaction between SE Linux and the kernel "capabilities" in CentOS 5.1? I'm trying to open a raw socket and keep getting permission denied errors. I've tried using the lcap library to find that CAP_SETPCAP appears to be off in the kernel. For compliance reasons, I don't want to turn this on. I've also tried a hand-crafted SE Linux

Hey I wanted to try my hand at doing some GPU passthrough so on my ASUS M5A97 which in the pass worked with an older BIOS (but said BIOS had issues after S3 suspend) - but with a BIOS the PCI passthrough does not work. That is due to:: (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization

Hi all, On my newly up-and-running nameserver (CentOS 5), I noticed the following alerts in /var/log/messages after restarting BIND. (lines inserted to aid in reading). As I'm new to SELinux, I'm hoping for some pointers on 1) if this is an issue which simply *must* be addressed, or if it's something I should live with, and 2) how to eliminate the warming messages without sacrificing

Today is my day! This is with Xen 4.4 (pulled today) when I build a kernel in dom0 and have two guests launching at the same time. This is what I get: (XEN) Assertion ''l1e_get_pfn(MAPCACHE_L1ENT(hashent->idx)) == hashent->mfn'' failed at domain_page.c:203 and it blows up. Here is the full log: \ \/ /___ _ __ | || | | || | _ _ _ __ ___| |_ __ _| |__ | | ___

Hello! I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). FreeBSD 6.3-STABLE was running fine on it, but I decided to update the machine to 9.1-STABLE. Well, neither my own custom kernel, nor even the official 9.1-RELEASE CD1 would boot... In both cases the boot process runs up to detecting uhub0, then either hangs forever or shuts off after a short while. Again, I thought I