Chris | 31 Oct 07:00 2014

CentOS 6.6: KVM not found

Dear All,

since upgrading from 6.5 to 6.6 I get the following error message when
trying to start a VM in virt-manager:

	Error starting domain: unsupported configuration: Domain
	requires KVM, but it is not available. Check that
	virtualization is enabled in the host BIOS, and host
	configuration is setup to load the kvm modules.

Qemu-kvm package is installed, kvm module is loaded and virtualization
is activated in BIOS.

Does anyone happen to know what the issue is?

--

-- 
Gruß,
Christian
_______________________________________________
CentOS mailing list
CentOS <at> centos.org
http://lists.centos.org/mailman/listinfo/centos
david | 31 Oct 02:47 2014

ZFS Scrubbing (might be off topic)

Folks

I have a ZFS file system.  It seems to be scrubbing too often.  As I 
type, it's 5 hours into the process with 36 hours to go, and seems to 
be doing it several times a week on a slow drive.

I cannot find an option to control the frequency; crontab has no 
references.  Any clues?

David
david | 31 Oct 01:45 2014

Centos7 Annoyances

Folks

I'm sure the Centos team has done a yeoman's job getting Centos7 
ready, and that the Redhat team has done marvels in creating rhel7, 
but here's a little voice from a personal hobbyist user.

Background:
  ('ve been maintaining several remote servers since Redhat 6 days, 
migrating from that to Whitebox, then Centos, and things have been 
running as expected including the current version of Centos6.  As an 
experiment, I've tried to play with Centos7 on an in-house virtual 
machine (VMWare on Win7), and have encountered a collection of 
annoyances greater than I've even seen.  Below is a note about 
them.  If someone has some elegant solution, I'd love to try, but 
Centos7 is still unusable for me.

1:  Firewall changes
  The change in firewall technology forced a complete re-do of my 
scripts which maintain firewalls, respond to attacks, etc.  I think 
I've programmed my way around the issues, but it wasn't easy.

2:  Apache changes
  These were subtle, but again were solved.

3:  Service -> systemd
  The change from object-oriented view of service:  (service httpd 
restart) to function-oriented (systemctl restart firewall) seems to 
be unnecessary, and counter to the way stuff is generally done in the 
modern world.  Nonetheless, it was possible to solve that with some 
adaptive script programming.
(Continue reading)

Negative | 30 Oct 23:54 2014
Picon

legacy-x

I recently installed Centos 7 on a new desktop, and I intended to put XFCE
on it, but I think I made a mistake by choosing the Legacy-X group, and now
I'm puzzled as to what I have.

I thought my first boot would be into runlevel 3, but I got a gui that
looks like an odd mix of Gnome 2 and KDE. The anaconda logs show a group
install of gnome-desktop and legacy-x, plus a lot of KDE stuff.

The mix looks ok, and handles my dual monitors fine, but there are some
prefs that simply don't work -- one important bit is that my monitors
mostly (but sometimes) go into power save, and I cannot find an option to
do it manually.

One option now is to install XFCE, but I don't know how that works. Maybe
better to uninstall gnome-desktop and legacy-x and just go with XFCE, and
I'll wind up with a coherent environment. Btw, I've tried both Gnome 3 and
xfce on an old machine in fedora, and much prefer XFCE. (Luckily, we have
choices.)

Any guidance?
Paul Heinlein | 30 Oct 20:01 2014

CentOS 6.6 Bacula-SELinux issue

I updated my backup server to CentOS 6.6 this morning. As usual, I 
unmounted the current (nightly) tape from the changer before the 
reboot. Now Bacula complains it cannot access the changer:

3301 Issuing autochanger "loaded? drive 0" command.
3991 Bad autochanger "loaded? drive 0" command: ERR=Child exited with code 1.
Results=cannot open SCSI device '/dev/changer' - Permission denied

SELinux is denying source context bacula_t from accessing target 
context tape_device_t. I took a look at the various SELinux boolean 
values but see none that applies.

Has anyone else observed this symptom since upgrading?

Is there a fix other than building a local policy by going through the 
"ausearch | audit2allow" iteration(s)?

--

-- 
Paul Heinlein
heinlein@...
45°38' N, 122°6' W
_______________________________________________
CentOS mailing list
CentOS@...
http://lists.centos.org/mailman/listinfo/centos
Leonard den Ottolander | 30 Oct 16:49 2014
Picon

Corrupt selinux-policy-targeted-3.7.19-260.el6.noarch.rpm

Hi,

Updating selinux-policy-targeted to 3.7.19-260 fails. The archive seems
corrupt. Got another copy from
http://mirror.centos.org/centos/6/os/x86_64/Packages/ which also fails:

# rpm -Fv selinux-policy-targeted-3.7.19-260.el6.noarch.rpm 
Preparing packages for installation...
selinux-policy-targeted-3.7.19-260.el6
warning: /etc/selinux/targeted/contexts/customizable_types saved
as /etc/selinux/targeted/contexts/customizable_types.rpmsave
error: unpacking of archive failed on
file /usr/share/selinux/targeted/audioentropy.pp.bz2: cpio: rename
failed - Input/output error

Regards,
Leonard.

--

-- 
mount -t life -o ro /dev/dna /genetic/research
centos | 30 Oct 13:00 2014

CentOS-announce Digest, Vol 116, Issue 15

Send CentOS-announce mailing list submissions to
	centos-announce@...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
	centos-announce-request@...

You can reach the person managing the list at
	centos-announce-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."

Today's Topics:

   1. CEEA-2014:1733 CentOS 6 tzdata Enhancement Update (Johnny Hughes)
   2. CEEA-2014:1733 CentOS 7 tzdata Enhancement Update (Johnny Hughes)
   3. CEEA-2014:1733 CentOS 5 tzdata Enhancement Update (Johnny Hughes)

----------------------------------------------------------------------

Message: 1
Date: Wed, 29 Oct 2014 20:15:10 +0000
From: Johnny Hughes <johnny@...>
To: centos-announce@...
Subject: [CentOS-announce] CEEA-2014:1733 CentOS 6 tzdata Enhancement
	Update
Message-ID: <20141029201510.GA8722@...>
Content-Type: text/plain; charset=us-ascii
(Continue reading)

Johan Vermeulen | 30 Oct 12:20 2014
Picon

lost a lvm after update to Centos6.6

Hello All,

the update to Centos6.6 got interrupted on a laptop.
I then did this:
package-cleanup --cleandupes
yum-complete-transaction
and remove and reinstall the latest kernel.

I now get an error message when booting:
/dev/mapper/vg_jvermeulen-lv_home does not exist.

I can boot into single user mode and run all commands.

in fdisk -l .....lv_home is not listed.

How can I re-add this?
I do have a backup of this machine.

Thanks for any help.

Greetings, Johan

--

-- 
Johan Vermeulen
IT-medewerker
Caw De Kempen
johan.vermeulen@...
0479.82.01.41

Powered by Linux.
(Continue reading)

Jason T. Slack-Moehrle | 30 Oct 01:50 2014
Picon

CentOS 6.5 equivalents in CentOS 7

I tried to install CentOS 7 on a new system. It works.

However, I'm noticing small things:
1. system-config-network-tui is not installed and yum cannot find it. I
realized for this -- nmtui

What about firewall? I can't seem to understand the replacement from
system-config-firewall-tui

Jason
Steven Stern | 29 Oct 23:16 2014

Re: Cannot get php errors to go to a file


On 10/29/2014 04:07 PM, Reindl Harald wrote:
> 
> Am 29.10.2014 um 19:54 schrieb Steven Stern:
>> Using basically the same setup that works on C6, I have a C7 site.
>>
>> in PHP.INI, it says "error_log = /tmp/php_errors.log"
>>
>> PHP errors do not go there (or anywhere).
>>
>> 1. Apache has write perms to /tmp
>> 2. I have restarted httpd since changing php.ini
>> 3. The base php.ini is from the development version in /usr/share
>> 4. Selinux is disabled
> 
> "PrivateTmp=true" works as you can see
> using /tmp for logfiles is plain stupid

OK ... final message. I'm logging to syslog which seems both secure and
readily findable.

> 

--

-- 
-- Steve
Steven Stern | 29 Oct 23:10 2014

Re: Cannot get php errors to go to a file


On 10/29/2014 04:07 PM, Reindl Harald wrote:
> 
> Am 29.10.2014 um 19:54 schrieb Steven Stern:
>> Using basically the same setup that works on C6, I have a C7 site.
>>
>> in PHP.INI, it says "error_log = /tmp/php_errors.log"
>>
>> PHP errors do not go there (or anywhere).
>>
>> 1. Apache has write perms to /tmp
>> 2. I have restarted httpd since changing php.ini
>> 3. The base php.ini is from the development version in /usr/share
>> 4. Selinux is disabled
> 
> "PrivateTmp=true" works as you can see
> using /tmp for logfiles is plain stupid
> 

I changed it to error_log = php_errors.log and now it writes errors into
the virtualhost's docroot.  How do I put it someplace not accessible to
the world, but readily found by me?

--

-- 
-- Steve

Gmane