Discuss May 2012

discuss@lists.centos.org

193 participants
202 discussions

mcelog SELinux errors
by James B. Byrne 28 May '12

28 May '12

Prowling around in the system logs this morning I discover the following entries: May 27 09:48:27 vhost01 mcelog: Cannot open logfile /var/log/mcelog: Permission denied May 27 09:48:27 vhost01 mcelog: failed to prefill DIMM database from DMI data May 27 09:48:27 vhost01 mcelog: Cannot bind to client unix socket `/var/run/mcel og-client': Permission denied and later: vhost01 setroubleshoot: SELinux is preventing /usr/sbin/mcelog from write access on the directory /var/run. For complete SELinux messages. run sealert -l 548d9d71-bac3-41eb-aa30-9b40e3f2a324 sealert -l 548d9d71-bac3-41eb-aa30-9b40e3f2a324 SELinux is preventing /usr/sbin/mcelog from write access on the directory /var/run. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that mcelog should be allowed write access on the run directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep mcelog /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp This seems to my mind a bug either with the distributed SELinux policies or the software itself or somehow something has become very, very misconfigured. However, an semodule -l does not reveal any local policies installed on this server, so whatever is wrong it does not seem likely that the cause was a local modification. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

Re: [CentOS] NTP and virtual guests
by James B. Byrne 28 May '12

28 May '12

On Mon, May 28, 2012 08:50, Reindl Harald wrote: > > > Am 28.05.2012 14:41, schrieb James B. Byrne: >> when power returned all of the restored guests were immediately >> shutdown by ntp because the time differential between the >> restored systems and that of the ntpd sync servers exceeded >> the panic threshold. > > how can ntpd shutdown a guest? I have no idea. Perhaps I misunderstood what the ntpd man page referred to as a panic. If it is not ntpd then I still need to discover some way of ensuring that all the KVM guests that were active at the time of a power failure automatically come back on line when the KVM host system starts up. I cannot find any reference to how this is done. Are there any recommended solutions? These systems are on UPS already but the power failure duration exceeded the endurance of the the UPS. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

NTP and virtual guests
by James B. Byrne 28 May '12

28 May '12

We encountered a problem with respect to KVM virtual host restore and NTP. Specifically, our VM test host was shutdown by an extended power outage and when power returned all of the restored guests were immediately shutdown by ntp because the time differential between the restored systems and that of the ntpd sync servers exceeded the panic threshold. This is not an acceptable situation so in the absence of something more elegant we are contemplating shutting down ntpd on virtual hosts and scheduling regular ntpd -q from cron instead. Is there an alternative to this? If not then what would be a recommended scheduling interval? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

CentOS-announce Digest, Vol 87, Issue 15
by centos-announce-request＠centos.org 27 May '12

27 May '12

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org 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(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. Mailserver move (Ralph Angenendt) ---------------------------------------------------------------------- Message: 1 Date: Sun, 27 May 2012 01:15:00 +0200 From: Ralph Angenendt <ralph.angenendt(a)gmail.com> Subject: [CentOS-announce] Mailserver move To: centos(a)centos.org, centos-devel(a)centos.org, centos-mirror(a)centos.org, centos-qa(a)centos.org, centos-announce(a)centos.org Message-ID: <20120526231500.GA28507(a)reboot.strg-alt-entf.org> Content-Type: text/plain; charset=us-ascii Hi subscribers, the sponsor of the machine our mailserver runs on will be physically moving the machine at around May 27th 04:00 UTC. This move will take until around May 27th 07:00 UTC (or shorter). This means that there will be no activity on the mailing lists during that time. We all hope that the machine will come up without problems again after the move. If it doesn't, service (mailing lists) might be interrupted for a few more hours. We apologize for any inconvenience this might cause you. Regards, Ralph ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 87, Issue 15 ***********************************************

1 0

Mailserver move
by Ralph Angenendt 27 May '12

27 May '12

Hi subscribers, the sponsor of the machine our mailserver runs on will be physically moving the machine at around May 27th 04:00 UTC. This move will take until around May 27th 07:00 UTC (or shorter). This means that there will be no activity on the mailing lists during that time. We all hope that the machine will come up without problems again after the move. If it doesn't, service (mailing lists) might be interrupted for a few more hours. We apologize for any inconvenience this might cause you. Regards, Ralph

2 1

Re: [CentOS] Mysterious versioning reported by file command
by Frank Cox 27 May '12

27 May '12

On Sat, 26 May 2012 21:32:52 +0200 Reindl Harald wrote: > from the binary, "file" does only print what a file contains Ok, then where does it come from, since it's not the current kernel version and it's not the elfutils version? gcc somehow finds that number and inserts it into the binary. Where did it find it and why is that number not the same as the other stuff, notably the kernel, since it appears to be a kernel version number? Just not the current kernel version number. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!

2 1

Re: [CentOS] Mysterious versioning reported by file command
by Frank Cox 26 May '12

26 May '12

On Sat, 26 May 2012 10:25:54 +0200 Reindl Harald wrote: > > Why does the output from file say "Linux 2.6.18" when the actual kernel in > > use is 2.6.32? > > it DOES NOT, learn to read outputs - it speaks about the elfutils > why should their output reflect the current kernel point version > it is not their job because "uname" exists [frankcox@mutt ~]$ rpm -q elfutils elfutils-0.152-1.el6.x86_64 That's not version 2.6.18 either. My question is, where does that 2.6.18 come from? It's not the current kernel version, it's not the gcc version, and it's not the current elfutils version either. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!

2 1

support for Broadcom BCM4313
by Philippe Naudin 26 May '12

26 May '12

Hello, The support for Broadcom Corporation BCM4313 802.11b/g/n Wireless is native in the kernel since 2.6.37 (module brcm80211, renamed brcmsmac since 2.6.39). But is it backported to some kernel available for CentOS ? Thanks, -- Philippe Naudin

4 7

Mysterious versioning reported by file command
by Frank Cox 26 May '12

26 May '12

I just noticed this, which doesn't actually seem to affect anything but does create a mystery: [frankcox@mutt temp]$ cat test.c #include <stdio.h> int main(void) { printf("Hello world\n"); return 0; } [frankcox@mutt temp]$ gcc -o test test.c [frankcox@mutt temp]$ file test test: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, not stripped [frankcox@mutt temp]$ uname -a Linux mutt.melvilletheatre.net 2.6.32-220.17.1.el6.x86_64 #1 SMP Wed May 16 00:01:37 BST 2012 x86_64 x86_64 x86_64 GNU/Linux Why does the output from file say "Linux 2.6.18" when the actual kernel in use is 2.6.32? -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com www.creekfm.com - FIFTY THOUSAND WATTS of POW WOW POWER!

1 0

biggest disk partition on 5.8?
by Alan McKay 26 May '12

26 May '12

Hey folks, I have a Sun J4400 SAS1 disk array with 24 x 1T drives in it connected to a Sunfire x2250 running 5.8 ( 64 bit ) I used 'arcconf' to create a big RAID60 out of (see below). But then I mount it and it is way too small This should be about 20TB : [root@solexa1 StorMan]# df -h /dev/sdb1 Filesystem Size Used Avail Use% Mounted on /dev/sdb1 186G 60M 176G 1% /mnt/J4400-1 Here is how I created it : ./arcconf create 1 logicaldrive name J4400-1-RAID60 max 60 0 0 0 1 0 2 0 3 0 4 0 5 0 6 0 7 0 8 0 9 0 10 0 11 0 12 0 13 0 14 0 15 0 16 0 17 0 18 0 19 0 20 0 21 0 22 0 23 noprompt [root@solexa1 StorMan]# ./arcconf getconfig 1 ld Controllers found: 1 ---------------------------------------------------------------------- Logical device information ---------------------------------------------------------------------- Logical device number 0 Logical device name : J4400-1-RAID60 RAID level : 60 XOR Status of logical device : Impacted Size : 19066880 MB Stripe-unit size : 256 KB Read-cache mode : Enabled Write-cache mode : Enabled (write-back) Write-cache setting : Enabled (write-back) when protected by battery Partitioned : Yes Protected by Hot-Spare : No Bootable : Yes Failed stripes : No -------------------------------------------------------- Logical device segment information -------------------------------------------------------- Group 0, Segment 0 : Present (0,0) 9QJ3ZAYQ Group 0, Segment 1 : Present (0,1) 9QJ3ZP3Y Group 0, Segment 2 : Present (0,2) 9QJ3X7GR Group 0, Segment 3 : Present (0,3) 9QJ3XJQW Group 0, Segment 4 : Present (0,4) 9QJ3TPK2 Group 0, Segment 5 : Present (0,5) 9QJ40PHP Group 0, Segment 6 : Present (0,6) GTE002PBHJEDBE Group 0, Segment 7 : Present (0,7) 9QJ3ZHE0 Group 0, Segment 8 : Present (0,8) 9QJ3Z053 Group 0, Segment 9 : Present (0,9) 9QJ3ZEX6 Group 0, Segment 10 : Present (0,10) 9QJ33XGG Group 0, Segment 11 : Present (0,11) 9QJ3X88X Group 1, Segment 0 : Present (0,12) 9QJ3YLR2 Group 1, Segment 1 : Present (0,13) GTE002PBHHNVZE Group 1, Segment 2 : Present (0,14) 9QJ3ZGM2 Group 1, Segment 3 : Present (0,15) GTE002PBGP9VZE Group 1, Segment 4 : Present (0,16) 9QJ3ZB4X Group 1, Segment 5 : Present (0,17) 9QJ3ZAE0 Group 1, Segment 6 : Present (0,18) 9QJ3Y8C8 Group 1, Segment 7 : Present (0,19) GTE002PBH30GKE Group 1, Segment 8 : Present (0,20) GTE002PAKXKDPE Group 1, Segment 9 : Present (0,21) 9QJ3VXEL Group 1, Segment 10 : Present (0,22) 9QJ3W4W6 Group 1, Segment 11 : Present (0,23) 9QJ3TPGR Make 1 big partition : sfdisk /dev/sdb <<EOF ,,L EOF [root@solexa1 StorMan]# sfdisk -l /dev/sdb Disk /dev/sdb: 2430685 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sdb1 0+ 24540- 24541- 197124430 83 Linux /dev/sdb2 0 - 0 0 0 Empty /dev/sdb3 0 - 0 0 0 Empty /dev/sdb4 0 - 0 0 0 Empty And then make an ext4 filesystem on that : [root@solexa1 StorMan]# mke4fs /dev/sdb1 mke4fs 1.41.12 (17-May-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 12320768 inodes, 49281107 blocks 2464055 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=4294967296 1504 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Writing inode tables: done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 30 mounts or 180 days, whichever comes first. Use tune4fs -c or -i to override. -- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food"

7 7

← Newer
1
2
3
4
5
6
7
8
9
...
21
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2012