Discuss

discuss@lists.centos.org

34753 discussions

DMARC and DKIM in mailman.
by James B. Byrne 19 Mar '15

19 Mar '15

https://rhn.redhat.com/errata/RHBA-2015-0706.html Looks like they have fixed the problem. -- *** 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] Kernel panic when adding partitioned virtio disk
by James B. Byrne 19 Mar '15

19 Mar '15

On Wed, March 18, 2015 10:59, m.roth(a)5-cent.us wrote: > Hi, James, > > James B. Byrne wrote: >> Kernel panic - not syncing: Attempted to kill init! > <snip> > Now, admittedly, a) I really haven't been following this thread, and > b) haven't worked a lot with VMs, and not with KVM, but could you > clarify something for me? Are you trying to make the virtual root > disk larger, or are you creating a new one, and just adding it the > the VM, like mounting another drive on an existing system? If the > latter, can't you mount it? > > Oh, and is the new virtual drive formatted? > I discovered my error and have corrected it. I am just providing this information in case someone else does something similar. The situation is this. I have a KVM guest that I keep as a clone template. It has one virtio disk of 32GB that is configured as an LVM partition with several lvs. I cloned this system to create an off-site backup host for our fax server. The archives of which exceeds 32GB by some margin. My requirement therefore was to create the necessary additional storage (2 x 32Gb virtio disks) and attach them to the cloned system. Initially this worked as it has in the past. However, I ran into a problem on the new guest when adding a new lv using the space from the new virtual disks that I had added to the volume group defined on the guest. And this is where I made my mistake. Instead of removing the lv first and then removing the virtio disks from the vg I deleted the disks from the guest. This meant that the guest LVM manager was looking for those drives whenever it was rebooted. If the drives that I added back in subsequent trials were not partitioned then they were not found by the lvm manager and the system booted. If the re-added disks were partitioned then the lvm manager found them, but they were not the disks expected. That probably tripped some sort of security or consistency check and that caused the kernel panic. The fix was to boot the system without the added disks. Then login and run the lvm utilities to remove the dangling lv, also remove the missing pvs from the vg, and then shutdown. Once this was done adding new partitioned virtio disks to the guest proceeded as expected and the problem disappeared from the next boot. -- *** 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

multiple memcached buckets in CentOS 7
by Tim Dunphy 19 Mar '15

19 Mar '15

Hey guys, OK so I'm pretty familiar with how to edit an init script for memcached so that I can get multiple memcached 'buckets' when starting up the service. The init script would ususally have multiple lines such as these under the start function: # cache_block /usr/local/bin/memcached -d -m 128 -l `hostname -i` -p 11318 -u daemon -c 8172 -v 2>> /tmp/memcached.log # cache_filter /usr/local/bin/memcached -d -m 512 -l `hostname -i` -p 11319 -u daemon -c 8172 -v 2>> /tmp/memcached.log # cache_form /usr/local/bin/memcached -d -m 128 -l `hostname -i` -p 11320 -u daemon -c 8172 -v 2>> /tmp/memcached.log Now, under CentOS 7, I see we have two files controlling memcached under the new sysctl system. At least, using sysctl is new to me! I see we have this file: [root@web1:~] #cat /usr/lib/systemd/system/memcached.service [Unit] Description=Memcached Before=httpd.service After=network.target [Service] Type=simple EnvironmentFile=-/etc/sysconfig/memcached ExecStart=/usr/bin/memcached -u $USER -p $PORT -m $CACHESIZE -c $MAXCONN $OPTIONS [Install] WantedBy=multi-user.target And we have this one under sysconfig: [root@web1:~] #cat /etc/sysconfig/memcached PORT="11211" USER="memcached" MAXCONN="1024" CACHESIZE="64" OPTIONS="" So I'm trying to figure out how to achive the same effect that I would under the old init script way of doing things. Can someone please give me an example of how to get the same thing done under the new system? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

2 3

Missing /sys/devices/system/cpu/cpu0/cpufreq
by lhecking＠users.sourceforge.net 19 Mar '15

19 Mar '15

What could be the reason for /sys/devices/system/cpu/cpu0/cpufreq non-existing? The cpu supports EIST. My guess is this may not be available because of cpu power/performance settings in the BIOS, but I can't take down production machines to play with this. Any ideas? The HW is Dell PER 5xx/7xx series. # cpupower frequency-info analyzing CPU 0: no or unknown cpufreq driver is active on this CPU boost state support: Supported: no Active: no 2400 MHz max turbo 4 active cores 2400 MHz max turbo 3 active cores 2400 MHz max turbo 2 active cores 2400 MHz max turbo 1 active cores # ls -l /sys/devices/system/cpu/cpu0/ total 0 drwxr-xr-x 6 root root 0 Feb 20 14:01 cache drwxr-xr-x 7 root root 0 Feb 20 14:01 cpuidle -r-------- 1 root root 4096 Feb 12 17:44 crash_notes lrwxrwxrwx 1 root root 0 Feb 20 14:01 node0 -> ../../node/node0 drwxr-xr-x 2 root root 0 Feb 20 14:01 thermal_throttle drwxr-xr-x 2 root root 0 Feb 20 14:01 topology # lsmod |grep cpufreq #

1 0

CentOS-announce Digest, Vol 121, Issue 7
by centos-announce-request＠centos.org 19 Mar '15

19 Mar '15

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. CESA-2015:0700 Moderate CentOS 6 unzip Security Update (Johnny Hughes) 2. CESA-2015:0696 Important CentOS 6 freetype Security Update (Johnny Hughes) 3. CEEA-2015:0701 CentOS 6 sssd Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 18 Mar 2015 18:53:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:0700 Moderate CentOS 6 unzip Security Update Message-ID: <20150318185306.GA15911(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:0700 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-0700.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: c55d5cfb1d69e130c0c79fbe4fb8fab2ca26eb2538f849f7c7f8056e9dfd1318 unzip-6.0-2.el6_6.i686.rpm x86_64: a6d953312c9adb593717177e0aaba2522451e5e83cabdc1dbcc901edd4d35ef4 unzip-6.0-2.el6_6.x86_64.rpm Source: ecbe9378128eed9ba62f7c4fd26b2931be25fe0114e87969dcc3da95de125769 unzip-6.0-2.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 18 Mar 2015 18:53:49 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:0696 Important CentOS 6 freetype Security Update Message-ID: <20150318185349.GA16033(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:0696 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-0696.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 45a77d6322ca6eba1839d5ae1a2d3600053b53442178c66b4a2922db7bf675e6 freetype-2.3.11-15.el6_6.1.i686.rpm 1148728004bb73f8c2fa6531699f759a8d0fa66cff1430d77a981496ce945726 freetype-demos-2.3.11-15.el6_6.1.i686.rpm cd21cd42093bd368199e183bff7ef9ad937d0697af2867f474bc711786737998 freetype-devel-2.3.11-15.el6_6.1.i686.rpm x86_64: 45a77d6322ca6eba1839d5ae1a2d3600053b53442178c66b4a2922db7bf675e6 freetype-2.3.11-15.el6_6.1.i686.rpm db9f9418457ac284178ce414f70dcd6e1aa55b3a02b450e3ea6441776a7b4ed3 freetype-2.3.11-15.el6_6.1.x86_64.rpm b496bebf66aef645bcb274a334663f9690dd9a232a77717132b38e932e09cf66 freetype-demos-2.3.11-15.el6_6.1.x86_64.rpm cd21cd42093bd368199e183bff7ef9ad937d0697af2867f474bc711786737998 freetype-devel-2.3.11-15.el6_6.1.i686.rpm 99fe82b0fac773c436701964c0a4870df7b18aa352a42d3d52c1cc3e87e231b3 freetype-devel-2.3.11-15.el6_6.1.x86_64.rpm Source: 02489b5951f7e555bb49d77d2c1531240b4b301cf0a75442b7c1e1c498bbf60f freetype-2.3.11-15.el6_6.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 18 Mar 2015 18:54:57 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2015:0701 CentOS 6 sssd Enhancement Update Message-ID: <20150318185457.GA16920(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2015:0701 Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-0701.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: c732f6ea6f8cd4e3002ed4b4a86dd813448faa1b73d3c0d8678a3a632a195265 libipa_hbac-1.11.6-30.el6_6.4.i686.rpm 2c64017af10cfb370b40b01e38f2d66e9e092d31c4233cc1bc30e3b7235e2062 libipa_hbac-devel-1.11.6-30.el6_6.4.i686.rpm 58c5cf1e04267cd1b4da1c4f39f04030caea6b13d08a17798eb4457031ffcaf1 libipa_hbac-python-1.11.6-30.el6_6.4.i686.rpm b8f075692a9c1f86ce952d4918b996ea9d3c3187a8fb661dd73204223e69032e libsss_idmap-1.11.6-30.el6_6.4.i686.rpm 9056764f5696e17b62ffb117e83deb9f8383f20fe157c806cc4ac75bd5ffd6d8 libsss_idmap-devel-1.11.6-30.el6_6.4.i686.rpm a4aa1deda59150eef50182146cf3068d720d5c72e5374a27fb7fc757b228d884 libsss_nss_idmap-1.11.6-30.el6_6.4.i686.rpm 05dc3bef5bc3c3c9ca4d640f896113de0acfa457865620a536a9c627ceb6bbf8 libsss_nss_idmap-devel-1.11.6-30.el6_6.4.i686.rpm 0bd1439b331f8e56dc303aea3cb630045ec079293397be75cd958d2bfdde239f libsss_nss_idmap-python-1.11.6-30.el6_6.4.i686.rpm 43ad7c250f903184929faa80c63573ca99a591ada6edcff70ba3e2bcbacf6002 python-sssdconfig-1.11.6-30.el6_6.4.noarch.rpm 8a58664365cd401608cc7d502d994350f73b47693907816da1dc7fea7669c6e5 sssd-1.11.6-30.el6_6.4.i686.rpm 7688c68f9c9bac5cd960e76d288183e34b2cff88f8c51b7126498e25dac23a7e sssd-ad-1.11.6-30.el6_6.4.i686.rpm 616c867706f445dc8fe1c286ffc433f15b2e291be60e39f6ea4a91de1ccd949b sssd-client-1.11.6-30.el6_6.4.i686.rpm 166ef324b2b06cc1a7f7638d0407d6fff9c345af6817a10938b64dd231c48fdd sssd-common-1.11.6-30.el6_6.4.i686.rpm 7a6a38282ce8659dcea22f478396b6e5468b5b96a6f75904e526291febdeb16e sssd-common-pac-1.11.6-30.el6_6.4.i686.rpm 81122fc3a12e05ba06dd0afc3e5e37d6b33fc5e9e83f9239b787e6eec60b0b94 sssd-dbus-1.11.6-30.el6_6.4.i686.rpm ac0f8ad1ca40951a8081eb85d9508a32dc22e901f72a8ffa2e13da2b98ccdaf4 sssd-ipa-1.11.6-30.el6_6.4.i686.rpm 08a68d4748eb9ba099c0d630b584b7cd10f1c215806d3cc2ef2627238e863046 sssd-krb5-1.11.6-30.el6_6.4.i686.rpm f5f18cccb8bcde48c97e86a1674bf787c437ad45fb4189b0af937cd19ecdd367 sssd-krb5-common-1.11.6-30.el6_6.4.i686.rpm 64495be2c2eace89d499822a1ea664c67a297c0f0427120851cd07d8b7ef0538 sssd-ldap-1.11.6-30.el6_6.4.i686.rpm dc38f030ecd3b3ba88e5d3b7589cf35b435d6d75a9fa97798430043cbc05f537 sssd-proxy-1.11.6-30.el6_6.4.i686.rpm 81889b946d39da62e1b168eceb9d7768cf26245b577d3ffbf95f410df99b03ac sssd-tools-1.11.6-30.el6_6.4.i686.rpm x86_64: c732f6ea6f8cd4e3002ed4b4a86dd813448faa1b73d3c0d8678a3a632a195265 libipa_hbac-1.11.6-30.el6_6.4.i686.rpm 6ff0c0c930b748aba85467352fd140298b93520e7e569565cc7ea0f95c33e3a0 libipa_hbac-1.11.6-30.el6_6.4.x86_64.rpm 2c64017af10cfb370b40b01e38f2d66e9e092d31c4233cc1bc30e3b7235e2062 libipa_hbac-devel-1.11.6-30.el6_6.4.i686.rpm c84b0bba97a817b0c00e8ebade89b52b6af17b5ed3b618f72fd025d494cb5fd0 libipa_hbac-devel-1.11.6-30.el6_6.4.x86_64.rpm eda5252af695b97b9e26f15d8d0952d4a4714102106129317896c0ec8b32a19c libipa_hbac-python-1.11.6-30.el6_6.4.x86_64.rpm b8f075692a9c1f86ce952d4918b996ea9d3c3187a8fb661dd73204223e69032e libsss_idmap-1.11.6-30.el6_6.4.i686.rpm cc39f2009b1a03ed6be2e32cfca96a06afd8e4b6ce77edd1affeebe25b633788 libsss_idmap-1.11.6-30.el6_6.4.x86_64.rpm 9056764f5696e17b62ffb117e83deb9f8383f20fe157c806cc4ac75bd5ffd6d8 libsss_idmap-devel-1.11.6-30.el6_6.4.i686.rpm 92dd8c7bcdf039532d09b864e50d399e1ed29ff2336be5f35b88193aacd35c8e libsss_idmap-devel-1.11.6-30.el6_6.4.x86_64.rpm a4aa1deda59150eef50182146cf3068d720d5c72e5374a27fb7fc757b228d884 libsss_nss_idmap-1.11.6-30.el6_6.4.i686.rpm 58f47134c98e575177f1d78a8e8314eac85dd7350c38879301d32661df4e994f libsss_nss_idmap-1.11.6-30.el6_6.4.x86_64.rpm 05dc3bef5bc3c3c9ca4d640f896113de0acfa457865620a536a9c627ceb6bbf8 libsss_nss_idmap-devel-1.11.6-30.el6_6.4.i686.rpm fe256269865062a529a3729012341c8bc8a51da17f9cfcf032c38e67b424bcb1 libsss_nss_idmap-devel-1.11.6-30.el6_6.4.x86_64.rpm da9fc6ba5b8d5124c8f4d541bc1a7a6a22bd5fddb4f219d8aa6a8948a879b551 libsss_nss_idmap-python-1.11.6-30.el6_6.4.x86_64.rpm 43ad7c250f903184929faa80c63573ca99a591ada6edcff70ba3e2bcbacf6002 python-sssdconfig-1.11.6-30.el6_6.4.noarch.rpm de7a69990f967d2e2c8d5b74898f8c1c3ce5bf79c278061b8f814260406661cb sssd-1.11.6-30.el6_6.4.x86_64.rpm bb2bb77a318ec0279e6ef15441ece1f0eadc959a89f2c7592421005b17494b7e sssd-ad-1.11.6-30.el6_6.4.x86_64.rpm 616c867706f445dc8fe1c286ffc433f15b2e291be60e39f6ea4a91de1ccd949b sssd-client-1.11.6-30.el6_6.4.i686.rpm 7638e1729357ed6b836f6a1217dfba95acde8e9600cd7b75cb89c6abf107263f sssd-client-1.11.6-30.el6_6.4.x86_64.rpm 166ef324b2b06cc1a7f7638d0407d6fff9c345af6817a10938b64dd231c48fdd sssd-common-1.11.6-30.el6_6.4.i686.rpm c5ffeece952a2fc991cf404c65a639d52a6eb29ed98a96facd6e5730d0dba130 sssd-common-1.11.6-30.el6_6.4.x86_64.rpm 256f10dcf22b24c337ee008b2b00821ff4241e8942fadda619b1af6e9167a677 sssd-common-pac-1.11.6-30.el6_6.4.x86_64.rpm 1d215006cfd98c0a61a5436ea461edcbf05f8fb6f3ce0a406eb18c809c19bc91 sssd-dbus-1.11.6-30.el6_6.4.x86_64.rpm 124e529a30f227014309827d1e48e5e2960799b51489a8c905738aef9e775617 sssd-ipa-1.11.6-30.el6_6.4.x86_64.rpm 3d67c3ddffbdac9c1349c56eb9b3eeceaef8c9465c05ef43091acf39acbad04e sssd-krb5-1.11.6-30.el6_6.4.x86_64.rpm 7a7c9a23f9fab5a314859ad02d5189de88d1d7b3bd530da684e703ec25f7f4a5 sssd-krb5-common-1.11.6-30.el6_6.4.x86_64.rpm 7cdb10c0183dcd7bd30dccf1b5321b62b7671b3ef83d0e2cc380fb16e483b443 sssd-ldap-1.11.6-30.el6_6.4.x86_64.rpm 8882608b252fc2c4c7c271aac80db84d59fcd8adcf7881de6e9e7088cae6dd66 sssd-proxy-1.11.6-30.el6_6.4.x86_64.rpm e356035a2446104809a24a2e38a43bb8c7017c77d2ffd5352b44fcb88d0d1e9c sssd-tools-1.11.6-30.el6_6.4.x86_64.rpm Source: f4d23eabdb133bb990e34dd99af19b2a4ddce1bb6a8ac19fc3a0bfe4c7f937af sssd-1.11.6-30.el6_6.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 121, Issue 7 ***********************************************

1 0

Bug 3831: basic_ncsa_auth Blowfish and SHA support, really fixed?
by Sergio Belkin 18 Mar '15

18 Mar '15

Hi, I'm using squid-3.3.8-12.el7_0.x86_64 on CentOS 7 I've configured squid for basic authentication, md5 password *works*, but if fails when I try to use either blowfish or sha password. Below is the cache.log when it fails: 2015/03/18 17:21:02.637 kid1| Checklist.cc(275) matchNode: 0x7f217e8baca8 matched=0 async=0 finished=0 2015/03/18 17:21:02.637 kid1| Checklist.cc(299) matchNode: 0x7f217e8baca8 simple mismatch 2015/03/18 17:21:02.637 kid1| Checklist.cc(160) checkAccessList: 0x7f217e8baca8 checking 'http_access allow squid_access' 2015/03/18 17:21:02.637 kid1| Acl.cc(336) matches: ACLList::matches: checking squid_access 2015/03/18 17:21:02.637 kid1| Acl.cc(319) checklistMatches: ACL::checklistMatches: checking 'squid_access' 2015/03/18 17:21:02.637 kid1| Acl.cc(281) aclCacheMatchFlush: aclCacheMatchFlush called for cache 0x7f217e9b8cc8 2015/03/18 17:21:02.637 kid1| Acl.cc(61) AuthenticateAcl: returning 2 sending credentials to helper. 2015/03/18 17:21:02.637 kid1| Acl.cc(321) checklistMatches: ACL::ChecklistMatches: result for 'squid_access' is -1 2015/03/18 17:21:02.637 kid1| Acl.cc(346) matches: squid_access needs async lookup 2015/03/18 17:21:02.637 kid1| Acl.cc(354) matches: squid_access result is false 2015/03/18 17:21:02.637 kid1| Checklist.cc(275) matchNode: 0x7f217e8baca8 matched=0 async=1 finished=0 2015/03/18 17:21:02.637 kid1| Checklist.cc(312) matchNode: 0x7f217e8baca8 going async 2015/03/18 17:21:02.637 kid1| Checklist.cc(131) asyncInProgress: ACLChecklist::asyncInProgress: 0x7f217e8baca8 async set to 1 2015/03/18 17:21:02.637 kid1| AclProxyAuth.cc(144) checkForAsync: checking password via authenticator 2015/03/18 17:21:02.637 kid1| Checklist.cc(256) matchNodes: 0x7f217e8baca8 awaiting async operation 2015/03/18 17:21:02.638 kid1| Checklist.cc(131) asyncInProgress: ACLChecklist::asyncInProgress: 0x7f217e8baca8 async set to 0 2015/03/18 17:21:02.638 kid1| Checklist.cc(160) checkAccessList: 0x7f217e8baca8 checking 'http_access allow squid_access' 2015/03/18 17:21:02.638 kid1| Acl.cc(336) matches: ACLList::matches: checking squid_access 2015/03/18 17:21:02.638 kid1| Acl.cc(319) checklistMatches: ACL::checklistMatches: checking 'squid_access' 2015/03/18 17:21:02.638 kid1| Acl.cc(66) AuthenticateAcl: returning 3 sending authentication challenge. 2015/03/18 17:21:02.638 kid1| Checklist.cc(146) markFinished: 0x7f217e8baca8 answer AUTH_REQUIRED for AuthenticateAcl exception 2015/03/18 17:21:02.638 kid1| Acl.cc(321) checklistMatches: ACL::ChecklistMatches: result for 'squid_access' is -1 2015/03/18 17:21:02.638 kid1| Acl.cc(343) matches: squid_access failed. 2015/03/18 17:21:02.638 kid1| Acl.cc(354) matches: squid_access result is false 2015/03/18 17:21:02.638 kid1| Checklist.cc(275) matchNode: 0x7f217e8baca8 matched=0 async=0 finished=1 2015/03/18 17:21:02.638 kid1| Checklist.cc(294) matchNode: 0x7f217e8baca8 exception: AUTH_REQUIRED 2015/03/18 17:21:02.638 kid1| Checklist.cc(88) matchNonBlocking: ACLChecklist::check: 0x7f217e8baca8 match found, calling back with AUTH_REQUIRED 2015/03/18 17:21:02.638 kid1| Checklist.cc(182) checkCallback: ACLChecklist::checkCallback: 0x7f217e8baca8 answer=AUTH_REQUIRED 2015/03/18 17:21:02.638 kid1| Gadgets.cc(58) aclGetDenyInfoPage: got called for squid_access 2015/03/18 17:21:02.638 kid1| Gadgets.cc(77) aclGetDenyInfoPage: aclGetDenyInfoPage: no match 2015/03/18 17:21:02.638 kid1| FilledChecklist.cc(77) ~ACLFilledChecklist: ACLFilledChecklist destroyed 0x7fffee83caa0 2015/03/18 17:21:02.638 kid1| Checklist.cc(334) ~ACLChecklist: ACLChecklist::~ACLChecklist: destroyed 0x7fffee83caa0 2015/03/18 17:21:02.638 kid1| FilledChecklist.cc(77) ~ACLFilledChecklist: ACLFilledChecklist destroyed 0x7fffee83caa0 2015/03/18 17:21:02.638 kid1| Checklist.cc(334) ~ACLChecklist: ACLChecklist::~ACLChecklist: destroyed 0x7fffee83caa0 2015/03/18 17:21:02.638 kid1| FilledChecklist.cc(77) ~ACLFilledChecklist: ACLFilledChecklist destroyed 0x7f217e8baca8 2015/03/18 17:21:02.638 kid1| Checklist.cc(334) ~ACLChecklist: ACLChecklist::~ACLChecklist: destroyed 0x7f217e8baca8 2015/03/18 17:21:02.639 kid1| FilledChecklist.cc(77) ~ACLFilledChecklist: ACLFilledChecklist destroyed 0x7f217e8baca8 2015/03/18 17:21:02.639 kid1| Checklist.cc(334) ~ACLChecklist: ACLChecklist::~ACLChecklist: destroyed 0x7f217e8baca8 Thanks in advance! -- -- Sergio Belkin http://www.sergiobelkin.com LPIC-2 Certified - http://www.lpi.org

1 0

unable to recover software raid1 install
by johan.vermeulen7＠telenet.be 18 Mar '15

18 Mar '15

Hello All, on a Centos5 system installed with software raid I'm getting: raid1: raid set md127 active with 2 out of 2 mirrors md:.... autorun DONE md: Autodetecting RAID arrays md: autorun..... md : autorun DONE trying to resume form /dev/md1 creating root device mounting root device mounting root filesystem ext3-fs : unable to read superblock mount : error mounting /dev/root on /sysroot as ext3: invalid argument setting up other filesystems.7 setting up new root fs setuproot: moving /dev failed : no such file of directory no fstab.sys, mounting internal defaults setuproot : error mounting /proc : no such file or directory setuproot: error mounting /sys : No such file of directory Switching to new root and running init unmounting old /dev unmounting old /proc unmounting old /sys switchroot : mount failed : No such file of directory kernel panic - not syncing : Attempted to kill init! Now I'm trying to boot into rescue mode from a Centos dvd, at the end of the Anaconda sequence I get: no linux partitions found. at the command prompt, fdisk -l gives me: /dev/sdb1* /dev/sdb2 /dev/sdb3 /dev/sda1* /dev/sda2 /dev/sda3 I'm not sure where to go from here. I try chrooting as described here :http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 but chrooting always fails with: chroot : failed to run command ' /usr/bin/bash" : no such file or directory. Any help would be deeply appreciated. greetings, Johan

2 3

Need help for write rpm spec
by Jegadeesh Kumar 18 Mar '15

18 Mar '15

Hi I am try to write rpm spec for install tomcat on a linux machine.But while build the rpm i found following error + /usr/lib/rpm/find-debuginfo.sh --strict-build-id /home/rpmbuild/BUILD/Install_tomcat-1.0 extracting debug info from /home/rpmbuild/BUILDROOT/Install_tomcat-1.0-1.el6.x86_64/usr/local/jdk1.7.0_13/lib/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so *** ERROR: No build ID note found in /home/rpmbuild/BUILDROOT/Install_tomcat-1.0-1.el6.x86_64/usr/local/jdk1.7.0_13/lib/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so error: Bad exit status from /home/rpmbuild/tmp/rpm-tmp.n1saIQ (%install) RPM build errors: Bad exit status from /home/rpmbuild/tmp/rpm-tmp.n1saIQ (%install) Below is my spec file Name: Install_tomcat Version: 1.0 Release: 1%{?dist} Summary: Tomcat installer Group: Application License: BSOFT Source0: Install_tomcat-1.0.tar.gz BuildArch: noarch BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX) #BuildRequires: #Requires: %description This RPM is used to install the tomcat application %clean rm -rf $RPM_BUILD_ROOT %prep %setup -q %build %install rm -rf $RPM_BUILD_ROOT install -d $RPM_BUILD_ROOT/usr/local cd $RPM_BUILD_ROOT/usr/local tar -xf %{_topdir}/SOURCES/Install_tomcat-1.0.tar.gz --strip 1 tar -xf jdk-7u13-linux-x64.gz ln -s jdk1.7.0_13/ $RPM_BUILD_ROOT/usr/local/java echo "export JAVA_HOME=/usr/local/java" >>/etc/profile echo "PATH=\${JAVA_HOME}/bin:\${PATH}" >>/etc/profile source /etc/profile java -version tar -xf apache-tomcat-7.0.32.tar.gz ln -s apache-tomcat-7.0.32/ $RPM_BUILD_ROOT/usr/local/tomcat %files %dir /usr/local %defattr(-,root,root,-) %doc %post chmod 755 -R /usr/local Please help me to solve the error Thanks Jegadeesh

3 2

Kernel panic when adding partitioned virtio disk
by James B. Byrne 18 Mar '15

18 Mar '15

I have a cloned kvm (that I can now get started following a shutdown and reboot of the hypervisor host). When it starts with its original virtio disk there is no problem. If I create a virtio disk and add it via virt-manager it also boots without issue, although one cannot see the new 'physical' disk. If I shutodwon the kvm guest, partition the new virtio disk, and reboot the guest then I see this: Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.32-504.12.2.el6.x86_64 #1 Call Trace: [ffffffff8152933c] ? panic+0xa7/0x16f [ffffffff8107a5f2] ? do_exit+0x862/0x870 [ffffffff8118fa25] ? fput+0x25/0x30 [ffffffff8107a658] ? do_group-exit+0x58/0xd0 [ffffffff8107a6e7] ? sys_exit_group+0x17/0x20 [ffffffff8100b072] ? system_call_fastpath+0x16/0x1b Does anyone have any idea what partitioning does to cause this behaviour? I have deleted and recreated the virtio disk several times with differing sizes and it always comes down to whether or not the disk is partitioned. I have added virtio disks to other kvm guests in the same fashion many times and have never run into this. -- *** 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

Re: [CentOS] KVM guest not running but cannot stop either
by James B. Byrne 18 Mar '15

18 Mar '15

On Tue, March 17, 2015 18:13, Dennis Jacobfeuerborn wrote: > > Have you tried restarting the libvirtd service? > > Regards, > Dennis > What does that do to the other running guest vm instances? -- *** 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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss