Re: [CentOS] replace string with sed but not the first one

[maverh]

Thanks


- Oorspronkelijk e-mail -
Van: "Mark Pryor" 
Aan: "CentOS mailing list" 
Verzonden: Dinsdag 19 juni 2012 07:36:54
Onderwerp: Re: [CentOS] replace string with sed but not the first one





- Original Message -
From: "mav...@telenet.be" 
To: centos@centos.org
Cc: 
Sent: Monday, June 18, 2012 10:30 PM
Subject: [CentOS] replace string with sed but not the first one




Hi, 
  
We have a the following file 
[ip-map] 
# Unchanged IP addresses: 
# Please review default IP addresses mapping below: 
192.168.1.10 shared    ->  192.168.123.6 shared 
[namexx] 
192.168.1.10 
naam   192.168.1.10 



We want to replace 192.168.1.10  to a other string but i don't want to change 
te first one. 
---
cat >> cml.txt<  192.168.123.6 shared 
[namexx] 
192.168.1.10 
naam   192.168.1.10 
EOL

sed -i -e 's/192.168.1.10$/192.168.1.11/g' cml.txt

-- 
Mark

___
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] vlc?

[Nicolas Thierry-Mieg]

Le 18/06/2012 22:00, m.r...@5-cent.us a écrit :
>
> I think you didn't read all of what I asked: none of the std. repos for
> CentOS have it (nor for 6.2); it seems to be at repoforge, yes, I do know

it's not in centos base, but as far as third party repos go repoforge is 
as standard as it gets. If you have epel configured and active you can 
get conflicts though. If you enable only centos and repoforge installing 
vlc should work, otherwise it means you have already installed some 
packages from another third party repo that cause a conflict.
vlc does have a lot of deps, as do most other media players. That's not 
something to worry about.
BTW you may want to try xine and mplayer as well, also available in 
repoforge and also very good players.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] we want to delete all files in a folder except the files with the most recent date

[maverh]

Hi, 

We want to delete all files in a folder except the files with the most recent 
date 
example 

ls -l 
jun 3 10:45 file1 
jun 3 12:20 file2 
jun 2 10:20 file3 
jun 2 05:00 file4 
jun 1 12:00 file5 
jun 1 10:00 file6 

jun2 en jun1 must be deleted 

regards, 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] we want to delete all files in a folder except the files with the most recent date

[John R Pierce]

On 06/19/12 12:26 AM, mav...@telenet.be wrote:
> We want to delete all files in a folder except the files with...

man find


I suggest you get a book on basic unix systems management.




-- 
john r pierceN 37, W 122
santa cruz ca mid-left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] What would cause dbus-daemon to fork() bomb?

[Robert Heller]

For some reason, my system (64-bit, CentOS 5.8) has started to have a
strange problem: dbus-daemon fork() bombing, typically overnight.  The
machine has been fine for months and months.  What could cause this?
This is my home desktop (it is also a server on my lan: dhcp, ldap,
dns, web, etc.).

-- 
Robert Heller -- 978-544-6933 / hel...@deepsoft.com
Deepwoods Software-- http://www.deepsoft.com/
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments


 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Configure Kickstart

[jiten jha]

Dear Friend ,

I want you help to configure kickstart on my centos5.4 server . I search on
google and found so many way to configure it even on centos web site also.
But It is not working and i am know so I can not understand it. So please
send me link that i can understand and configure it.

-- 
Regards
Jitendra Jha
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] we want to delete all files in a folder except the files with the most recent date

[Ken godee]

#!/bin/sh
find /files/* -mtime +2 -exec rm {} \;



On 6/19/2012 12:26 AM, mav...@telenet.be wrote:
>
>
> Hi,
>
> We want to delete all files in a folder except the files with the most recent 
> date
> example
>
> ls -l
> jun 3 10:45 file1
> jun 3 12:20 file2
> jun 2 10:20 file3
> jun 2 05:00 file4
> jun 1 12:00 file5
> jun 1 10:00 file6
>
> jun2 en jun1 must be deleted
>
> regards,
> ___
> 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] Configure Kickstart

[John Doe]

From: jiten jha 

> I want you help to configure kickstart on my centos5.4 server . I search on
> google and found so many way to configure it even on centos web site also.
> But It is not working and i am know so I can not understand it. So please
> send me link that i can understand and configure it.

http://www.microsofttranslator.com/bv.aspx?from=en&to=hi&a=http://fedoraproject.org/wiki/Anaconda/Kickstart

JD
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Configure Kickstart

[Pete Travis]

On Jun 19, 2012 9:04 AM, "John Doe"  wrote:
>
> From: jiten jha 
>
> > I want you help to configure kickstart on my centos5.4 server . I
search on
> > google and found so many way to configure it even on centos web site
also.
> > But It is not working and i am know so I can not understand it. So
please
> > send me link that i can understand and configure it.
>
>
http://www.microsofttranslator.com/bv.aspx?from=en&to=hi&a=http://fedoraproject.org/wiki/Anaconda/Kickstart
>
> JD
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

The anaconda guys update that resource as they go along. As the bleeding
edge of anaconda docs, many described features won't even be realized in
the most recent Fedora release.  However, the Installation Guides at
https://docs.fedoraproject.org should reflect the feature set of a given
anaconda version, and are already translated into many languages.

The RHEL Installation Guide also documents the kickstart process.

--pete
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Deleting Files

[Matt]

>> I want to safely delete all files in a certain directory that are
>> exactly 32 characters long.  This is on CentOS 5.x.  How would I do
>> that?
>
> Let me guess; homework...  'cos this sure ain't a CentOS question!

No, cluttered directory.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 88, Issue 11

[centos-announce-request]

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. CESA-2012:0744 Moderate CentOS 6 python Update (Johnny Hughes)
   2. CESA-2012:0743 Important CentOS 6 kernel Update (Johnny Hughes)


--

Message: 1
Date: Mon, 18 Jun 2012 16:35:36 +
From: Johnny Hughes 
Subject: [CentOS-announce] CESA-2012:0744 Moderate CentOS 6 python
Update
To: centos-annou...@centos.org
Message-ID: <20120618163536.ga1...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2012:0744 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0744.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 


i386:
68b40bb24637e5151d56ff980b14ede5db07951b6325d9a54ead3498527e65fd  
python-2.6.6-29.el6_2.2.i686.rpm
8bcda8f75bde9eae4b89b264a28be6596a5a0bbe74caa150c745e0c517f59533  
python-devel-2.6.6-29.el6_2.2.i686.rpm
a97bcae9e9764c21665fd4b43f3ef67897b8aa336c997078b5b079df1a3f458b  
python-libs-2.6.6-29.el6_2.2.i686.rpm
0d659305707e6e7eabbdbf14b06367a4c2220c7c8446469d02851d1d9291a25d  
python-test-2.6.6-29.el6_2.2.i686.rpm
d45f3d643582177adf242981bf66c89a8bcdf048bd64cdfceed6248a5e07364a  
python-tools-2.6.6-29.el6_2.2.i686.rpm
5f5c9798bf941d3061a159484a1816b29cef3928404eda6da69ceb661d6439d3  
tkinter-2.6.6-29.el6_2.2.i686.rpm

x86_64:
68b40bb24637e5151d56ff980b14ede5db07951b6325d9a54ead3498527e65fd  
python-2.6.6-29.el6_2.2.i686.rpm
9d5f64d06c7cc75c166f635bd8d0a842d999d5a1f46ba51eb57c2b4ce3ac09f1  
python-2.6.6-29.el6_2.2.x86_64.rpm
8bcda8f75bde9eae4b89b264a28be6596a5a0bbe74caa150c745e0c517f59533  
python-devel-2.6.6-29.el6_2.2.i686.rpm
cd2eeb31d0c9795045d7fb38abe545193393af71257d98e382ca2a3c5d314e51  
python-devel-2.6.6-29.el6_2.2.x86_64.rpm
a97bcae9e9764c21665fd4b43f3ef67897b8aa336c997078b5b079df1a3f458b  
python-libs-2.6.6-29.el6_2.2.i686.rpm
901dd463ec89fb78dfc7f67e23f3d045422fd2d5a83d4d2bfa0ec4ea4aa4f929  
python-libs-2.6.6-29.el6_2.2.x86_64.rpm
de7ddc6b116cd5b88aabb4d6b00d2f41bc0f95aa247c6e21790f59e78c58464b  
python-test-2.6.6-29.el6_2.2.x86_64.rpm
00a7b81b38b804b71667f45570c54c5910c4d53c08aeb8072d21d4a381c5f4ac  
python-tools-2.6.6-29.el6_2.2.x86_64.rpm
98339b5d758e08f8e9b6753c403da3879250b2d474197727cb417263f902efdf  
tkinter-2.6.6-29.el6_2.2.x86_64.rpm

Source:
e6e6fdbb082ebe1240c55739e9ba357a86fd37a59b757fa51faf174e18526c96  
python-2.6.6-29.el6_2.2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Tue, 19 Jun 2012 10:27:24 +
From: Johnny Hughes 
Subject: [CentOS-announce] CESA-2012:0743 Important CentOS 6 kernel
Update
To: centos-annou...@centos.org
Message-ID: <20120619102724.ga20...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2012:0743 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0743.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 


i386:
ea56dcbea54d7249587d63c247dd5cda34b92a3cef1b281c82441400ef71  
kernel-2.6.32-220.23.1.el6.i686.rpm
e47fb9d96ad61173552f60a5e10bd6a81a30f1a3b35327bf8dbabfed7616e5e2  
kernel-debug-2.6.32-220.23.1.el6.i686.rpm
c94d9f48253cdf655c88366fd7d2341e4d3247c77f266a5a14abf372a4cefc03  
kernel-debug-devel-2.6.32-220.23.1.el6.i686.rpm
0e269b17567c91f68f9b8926de52c331515f71efb2575a42f297a561ec9a1943  
kernel-devel-2.6.32-220.23.1.el6.i686.rpm
c1a415fcb071c2eb3f0337d55063590a3d45a2185a253b3ab8092569e24970cb  
kernel-doc-2.6.32-220.23.1.el6.noarch.rpm
ae35c0d77e4968b882a4f419ca00c87171ae23f909f0ddefb61316e3c33b6676  
kernel-firmware-2.6.32-220.23.1.el6.noarch.rpm
5c98cd2662d7a7350ce19c95f5666c0bd8db7a7a1f85a4aac5eec89cdd6d3b50  
kernel-headers-2.6.32-220.23.1.el6.i686.rpm
766ad9e000c8e6d65a09352bb98956eaa0e92808de2e0621df05f6f6136fcfd8  
perf-2.6.32-220.23.1.el6.i686.rpm
adb363026b40404f4a6e445b6d247787a51f4c270e9a477a5704bbb1b9bdacfd  
python-perf-2.6.32-220.23.1.el6.i686.rpm

x86_64:
2d950cad03e58fbe41b18ea9f676e9f8035c50e1110e35d7ade84357d531b0b0  
kernel-2.6.32-220.23.1.el6.x86_64.rpm
cbdc58c22ea03c12a2a06c56d448d3fabeb88cb0e807b801b8f7366e7dc5753d  
kernel-debug-2.6.32-220.23.1.el6.x86_64.rpm
8d4a7488b3cf9797c4f0a2770a2b6545eebbd8db2f3675e8d72c47f2566792df  
kernel-debug-devel-2.6.32-220.23.1.el6.x86_64.rpm
e1a91610aef2da26f16df08e67e7103c939e8

Re: [CentOS] Best way to duplicate a live Centos 5 server?

[Cal Sawyer]

Subject: Re: [CentOS] Best way to duplicate a live Centos 5 server?
To: CentOS mailing list 
On Mon, Jun 18, 2012 at 11:21 AM,
Cal Sawyer  wrote:
>> >
>> > ReaR has suddenly become very interesting to me, probably explaining why
>> > it utterly fails to work properly (for me).I'm using 1.13 to pull a
>> > USB-based recovery image, but there's an error in the
>> > backup/NETFS/default/50_make_backup.sh script that doesn't mount the USB
>> > device after the mkrecovery step, so subsequent tar fails on write to
>> > the non-existent mountpoint. I fixed that, but on recovery it fails to
>> > mount the necessary directories on the restore drive as well, so "rear
>> > recover" quickly bombs out. Is anyone having any success actually using
>> > ReaR on CentOS 6.x? - csawyer
> It intentionally doesn't deal with drives the kernel has marked as
> removable.   I had trouble with that with the main drives on a SAS
> hotswap backplane in an earlier version but I think that is fixed now.
>
> I'd recommend asking how to override this on the ReaR mail list.
> While the code seems usable (and yes, I have succeeded in using it on
> Centos 6x.), the documentation either doesn't exist yet or is very out
> of date.   But, the authors are very responsive and it would be good
> to let them know about any bugs or usability problems.  The mail list
> is still at sourceforge although the code has been moved to github and
> there is talk of moving the list elsewhere.
>
> -- Les Mikesell lesmikes...@gmail.com

ReaR hasn't posed any insurmountable problems with USB removable media
but i can see SATA/SAS needing some massaging in the device detection dep't.

Yes, i've gotten myself on the ReaR mailing list now. 

You're right - documentation is pretty dire.  Guess i'm not alone in
hating doing it.

USB backup is broken due to the order in which path variables get set -
sure is lot of fun trawling through the scripts to find out what gets
set when.  Hope the ReaR maintainers are interested in this and haven't
gotten themselves mired in tape
archive integration - i would have thought USB backup was the winner in
terms of getting broad acceptance as a bare-metal DR solution.

However, when it works - wow.  Just restored an HP dl360 w/HWRAID to a
Presario desktop machine and it lives!  No network, but that's small
beans compared to the larger win.

- csawyer
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Resizing est4 filesystem while mounted

[Jeff Boyce]

Replying to the daily digest, with my response at the bottom.


> Message: 18
> Date: Mon, 18 Jun 2012 22:28:31 +0200
> From: Dennis Jacobfeuerborn 
> Subject: Re: [CentOS] Resizing est4 filesystem while mounted
> To: centos@centos.org
> Message-ID: <4fdf8f6f.8030...@conversis.de>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 06/18/2012 10:09 PM, Jeff Boyce wrote:
>> Replying to the daily digest, with my response at the bottom.
>>
>>
>>
>>> Message: 13
>>> Date: Fri, 15 Jun 2012 12:22:08 -0700
>>> From: Ray Van Dolson 
>>> Subject: Re: [CentOS] Resizing est4 filesystem while mounted
>>> To: centos@centos.org
>>> Message-ID: <20120615192207.ga23...@bludgeon.org>
>>> Content-Type: text/plain; charset=us-ascii
>>>
>>> On Fri, Jun 15, 2012 at 12:10:09PM -0700, Jeff Boyce wrote:
 Greetings -

 I had a logical volume that was running out of space on a virtual
 machine.
 I successfully expanded the LV using lvextend, and lvdisplay shows that
 it
 has been expanded. Then I went to expand the filesystem to fill the new
 space (# resize2fs -p /dev/vde1) and I get the results that the
 filesystem
 is already xx blocks long, nothing to do. If I do a # df -h, I can see
 that
 the filesystem has not been extended. I could kick the users off the 
 VM,
 reboot the VM using a GParted live CD and extend the filesystem that 
 way,
 but I thought that it was possible to do this live and mounted? The RH
 docs
 say this is possible; the man page for resize2fs also says it is 
 possible
 with ext4. What am I missing here? This is a Centos 6.2 VM with an ext4
 filesystem. The logical volumes are setup on the host system which is
 also
 a Centos 6.2 system.
>>>
>>> Try resize4fs (assuming your FS is ext4).
>>>
>>> Ray
>>
>> Well, I have never seen a reference to resize4fs before (and yes my FS is
>> ext4).  It is not on my Centos 6.2 system, and doing a little searching
>> through repositories for that specifically, or e4fsprogs, and I can't 
>> find
>> it anywhere to even try it.  Any google reference seems to point back to
>> resize2fs.  I ended up booting a live SystemRescueCD and using GParted 
>> via
>> the GUI.  My notes indicate that is what I had done previously also.  I 
>> am
>> still stumped, everything that I have read indicates that resize2fs can 
>> do a
>> live resizing on ext4 file systems.  Can anybody confirm or deny this? 
>> Is
>> the reason I can't do this because it is on an LVM logical volume? 
>> Thanks.
>
> Please post some details about your storage topology. Without this
> information its not really possible to be sure what is going on.
> resizefs cannot work as long as the underlying layers don't see any change
> in size and you didn't seem to look for that.
>
> Regards,
>   Dennis


I provided some of that information in my original post, but if you can help 
explain why I couldn't seem to resize the file system while mounted here is 
more information.

Host system is Centos 6.2 on a Dell PE T610 with hardware raid on a PERC 
H700.  Raid 5 is setup across three disks with a fourth hot spare.  I have 
created a volume group within the raid 5 encompassing most of my drive 
space.  Within the VG I have created numerous logical volumes that are 
assigned to specific systems.

Volume Group:  vg_mei
Logical Volumes:
   lv_earthroot
   lv_earthswap
   lv_earthvar
   lv_sequoiaroot
   lv_sequoiaswap
   lv_sequoiavar
   lv_sequoiahome
   lv_sequoiaecosystem

Earth is my host system and Sequoia is one of the guest systems. 
lv_sequoiaecosystem is the space dedicated to our Samba server and is the LV 
that I was expanding to make more space available to the rest of the staff. 
I had successfully extended lv_sequoiaecosystem using the following command 
from root on earth (lvextend -L+50G /dev/vg_mei/lv_sequoiaecosystem). 
Issuing the command  (lvdisplay /dev/vg_mei/lv_sequoiaecosystem) following 
this showed that the LV was successfully extended from 100 to 150 GB.

I then logged onto sequoia as root and issued a df -h to determine which 
device needed the file system to be resized (/dev/vde1).  The output below 
is current, after I resized the filesystem using GParted.

[root@sequoia ~]# df -h
FilesystemSize  Used Avail Use% Mounted on
/dev/vda2 4.5G  2.5G  1.8G  59% /
tmpfs1004M  112K 1004M   1% /dev/shm
/dev/vda1 485M   55M  406M  12% /boot
/dev/vde1 148G   85G   56G  61% /ecosystem
/dev/vdd1  20G  1.3G   18G   7% /home
/dev/vdc1 2.0G  266M  1.7G  14% /var

Then from root on sequoia I issued the command (resize2fs -p /dev/vde1) and 
got back the result that the filesystem is already 26214144 blocks long, 
nothing to do.  That is when I posted my first question about not being able 
to resize a live mounted filesystem.  Is that enough information for your 
question, or is there something that I am not providing?  Thanks.

Jeff

Re: [CentOS] Best way to duplicate a live Centos 5 server?

[Les Mikesell]

On Tue, Jun 19, 2012 at 12:03 PM, Cal Sawyer  wrote:
>
> You're right - documentation is pretty dire.  Guess i'm not alone in
> hating doing it.

Yes, I really, really wish the stuff they are doing was documented,
somewhere, anywhere.  Not just how to use the program itself which is
supposed to 'just work' unattended once you set it up, but the black
magic of how they detect and reproduce all of the hardware, lvm, raid,
filesystem, etc. across different distributions and versions.

> USB backup is broken due to the order in which path variables get set -
> sure is lot of fun trawling through the scripts to find out what gets
> set when.  Hope the ReaR maintainers are interested in this and haven't
> gotten themselves mired in tape
> archive integration - i would have thought USB backup was the winner in
> terms of getting broad acceptance as a bare-metal DR solution.

USB is sort of 'hands-on' for something that should be unattended, and
adds a lot of unpredictable messiness in drive detection, boot order,
etc.All you really have to do is export some NFS space and point
ReaR to it.  At least that is the easy way to get started.  If you
have another Linux box, just plug your USB drive in there and access
it over NFS...  problem solved.

Clonezilla-live plays in this space too, but it doesn't do raid or
multiple disks at once, and you have to shut down to take the image.

My 'ideal' system would be to  have ReaR generate a directory of what
will be on the boot iso leaving that somewhere on the host without
actually making the image.   Then use backuppc to back up the whole
host and its normal duplicate-pooling mechanism will keep the extra
copies of the tools from taking extra space.  Then when/if you need a
bare-metal restore, you would first grab the directory of the iso
contents, burn a boot CD, let that reconstruct the filesystem, then
tell backuppc to restore to it.  That way would be completely
automatic and always be up to date, with the advantage of backuppc's
efficient storage and easy online access to individual files and
directories.   If you don't mind wasting a small amount of space for
the isos, I think that approach would already work if you tell ReaR to
just make the boot image and to wait for an external program to do the
restore after the filesystem has been rebuilt.

> However, when it works - wow.  Just restored an HP dl360 w/HWRAID to a
> Presario desktop machine and it lives!  No network, but that's small
> beans compared to the larger win.

Yes, I've even modified the filesystem layout file to go from a
software RAID to a non-RAID, and to change partition sizes during the
restores.   If it was documented, that capability by itself would be
fantastic.

-- 
Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] PMA attacks

[m . roth]

It appears to be a low-level attack, not so frequent as to be banned
permanently, just a number of times a day.

I did google on this, and I gather it's looking for phpmyadmin. We've been
getting one from one specific network in Russia for weeks

Here are more information about 91.201.64.24:

[Querying whois.ripe.net]
[whois.ripe.net]

% Information related to '91.201.64.0 - 91.201.67.255'

inetnum: 91.201.64.0 - 91.201.67.255
netname: Donekoserv
descr:   DonEkoService Ltd
country: RU


But now I'm seeing the same from Azerbaijan, and France, and elsewhere.
Two questions: first, are other folks seeing this? and second, I can't
imagine malware this stupid, to keep hitting the same sites over and over
when it's not found, rather than bad password or user, so I'm wondering if
this could be a targetting vector for an upcoming serious attack using
another vector.

Opinions?

  mark


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PMA attacks

[John Hinton]

On 6/19/2012 2:31 PM, m.r...@5-cent.us wrote:
> It appears to be a low-level attack, not so frequent as to be banned
> permanently, just a number of times a day.
>
> I did google on this, and I gather it's looking for phpmyadmin. We've been
> getting one from one specific network in Russia for weeks
>
> Here are more information about 91.201.64.24:
>
> [Querying whois.ripe.net]
> [whois.ripe.net]
> 
> % Information related to '91.201.64.0 - 91.201.67.255'
>
> inetnum: 91.201.64.0 - 91.201.67.255
> netname: Donekoserv
> descr:   DonEkoService Ltd
> country: RU
> 
>
> But now I'm seeing the same from Azerbaijan, and France, and elsewhere.
> Two questions: first, are other folks seeing this? and second, I can't
> imagine malware this stupid, to keep hitting the same sites over and over
> when it's not found, rather than bad password or user, so I'm wondering if
> this could be a targetting vector for an upcoming serious attack using
> another vector.
>
> Opinions?
>
>mark
>
>
I also see these frequently. As for dumb script? Well there are plenty 
of those out there. And, if you care to, you can set up rules in 
Fail2Ban to auto block these.

This brings up a question I have. We do virtualhosting and keep separate 
http logs for every website. I have not been running any Fail2Ban rules 
on those logs as many are very active and spread about. I suppose I 
could concentrate only on the error logs which would be much smaller. My 
question... is anybody running something like Fail2Ban under a situation 
like this and does it use much horsepower?

-- 
John Hinton
877-777-1407 ext 502
http://www.ew3d.com
Comprehensive Online Solutions

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.2 on partitionable mdadm RAID1 (md_d0) - kernel panic with either disk not present

[m . roth]

Arun Khan wrote:

> Following the instructions on CentOS Wiki
>   I
> installed a min. server in Linux KVM setup (script shown below)

> The system boots fine when both disks are available.
> When I remove either of the disks (delete the -drive file= line), the
> system boots to a point wherein the GRUB menu is displayed and the
> progress bar displays for a while till the white bar reaches about
> halfway point and then it:
>
> Kernel panic - not syncing: Attempted to kill init!

> 
> root@centos62-raid1 ~ >
> # fdisk -l
>
> Disk /dev/sda: 10.7 GB, 10737418240 bytes
> 255 heads, 63 sectors/track, 1305 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000e8353
>
>Device Boot  Start End  Blocks   Id  System
> /dev/sda1   *   1 523 4194304   83  Linux
> Partition 1 does not end on cylinder boundary.
> /dev/sda2 5231045 4194304   83  Linux
> /dev/sda310451176 1048576   82  Linux swap /
> Solaris

Ok, I see that it's hardware 512b blocks, so you're not running into
issues with 4k hardware blocks. I trust you installed grub on /dev/md0,
which I assume is /dev/sda1 and /dev/sdb1?

  mark


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] PMA attacks

[Dennis Jacobfeuerborn]

On 06/19/2012 08:31 PM, m.r...@5-cent.us wrote:
> It appears to be a low-level attack, not so frequent as to be banned
> permanently, just a number of times a day.
> 
> I did google on this, and I gather it's looking for phpmyadmin. We've been
> getting one from one specific network in Russia for weeks
> 
> Here are more information about 91.201.64.24:
> 
> [Querying whois.ripe.net]
> [whois.ripe.net]
> 
> % Information related to '91.201.64.0 - 91.201.67.255'
> 
> inetnum: 91.201.64.0 - 91.201.67.255
> netname: Donekoserv
> descr:   DonEkoService Ltd
> country: RU
> 
> 
> But now I'm seeing the same from Azerbaijan, and France, and elsewhere.
> Two questions: first, are other folks seeing this? and second, I can't
> imagine malware this stupid, to keep hitting the same sites over and over
> when it's not found, rather than bad password or user, so I'm wondering if
> this could be a targetting vector for an upcoming serious attack using
> another vector.
> 
> Opinions?

Why is this stupid? Yes it might not find anything today but you might
install it tomorrow.
Since this is common I always put PMA (and similar tools) either in it's
own management network that is only accessible using a tunnel or at least
behind HTTP authentication. I've seen this exploited once and the attackers
installed a few perl scripts that were launching attacks from the system.

Regards,
  Dennis
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] My ROOT PASSWORD Is GETTING RESET After EVERY REBOOT

[chiong lawrence]

Hello there,

I'm using CentOS v6.2 x86_64bit. I'm confuse and can't figured-it-out after
I run my KVM virtual machine the root password is getting RESET after every
reboot of my VM.

Any help is very much appreciated.

Thank you.
**
*Please consider the environment before printing this email.*
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.2 on partitionable mdadm RAID1 (md_d0) - kernel panic with either disk not present

[Arun Khan]

On Wed, Jun 20, 2012 at 12:11 AM,   wrote:
> Arun Khan wrote:
>>    Device Boot      Start         End      Blocks   Id  System
>> /dev/sda1   *           1         523     4194304   83  Linux
>> Partition 1 does not end on cylinder boundary.
>> /dev/sda2             523        1045     4194304   83  Linux
>> /dev/sda3            1045        1176     1048576   82  Linux swap /
>> Solaris
> 
> Ok, I see that it's hardware 512b blocks, so you're not running into
> issues with 4k hardware blocks. I trust you installed grub on /dev/md0,
> which I assume is /dev/sda1 and /dev/sdb1?
>

>From the wiki instructions, there is no re-installation of GRUB, only
a couple of changes in /boot/grub/grub.conf file installed by the
regular installation on /dev/sda.   During the RAID1 creation process
the  grub from /dev/sda would mirrored into the RAID1 device and
appear on the MBR of both the disks.

As I said in the OP, I do see the grub menu with either of the disks
"unplugged"  i.e. missing.   The kernel does boot and the white
progress bar goes upto about 50% when the kernel panic occurs.  I will
turn off the splash and see what comes up on the console.   Gut
feeling --  I suspect the problem is with the initrd image created
with the "dracut"

-- Arun Khan
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.2 on partitionable mdadm RAID1 (md_d0) - kernel panic with either disk not present

[m . roth]

Arun Khan wrote:
> On Wed, Jun 20, 2012 at 12:11 AM,   wrote:
>> Arun Khan wrote:
>>>    Device Boot      Start         End      Blocks   Id  System
>>> /dev/sda1   *           1         523     4194304   83  Linux
>>> Partition 1 does not end on cylinder boundary.
>>> /dev/sda2             523        1045     4194304   83  Linux
>>> /dev/sda3            1045        1176     1048576   82  Linux swap /
>>> Solaris
>> 
>> Ok, I see that it's hardware 512b blocks, so you're not running into
>> issues with 4k hardware blocks. I trust you installed grub on /dev/md0,
>> which I assume is /dev/sda1 and /dev/sdb1?
>
>>From the wiki instructions, there is no re-installation of GRUB, only
> a couple of changes in /boot/grub/grub.conf file installed by the
> regular installation on /dev/sda.   During the RAID1 creation process
> the  grub from /dev/sda would mirrored into the RAID1 device and
> appear on the MBR of both the disks.
>
> As I said in the OP, I do see the grub menu with either of the disks
> "unplugged"  i.e. missing.   The kernel does boot and the white
> progress bar goes upto about 50% when the kernel panic occurs.  I will
> turn off the splash and see what comes up on the console.   Gut
> feeling --  I suspect the problem is with the initrd image created
> with the "dracut"

For one thing, edit grub.conf and get *rid* of that idiot rhgb and quiet,
so you can actually see what's happening. Sounds to me as though it's
trying to switch root to a real drive from the virtual drive of the ramfs,
and it's not working. One thing you *might* also try is before you boot,
edit the kernel line in grub, and add rdshell at the end, so you boot into
grub's rudimentary shell if/when it fails, and you can look around and
find what it's seeing.

   mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.2 on partitionable mdadm RAID1 (md_d0) - kernel panic with either disk not present

[Rob Kampen]

On 06/20/2012 07:23 AM, Arun Khan wrote:

On Wed, Jun 20, 2012 at 12:11 AM,  wrote:

Arun Khan wrote:

Device Boot  Start End  Blocks   Id  System
/dev/sda1   *   1 523 4194304   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 5231045 4194304   83  Linux
/dev/sda310451176 1048576   82  Linux swap /
Solaris

raid needs Id of fd rather than 83 to auto detect??


Ok, I see that it's hardware 512b blocks, so you're not running into
issues with 4k hardware blocks. I trust you installed grub on /dev/md0,
which I assume is /dev/sda1 and /dev/sdb1?


> From the wiki instructions, there is no re-installation of GRUB, only
a couple of changes in /boot/grub/grub.conf file installed by the
regular installation on /dev/sda.   During the RAID1 creation process
the  grub from /dev/sda would mirrored into the RAID1 device and
appear on the MBR of both the disks.

As I said in the OP, I do see the grub menu with either of the disks
"unplugged"  i.e. missing.   The kernel does boot and the white
progress bar goes upto about 50% when the kernel panic occurs.  I will
turn off the splash and see what comes up on the console.   Gut
feeling --  I suspect the problem is with the initrd image created
with the "dracut"

-- Arun Khan
___
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] CentOS 6.2 on partitionable mdadm RAID1 (md_d0) - kernel panic with either disk not present

[m . roth]

Rob Kampen wrote:
> On 06/20/2012 07:23 AM, Arun Khan wrote:
>> On Wed, Jun 20, 2012 at 12:11 AM,  wrote:
>>> Arun Khan wrote:
 Device Boot  Start End  Blocks   Id  System
 /dev/sda1   *   1 523 4194304   83  Linux
 Partition 1 does not end on cylinder boundary.
 /dev/sda2 5231045 4194304   83  Linux
 /dev/sda310451176 1048576   82  Linux swap /
 Solaris
> raid needs Id of fd rather than 83 to auto detect??

Good catch. A quick google got me a page on filesystem types, which had
this line:
fd Linux raid partition with autodetect using persistent superblock

 

   mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Memory recognition in 6.2

[Hugh E Cruickshank]

Hi All:

I have an HP DL380G5 server which I am loading CentOS 6.2 on and it does
not appear to recognize all of the RAM installed on the server. The BIOS
is reporting 26GB however top is reporting:

  Mem:  15720140k total, 418988k used, 15301152k free,  30256k buffers
  Swap: 17956856k total,  0k used, 17956856k free, 135536k cached 

and free is reporting:

   total   used free shared buffers cached
  Mem:  15720140 418848 15301292  0   30256 135536
  -/+ buffers/cache: 253056 15467084
  Swap: 17956856  0 17956856

I have tried adding the mem= parameter to the /boot/grub/grub.conf file
as in:

  title CentOS (2.6.32-220.17.1.el6.i686)
  root (hd0,0)
  kernel /vmlinuz-2.6.32-220.17.1.el6.i686 ro [SNIP]
  initrd /initramfs-2.6.32-220.17.1.el6.i686.img
  mem=26624M

but this has not appeared to work.

Any suggestions would be gratefully appreciated.

TIA

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Scott Silva]

on 6/19/2012 3:37 PM Hugh E Cruickshank spake the following:
> Hi All:
> 
> I have an HP DL380G5 server which I am loading CentOS 6.2 on and it does
> not appear to recognize all of the RAM installed on the server. The BIOS
> is reporting 26GB however top is reporting:
> 
>   Mem:  15720140k total, 418988k used, 15301152k free,  30256k buffers
>   Swap: 17956856k total,  0k used, 17956856k free, 135536k cached 
> 
> and free is reporting:
> 
>total   used free shared buffers cached
>   Mem:  15720140 418848 15301292  0   30256 135536
>   -/+ buffers/cache: 253056 15467084
>   Swap: 17956856  0 17956856
> 
> I have tried adding the mem= parameter to the /boot/grub/grub.conf file
> as in:
> 
>   title CentOS (2.6.32-220.17.1.el6.i686)
>   root (hd0,0)
>   kernel /vmlinuz-2.6.32-220.17.1.el6.i686 ro [SNIP]
>   initrd /initramfs-2.6.32-220.17.1.el6.i686.img
>   mem=26624M
> 
> but this has not appeared to work.
> 
> Any suggestions would be gratefully appreciated.
> 
> TIA
> 
> Regards, Hugh
> 
It looks like you installed 32 bit OS... I don't think it sees over 16 gigs...



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Joseph L. Casale]

>  title CentOS (2.6.32-220.17.1.el6.i686)
>  root (hd0,0)
>  kernel /vmlinuz-2.6.32-220.17.1.el6.i686 ro [SNIP]
>  initrd /initramfs-2.6.32-220.17.1.el6.i686.img
>  mem=26624M

Do i read that right? 26g of ram and you're using a non PAE x86 kernel?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Yves Bellefeuille]

On Tuesday 19 June 2012, "Hugh E Cruickshank"  wrote:

> I have an HP DL380G5 server which I am loading CentOS 6.2 on and it
>  does not appear to recognize all of the RAM installed on the server.
>  The BIOS is reporting 26GB however top is reporting:
> 
>   Mem:  15720140k total, 418988k used, 15301152k free,  30256k
>  buffers Swap: 17956856k total,  0k used, 17956856k free, 135536k
>  cached


>   title CentOS (2.6.32-220.17.1.el6.i686)

I can't find the limit for CentOS 6, but CentOS 5 x86 was limited to 16 
Gb of RAM: https://www.centos.org/product.html . You should use x86_64.

-- 
Yves Bellefeuille 
"La Esperanta Civito ne rifuzas anticipe la kunlaboron de erarintoj, se
ili konscias pri sia eraro." -- Heroldo Komunikas, n-ro 473.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Bug in Latest Adobe Flash Plugin

[Keith Roberts]

I'm running Centos 5.7 32 bit with Firefox 10.0.5 ESR

Not sure if this has been mentioned on the list yet, but the 
latest version of Adobe flash-plugin 11.2.202 has a bug 
which causes it to hang and not play SWF files.

I've been pulling my hair out trying to identify why I could 
not get any SWF videos to play.

I finally found the answer here:
https://bbs.archlinux.org/viewtopic.php?pid=1080414

I have downgraded the flash-plugin now to version 10.3.183
from rpmforge repo. It works fine now :)

I've also added exclude=flash-plugin to the end 
of /etc/yum.conf file, to make sure this does not get 
upgraded again.

Kind Regards,

Keith Roberts

---
Websites:
http://www.karsites.net
http://www.php-debuggers.net
http://www.raised-from-the-dead.org.uk

All email addresses are challenge-response protected with
TMDA [http://tmda.net]
---
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Hugh E Cruickshank]

From: Scott Silva Sent: June 19, 2012 15:51
>
> It looks like you installed 32 bit OS... I don't think it 
> sees over 16 gigs...

Yes it is 32-bit but if there is a 16GB limit on memory then I am
going to need to revert to CentOS 5.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Hugh E Cruickshank]

From: Joseph L. Casale Sent: June 19, 2012 15:52
> >  title CentOS (2.6.32-220.17.1.el6.i686)
> >  root (hd0,0)
> >  kernel /vmlinuz-2.6.32-220.17.1.el6.i686 ro [SNIP]
> >  initrd /initramfs-2.6.32-220.17.1.el6.i686.img
> >  mem=26624M
> 
> Do i read that right? 26g of ram and you're using a non PAE 
> x86 kernel?

It was my understanding that PAE is now built into the standard kernel
but I will check on this further.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Yves Bellefeuille]

On Tuesday 19 June 2012, "Hugh E Cruickshank"  wrote:

> Yes it is 32-bit but if there is a 16GB limit on memory then I am
> going to need to revert to CentOS 5.

Same limit in CentOS 5.

Is there a reason you don't want to use x86_64?

-- 
Yves Bellefeuille 
"La Esperanta Civito ne rifuzas anticipe la kunlaboron de erarintoj, se
ili konscias pri sia eraro." -- Heroldo Komunikas, n-ro 473.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Hugh E Cruickshank]

From: Yves Bellefeuille Sent: June 19, 2012 15:55
> 
> I can't find the limit for CentOS 6, but CentOS 5 x86 was 
> limited to 16 
> Gb of RAM: https://www.centos.org/product.html . You should 
> use x86_64.

If that is the case then both CentOS 5 and 6 are not viable for us. I
will have to go for RHEL5 (or possibly 6) which does support the memory
in 32-bit mode.

The reason for the restriction to 32-bit is because of other software
that we must run that does not work correctly on a 64-bit OS.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Scott Silva]

on 6/19/2012 4:22 PM Hugh E Cruickshank spake the following:
> From: Yves Bellefeuille Sent: June 19, 2012 15:55
>>
>> I can't find the limit for CentOS 6, but CentOS 5 x86 was 
>> limited to 16 
>> Gb of RAM: https://www.centos.org/product.html . You should 
>> use x86_64.
> 
> If that is the case then both CentOS 5 and 6 are not viable for us. I
> will have to go for RHEL5 (or possibly 6) which does support the memory
> in 32-bit mode.
> 
> The reason for the restriction to 32-bit is because of other software
> that we must run that does not work correctly on a 64-bit OS.
> 
> Regards, Hugh
> 
You can always virtualize...



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[John R Pierce]

On 06/19/12 4:13 PM, Hugh E Cruickshank wrote:
> From: Joseph L. Casale Sent: June 19, 2012 15:52
>>> > >  title CentOS (2.6.32-220.17.1.el6.i686)
>>> > >  root (hd0,0)
>>> > >  kernel /vmlinuz-2.6.32-220.17.1.el6.i686 ro [SNIP]
>>> > >  initrd /initramfs-2.6.32-220.17.1.el6.i686.img
>>> > >  mem=26624M
>> >
>> >Do i read that right? 26g of ram and you're using a non PAE
>> >x86 kernel?
> It was my understanding that PAE is now built into the standard kernel
> but I will check on this further.

If I recall correctly, PAE is limited to 16GB because the page tables 
are obscenely huge for more than that, and use over a gigabyte of the 
32bit kernel space





-- 
john r pierceN 37, W 122
santa cruz ca mid-left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[John R Pierce]

On 06/19/12 4:22 PM, Hugh E Cruickshank wrote:
> The reason for the restriction to 32-bit is because of other software
> that we must run that does not work correctly on a 64-bit OS.

fix that other software.   or run in 16GB.
there's no excuse in 2012 for not supporting 64bit, even my budget 
laptop has 8GB of memory and a 64bit OS.

as an example of the problems see this message,
http://www.redhat.com/archives/rhelv5-list/2008-September/msg00194.html
and its various followups...

PAE was a kludge to let 32 bit OS's, normally limited to 4GB max memory 
address more.   the kludge breaks things above 16GB in spite of the 
theoretical 64GB limit enforced by the hardware.


also see this
https://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits

EL *4* supported a nasty 'hugemem' kernel that could get you past 16GB 
but only at great overhead.  this caused MANY problems and was 
discontinued in EL5 and 6 32bit systems, where 64bit is the correct 
choice for all modern servers.



-- 
john r pierceN 37, W 122
santa cruz ca mid-left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Deleting Files

[Diego Sanchez]

find /whe/re -mtime +2 -exec echo {} \;

If you get "Argument list too long" error, you can use

find . -name "*" -print | xargs rm

-- 
Diego - Yo no soy paranoico! (pero que me siguen, me siguen)
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Yves Bellefeuille]

On Tuesday 19 June 2012, "Hugh E Cruickshank"  wrote:

> If that is the case then both CentOS 5 and 6 are not viable for us. I
> will have to go for RHEL5 (or possibly 6) which does support the
> memory in 32-bit mode.

The limit's the same with RHEL 5 and 6. CentOS is "bug-for-bug 
compatible" with RHEL.

> The reason for the restriction to 32-bit is because of other software
> that we must run that does not work correctly on a 64-bit OS.

Your 32-bit applications will be restricted to 4 Gb of memory each 
anyway. If you must use x86, memory over 16 Gb is pretty much wasted, 
unless you install x86_64 and virtualize x86 as necessary.

-- 
Yves Bellefeuille 
"La Esperanta Civito ne rifuzas anticipe la kunlaboron de erarintoj, se
ili konscias pri sia eraro." -- Heroldo Komunikas, n-ro 473.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[John R Pierce]

On 06/19/12 6:31 PM, Yves Bellefeuille wrote:
> Your 32-bit applications will be restricted to 4 Gb of memory each
> anyway.

sctually, they only get 2 or 3gb of that for user space, the other 1 or 
2gb of the 32bit space is used by the kernel which is in every process 
address space.   I believe with PAE, you actually get LESS per process 
address space

-- 
john r pierceN 37, W 122
santa cruz ca mid-left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.2 on partitionable mdadm RAID1 (md_d0) - kernel panic with either disk not present

[Arun Khan]

On Wed, Jun 20, 2012 at 2:18 AM,   wrote:
> Rob Kampen wrote:
>> On 06/20/2012 07:23 AM, Arun Khan wrote:
>>> On Wed, Jun 20, 2012 at 12:11 AM,  wrote:
 Arun Khan wrote:
>     Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1         523     4194304   83  Linux
> Partition 1 does not end on cylinder boundary.
> /dev/sda2             523        1045     4194304   83  Linux
> /dev/sda3            1045        1176     1048576   82  Linux swap /
> Solaris
>> raid needs Id of fd rather than 83 to auto detect??
>
> Good catch. A quick google got me a page on filesystem types, which had
> this line:
> fd Linux raid partition with autodetect using persistent superblock
>

But this is supposed to be RAID1 on the *entire* disks and not on the
individual partitions.

The instruction on the wiki clearly states do a "regular" install on
the first disk (I did leave a few blocks at the end of the first disk
as per the instructions) and then create a "partitionable" RAID1
md_d0.





..

Why would you want to have a system installed on a partitionable software RAID1?

If you are installing a system on a partitionable RAID you can use the
whole hard drive as a RAID component device, and since RAID1 is a
mirror, you will be able to boot your system from any of the drives in
case of failure without any additional tricks required to preserve
bootloader configuration, etc. And when you need to repair a failed
RAID volume with the whole hard drive as a RAID component, all you
have to do is to insert a new hard drive and run mdadm --add; no
partitioning or anything else required.

...

Steps for both CentOS 5 & 6

1. Install CentOS using standard installer on the first hard disk,
/dev/sda. Select manual partitioning during the installation, and
leave at least 1 unit at the very end of the disk unpartitioned. You
will be able to redeem most of this space back later. You need to
reserve this space for mdadm which stores it's metadata at the last
chunk of a raid volume.

2. Boot from the CentOS installation disk in the Rescue mode. The
installer will ask you if you wish to mount an existing CentOS
installation, you must refuse.

3. Build the software RAID1 using mdadm in degraded mode, with
/dev/sda as the only drive:
mdadm --create --metadata=0.90 --level=1 --raid-devices=2 /dev/md_d0
/dev/sda missing

4. Add the mirror drive /dev/sdb into the raid and check /proc/mdstat
to see that the raid started building:
mdadm --add /dev/md_d0 /dev/sdb
cat /proc/mdstat
...



-- Arun Khan
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6.2 on partitionable mdadm RAID1 (md_d0) - kernel panic with either disk not present

[Arun Khan]

On Wed, Jun 20, 2012 at 1:00 AM,   wrote:

 snip 

> For one thing, edit grub.conf and get *rid* of that idiot rhgb and quiet,
> so you can actually see what's happening. Sounds to me as though it's
> trying to switch root to a real drive from the virtual drive of the ramfs,
> and it's not working. One thing you *might* also try is before you boot,
> edit the kernel line in grub, and add rdshell at the end, so you boot into
> grub's rudimentary shell if/when it fails, and you can look around and
> find what it's seeing.


Will try your suggestion and report back.

-- Arun Khan
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Memory recognition in 6.2

[Hugh E Cruickshank]

Hi All:

Thanks for all the responses and suggestions. I have been doing some
more research and I believe that it may be possible to go 64-bit. I
am going to leave this for now and have another look at it in the
morning when I am, hopefully, awake before I make the final decision.

Good night.

Regards, Hugh

-- 
Hugh E Cruickshank, Forward Software, www.forward-software.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos