Re: [CentOS] centos 6.3
On 12/1/2014 11:29 PM, Hadi Motamedi wrote:
I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?
As the others said, the OS is "CentOS 6"... "6.3" was simply a
snapshot of the updates as of July 2012. As soon as you update it with
current fixes ('yum update') you'll be on the current point release,
which is CentOS 6.6 at the moment.
As has been pointed out several times here, you should NOT assume you
can just install individual fixes such as the latest openssl for the
heartbeat fixes, and so forth, as these have only been tested running
with ALL the latest packages, not every conceivable combination of
component versions over the past 4 years or so.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] centos 6.3
> > As has been pointed out several times here, you should NOT assume you > can just install individual fixes such as the latest openssl for the > heartbeat fixes, and so forth, as these have only been tested running > with ALL the latest packages, not every conceivable combination of > component versions over the past 4 years or so. > > > > > -- > john r pierce 37N 122W > somewhere on the middle of the left coast > > ___ Please let me to post my special thanks to you as your comments solved my problem. Thank you again for assigning your valuable time and experience . ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] yum update on CentOS6 failing
Hi anyone else having this problem? Error: Package: perl-IO-Compress-Bzip2-2.021-136.el6.x86_64 (@base) Requires: perl = 4:5.10.1-136.el6 Removing: 4:perl-5.10.1-136.el6.x86_64 (@base) perl = 4:5.10.1-136.el6 Updated By: 4:perl-5.10.1-136.el6_6.1.x86_64 (updates) perl = 4:5.10.1-136.el6_6.1 tried a yum clean all and still an issue TIA ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SEtroubleshootd Crashing
I'll jump in here to say we'll try your suggestion, but I guess what's not been mentioned is that we get the setroubleshoot abrt's only a few times a day, but we're getting 1s of setroubleshoot messages in /var/log/messages a day. e.g. Dec 2 10:03:55 server audispd: queue is full - dropping event Dec 2 10:04:00 server audispd: last message repeated 199 times Dec 2 10:04:00 server rsyslogd-2177: imuxsock begins to drop messages from pid 5967 due to rate-limiting Dec 2 10:04:01 server rsyslogd-2177: imuxsock lost 2 messages from pid 5967 due to rate-limiting Dec 2 10:04:01 server audispd: queue is full - dropping event Dec 2 10:04:02 server audispd: last message repeated 134 times Dec 2 10:04:02 server setroubleshoot: SELinux is preventing /bin/ps from read access on the file /proc//stat. For complete SELinux messages. run sealert -l 2274b1c7-fd69-4fa8-8e67-cd7a9da9eff4 Dec 2 10:04:02 server audispd: queue is full - dropping event Dec 2 10:04:03 server audispd: last message repeated 48 times Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from getattr access on the directory /proc/. For complete SELinux messages. run sealert -l 2d09d555-8834-4c27-976b-6647f8673286 Dec 2 10:04:03 server audispd: queue is full - dropping event Dec 2 10:04:03 server audispd: last message repeated 15 times Dec 2 10:04:03 server rsyslogd-2177: imuxsock begins to drop messages from pid 5967 due to rate-limiting Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from search access on the directory /proc//stat. For complete SELinux messages. run sealert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from getattr access on the directory /proc/. For complete SELinux messages. run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from search access on the directory /proc//stat. For complete SELinux messages. run sealert -l 2448a46d-5089-4f85-aae8-e9013341471f Dec 2 10:04:05 server setroubleshoot: last message repeated 2 times Dec 2 10:04:05 server setroubleshoot: SELinux is preventing /bin/ps from getattr access on the directory /proc/. 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//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 wrote: > > On 12/01/2014 10:39 AM, Gary Smithson wrote: > > 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 > Ok might not be related. One other suggestion would be to clear the > database out. And see if there > was something in the database that was causing it problems. > > Make sure there is no setroubleshootd running and > > >/var/lib/setroubleshoot/setroubleshoot_database.xml > > -Original Message- > > From: centos-boun...@centos.org [mailto:centos-boun...@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 just seeing email on this today. Could you try to > downgrade the latest version of libxml to see if the problem goes away. > > > > On 12/01/2014 10:01 AM, Gary Smithson wrote: > >> Thanks > >> > >> Could you please clarify, which version libxml is broken and has there > been a newer version released that will fix it. > >> > >> -Original Message- > >> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > >> Behalf Of Daniel J Walsh > >> Sent: 01 December 2014 14:58 > >> To: CentOS mailing list > >> Subject: Re: [CentOS] SEtroubleshootd Crashing > >> > >> This seems to be a problem with an updated version of libxml. > >> On 11/28/2014 09:04 AM, Gary Smithson wrote: > >>> When running Node.js through Phusion Passenger on Centos 6.5 ( Linux > 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 > x86_64 x86_64 GNU/Linux), with SELinux enabled in permissive mode we > receive a large number of entries in the audit.log and setroubleshootd > randomly crashes with the following error, We have resolved the selinux > alerts by following the troubleshooting steps recommend by running > sealert,However we are concerned by setroubleshootd crashing and are > concered that we may have masked the issue by fixing the entries in the > audit.log. > >>> > >>> > >>> > >>> abrt_version: 2.0.8 > >>> > >>> cmdline:
[CentOS] CentOS-announce Digest, Vol 118, Issue 1
Send CentOS-announce mailing list submissions to
centos-annou...@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-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@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. CEEA-2014:1918 CentOS 6 oprofile Enhancement Update
(Johnny Hughes)
2. CESA-2014:1911 Moderate CentOS 6 ruby SecurityUpdate
(Johnny Hughes)
3. CESA-2014:1912 Moderate CentOS 7 ruby SecurityUpdate
(Johnny Hughes)
4. CEEA-2014:1917 CentOS 7 ibus-hangul FASTTRACK Enhancement
Update (Johnny Hughes)
--
Message: 1
Date: Mon, 1 Dec 2014 12:57:15 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEEA-2014:1918 CentOS 6 oprofile
Enhancement Update
Message-ID: <20141201125715.ga55...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Enhancement Advisory 2014:1918
Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-1918.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
0f0c9183544e6f82486346105c34a54afcd715514e13cc2ce28069102d32b057
oprofile-0.9.9-6.el6_6.i686.rpm
3fc7bf59184123d3d58fec29595f06bde27cc8013fa7788da7346a35c36fc612
oprofile-devel-0.9.9-6.el6_6.i686.rpm
e26a9af62cee1cd14bccb46dcc7aff11770f931088f29a442abc51c707e67fdb
oprofile-gui-0.9.9-6.el6_6.i686.rpm
6cc09ce4e5f89e9864bb47d0098100f43d9693f33919237e3f7924c1c6440144
oprofile-jit-0.9.9-6.el6_6.i686.rpm
x86_64:
b831f62d7a85743993d2ce5a330fc83c944643667022507185ba0c1f06d3d2d6
oprofile-0.9.9-6.el6_6.x86_64.rpm
3fc7bf59184123d3d58fec29595f06bde27cc8013fa7788da7346a35c36fc612
oprofile-devel-0.9.9-6.el6_6.i686.rpm
1c47a22ad84b114e788344171305918ee08e64d4d021f1d3179382cc3ac6d198
oprofile-devel-0.9.9-6.el6_6.x86_64.rpm
507d9e274357fb29b1dfdb91517a7d6430fdd91fa8aa16b338b96ac64cfbc81b
oprofile-gui-0.9.9-6.el6_6.x86_64.rpm
6cc09ce4e5f89e9864bb47d0098100f43d9693f33919237e3f7924c1c6440144
oprofile-jit-0.9.9-6.el6_6.i686.rpm
70acdcd638b6363e6f2ad044dcc09ee200cfdaf3342058b9fef8cc2edbfd627d
oprofile-jit-0.9.9-6.el6_6.x86_64.rpm
Source:
0c12801fcb07266a3bf6c718b3fa5566ec0ea7e59da800effba6a536a8a93cb7
oprofile-0.9.9-6.el6_6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
Message: 2
Date: Mon, 1 Dec 2014 12:57:41 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2014:1911 Moderate CentOS 6 ruby
SecurityUpdate
Message-ID: <20141201125741.ga55...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2014:1911 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1911.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
31d5707695b299bd4581acda718ed7b845066ba3c68b3fde46bfa1910b484546
ruby-1.8.7.374-3.el6_6.i686.rpm
93b81ec1e635b3c33f1a83e899a30ed5ad6a46c460de6b2ff371f965ff24b813
ruby-devel-1.8.7.374-3.el6_6.i686.rpm
7d10fa2773e093898074bb58a168049547da12e0b99405906782ff00136d14a2
ruby-docs-1.8.7.374-3.el6_6.i686.rpm
6954b286ff3c8f183e717b5bf9827683e440bb7702e1d8f956615f6ff6d2f2b2
ruby-irb-1.8.7.374-3.el6_6.i686.rpm
cf2ee4436dab4202ecb4441e6b43ee7b64e53d19e5cea664b23a4e709d84fb58
ruby-libs-1.8.7.374-3.el6_6.i686.rpm
eefe4e31c899d554e0dabecc15cef3ed4d015beff9e05d15f995cfff4cb5bdcf
ruby-rdoc-1.8.7.374-3.el6_6.i686.rpm
551bc361956144198996fdcab5a7a97610232f962cd5e3bc0dfdd6605156a1d8
ruby-ri-1.8.7.374-3.el6_6.i686.rpm
8958034cac5db419509716d387f1df5a4722c1fba5aa6e1b331d63ea6809cf10
ruby-static-1.8.7.374-3.el6_6.i686.rpm
32cd9786acbe51cf36bf3b94578cd40055308609879069393e38e1d534a89811
ruby-tcltk-1.8.7.374-3.el6_6.i686.rpm
x86_64:
909643760630c61085fcbc1a888d532625ce3fdd2e83ab0becbd1d13a8974d32
ruby-1.8.7.374-3.el6_6.x86_64.rpm
93b81ec1e635b3c33f1a83e899a30ed5ad6a46c460de6b2ff371f965ff24b813
ruby-devel-1.8.7.374-3.el6_6.i686.rpm
813cdc7b12018f27fd0a8b9317016698f0224eee262f50d51caaf59db4756da2
ruby-devel-1.8.7.374-3.el6_6.x86_64.rpm
bd94514b57dfe24f7a0b56bdfd00f9d2b966112298c1224d58c15c434118cd16
ruby-docs-1.8.7.374-3.el6_6.x86_64.rpm
82c7d51431ae43ae88134d7f34c903fcd7286d09fdb71e7946f4bbd7ae26314e
ruby-irb-1.8.7.374-3.el6_6.x86_64.rpm
cf2ee4436dab4202ecb4441e6b43ee7b64e53d19e5cea664b23a4e709d84fb58
ruby-libs-1.8.7.374-3.el6_6.i686.rpm
19313fe28cfc5ff4fc0977eb5a4589457d7c7b393ee95cd364a2cf62c2679f8e
ruby-libs-1.8.7.374-3.el6_
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Mon, December 1, 2014 16:48, Les Mikesell wrote: > > Is there anyone who has more than a few boxes at more than one > location who _doesn't_ have this issue? I'd like to see a FAQ or > something by whoever designed the network configuration system about > how they planned for it to work (with and without GUI availability). > Likewise for what is supposed to happen when you restore a backup onto > different hardware. > Think 'laptop'. -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@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 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Building QT on CentOS 5
I am building QT 4.8.6 on CentOS 5 and it is failing on building the webkit module with __sync_add_and_fetch_4 not being defined. My build is for Embedded Linux, which allows me to use the framebuffer. Posts report this error when trying to cross-compile for ARM, but I am building for X86. Several posts also indicate that this is due to the old GCC used by CentOS 5. Does anyone have any suggestions? Thanks, -- Wade Hampton ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos7 ds-389
Op 26-11-14 om 09:27 schreef Johan Vermeulen: Op 25-11-14 om 19:08 schreef Tris Hoar: On 25/11/2014 16:52, Johan Vermeulen wrote: Hello All, I'm looking at setting up ds-389 on both Centos6.6 en Centos7, both minimal installs with epel repo enabled. When running yum search ds-389 on Centos7 I get only 3 packages, 389-ds-base 389-ds-base-devel 389-ds-base-libs On Centos6.6 I get the whole list: 389-ds.noarch : 389 Directory, Administration, and Console Suite 389-ds-base.x86_64 : 389 Directory Server (base) 389-ds-base-devel.i686 : Development libraries for 389 Directory Server 389-ds-base-devel.x86_64 : Development libraries for 389 Directory Server 389-ds-base-libs.i686 : Core libraries for 389 Directory Server 389-ds-base-libs.x86_64 : Core libraries for 389 Directory Server 389-ds-console.noarch : 389 Directory Server Management Console 389-ds-console-doc.noarch : Web docs for 389 Directory Server Management Console 389-dsgw.x86_64 : 389 Directory Server Gateway (dsgw) Is this a change in policy? I apologise if this has been answered before. A quick google did not provide an answer. Greetings, Johan Half the those packages are for i686 which is not longer a supported architecture in 7, and many of the others are from epel 389-ds-base.x86_64 1.2.11.15-48.el6_6 rhel-x86_64-server-6 389-ds-base-devel.x86_64 1.2.11.15-48.el6_6 rhel-x86_64-server-optional-6 389-ds-base-libs.x86_64 1.2.11.15-48.el6_6 rhel-x86_64-server-6 Is what I see on one of my RHEL6 servers. Tris * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmas...@bgfl.org The views expressed within this email are those of the individual, and not necessarily those of the organisation * ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hello Tris, thanks for the reply. You are right, some of the packages are i686, logically they are nog in Centos7. But I have epel enabled on the Centos7 box and I am not seeing 389-admin.x86_64 : 389 Administration Server (admin) 389-admin-console.noarch : 389 Admin Server Management Console The setup works without 389-admin as far as I can see on a first test, but launching the console is difficult without 389-admin-console. Greetings, Johan I found the answer here: https://fedorahosted.org/389/ticket/47865 Looks like the other 389-ds packages are due for Centos7.1. Greetings, J. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SEtroubleshootd Crashing
Could you send me a copy of your audit.log. You should not be getting hundreds of AVC's a day. ausearch -m avc,user_avc -ts today On 12/02/2014 05:08 AM, John Beranek wrote: > I'll jump in here to say we'll try your suggestion, but I guess what's not > been mentioned is that we get the setroubleshoot abrt's only a few times a > day, but we're getting 1s of setroubleshoot messages in > /var/log/messages a day. > > e.g. > > Dec 2 10:03:55 server audispd: queue is full - dropping event > Dec 2 10:04:00 server audispd: last message repeated 199 times > Dec 2 10:04:00 server rsyslogd-2177: imuxsock begins to drop messages from > pid 5967 due to rate-limiting > Dec 2 10:04:01 server rsyslogd-2177: imuxsock lost 2 messages from pid > 5967 due to rate-limiting > Dec 2 10:04:01 server audispd: queue is full - dropping event > Dec 2 10:04:02 server audispd: last message repeated 134 times > Dec 2 10:04:02 server setroubleshoot: SELinux is preventing /bin/ps from > read access on the file /proc//stat. For complete SELinux messages. > run sealert -l 2274b1c7-fd69-4fa8-8e67-cd7a9da9eff4 > Dec 2 10:04:02 server audispd: queue is full - dropping event > Dec 2 10:04:03 server audispd: last message repeated 48 times > Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from > getattr access on the directory /proc/. For complete SELinux messages. > run sealert -l 2d09d555-8834-4c27-976b-6647f8673286 > Dec 2 10:04:03 server audispd: queue is full - dropping event > Dec 2 10:04:03 server audispd: last message repeated 15 times > Dec 2 10:04:03 server rsyslogd-2177: imuxsock begins to drop messages from > pid 5967 due to rate-limiting > Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from > search access on the directory /proc//stat. For complete SELinux > messages. run sealert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 > Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > getattr access on the directory /proc/. For complete SELinux messages. > run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > search access on the directory /proc//stat. For complete SELinux > messages. run sealert -l 2448a46d-5089-4f85-aae8-e9013341471f > Dec 2 10:04:05 server setroubleshoot: last message repeated 2 times > Dec 2 10:04:05 server setroubleshoot: SELinux is preventing /bin/ps from > getattr access on the directory /proc/. 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//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 wrote: > >> On 12/01/2014 10:39 AM, Gary Smithson wrote: >>> 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 >> Ok might not be related. One other suggestion would be to clear the >> database out. And see if there >> was something in the database that was causing it problems. >> >> Make sure there is no setroubleshootd running and >> >>> /var/lib/setroubleshoot/setroubleshoot_database.xml >>> -Original Message- >>> From: centos-boun...@centos.org [mailto:centos-boun...@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 just seeing email on this today. Could you try to >> downgrade the latest version of libxml to see if the problem goes away. >>> On 12/01/2014 10:01 AM, Gary Smithson wrote: Thanks Could you please clarify, which version libxml is broken and has there >> been a newer version released that will fix it. -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Daniel J Walsh Sent: 01 December 2014 14:58 To: CentOS mailing list Subject: Re: [CentOS] SEtroubleshootd Crashing This seems to be a problem with an updated version of libxml. On 11/28/2014 09:04 AM, Gary Smithson wrote: > When running Node.js through Phusion Passenger on Centos 6.5 ( Linux >> 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 >> x86_64 x86_64 GNU/Linux), with SELinux enabled in permissive mode we >> receive a large number of entries in the audit.log and setroubleshootd >> randomly crashes with the following error, We have resolved the selinux >> alerts by f
Re: [CentOS] CentOs 7.0 and reboot failure
I don't want to hi-jack this but I may have a clew for you. I am troubleshooting a similar problem and have found a trail. I recently installed centos7 on my (improperly complicated system) and sometimes it will boot and sometimes not. My problem is apparently caused by having three hard drives . From boot to boot they get mounted in different orders. The drive with my os7 sometimes is mounted as/dev/sda and sometimes /dev/sdc. In grub.cfg on the os7 partition there is a statement "set root=hd0, msdos3" I think that may be the villain but I don't know where it comes from. (The kernel lines use blockid's,) That statement is in centos7, but not in centos6 where I have not had the problem. I intend to search a while, and maybe learn something or take out a couple of drives.Hopefully this helps. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Help with at Bash script
I am attempting to get a script borrowed from DJB to work on my CentOS-6.6
box. Simplified it looks like this:
tcpdump -l -n -e port 53 \
| awk '{if ($14 ~ /A.*?/) print $15}' \
| while read domain ; do echo $domain ; done ;
The sticking point is the 'while read' construct. Run just as 'tcpdum | awk'
I get this:
english.stackexchange.com.
www.urbandictionary.com.
www.urbandictionary.com.
www.urbandictionary.com.
www.urbandictionary.com.
api.mywot.com.
a.udimg.com.
a.udimg.com.
fonts.googleapis.com.
. . .
Run with the 'while read $domain ; do echo ' pipe nothing appears whatsoever.
What am I doing wrong?
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrnemailto:byrn...@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
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] yum update on CentOS6 failing
On 12/02/2014 10:55 AM, Rob Kampen wrote: Hi anyone else having this problem? Error: Package: perl-IO-Compress-Bzip2-2.021-136.el6.x86_64 (@base) Requires: perl = 4:5.10.1-136.el6 Removing: 4:perl-5.10.1-136.el6.x86_64 (@base) perl = 4:5.10.1-136.el6 Updated By: 4:perl-5.10.1-136.el6_6.1.x86_64 (updates) perl = 4:5.10.1-136.el6_6.1 tried a yum clean all and still an issue TIA perl-IO-Compress-Bzip2-2.021-136.el6_6.1.x86_64 is in updates. You must have an excludes, or an installed rpm that requires the older version of that package and prevents it from updating. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOs 7.0 and reboot failure
On Mon, 2014-12-01 at 18:50 +, Ned Slider wrote: > On 01/12/14 18:36, Gregory P. Ennis wrote: > > On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote: > >> On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote: > >>> Date: Sun, 23 Nov 2014 13:50:17 -0600 > >>> > >>> On Sun, 23 Nov 2014 13:07:47 -0600 > >>> Gregory P. Ennis wrote: > >>> > I also changed the boot level to 5. > >>> > >>> Do you mean the runlevel? If so, are you sure that you changed it > >>> correctly? > >>> > >>> Centos 7 doesn't use runlevels set in inittab like previous versions did. > >>> I see that fact is actually noted in /etc/inittab, along with the > >>> expected way to do it. > >>> - > >>> > >>> Frank, > >>> > >>> Yes, you are correct, I changed the run level and not boot level to 5 > >>> and did so by using the command : > >>> > >>> ln -sf /lib/systemd/system/graphical.target > >>> /etc/systemd/system/default.target > >>> > >>> Also, I appreciate everybody's input on this, but I am still at a loss > >>> as to how to fix this. Without being able to reboot, it sure makes the > >>> set up difficult. > >>> > >>> Does anyone else have any ideas?? > >>> > >>> Greg > >>> > >> > >> I have tried some additional changes that have not made a difference. > >> > >> I disabled selinux - that made no difference > >> I stopped and disabled firewalld - that made no difference. > >> > >> I can boot this machine after I turn it off and then back on, but when I > >> try to do a shutdown now -r, the system hangs right after picking the OS > >> that is desired "CentOS Linux..". > >> > >> After the machine is turned off the boot process occurs normally after > >> this choice and I get two penguins in the upper left hand corner, and > >> the boot proceeds. When I do a shutdown now -r, I do not get to the > >> penguins and the machine hangs forever until I either unplug it or press > >> the power button for 5 seconds. > >> > >> Any help would be appreciated!!! > >> > >> Greg > >> > > --- > > > > Everyone, > > > > I did not get much of a response on the list so I filed a bug report. I > > wanted to document the bug report for anyone else that is having a > > reboot problem. > > > > https://bugs.centos.org/view.php?id=7949 > > > > > > Greg Ennis > > > > Seems little point in filing a bug report when you have no idea what the > issue is. Bugs are not a means of troubleshooting nor a support forum. > However, you did get my attention so lets see if we can stimulate some > further interest in troubleshooting this. > > So the system will perform a cold reboot, but not a warm reboot. Sounds > like a hardware issue to me. > > Any clues in /var/log/messages ? > > Tried updating the BIOS? > > Any hardware firmwares being loaded? > > > ___ Ned, Thanks for your response!!! Sorry, if posting a bug report was the wrong venue !!! There are no messages in the message logs that I could identify as problems, but the system fails before the OS is active. I have not updated the BIOS, and do not know how to do this... but this is my testing machine so I am more than open to doing this. I am using a Gateway SX2855-UB12P. I will take a look at the Gateway site; if there are tutorials you could point me to I would appreciate it. The only hardware that has been added has been a usb ethernet connection so that I have the motherboard nic card and the usb nic connection. I wanted to use this setup to test the firewalld capabilities for a network gateway. The machine does not have a monitor, and is without a mouse or keyboard. It should be noted that this machine previously had CentOS 6 with a 3T Seagate drive that worked without a problem, but recently developed a disc failure. I replaced the drive with a 4T WesternDigital drive and installed CentOs 7.0 from a DVD. Thanks again for your help!!! Greg ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOs 7.0 and reboot failure
On Tue, 2014-12-02 at 12:34 -0600, Gregory P. Ennis wrote: > On Mon, 2014-12-01 at 18:50 +, Ned Slider wrote: > > On 01/12/14 18:36, Gregory P. Ennis wrote: > > > On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote: > > >> On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote: > > >>> Date: Sun, 23 Nov 2014 13:50:17 -0600 > > >>> > > >>> On Sun, 23 Nov 2014 13:07:47 -0600 > > >>> Gregory P. Ennis wrote: > > >>> > > I also changed the boot level to 5. > > >>> > > >>> Do you mean the runlevel? If so, are you sure that you changed it > > >>> correctly? > > >>> > > >>> Centos 7 doesn't use runlevels set in inittab like previous versions > > >>> did. I see that fact is actually noted in /etc/inittab, along with the > > >>> expected way to do it. > > >>> - > > >>> > > >>> Frank, > > >>> > > >>> Yes, you are correct, I changed the run level and not boot level to 5 > > >>> and did so by using the command : > > >>> > > >>> ln -sf /lib/systemd/system/graphical.target > > >>> /etc/systemd/system/default.target > > >>> > > >>> Also, I appreciate everybody's input on this, but I am still at a loss > > >>> as to how to fix this. Without being able to reboot, it sure makes the > > >>> set up difficult. > > >>> > > >>> Does anyone else have any ideas?? > > >>> > > >>> Greg > > >>> > > >> > > >> I have tried some additional changes that have not made a difference. > > >> > > >> I disabled selinux - that made no difference > > >> I stopped and disabled firewalld - that made no difference. > > >> > > >> I can boot this machine after I turn it off and then back on, but when I > > >> try to do a shutdown now -r, the system hangs right after picking the OS > > >> that is desired "CentOS Linux..". > > >> > > >> After the machine is turned off the boot process occurs normally after > > >> this choice and I get two penguins in the upper left hand corner, and > > >> the boot proceeds. When I do a shutdown now -r, I do not get to the > > >> penguins and the machine hangs forever until I either unplug it or press > > >> the power button for 5 seconds. > > >> > > >> Any help would be appreciated!!! > > >> > > >> Greg > > >> > > > --- > > > > > > Everyone, > > > > > > I did not get much of a response on the list so I filed a bug report. I > > > wanted to document the bug report for anyone else that is having a > > > reboot problem. > > > > > > https://bugs.centos.org/view.php?id=7949 > > > > > > > > > Greg Ennis > > > > > > > Seems little point in filing a bug report when you have no idea what the > > issue is. Bugs are not a means of troubleshooting nor a support forum. > > However, you did get my attention so lets see if we can stimulate some > > further interest in troubleshooting this. > > > > So the system will perform a cold reboot, but not a warm reboot. Sounds > > like a hardware issue to me. > > > > Any clues in /var/log/messages ? > > > > Tried updating the BIOS? > > > > Any hardware firmwares being loaded? > > > > > > ___ > > Ned, > > Thanks for your response!!! > > Sorry, if posting a bug report was the wrong venue !!! > > There are no messages in the message logs that I could identify as > problems, but the system fails before the OS is active. > > I have not updated the BIOS, and do not know how to do this... but this > is my testing machine so I am more than open to doing this. I am using > a Gateway SX2855-UB12P. I will take a look at the Gateway site; if > there are tutorials you could point me to I would appreciate it. > > The only hardware that has been added has been a usb ethernet connection > so that I have the motherboard nic card and the usb nic connection. I > wanted to use this setup to test the firewalld capabilities for a > network gateway. The machine does not have a monitor, and is without a > mouse or keyboard. > > It should be noted that this machine previously had CentOS 6 with a 3T > Seagate drive that worked without a problem, but recently developed a > disc failure. I replaced the drive with a 4T WesternDigital drive and > installed CentOs 7.0 from a DVD. > > Thanks again for your help!!! > > Greg > Ned, I have printed the bios of this machine below. I reviewed the American Megatrends website, but have not identified whether an upgrade has been created for this bios, or how to install it. This machine was a Windows7 machine originally with a 500G drive, that I removed and replaced with the 3T Seagate drive that failed. [root@HmWk ~]# dmidecode -t bios -q BIOS Information Vendor: American Megatrends Inc. Version: P01-B2 Release Date: 08/16/2011 Address: 0xF Runtime Size: 64 kB ROM Size: 4096 kB Characteristics: PCI is supported
Re: [CentOS] Help with at Bash script
Am 02.12.2014 um 19:05 schrieb James B. Byrne:
I am attempting to get a script borrowed from DJB to work on my CentOS-6.6
box. Simplified it looks like this:
tcpdump -l -n -e port 53 \
| awk '{if ($14 ~ /A.*?/) print $15}' \
| while read domain ; do echo $domain ; done ;
The sticking point is the 'while read' construct. Run just as 'tcpdum | awk'
I get this:
english.stackexchange.com.
www.urbandictionary.com.
www.urbandictionary.com.
www.urbandictionary.com.
www.urbandictionary.com.
api.mywot.com.
a.udimg.com.
a.udimg.com.
fonts.googleapis.com.
. . .
Run with the 'while read $domain ; do echo ' pipe nothing appears whatsoever.
What am I doing wrong?
while read domain; do
echo ${domain}
done < <(tcpdump -l -n -e port 53 | awk '{if ($14 ~ /A.*?/) print $15}')
The "echo ${domain}" part is certainly just a simplification of a more
complex command to run on the variable. Else it would be pointless as
awk is printing out the domain field 15.
Alexander
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with at Bash script
On Tue, Dec 2, 2014 at 2:19 PM, Alexander Dalloz wrote:
> Am 02.12.2014 um 19:05 schrieb James B. Byrne:
>
>> I am attempting to get a script borrowed from DJB to work on my CentOS-6.6
>> box. Simplified it looks like this:
>>
>> tcpdump -l -n -e port 53 \
>>| awk '{if ($14 ~ /A.*?/) print $15}' \
>>| while read domain ; do echo $domain ; done ;
>>
>> The sticking point is the 'while read' construct. Run just as 'tcpdum |
>> awk'
>> I get this:
>>
>> english.stackexchange.com.
>> www.urbandictionary.com.
>> www.urbandictionary.com.
>> www.urbandictionary.com.
>> www.urbandictionary.com.
>> api.mywot.com.
>> a.udimg.com.
>> a.udimg.com.
>> fonts.googleapis.com.
>> . . .
>>
>> Run with the 'while read $domain ; do echo ' pipe nothing appears
>> whatsoever.
>> What am I doing wrong?
>>
>
> while read domain; do
> echo ${domain}
> done < <(tcpdump -l -n -e port 53 | awk '{if ($14 ~ /A.*?/) print $15}')
>
> The "echo ${domain}" part is certainly just a simplification of a more
> complex command to run on the variable. Else it would be pointless as awk
> is printing out the domain field 15.
>
> Alexander
>
If not a typo in the message, your mistake, and I do it all the time, is
using
while read $domain
instead of
while read domain
Tony
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with at Bash script
Am 02.12.2014 um 20:47 schrieb Tony Schreiner:
while read domain; do
> echo ${domain}
>done < <(tcpdump -l -n -e port 53 | awk '{if ($14 ~ /A.*?/) print $15}')
[ ... ]
>Alexander
>
If not a typo in the message, your mistake, and I do it all the time, is
using
while read $domain
instead of
while read domain
Tony
Tony,
no, "while read $domain" is wrong.
Alexander
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOs 7.0 and reboot failure
On 02/12/14 18:34, Gregory P. Ennis wrote: > On Mon, 2014-12-01 at 18:50 +, Ned Slider wrote: >> On 01/12/14 18:36, Gregory P. Ennis wrote: >>> On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote: On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote: > Date: Sun, 23 Nov 2014 13:50:17 -0600 > > On Sun, 23 Nov 2014 13:07:47 -0600 > Gregory P. Ennis wrote: > >> I also changed the boot level to 5. > > Do you mean the runlevel? If so, are you sure that you changed it > correctly? > > Centos 7 doesn't use runlevels set in inittab like previous versions did. > I see that fact is actually noted in /etc/inittab, along with the > expected way to do it. > - > > Frank, > > Yes, you are correct, I changed the run level and not boot level to 5 > and did so by using the command : > > ln -sf /lib/systemd/system/graphical.target > /etc/systemd/system/default.target > > Also, I appreciate everybody's input on this, but I am still at a loss > as to how to fix this. Without being able to reboot, it sure makes the > set up difficult. > > Does anyone else have any ideas?? > > Greg > I have tried some additional changes that have not made a difference. I disabled selinux - that made no difference I stopped and disabled firewalld - that made no difference. I can boot this machine after I turn it off and then back on, but when I try to do a shutdown now -r, the system hangs right after picking the OS that is desired "CentOS Linux..". After the machine is turned off the boot process occurs normally after this choice and I get two penguins in the upper left hand corner, and the boot proceeds. When I do a shutdown now -r, I do not get to the penguins and the machine hangs forever until I either unplug it or press the power button for 5 seconds. Any help would be appreciated!!! Greg >>> --- >>> >>> Everyone, >>> >>> I did not get much of a response on the list so I filed a bug report. I >>> wanted to document the bug report for anyone else that is having a >>> reboot problem. >>> >>> https://bugs.centos.org/view.php?id=7949 >>> >>> >>> Greg Ennis >>> >> >> Seems little point in filing a bug report when you have no idea what the >> issue is. Bugs are not a means of troubleshooting nor a support forum. >> However, you did get my attention so lets see if we can stimulate some >> further interest in troubleshooting this. >> >> So the system will perform a cold reboot, but not a warm reboot. Sounds >> like a hardware issue to me. >> >> Any clues in /var/log/messages ? >> >> Tried updating the BIOS? >> >> Any hardware firmwares being loaded? >> >> >> ___ > > Ned, > > Thanks for your response!!! > > Sorry, if posting a bug report was the wrong venue !!! > > There are no messages in the message logs that I could identify as > problems, but the system fails before the OS is active. > > I have not updated the BIOS, and do not know how to do this... but this > is my testing machine so I am more than open to doing this. I am using > a Gateway SX2855-UB12P. I will take a look at the Gateway site; if > there are tutorials you could point me to I would appreciate it. You'd have to check the Gateway website to see if a bios update is available to download for your model. Instructions are normally included / available. > > The only hardware that has been added has been a usb ethernet connection > so that I have the motherboard nic card and the usb nic connection. Just to eliminate the easy option first, does unplugging the USB ethernet adapter (before rebooting) solve the problem? > wanted to use this setup to test the firewalld capabilities for a > network gateway. The machine does not have a monitor, and is without a > mouse or keyboard. > > It should be noted that this machine previously had CentOS 6 with a 3T > Seagate drive that worked without a problem, but recently developed a > disc failure. I replaced the drive with a 4T WesternDigital drive and > installed CentOs 7.0 from a DVD. > I wouldn't think the drive swap would make a difference. > Thanks again for your help!!! > > Greg > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Dec 1, 2014, at 10:27 PM, Rob Kampen wrote: > Have you put > NM_CONTROLLED="no" > in the ifcfg-eth0 script? How is that better than systemctl stop NetworkManager systemctl disable NetworkManager Again, I’m not really after a way to make this work without NetworkManager. We’ve already got that. What I want is a way to tell NM to obey the MAC binding. This configuration *here* goes with that MAC chip *there*. Given that, we don’t need to disable NetworkManager. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with at Bash script
On Tue, Dec 2, 2014 at 1:19 PM, Alexander Dalloz wrote:
> Am 02.12.2014 um 19:05 schrieb James B. Byrne:
>>
>> I am attempting to get a script borrowed from DJB to work on my CentOS-6.6
>> box. Simplified it looks like this:
>>
>> tcpdump -l -n -e port 53 \
>>| awk '{if ($14 ~ /A.*?/) print $15}' \
>>| while read domain ; do echo $domain ; done ;
>>
>> The sticking point is the 'while read' construct. Run just as 'tcpdum |
>> awk'
>> I get this:
>>
>> english.stackexchange.com.
>> www.urbandictionary.com.
>> www.urbandictionary.com.
>> www.urbandictionary.com.
>> www.urbandictionary.com.
>> api.mywot.com.
>> a.udimg.com.
>> a.udimg.com.
>> fonts.googleapis.com.
>> . . .
>>
>> Run with the 'while read $domain ; do echo ' pipe nothing appears
>> whatsoever.
>> What am I doing wrong?
Works for me as is. You just have to wait for your pipe buffer to
fill so the output is bursty.
--
Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Tue, Dec 2, 2014 at 2:26 PM, Warren Young wrote: > On Dec 1, 2014, at 10:27 PM, Rob Kampen wrote: > >> Have you put >> NM_CONTROLLED="no" >> in the ifcfg-eth0 script? > > How is that better than > > systemctl stop NetworkManager > systemctl disable NetworkManager > > Again, I’m not really after a way to make this work without NetworkManager. > We’ve already got that. What I want is a way to tell NM to obey the MAC > binding. This configuration *here* goes with that MAC chip *there*. > > Given that, we don’t need to disable NetworkManager. What part of the breakage that NetworkManager does is good for a wired, static-addressed server?But, in your scenario where both nics are plugged in and your only problem is the non-working gateway IP you should be able to ssh to some other box on the working network, then over to the new ones DHCP address. The gateway won't matter if both ends are on the same subnet. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Tue, Dec 2, 2014 at 7:52 AM, James B. Byrne wrote: > > On Mon, December 1, 2014 16:48, Les Mikesell wrote: >> >> Is there anyone who has more than a few boxes at more than one >> location who _doesn't_ have this issue? I'd like to see a FAQ or >> something by whoever designed the network configuration system about >> how they planned for it to work (with and without GUI availability). >> Likewise for what is supposed to happen when you restore a backup onto >> different hardware. >> > > Think 'laptop'. Why would you need a static IP to stick to a laptop? Or have multiple NICs on one? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Dec 2, 2014, at 1:36 PM, Les Mikesell wrote: > On Tue, Dec 2, 2014 at 2:26 PM, Warren Young wrote: >> Again, I’m not really after a way to make this work without NetworkManager. > > What part of the breakage that NetworkManager does is good for a > wired, static-addressed server? If you disable NM, the network configuration GUI stops working in EL7. (I didn’t do much with EL6, but I thought its GUI had a fall-back for the non-NM case.) We don’t need this GUI, but our semi-technical customers sometimes do. It can be the difference between rolling a truck to a remote site vs letting the on-site people take care of the problem. > you should be able to ssh to some other box on the working network, I did mention that these sites rarely have local staff who know Linux. You can correctly infer from that there *are* no other SSH servers, just ours. These are K-12 schools, for the most part. They often don’t have technical staff on-site at all. We have to schedule time with overworked district-level staff who often only know Windows to get anything at this level done. We’ve built up nasty hacks to solve this before; VPN -> RDP -> PuTTY -> Linux server, for instance. Getting protective network admins to allow all this can chew up weeks of time. It’s far, far better if the Linux box just phones home with the info we need to fix it. It can cut a 4-week phone tag game down to 15 minutes. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Dec 2, 2014, at 2:10 PM, Les Mikesell wrote: >> Think 'laptop'. > > Why would you need a static IP to stick to a laptop? Or have > multiple NICs on one? Wired and WiFi. If you configure a static IP with the wired Ethernet plugged in, you probably want that static IP to continue being used when you unplug the Ethernet cable and NM switches you over automatically to WiFi. NM does this. This is why I want a checkbox in the NM GUI: “This is a 4U server, dummy, not a laptop.” ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Tue, Dec 2, 2014 at 3:14 PM, Warren Young wrote: > > >> What part of the breakage that NetworkManager does is good for a >> wired, static-addressed server? > > If you disable NM, the network configuration GUI stops working in EL7. (I > didn’t do much with EL6, but I thought its GUI had a fall-back for the non-NM > case.) > > We don’t need this GUI, but our semi-technical customers sometimes do. It > can be the difference between rolling a truck to a remote site vs letting the > on-site people take care of the problem. But can't you still set NM_CONTROLLED=no on an interface? >> you should be able to ssh to some other box on the working network, > > I did mention that these sites rarely have local staff who know Linux. You > can correctly infer from that there *are* no other SSH servers, just ours. > > These are K-12 schools, for the most part. They often don’t have technical > staff on-site at all. We have to schedule time with overworked > district-level staff who often only know Windows to get anything at this > level done. > We’ve built up nasty hacks to solve this before; VPN -> RDP -> PuTTY -> Linux > server, for instance. Getting protective network admins to allow all this > can chew up weeks of time. I'm way too familiar with the problem - but we usually have several boxes in one place. > It’s far, far better if the Linux box just phones home with the info we need > to fix it. It can cut a 4-week phone tag game down to 15 minutes. I've done some weird stuff like scripts that bring up all the interfaces, look for link, apply one of the IPs that the box should have to one of the interfaces with link up, try to ping the gateway, lather, rinse, repeat, but I've never been happy with any of it. Maybe a USB wifi adapter could be set up to make an openvpn connection back to a home server if you know the location has wifi. That could give you a known private IP to connect to for the rest of the configuration. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Tue, Dec 2, 2014 at 3:17 PM, Warren Young wrote: > On Dec 2, 2014, at 2:10 PM, Les Mikesell wrote: > >>> Think 'laptop'. >> >> Why would you need a static IP to stick to a laptop? Or have >> multiple NICs on one? > > Wired and WiFi. > > If you configure a static IP with the wired Ethernet plugged in, you probably > want that static IP to continue being used when you unplug the Ethernet cable > and NM switches you over automatically to WiFi. NM does this. Really? That's insane. Our wired jacks are not on the same subnets as our access points. I'm not sure that's even possible with the Cisco units that have separate controllers. > This is why I want a checkbox in the NM GUI: “This is a 4U server, dummy, not > a laptop.” How about just 'don't be stupid' ? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Dec 2, 2014, at 2:28 PM, Les Mikesell wrote: > On Tue, Dec 2, 2014 at 3:14 PM, Warren Young wrote: >>> >>> What part of the breakage that NetworkManager does is good for a >>> wired, static-addressed server? >> >> If you disable NM, the network configuration GUI stops working in EL7. > > But can't you still set NM_CONTROLLED=no on an interface? That still effectively breaks the network settings GUI. Interfaces you mark that way show as “unmanaged” in the GUI, and you can’t modify any of their settings. You can’t change them back to “managed” via the GUI. You can’t even add an IP alias to them via the GUI. If you’re suggesting that I do this only to the static interface and leave the DHCP one under NM’s control, the only improvement relative to disabling NM entirely is that it at least gives the semi-technical people on site the option of repurposing the DHCP interface as a secondary static interface. That’s not useless, but it’s a far cry from the MAC bonding I’m after. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Dec 2, 2014, at 2:34 PM, Les Mikesell wrote: > On Tue, Dec 2, 2014 at 3:17 PM, Warren Young wrote: >> On Dec 2, 2014, at 2:10 PM, Les Mikesell wrote: >> Think 'laptop'. >>> >>> Why would you need a static IP to stick to a laptop? Or have >>> multiple NICs on one? >> >> Wired and WiFi. >> >> If you configure a static IP with the wired Ethernet plugged in, you >> probably want that static IP to continue being used when you unplug the >> Ethernet cable and NM switches you over automatically to WiFi. NM does this. > > > Really? That's insane. Our wired jacks are not on the same subnets > as our access points. I'm not sure that's even possible with the > Cisco units that have separate controllers. In such a network, you won’t run static IP configuration on such boxes. You’ll use DHCP. On my home LAN, this automatic static IP migration is *exactly* what I want on my laptop. The current NetworkManager design isn’t unequivocally wrong. It’s a sensible default for Fedora. It’s just not the right choice for enterprise Linux servers. If you want to go and argue that Fedora shouldn’t be driving CentOS, it’s not an impossible position to take, but you have to fill in the blank spot it leaves. What would drive CentOS instead? >> This is why I want a checkbox in the NM GUI: “This is a 4U server, dummy, >> not a laptop.” > > How about just 'don't be stupid’ ? More like “Don’t be clever, NetworkManager, I’m better at it.” ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NetworkManager fights with DHCP-only backup NIC
On Tue, Dec 2, 2014 at 5:00 PM, Warren Young wrote: > >> Really? That's insane. Our wired jacks are not on the same subnets >> as our access points. I'm not sure that's even possible with the >> Cisco units that have separate controllers. > > In such a network, you won’t run static IP configuration on such boxes. > You’ll use DHCP. > > On my home LAN, this automatic static IP migration is *exactly* what I want > on my laptop. I don't get it. Laptops are portable. Don't you ever go out of your house? If you control everything you can easily tell your dhcp server what IP to give it when you are there. > The current NetworkManager design isn’t unequivocally wrong. It’s a sensible > default for Fedora. It’s just not the right choice for enterprise Linux > servers. > > If you want to go and argue that Fedora shouldn’t be driving CentOS, it’s not > an impossible position to take, but you have to fill in the blank spot it > leaves. What would drive CentOS instead? I'd argue that splitting the community into separate groups - one that likes the design of unix/linux and runs large numbers of servers because they like it, and one that would really rather have a windows desktop for their only machine was the wrong thing to do in the first place. And having broken the community, letting the group that doesn't like the product in the first place control the design is probably a bad thing too. Red Hat wasn't that bad back when the people using it contributed directly to its development and were able to use the result. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] DegradedArray message
Received the following message in mail to root: Message 257: >From root@desk4.localdomain Tue Oct 28 07:25:37 2014 Return-Path: X-Original-To: root Delivered-To: root@desk4.localdomain From: mdadm monitoring To: root@desk4.localdomain Subject: DegradedArray event on /dev/md0:desk4 Date: Tue, 28 Oct 2014 07:25:27 -0400 (EDT) Status: RO This is an automatically generated mail message from mdadm running on desk4 A DegradedArray event had been detected on md device /dev/md0. Faithfully yours, etc. P.S. The /proc/mdstat file currently contains the following: Personalities : [raid1] md0 : active raid1 dm-2[1] 243682172 blocks super 1.1 [2/1] [_U] bitmap: 2/2 pages [8KB], 65536KB chunk md1 : active raid1 dm-3[0] dm-0[1] 1953510268 blocks super 1.1 [2/2] [UU] bitmap: 3/15 pages [12KB], 65536KB chunk unused devices: & q Held 314 messages in /var/spool/mail/root You have mail in /var/spool/mail/root Ran a madam query against both raid partitions: [root@desk4 ~]# mdadm --query --detail /dev/md0 /dev/md0: Version : 1.1 Creation Time : Thu Nov 15 19:24:17 2012 Raid Level : raid1 Array Size : 243682172 (232.39 GiB 249.53 GB) Used Dev Size : 243682172 (232.39 GiB 249.53 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Tue Dec 2 20:02:55 2014 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : desk4.localdomain:0 UUID : 29f70093:ae78cf9f:0ab7c1cd:e380f50b Events : 266241 Number Major Minor RaidDevice State 0 000 removed 1 25331 active sync /dev/dm-3 [root@desk4 ~]# [root@desk4 ~]# mdadm --query --detail /dev/md1 /dev/md1: Version : 1.1 Creation Time : Thu Nov 15 19:24:19 2012 Raid Level : raid1 Array Size : 1953510268 (1863.01 GiB 2000.39 GB) Used Dev Size : 1953510268 (1863.01 GiB 2000.39 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Tue Dec 2 20:06:21 2014 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : desk4.localdomain:1 UUID : 1bef270d:36301a24:7b93c7a9:a2a95879 Events : 108306 Number Major Minor RaidDevice State 0 25300 active sync /dev/dm-0 1 25311 active sync /dev/dm-1 [root@desk4 ~]# Appears to me that device 0 (/dev/dm-2) on md0 has been removed because of problems. This is my first encounter with a raid failure. I suspect I should replace disk 0 and let the raid rebuild itself. Seeking guidance and a good source for the procedures. Dave M ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Selinux logging and reporting in centos 7
Seems odd the stock logwatch polls for audit data in messages while the stock config has that data sent to /var/log/audit/audit.log? Not sure why that doesn't have a distro specific override... So on that premise, what are people using for reports on headless c7 instances without a gui? Anything better than logwatch worth investigating? Thanks, jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DegradedArray message
On 02/12/14 08:14 PM, David McGuffey wrote: Received the following message in mail to root: Message 257: From root@desk4.localdomain Tue Oct 28 07:25:37 2014 Return-Path: X-Original-To: root Delivered-To: root@desk4.localdomain From: mdadm monitoring To: root@desk4.localdomain Subject: DegradedArray event on /dev/md0:desk4 Date: Tue, 28 Oct 2014 07:25:27 -0400 (EDT) Status: RO This is an automatically generated mail message from mdadm running on desk4 A DegradedArray event had been detected on md device /dev/md0. Faithfully yours, etc. P.S. The /proc/mdstat file currently contains the following: Personalities : [raid1] md0 : active raid1 dm-2[1] 243682172 blocks super 1.1 [2/1] [_U] bitmap: 2/2 pages [8KB], 65536KB chunk md1 : active raid1 dm-3[0] dm-0[1] 1953510268 blocks super 1.1 [2/2] [UU] bitmap: 3/15 pages [12KB], 65536KB chunk unused devices: & q Held 314 messages in /var/spool/mail/root You have mail in /var/spool/mail/root Ran a madam query against both raid partitions: [root@desk4 ~]# mdadm --query --detail /dev/md0 /dev/md0: Version : 1.1 Creation Time : Thu Nov 15 19:24:17 2012 Raid Level : raid1 Array Size : 243682172 (232.39 GiB 249.53 GB) Used Dev Size : 243682172 (232.39 GiB 249.53 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Tue Dec 2 20:02:55 2014 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : desk4.localdomain:0 UUID : 29f70093:ae78cf9f:0ab7c1cd:e380f50b Events : 266241 Number Major Minor RaidDevice State 0 000 removed 1 25331 active sync /dev/dm-3 [root@desk4 ~]# [root@desk4 ~]# mdadm --query --detail /dev/md1 /dev/md1: Version : 1.1 Creation Time : Thu Nov 15 19:24:19 2012 Raid Level : raid1 Array Size : 1953510268 (1863.01 GiB 2000.39 GB) Used Dev Size : 1953510268 (1863.01 GiB 2000.39 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Tue Dec 2 20:06:21 2014 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : desk4.localdomain:1 UUID : 1bef270d:36301a24:7b93c7a9:a2a95879 Events : 108306 Number Major Minor RaidDevice State 0 25300 active sync /dev/dm-0 1 25311 active sync /dev/dm-1 [root@desk4 ~]# Appears to me that device 0 (/dev/dm-2) on md0 has been removed because of problems. This is my first encounter with a raid failure. I suspect I should replace disk 0 and let the raid rebuild itself. Seeking guidance and a good source for the procedures. Dave M In short, buy a replacement disk equal or greater size, create matching partitions and then use mdadm to add the replacement partition (of appropriate size) back into the array. An example command to add a replacement partition would be: mdadm --manage /dev/md0 --add /dev/sda1 I strongly recommend creating a virtual machine with a pair of virtual disks and simulating the replacement of the drive before trying it out on your real system. In any case, be sure to have good backups (immediately). -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DegradedArray message
On Tue, Dec 02, 2014 at 08:14:19PM -0500, David McGuffey wrote: > Received the following message in mail to root: > > Message 257: > >From root@desk4.localdomain Tue Oct 28 07:25:37 2014 > Return-Path: > X-Original-To: root > Delivered-To: root@desk4.localdomain > From: mdadm monitoring > To: root@desk4.localdomain > Subject: DegradedArray event on /dev/md0:desk4 > Date: Tue, 28 Oct 2014 07:25:27 -0400 (EDT) > Status: RO > > This is an automatically generated mail message from mdadm > running on desk4 > > A DegradedArray event had been detected on md device /dev/md0. > > Faithfully yours, etc. > > P.S. The /proc/mdstat file currently contains the following: > > Personalities : [raid1] > md0 : active raid1 dm-2[1] > 243682172 blocks super 1.1 [2/1] [_U] > bitmap: 2/2 pages [8KB], 65536KB chunk > > md1 : active raid1 dm-3[0] dm-0[1] > 1953510268 blocks super 1.1 [2/2] [UU] > bitmap: 3/15 pages [12KB], 65536KB chunk > > unused devices: Could be a bad drive, as digimer alludes in his reply. OTOH, I had a perfectly good drive get kicked out of my RAID-1 array a fewyears ago just because, well, I guess I could say "it felt like it". In reality, I had (in my ignorance) purchased a pair of WD drives that aren't intended to be used in a RAID array, and once in a long while (that was actually the only such instance in the 4-5 years I've had that RAID array) it doesn't respond to some HD command or other and gets dropped. turned out to be easy to reinsert it and it ran for a long time thereafter without trouble. I can dig for the info on the drives and the nature of the problem if anyone wants to see it. Fred -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The Lord is like a strong tower. Those who do what is right can run to him for safety. --- Proverbs 18:10 (niv) - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DegradedArray message
On 2014-12-03, David McGuffey wrote: > > Appears to me that device 0 (/dev/dm-2) on md0 has been removed because > of problems. That looks about right. There may be more error messages in your system logs (e.g., /var/log/messages, dmesg), which might tell you more about the nature of the failure. > This is my first encounter with a raid failure. I suspect I should > replace disk 0 and let the raid rebuild itself. > > Seeking guidance and a good source for the procedures. The linux RAID wiki is often a good (though sometimes dated) resource. https://raid.wiki.kernel.org/index.php/Reconstruction If you wish to attempt a hot swap, make *sure* you pull the correct device! If you're not sure, or not sure your system even supports it, it's safer to power down to do the swap. You should verify which drive has failed before shutting down, though this will be less catastrophic if you pick the wrong one. As long as you are careful, reconstructing a degraded RAID is usually pretty straightforward. --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DegradedArray message
On 12/2/2014 6:24 PM, Fred Smith wrote: In reality, I had (in my ignorance) purchased a pair of WD drives that aren't intended to be used in a RAID array, and once in a long while (that was actually the only such instance in the 4-5 years I've had that RAID array) it doesn't respond to some HD command or other and gets dropped. desktop class SATA drives will report 'write successful' when there's still data in its buffers, so the raid will happily continue, then if the drive actually gets a unrecoverable write error, things are toast, the raid is out of sync. this is a major reason I'm leaning towards using ZFS for future raids (primarily via using FreeBSD), because ZFS checksums and timestamps every block it writes, so it can look at the two blocks that a regular raid can only say "something is wrong here, but what it is I ain't exactly sure" and go "A is good, B is bad/stale, lets replicate A back to B", as part of the zpool 'scrub' process. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOs 7.0 and reboot failure
On Tue, 2014-12-02 at 16:32 -0600, Gregory P. Ennis wrote: > On Tue, 2014-12-02 at 20:23 +, Ned Slider wrote: > > On 02/12/14 18:34, Gregory P. Ennis wrote: > > > On Mon, 2014-12-01 at 18:50 +, Ned Slider wrote: > > >> On 01/12/14 18:36, Gregory P. Ennis wrote: > > >>> On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote: > > On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote: > > > Date: Sun, 23 Nov 2014 13:50:17 -0600 > > > > > > On Sun, 23 Nov 2014 13:07:47 -0600 > > > Gregory P. Ennis wrote: > > > > > >> I also changed the boot level to 5. > > > > > > Do you mean the runlevel? If so, are you sure that you changed it > > > correctly? > > > > > > Centos 7 doesn't use runlevels set in inittab like previous versions > > > did. I see that fact is actually noted in /etc/inittab, along with > > > the expected way to do it. > > > - > > > > > > Frank, > > > > > > Yes, you are correct, I changed the run level and not boot level to 5 > > > and did so by using the command : > > > > > > ln -sf /lib/systemd/system/graphical.target > > > /etc/systemd/system/default.target > > > > > > Also, I appreciate everybody's input on this, but I am still at a loss > > > as to how to fix this. Without being able to reboot, it sure makes > > > the > > > set up difficult. > > > > > > Does anyone else have any ideas?? > > > > > > Greg > > > > > > > I have tried some additional changes that have not made a difference. > > > > I disabled selinux - that made no difference > > I stopped and disabled firewalld - that made no difference. > > > > I can boot this machine after I turn it off and then back on, but when > > I > > try to do a shutdown now -r, the system hangs right after picking the > > OS > > that is desired "CentOS Linux..". > > > > After the machine is turned off the boot process occurs normally after > > this choice and I get two penguins in the upper left hand corner, and > > the boot proceeds. When I do a shutdown now -r, I do not get to the > > penguins and the machine hangs forever until I either unplug it or > > press > > the power button for 5 seconds. > > > > Any help would be appreciated!!! > > > > Greg > > > > >>> --- > > >>> > > >>> Everyone, > > >>> > > >>> I did not get much of a response on the list so I filed a bug report. I > > >>> wanted to document the bug report for anyone else that is having a > > >>> reboot problem. > > >>> > > >>> https://bugs.centos.org/view.php?id=7949 > > >>> > > >>> > > >>> Greg Ennis > > >>> > > >> > > >> Seems little point in filing a bug report when you have no idea what the > > >> issue is. Bugs are not a means of troubleshooting nor a support forum. > > >> However, you did get my attention so lets see if we can stimulate some > > >> further interest in troubleshooting this. > > >> > > >> So the system will perform a cold reboot, but not a warm reboot. Sounds > > >> like a hardware issue to me. > > >> > > >> Any clues in /var/log/messages ? > > >> > > >> Tried updating the BIOS? > > >> > > >> Any hardware firmwares being loaded? > > >> > > >> > > >> ___ > > > > > > Ned, > > > > > > Thanks for your response!!! > > > > > > Sorry, if posting a bug report was the wrong venue !!! > > > > > > There are no messages in the message logs that I could identify as > > > problems, but the system fails before the OS is active. > > > > > > I have not updated the BIOS, and do not know how to do this... but this > > > is my testing machine so I am more than open to doing this. I am using > > > a Gateway SX2855-UB12P. I will take a look at the Gateway site; if > > > there are tutorials you could point me to I would appreciate it. > > > > You'd have to check the Gateway website to see if a bios update is > > available to download for your model. Instructions are normally included > > / available. > > > > > > > > The only hardware that has been added has been a usb ethernet connection > > > so that I have the motherboard nic card and the usb nic connection. > > > > > > Just to eliminate the easy option first, does unplugging the USB > > ethernet adapter (before rebooting) solve the problem? > > > > > > > wanted to use this setup to test the firewalld capabilities for a > > > network gateway. The machine does not have a monitor, and is without a > > > mouse or keyboard. > > > > > > It should be noted that this machine previously had CentOS 6 with a 3T > > > Seagate drive that worked without a problem, but recently developed a > > > disc failure. I replaced the drive with a 4T WesternDigital drive and > >
Re: [CentOS] Help with at Bash script
You have to do
cat domain
in back tiks
instead of read domain.
(Sent from iPhone, so please accept my apologies in advance for any spelling or
grammatical errors.)
> On Dec 2, 2014, at 12:05 PM, James B. Byrne wrote:
>
> I am attempting to get a script borrowed from DJB to work on my CentOS-6.6
> box. Simplified it looks like this:
>
> tcpdump -l -n -e port 53 \
> | awk '{if ($14 ~ /A.*?/) print $15}' \
> | while read domain ; do echo $domain ; done ;
>
> The sticking point is the 'while read' construct. Run just as 'tcpdum | awk'
> I get this:
>
> english.stackexchange.com.
> www.urbandictionary.com.
> www.urbandictionary.com.
> www.urbandictionary.com.
> www.urbandictionary.com.
> api.mywot.com.
> a.udimg.com.
> a.udimg.com.
> fonts.googleapis.com.
> . . .
>
> Run with the 'while read $domain ; do echo ' pipe nothing appears whatsoever.
> What am I doing wrong?
>
> --
> *** E-Mail is NOT a SECURE channel ***
> James B. Byrnemailto:byrn...@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
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with at Bash script
What is domain, BTW?
(Sent from iPhone, so please accept my apologies in advance for any spelling or
grammatical errors.)
> On Dec 2, 2014, at 12:05 PM, James B. Byrne wrote:
>
> I am attempting to get a script borrowed from DJB to work on my CentOS-6.6
> box. Simplified it looks like this:
>
> tcpdump -l -n -e port 53 \
> | awk '{if ($14 ~ /A.*?/) print $15}' \
> | while read domain ; do echo $domain ; done ;
>
> The sticking point is the 'while read' construct. Run just as 'tcpdum | awk'
> I get this:
>
> english.stackexchange.com.
> www.urbandictionary.com.
> www.urbandictionary.com.
> www.urbandictionary.com.
> www.urbandictionary.com.
> api.mywot.com.
> a.udimg.com.
> a.udimg.com.
> fonts.googleapis.com.
> . . .
>
> Run with the 'while read $domain ; do echo ' pipe nothing appears whatsoever.
> What am I doing wrong?
>
> --
> *** E-Mail is NOT a SECURE channel ***
> James B. Byrnemailto:byrn...@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
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] Radeon graphics problems with CentOS 6.6
Hello, I saw in the CentOS 6.6 release notes that the Xorg ABI has changed but that "This should not concern anyone who uses the default drivers shipped with CentOS." I'm using the ATI drivers in Base but X still fails when I boot a CentOS 6.6 kernel. I was hoping this is a known problem that would get fixed with a kernel update but I'm still having problems with the 2.6.32-504.1.3.el6.x86_64 kernel. Relevant info below. Any ideas? Thanks, Darby [root@c6 ~]# lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6530D] [root@c6 ~]# uname -a Linux c6 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@c6 ~]# yum list xorg-x11-drv-ati.x86_64 xorg-x11-drv-ati-firmware.noarch Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: repos.dfw.quadranet.com * epel: mirror.compevo.com * extras: repos.dfw.quadranet.com * updates: repos.dfw.quadranet.com Installed Packages xorg-x11-drv-ati.x86_647.3.99-2.el6 @base xorg-x11-drv-ati-firmware.noarch 7.3.99-2.el6 @base [root@c6 ~]# Log messages containing "radeon" from booting into the CentOS 6.6 kernel: c6 kernel: [drm] radeon kernel modesetting enabled. c6 kernel: fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver c6 kernel: radeon :00:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 c6 kernel: radeon :00:01.0: VRAM: 512M 0x - 0x1FFF (512M used) c6 kernel: radeon :00:01.0: GTT: 1024M 0x2000 - 0x5FFF c6 kernel: [drm] radeon: 512M of VRAM memory ready c6 kernel: [drm] radeon: 1024M of GTT memory ready. c6 kernel: radeon :00:01.0: firmware: requesting radeon/SUMO_pfp.bin c6 kernel: radeon :00:01.0: firmware: requesting radeon/SUMO_me.bin c6 kernel: radeon :00:01.0: firmware: requesting radeon/SUMO_rlc.bin c6 kernel: [drm] radeon: dpm initialized c6 kernel: radeon :00:01.0: firmware: requesting radeon/SUMO_uvd.bin c6 kernel: radeon :00:01.0: WB enabled c6 kernel: radeon :00:01.0: fence driver on ring 0 use gpu addr 0x2c00 and cpu addr 0x8801b6e81c00 c6 kernel: radeon :00:01.0: fence driver on ring 3 use gpu addr 0x2c0c and cpu addr 0x8801b6e81c0c c6 kernel: radeon :00:01.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xc900229b2118 c6 kernel: radeon :00:01.0: radeon: using MSI. c6 kernel: [drm] radeon: irq initialized. c6 kernel: [drm] Radeon Display Connectors c6 kernel: fbcon: radeondrmfb (fb0) is primary device c6 kernel: radeon :00:01.0: fb0: radeondrmfb frame buffer device c6 kernel: radeon :00:01.0: registered panic notifier c6 kernel: [drm] Initialized radeon 2.37.0 20080528 for :00:01.0 on minor 0 c6 kernel: powernow-k8: Found 1 AMD A6-3600 APU with Radeon(tm) HD Graphics (4 cpu cores) (version 2.20.00) Log messages from booting into the CentOS 6.5 kernel: c6 kernel: [drm] radeon kernel modesetting enabled. c6 kernel: fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver c6 kernel: radeon :00:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 c6 kernel: radeon :00:01.0: VRAM: 512M 0x - 0x1FFF (512M used) c6 kernel: radeon :00:01.0: GTT: 512M 0x2000 - 0x3FFF c6 kernel: [drm] radeon: 512M of VRAM memory ready c6 kernel: [drm] radeon: 512M of GTT memory ready. c6 kernel: platform radeon_cp.0: firmware: requesting radeon/SUMO_pfp.bin c6 kernel: platform radeon_cp.0: firmware: requesting radeon/SUMO_me.bin c6 kernel: platform radeon_cp.0: firmware: requesting radeon/SUMO_rlc.bin c6 kernel: radeon :00:01.0: WB enabled c6 kernel: radeon :00:01.0: fence driver on ring 0 use gpu addr 0x2c00 and cpu addr 0x8801b83aec00 c6 kernel: radeon :00:01.0: fence driver on ring 3 use gpu addr 0x2c0c and cpu addr 0x8801b83aec0c c6 kernel: radeon :00:01.0: radeon: using MSI. c6 kernel: [drm] radeon: irq initialized. c6 kernel: [drm] Radeon Display Connectors c6 kernel: [drm] radeon: power management initialized c6 kernel: fbcon: radeondrmfb (fb0) is primary device c6 kernel: radeon :00:01.0: fb0: radeondrmfb frame buffer device c6 kernel: radeon :00:01.0: registered panic notifier c6 kernel: [drm] Initialized radeon 2.30.0 20080528 for :00:01.0 on minor 0 c6 kernel: powernow-k8: Found 1 AMD A6-3600 APU with Radeon(tm) HD Graphics (4 cpu cores) (version 2.20.00) c6 kernel: CPU0: AMD A6-3600 APU with Radeon(tm) HD Graphics stepping 00 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with at Bash script
On 2014-12-03, Hal Wigoda wrote: > You have to do > cat domain > in back tiks > > instead of read domain. This is an error you can't blame on your device. domain is not a file, but a bash variable. read takes stdin (which is what the OP's snippet is doing) and populates the named variable(s) (domain in this case). --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Help with at Bash script
Never used that construct in this context. On Tue, Dec 2, 2014 at 11:07 PM, Keith Keller wrote: > On 2014-12-03, Hal Wigoda wrote: >> You have to do >> cat domain >> in back tiks >> >> instead of read domain. > > This is an error you can't blame on your device. domain is not a file, > but a bash variable. read takes stdin (which is what the OP's snippet > is doing) and populates the named variable(s) (domain in this case). > > --keith > > > -- > kkel...@wombat.san-francisco.ca.us > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos -- - Hal Wigoda Chicago ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DegradedArray message
On 12/03/2014 03:24 AM, Fred Smith wrote: OTOH, I had a perfectly good drive get kicked out of my RAID-1 array a fewyears ago just because, well, I guess I could say "it felt like it". I've seen that too several times on my home "server". Once in a while (usually on one of the first days I'm on vacation) one of the drives stops responding. A shutdown and cold restart is necessary to bring the drive alive again, just a reboot won't fix it. After this, I rebuild the RAID partitions and all is OK. smartctl shows no sign of problems with the drive, so I suspect a controller problem. This is on a desktop machine used as a server. I guess this explains why we have server grade hardware :-) Mogens -- Mogens Kjaer, m...@lemo.dk http://www.lemo.dk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
