[CentOS] emergency! linux kickstart pxe boot needed
Hey folks, I'm at colocaiton in the middle of a big rebuild and it seems I have a faulty CD rom in the server that I need to put Centos on via Kickstart. So I cannot boot the Centos 5.4 net install CD. Is PXE kickstart easy to set up? I have a laptop here with DHCP already going. I google and a bunch of stuff comes up but it does not look simple. I'm just shooting htis out ther eon the odd chance someone gets it soon nad knows of a really easy howto for this thanks! -- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In Defense of Food" ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] emergency! linux kickstart pxe boot needed
2010/2/28 Alan McKay : > Hey folks, > > I'm at colocaiton in the middle of a big rebuild and it seems I have a > faulty CD rom in the server that I need to put Centos on via > Kickstart. So I cannot boot the Centos 5.4 net install CD. > > Is PXE kickstart easy to set up? I have a laptop here with DHCP > already going. I google and a bunch of stuff comes up but it does > not look simple. http://wiki.centos.org/HowTos/PXE , maybe it's a bit easier to download full centos dvd and install from it? -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] emergency! linux kickstart pxe boot needed
On 28 Feb 2010, at 16:51, Alan McKay wrote: > I'm at colocaiton in the middle of a big rebuild and it seems I have a > faulty CD rom in the server that I need to put Centos on via > Kickstart. Had a similar problem and easiest solution in the end was to buy a USB CD drive from local computer store. Good luck! Ben ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] emergency! linux kickstart pxe boot needed
>Is PXE kickstart easy to set up? I have a laptop here with DHCP >already going. I google and a bunch of stuff comes up but it does >not look simple. Sure, http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Installation_Guide/ch-pxe.html Also, if you have an OS on the server, you can tweak grub to boot into install and pull from a url instead of disc, and look for a ks file as well. jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LDAP Server Access Problem
On Sun, 2010-02-21 at 23:23 -0700, Craig White wrote: > Note that ldap 'client' applications like ldapsearch > use /etc/openldap/ldap.conf so I would suspect that the 'certificates' > used by the 2 machines are different. I thought I would follow up on this problem. I did finally get the ldapsearch to function properly on the remote machine. However, I am puzzled as to what I had to do to get it to work. I originally never setup a certificate for the client as I did not think they were needed. In my /etc/openldap/slapd.conf file I had to set up the LDAP server with the following: TLSVerifyClient never I had the initial setup with TLSVerifyClient allow According to man slapd.conf: TLSVerifyClient Specifies what checks to perform on client certificates in an incoming TLS session, if any. Thecan be specified as one of the following keywords: never This is the default. slapd will not ask the client for a certificate. allow The client certificate is requested. If no certificate is provided, the session proceeds normally. If a bad certificate is provided, it will be ignored and the session proceeds normally. tryThe client certificate is requested. If no certificate is provided, the session proceeds normally. If a bad certificate is provided, the session is immediately terminated. demand | hard | true These keywords are all equivalent, for compatibility reasons. The client certificate is requested. If no certificate is provided, or a bad certificate is provided, the session is immediately terminated. Note that a valid client certificate is required in order to use the SASL EXTERNAL authentication mechanism with a TLS session. As such, a non-default TLSVerifyClient setting must be chosen to enable SASL EXTERNAL authentication. Note that according to the documentation the original setup should have worked properly. Why doesn't "allow" work? -- Paul (ga...@nurdog.com) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LDAP Server Access Problem
On Mon, 2010-02-22 at 17:24 -0700, Craig White wrote: > doing a new setup using methodologies that have already been tagged as > deprecated seems to be a really bad idea. Even though it currently > works, you can be certain that at some point down the road, it will > cease to work... that is what deprecated means. My LDAP server has been running for several years now and was initially setup to use ldaps. Only recently I wanted to use it for remote authentication which is how I ended up going down this path. It doesn't take that much effort to fix the LDAP server to use TLS which I will do as soon as I can get to it. -- Paul (ga...@nurdog.com) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] emergency! linux kickstart pxe boot needed
> http://wiki.centos.org/HowTos/PXE , maybe it's a bit easier to > download full centos dvd and install from it? It's a hardware issue with the server drive. Having said that, the CentOS net install CD is pretty small, so server's drive might read it enough to get going... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] emergency! linux kickstart pxe boot needed
On 28 February 2010 17:42, Ian Murray wrote: > It's a hardware issue with the server drive. Having said that, the CentOS net > install CD is pretty small, so server's drive might read it enough to get > going... Any virtual drive support in the ILO / similar? Ben ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] emergency! linux kickstart pxe boot needed
> Is PXE kickstart easy to set up? I have a laptop here with DHCP
> already going. I google and a bunch of stuff comes up but it does
> not look simple.
system-config-netboot should be able to take care of almost everything for
you .. although you will need to add a statement like the following in the
subnet statement for your dhcp server:
allow booting; allow bootp; class "pxeclients" { match if substring(option
vendor-class-identifier, 0, 9) = "PXEClient"; next-server ;
filename "linux-install/pxelinux.0"; }
In case you have issues on the client side with pxe booting .. check out
some gPXE (formerly Etherboot) howtos at
http://www.etherboot.org/wiki/howtos which allow you to boot over http.
Hope this helps,
Barry
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LDAP Server Access Problem
On Sun, 2010-02-28 at 10:07 -0700, Paul R. Ganci wrote: > On Sun, 2010-02-21 at 23:23 -0700, Craig White wrote: > > Note that ldap 'client' applications like ldapsearch > > use /etc/openldap/ldap.conf so I would suspect that the 'certificates' > > used by the 2 machines are different. > > I thought I would follow up on this problem. I did finally get the > ldapsearch to function properly on the remote machine. However, I am > puzzled as to what I had to do to get it to work. I originally never > setup a certificate for the client as I did not think they were needed. > In my /etc/openldap/slapd.conf file I had to set up the LDAP server with > the following: > > TLSVerifyClient never > > I had the initial setup with > > TLSVerifyClient allow > > According to man slapd.conf: > > TLSVerifyClient >Specifies what checks to perform on client certificates in an > incoming >TLS session, if any. Thecan be specified as one of > the >following keywords: > >never This is the default. slapd will not ask the client for > a > certificate. > >allow The client certificate is requested. If no certificate > is > provided, the session proceeds normally. If a bad certificate > is > provided, it will be ignored and the session proceeds normally. > >tryThe client certificate is requested. If no certificate > is > provided, the session proceeds normally. If a bad certificate > is > provided, the session is immediately terminated. > >demand | hard | true > These keywords are all equivalent, for compatibility > reasons. > The client certificate is requested. If no certificate > is > provided, or a bad certificate is provided, the session > is > immediately terminated. > > Note that a valid client certificate is required in order to > use > the SASL EXTERNAL authentication mechanism with a TLS > session. > As such, a non-default TLSVerifyClient setting must be chosen > to > enable SASL EXTERNAL authentication. > > Note that according to the documentation the original setup should have > worked properly. Why doesn't "allow" work? do you mean other than the fact that this simply talks about TLS Client and that SSL is deprecated and generally ignored in the documentation? SSL communication is different than TLS. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LDAP Server Access Problem
On Sun, 2010-02-28 at 11:22 -0700, Craig White wrote: > > do you mean other than the fact that this simply talks about TLS Client > and that SSL is deprecated and generally ignored in the documentation? > > SSL communication is different than TLS. With all due respect deprecated doesn't mean broken. While SSL is different than TLS using "TLSVerifyClient allow" works on the server. For that matter so does "TLSVerifyClient demand". In fact if I use the latter configuration and do not provide a client certificate ldap_bind fails as expected. From what I can tell the server certificate is never passed to the client unless "TLSVerifyClient never" as seen from: > ldapsearch -d 1 -x -LLL -H ldaps://incoming.mric.net:636 "(uid=acaplan)" sn uid ldap_create ldap_url_parse_ext(ldaps://incoming.mric.net:636) ldap_bind ldap_simple_bind ldap_sasl_bind ldap_send_initial_request ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_host: TCP incoming.mric.net:636 ldap_new_socket: 3 ldap_prepare_socket: 3 ldap_connect_to_host: Trying 208.139.195.124:636 ldap_connect_timeout: fd: 3 tm: -1 async: 0 TLS trace: SSL_connect:before/connect initialization TLS trace: SSL_connect:SSLv2/v3 write client hello A TLS trace: SSL_connect:SSLv3 read server hello A TLS certificate verification: depth: 1, err: 0, subject: /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing Authority/emailaddress=supp...@cacert.org, issuer: /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing Authority/emailaddress=supp...@cacert.org TLS certificate verification: depth: 0, err: 0, subject: /CN=incoming.mric.net, issuer: /O=Root CA/OU=http://www.cacert.org/CN=CA Cert Signing Authority/emailaddress=supp...@cacert.org TLS trace: SSL_connect:SSLv3 read server certificate A The client requests hangs because the LDAP server is not providing its certificate. I just found it strange that the communication process works fine as long as all the communication occurs on the server. I find it even stranger that the failure mode seems to be that the LDAP server doesn't pass its certificate to the client ... that seems really broke to me whether or not SSL is deprecated. In any event this is all moot because I am in the process of switching over to TLS. Thanks to everyone who helped sort this issue. -- Paul (ga...@nurdog.com) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] cron mystery
I've just noticed that cron.daily, etc, do not seem to be running on my CentOS-5.4 system. The scripts in /etc/cron.d/ all run fine, but those in /etc/cron.hourly, etc, seem to be ignored. I see that according to /var/log/cron these commands are seen, eg Feb 28 18:01:01 helen crond[6680]: (root) CMD (run-parts /etc/cron.hourly) but none of the scripts in this directory seem to be touched. I've tried running them by hand, and this seems to work fine. Is there some problem, or subtlety, about crond under CentOS? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] emergency! linux kickstart pxe boot needed
- Original Message > From: Alan McKay > To: CentOS mailing list > Sent: Sun, February 28, 2010 1:51:18 PM > Subject: [CentOS] emergency! linux kickstart pxe boot needed > > Is PXE kickstart easy to set up? I have a laptop here with DHCP > already going. I google and a bunch of stuff comes up but it does > not look simple. > > I'm just shooting htis out ther eon the odd chance someone gets it > soon nad knows of a really easy howto for this "yum install cobbler" and use cobbler to build a netinstall server in 10 minutes :) These are very handy: http://wiki.xdroop.com/space/RedHat/kickstart/Cobbler http://magazine.redhat.com/2007/08/10/cobbler-how-to-set-up-a-network-boot-server-in-10-minutes/ And the oficial documentation https://fedorahosted.org/cobbler/ Hope this helps Fer ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] puzzling md error ?
this has never happened to me before, and I'm somewhat at a loss. got a email from the cron thing... /etc/cron.weekly/99-raid-check: WARNING: mismatch_cnt is not 0 on /dev/md10 WARNING: mismatch_cnt is not 0 on /dev/md11 ok, md10 and md11 are each raid1's made from 2 x 72GB scsi drives, on a dell 2850 or something dual single-core 3ghz server. these two md's are in turn a striped LVM volume group dmesg shows md: syncing RAID array md10 md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for reconstruction. md: using 128k window, over a total of 143374656 blocks. md: syncing RAID array md11 md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for reconstruction. md: using 128k window, over a total of 143374656 blocks. md: md10: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:sdc1 disk 1, wo:0, o:1, dev:sdd1 md: md11: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:sde1 disk 1, wo:0, o:1, dev:sdf1 I'm not sure what thats telling me. the last thing prior to this in dmesg was when I added a swap to this vg last week. and mdadm --detail shows... # mdadm --detail /dev/md10 /dev/md10: Version : 0.90 Creation Time : Wed Oct 8 12:54:48 2008 Raid Level : raid1 Array Size : 143374656 (136.73 GiB 146.82 GB) Used Dev Size : 143374656 (136.73 GiB 146.82 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 10 Persistence : Superblock is persistent Update Time : Sun Feb 28 04:53:29 2010 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : b6da4dc5:c7372d6e:63f32b9c:49fa95f9 Events : 0.84 Number Major Minor RaidDevice State 0 8 330 active sync /dev/sdc1 1 8 491 active sync /dev/sdd1 # mdadm --detail /dev/md11 /dev/md11: Version : 0.90 Creation Time : Wed Oct 8 12:54:57 2008 Raid Level : raid1 Array Size : 143374656 (136.73 GiB 146.82 GB) Used Dev Size : 143374656 (136.73 GiB 146.82 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 11 Persistence : Superblock is persistent Update Time : Sun Feb 28 11:49:45 2010 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : be475cd9:b98ee3ff:d18e668c:a5a6e06b Events : 0.62 Number Major Minor RaidDevice State 0 8 650 active sync /dev/sde1 1 8 811 active sync /dev/sdf1 I don't see anything wrong here ? lvm shows no problems I detect either... # vgdisplay vg1 Volume group "vgdisplay" not found LV VG Attr LSize Origin Snap% Move Log Copy% Convert glassfish vg1 -wi-ao 10.00G lv1vg1 -wi-ao 97.66G oradatavg1 -wi-ao 30.00G pgdata vg1 -wi-ao 25.00G pgdata_lss_idx vg1 -wi-ao 20.00G pgdata_lss_tab vg1 -wi-ao 20.00G swappervg1 -wi-ao 3.00G vmware vg1 -wi-ao 50.00G # pvdisplay /dev/md10 /dev/md11 --- Physical volume --- PV Name /dev/md10 VG Name vg1 PV Size 136.73 GB / not usable 2.31 MB Allocatable yes PE Size (KByte) 4096 Total PE 35003 Free PE 1998 Allocated PE 33005 PV UUID oAgJY7-Tmf7-ac35-KoUH-15uz-Q5Ae-bmFCys --- Physical volume --- PV Name /dev/md11 VG Name vg1 PV Size 136.73 GB / not usable 2.31 MB Allocatable yes PE Size (KByte) 4096 Total PE 35003 Free PE 2560 Allocated PE 32443 PV UUID A4Qb3P-j5Lr-8ZEv-FjbC-Iczm-QkC8-bqP0zv ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
2010/2/28 John R Pierce : > this has never happened to me before, and I'm somewhat at a loss. got a > email from the cron thing... > > /etc/cron.weekly/99-raid-check: > > WARNING: mismatch_cnt is not 0 on /dev/md10 > WARNING: mismatch_cnt is not 0 on /dev/md11 > > > ok, md10 and md11 are each raid1's made from 2 x 72GB scsi drives, on a > dell 2850 or something dual single-core 3ghz server. > > these two md's are in turn a striped LVM volume group > > dmesg shows > > md: syncing RAID array md10 > md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. > md: using maximum available idle IO bandwidth (but not more than > 20 KB/sec) for reconstruction. > md: using 128k window, over a total of 143374656 blocks. > md: syncing RAID array md11 > md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. > md: using maximum available idle IO bandwidth (but not more than > 20 KB/sec) for reconstruction. > md: using 128k window, over a total of 143374656 blocks. > md: md10: sync done. > RAID1 conf printout: > --- wd:2 rd:2 > disk 0, wo:0, o:1, dev:sdc1 > disk 1, wo:0, o:1, dev:sdd1 > md: md11: sync done. > RAID1 conf printout: > --- wd:2 rd:2 > disk 0, wo:0, o:1, dev:sde1 > disk 1, wo:0, o:1, dev:sdf1 > > I'm not sure what thats telling me. the last thing prior to this in > dmesg was when I added a swap to this vg last week. > > > and mdadm --detail shows... > > # mdadm --detail /dev/md10 > /dev/md10: > Version : 0.90 > Creation Time : Wed Oct 8 12:54:48 2008 > Raid Level : raid1 > Array Size : 143374656 (136.73 GiB 146.82 GB) > Used Dev Size : 143374656 (136.73 GiB 146.82 GB) > Raid Devices : 2 > Total Devices : 2 > Preferred Minor : 10 > Persistence : Superblock is persistent > > Update Time : Sun Feb 28 04:53:29 2010 > State : clean > Active Devices : 2 > Working Devices : 2 > Failed Devices : 0 > Spare Devices : 0 > > UUID : b6da4dc5:c7372d6e:63f32b9c:49fa95f9 > Events : 0.84 > > Number Major Minor RaidDevice State > 0 8 33 0 active sync /dev/sdc1 > 1 8 49 1 active sync /dev/sdd1 > # mdadm --detail /dev/md11 > /dev/md11: > Version : 0.90 > Creation Time : Wed Oct 8 12:54:57 2008 > Raid Level : raid1 > Array Size : 143374656 (136.73 GiB 146.82 GB) > Used Dev Size : 143374656 (136.73 GiB 146.82 GB) > Raid Devices : 2 > Total Devices : 2 > Preferred Minor : 11 > Persistence : Superblock is persistent > > Update Time : Sun Feb 28 11:49:45 2010 > State : clean > Active Devices : 2 > Working Devices : 2 > Failed Devices : 0 > Spare Devices : 0 > > UUID : be475cd9:b98ee3ff:d18e668c:a5a6e06b > Events : 0.62 > > Number Major Minor RaidDevice State > 0 8 65 0 active sync /dev/sde1 > 1 8 81 1 active sync /dev/sdf1 > > > > I don't see anything wrong here ? > > lvm shows no problems I detect either... > > # vgdisplay vg1 > Volume group "vgdisplay" not found > LV VG Attr LSize Origin Snap% Move Log Copy% Convert > glassfish vg1 -wi-ao 10.00G > lv1 vg1 -wi-ao 97.66G > oradata vg1 -wi-ao 30.00G > pgdata vg1 -wi-ao 25.00G > pgdata_lss_idx vg1 -wi-ao 20.00G > pgdata_lss_tab vg1 -wi-ao 20.00G > swapper vg1 -wi-ao 3.00G > vmware vg1 -wi-ao 50.00G > > > # pvdisplay /dev/md10 /dev/md11 > --- Physical volume --- > PV Name /dev/md10 > VG Name vg1 > PV Size 136.73 GB / not usable 2.31 MB > Allocatable yes > PE Size (KByte) 4096 > Total PE 35003 > Free PE 1998 > Allocated PE 33005 > PV UUID oAgJY7-Tmf7-ac35-KoUH-15uz-Q5Ae-bmFCys > > --- Physical volume --- > PV Name /dev/md11 > VG Name vg1 > PV Size 136.73 GB / not usable 2.31 MB > Allocatable yes > PE Size (KByte) 4096 > Total PE 35003 > Free PE 2560 > Allocated PE 32443 > PV UUID A4Qb3P-j5Lr-8ZEv-FjbC-Iczm-QkC8-bqP0zv maybe this helps: http://www.arrfab.net/blog/?p=199 -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
Am 28.02.2010 22:03, schrieb John R Pierce: > WARNING: mismatch_cnt is not 0 on Have a look at http://www.arrfab.net/blog/?p=199 It says: > A `echo repair >/sys/block/md0/md/sync_action` followed by a `echo > check >/sys/block/md0/md/sync_action` seems to have corrected it. Now > `cat /sys/block/md0/md/mismatch_cnt` returns 0 … Regards, Peter signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
On 01/03/10 10:16, Peter Hinse wrote: Am 28.02.2010 22:03, schrieb John R Pierce: WARNING: mismatch_cnt is not 0 on Have a look at http://www.arrfab.net/blog/?p=199 It says: A `echo repair>/sys/block/md0/md/sync_action` followed by a `echo check>/sys/block/md0/md/sync_action` seems to have corrected it. Now `cat /sys/block/md0/md/mismatch_cnt` returns 0 … Regards, Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi, This is happening specifically because of the way swap works. So the issue will re-appear but it isn't actually anything to worry about. I'd suggest that you remove the particular drive from the list being scanned. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
Peter Hinse wrote: > Am 28.02.2010 22:03, schrieb John R Pierce: > >> WARNING: mismatch_cnt is not 0 on >> > > Have a look at http://www.arrfab.net/blog/?p=199 > It says: > > >> A `echo repair >/sys/block/md0/md/sync_action` followed by a `echo >> check >/sys/block/md0/md/sync_action` seems to have corrected it. Now >> `cat /sys/block/md0/md/mismatch_cnt` returns 0 … >> Thanks. I was trying to figure out how from the mdadm commands (UGH!) to do a scan. # cat /sys/block/md10/md/mismatch_cnt 8448 # cat /sys/block/md11/md/mismatch_cnt 7296 fugly. Since the mirrors aren't checksummed, can i assume this means there's likely some data messups here? Anyways, the repair is running on both md10 and md11, i'll check back with my final results... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
On 01/03/10 10:23, John R Pierce wrote: > Peter Hinse wrote: > >> Am 28.02.2010 22:03, schrieb John R Pierce: >> >> >>> WARNING: mismatch_cnt is not 0 on >>> >>> >> Have a look at http://www.arrfab.net/blog/?p=199 >> It says: >> >> >> >>> A `echo repair>/sys/block/md0/md/sync_action` followed by a `echo >>> check>/sys/block/md0/md/sync_action` seems to have corrected it. Now >>> `cat /sys/block/md0/md/mismatch_cnt` returns 0 … >>> >>> > Thanks. I was trying to figure out how from the mdadm commands (UGH!) > to do a scan. > > # cat /sys/block/md10/md/mismatch_cnt > 8448 > # cat /sys/block/md11/md/mismatch_cnt > 7296 > > fugly. Since the mirrors aren't checksummed, can i assume this means > there's likely some data messups here? > > Anyways, the repair is running on both md10 and md11, i'll check back > with my final results... > > > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > Hi It has to do with aborted writes in SWAP. Your data should be fine ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
Clint Dilks wrote: > It has to do with aborted writes in SWAP. Your data should be fine so swap on LVM on MD mirrors is a bad idea? frankly, I usually avoid LVM< but I figured I'd setup this system with it and see how it goes. its just a dev box, but we're about to put some oracle stuff on it (for development, but still) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
On 01/03/10 10:27, Clint Dilks wrote: > On 01/03/10 10:23, John R Pierce wrote: > >> Peter Hinse wrote: >> >> >>> Am 28.02.2010 22:03, schrieb John R Pierce: >>> >>> >>> WARNING: mismatch_cnt is not 0 on >>> Have a look at http://www.arrfab.net/blog/?p=199 >>> It says: >>> >>> >>> >>> A `echo repair>/sys/block/md0/md/sync_action` followed by a `echo check>/sys/block/md0/md/sync_action` seems to have corrected it. Now `cat /sys/block/md0/md/mismatch_cnt` returns 0 … >> Thanks. I was trying to figure out how from the mdadm commands (UGH!) >> to do a scan. >> >> # cat /sys/block/md10/md/mismatch_cnt >> 8448 >> # cat /sys/block/md11/md/mismatch_cnt >> 7296 >> >> fugly. Since the mirrors aren't checksummed, can i assume this means >> there's likely some data messups here? >> >> Anyways, the repair is running on both md10 and md11, i'll check back >> with my final results... >> >> >> >> >> ___ >> CentOS mailing list >> CentOS@centos.org >> http://lists.centos.org/mailman/listinfo/centos >> >> >> > Hi > > It has to do with aborted writes in SWAP. Your data should be fine > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > See http://forum.nginx.org/read.php?24,16699 for more info ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
On 01/03/10 10:31, John R Pierce wrote: > Clint Dilks wrote: > >> It has to do with aborted writes in SWAP. Your data should be fine >> > so swap on LVM on MD mirrors is a bad idea? > > > frankly, I usually avoid LVM< but I figured I'd setup this system with > it and see how it goes. its just a dev box, but we're about to put some > oracle stuff on it (for development, but still) > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > SWAP inside LVM is fine in my experience. Personally I consider this a benign error and generally ignore it unless the mismatch count is very high. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cron mystery
On 02/28/2010 01:00 PM, Timothy Murphy wrote: > I've just noticed that cron.daily, etc, > do not seem to be running on my CentOS-5.4 system. > The scripts in /etc/cron.d/ all run fine, > but those in /etc/cron.hourly, etc, seem to be ignored. > > I see that according to /var/log/cron > these commands are seen, eg > > Feb 28 18:01:01 helen crond[6680]: (root) CMD (run-parts /etc/cron.hourly) > > but none of the scripts in this directory > seem to be touched. > I've tried running them by hand, and this seems to work fine. > > Is there some problem, or subtlety, about crond under CentOS? Missing execute permissions on the scripts, perhaps?? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOLVED - Shutdown/poweroff does not power off machine
Eero Volotinen wrote: > On 1/4/10 10:57 PM, Scot P. Floess wrote: >> I've got a Dell Optiplex GX240 I am running CentOS 5.4 >> (kernel 2.6.18-164.9.1.el5.centos.plus)... When I had Fedora 11 and 12 on >> it, I could issue a poweroff command and the machine would power itself off. >> However, under CentOS it doesn't turn the machine off whatsoever. When it >> completes, the machine is still running with a message of "system halted." >> Then I have to physically hit the power button to turn it off... I >> believe at some point I did try to issue a shutdown command - but had the >> same results... >> >> Anyone have any recommendations or suggestions? > > buggy acpi support on server? Try updating to latest bios? No, I'm not the OP. But, I found a solution for my system. During boot, I noticed an error line -- "BIOS fails cutoff age - ACPI might not work. Use acpi=force to fix." So I did; the machine now actually turns off after shutdown. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
Clint Dilks wrote: > SWAP inside LVM is fine in my experience. Personally I consider this a > benign error and generally ignore it unless the mismatch count is very high And how do I know all these mirror data mismatches are Swap? does not each mismatch mean the mirrors disagree, which means one of them is wrong. Which one? since they aren't timestamped or checksummed (like vxvm, zfs do), I am playing 'data maybe'.As someone who adminstrates database servers, i have a real problem with that. btw, this is centos 5.4+latest x86_64, its primarily running postgres, and our inhouse java middleware apps. and was going to be a oracle grid operations server. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
John R Pierce wrote: > Clint Dilks wrote: > >> SWAP inside LVM is fine in my experience. Personally I consider this a >> benign error and generally ignore it unless the mismatch count is very high >> > > And how do I know all these mirror data mismatches are Swap? does not > each mismatch mean the mirrors disagree, which means one of them is > wrong. Which one? since they aren't timestamped or checksummed (like > vxvm, zfs do), I am playing 'data maybe'.As someone who adminstrates > database servers, i have a real problem with that. > Turn off the swap and see if the problem goes away. Or move the swap somewhere else than the software RAID and, again, see if the problem goes away. It isn't that hard to localize. -- Benjamin Franz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOLVED - Shutdown/poweroff does not power off machine
Neat - I'll give that a try. The machine is running Fedora right now...but maybe I'll reinstall CentOS :) On Sun, 28 Feb 2010, Michael Klinosky wrote: > Eero Volotinen wrote: >> On 1/4/10 10:57 PM, Scot P. Floess wrote: >>> I've got a Dell Optiplex GX240 I am running CentOS 5.4 >>> (kernel 2.6.18-164.9.1.el5.centos.plus)... When I had Fedora 11 and 12 on >>> it, I could issue a poweroff command and the machine would power itself off. >>> However, under CentOS it doesn't turn the machine off whatsoever. When it >>> completes, the machine is still running with a message of "system halted." >>> Then I have to physically hit the power button to turn it off... I >>> believe at some point I did try to issue a shutdown command - but had the >>> same results... >>> >>> Anyone have any recommendations or suggestions? >> >> buggy acpi support on server? Try updating to latest bios? > > No, I'm not the OP. But, I found a solution for my system. > > During boot, I noticed an error line -- > "BIOS fails cutoff age - ACPI might not work. Use acpi=force to fix." > > So I did; the machine now actually turns off after shutdown. > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-890-8117 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
On 01/03/10 11:37, John R Pierce wrote: > Clint Dilks wrote: > >> SWAP inside LVM is fine in my experience. Personally I consider this a >> benign error and generally ignore it unless the mismatch count is very high >> > And how do I know all these mirror data mismatches are Swap? does not > each mismatch mean the mirrors disagree, which means one of them is > wrong. Which one? since they aren't timestamped or checksummed (like > vxvm, zfs do), I am playing 'data maybe'.As someone who adminstrates > database servers, i have a real problem with that. > > btw, this is centos 5.4+latest x86_64, its primarily running postgres, > and our inhouse java middleware apps. and was going to be a oracle grid > operations server. > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > Even if this isn't SWAP the issue is to do with aborted writes. As I understand it. Situations occur where a write is requested, written to 1st drive but then aborted. There are two ways this can be handled. Drive 2 doesn't have the data on it yet so doesn't matter. But Drive1 you can either delete the unwanted block and then mark it as free. Or you can just skip the delete. The second option is what Software Raid does. So the differences being detected all relate to blocks that marked as free for re-use. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
On Sun, Feb 28, 2010 at 02:37:13PM -0800, John R Pierce wrote: > And how do I know all these mirror data mismatches are Swap? does not > each mismatch mean the mirrors disagree, which means one of them is > wrong. Which one? since they aren't timestamped or checksummed (like This thread is very timely. I updated my C5.3 to 5.4 last week (not sure why it took me so long) and this morning noticed my raid5 was resyncing. 5*1Tbyte disks. The resync took... Feb 28 04:22:02 mercury kernel: md: syncing RAID array md3 Feb 28 16:27:06 mercury kernel: md: md3: sync done. Performance was bad during this time. Not terrible from an interactive point of view, but a job that normally run from 4am to 10am didn't finish until 3pm. I like the concept of checking the disks are good, but it really sounds like there are practical problems (false positives, performance degregation) . So I think /etc/sysconfig/raid-check is going to read ENABLED=no -- rgds Stephen ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] puzzling md error ?
On Feb 28, 2010, at 7:15 PM, Stephen Harris wrote: > On Sun, Feb 28, 2010 at 02:37:13PM -0800, John R Pierce wrote: >> And how do I know all these mirror data mismatches are Swap? does >> not >> each mismatch mean the mirrors disagree, which means one of them is >> wrong. Which one? since they aren't timestamped or checksummed >> (like > > This thread is very timely. I updated my C5.3 to 5.4 last week (not > sure why it took me so long) and this morning noticed my raid5 was > resyncing. 5*1Tbyte disks. The resync took... > Feb 28 04:22:02 mercury kernel: md: syncing RAID array md3 > Feb 28 16:27:06 mercury kernel: md: md3: sync done. > > Performance was bad during this time. Not terrible from an > interactive > point of view, but a job that normally run from 4am to 10am didn't > finish > until 3pm. > > I like the concept of checking the disks are good, but it really > sounds like there are practical problems (false positives, performance > degregation) . > > So I think /etc/sysconfig/raid-check is going to read > ENABLED=no It would be nice if the mismatch_cnt could be compared to a count of aborted writes and only resync if they differ, but mismatch_cnt persists and aborted writes is only maintained since last reboot. Ideally the md raid code needs to make the writes completely atomic, so they either complete on all members or none and not allow an abort task to preempt a write in progress. -Ross ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 4.8 - PHP Version 5.1.6 and SQLite
I wish to use the SQLite extensions for php but the version I updated to with yum update (see above) was compiled '--without-sqlite'. I could sure use some help getting these extensions enabled. As I am unfamiliar with OOP the references to PDO on the web have been meaningless to me. Furthermore, a trip to the local book store today (Barnes & Noble) revealed no php books that even mention PDO! PHP.net documentation seems to be written as if PDO is the preferred method but I cannot even get a simple query to execute. Alternatively, can someone point me to a reference that shows actual examples of how to use PDO and SQLite? Regards, Ron +++ Little tiny dreams require little tiny thoughts and little tiny steps. Great big dreams require great big thoughts and little tiny steps. +++ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
