Discuss July 2006

discuss@lists.centos.org

213 participants
260 discussions

Start a nNew thread

Centos v3.3 CD 2
by Luis-Miguel Astudillo 15 Nov '11

15 Nov '11

Sorry, I have been away for a while. has anyone fixed CD2 fotr CentOS v3.3 ? -- Luis

6 7

what pkg contains libstdc++-libc6.2-2.so.3
by Fong Vang 02 Feb '11

02 Feb '11

In CentOS 4.1/2, what package contains this library: libstdc++-libc6.2-2.so.3? I installed a couple of the compat- packages, but this library is still missing.

8 8

Gnumeric
by centos＠911networks.com 31 Mar '08

31 Mar '08

Hi, I am trying to install Gnumeric in CentOS 4 and I can't. It complains about quite a few dependencies failing. It suggested installing some postgresql librairies, openldap librairies... I did that, now I still get: dependencies failed: libmdb/libmdbsq/libsqlite/libxbase/libtds. Is there a yum repository that has them or a yum repository for gnumeric? I have tried Dag, he does not, he has libgda, but that has other requirements... -- Thanks

7 21

CentOS4 and older megaraid
by Craig White 01 Sep '07

01 Sep '07

Release notes say no support for the RAID card in a box I just picked up...is there no hope for this box running 2.6 kernel? http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release- notes/as-x86/ The kernel shipped with Red Hat Enterprise Linux 4 includes the new megaraid_mbox driver from LSI Logic, which replaces the megaraid driver. The megaraid_mbox driver has an improved design, is compatible with the 2.6 kernel, and includes support for the latest hardware. However, megaraid_mbox does not support some of the older hardware that was supported by the megaraid driver. Adapters with the following PCI vendor ID and device ID pairs are not supported by the megaraid_mbox driver: vendor, device 0x101E, 0x9010 0x101E, 0x9060 0x8086, 0x1960 <--- my card ---< The lspci -n command can be used to display the IDs for adapters installed in a particular machine. Products with these IDs are known by (but not limited to) the following model names: * Dell PERC (dual-channel fast/wide SCSI) RAID controller * Dell PERC2/SC (single-channel Ultra SCSI) RAID controller * Dell PERC2/DC (dual-channel Ultra SCSI) RAID controller * Dell CERC (four-channel ATA/100) RAID controller * MegaRAID 428 * MegaRAID 466 * MegaRAID Express 500 * HP NetRAID 3Si and 1M Both Dell and LSI Logic have indicated that they no longer support these models in the 2.6 kernel. As a result, these adapters are not supported in Red Hat Enterprise Linux 4. Craig

10 40

Moving the Home dir to new server
by Todd Cary 28 Feb '07

28 Feb '07

I have a new Centos installation that has an empty /home dir and there are no users...just root. I want to move the home directory from another server to the new one. At this time the old /home directory has been tarred with "-prf". That will keep permissions which could be a problem. Is there a simple way to move the /home directory? And the non-system users in the password and group files? Todd -- Ariste Software 200 D Street Ext Petaluma, CA 94952 (707) 773-4523

7 14

APIC error on CPU0: 60(60)
by Erick Perez 18 Oct '06

18 Oct '06

I have a lot of this errors in my Centos stock 4.3 version in an Intel D945gnt motherboard with a Pentium D (dual core) If I disable apic in the grub.conf (apic=off) will I get a performance hit? Im running Asterisk on that machine. 40 is Received Illegal Vector 20 is Send Illegal Vector 60 means you're getting both errors at the same time. Basically it means that the APIC bus messages are malformed. The cause can be hardware or software, it's difficult to tell. APIC error on CPU0: 60(60) APIC error on CPU0: 60(60) APIC error on CPU0: 60(60) cat /proc/cpuinfo shows: processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) D CPU 2.66GHz stepping : 7 cpu MHz : 2666.770 cache size : 1024 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cid cx16 xtpr bogomips : 5333.47 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) D CPU 2.66GHz stepping : 7 cpu MHz : 2666.770 cache size : 1024 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl tm2 cid cx16 xtpr bogomips : 5338.11 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: -- ------------------------------------------------------------ Erick Perez Panama Sistemas Integradores de Telefonia IP y Soluciones Para Centros de Datos Panama, Republica de Panama Cel Panama. +(507) 6694-4780 mailto: eaperezh(a)gmail.com mailto: eperez(a)ptysystems.com ------------------------------------------------------------

5 6

Re: [CentOS] Installing Java 1.4.2
by Robert Moskowitz 03 Oct '06

03 Oct '06

Back home and back working on my servers.... At 11:13 AM 1/6/2006, Jim Perrin wrote: >On 1/6/06, Robert Moskowitz <rgm(a)htt-consult.com> wrote: > > At 10:45 AM 1/6/2006, Rodrigo Barbosa wrote: > > > > > > >Unfortunately, that won't do. That java implementation you see is the > > >GNU one. For Scalix, you will need Sun's JDK. You can get it at > > >www.java.com, if I recall. > > > > thanks. Does that mean I unistall the GNU one? Or installing the > > SUN one will 'override' the GNU one. > >No you don't need to uninstall the gnu one. Java on rhel uses (or >should, in a perfect world) the alternatives framework, which allows >for multiple programs to provide an application or utility. That said, >the java packages from sun are a bit braindead. You can get the java >sdk rpm or bin from sun and install it but it won't do much for you, >and it doesn't put java in a place where the system can "Just use it". >The best way is to get the sun java sdk package, and then get the sun >java compat rpm from jpackage.org -> >http://jpackage.org/rpm.php?id=3320 > >This rpm tells your system all about the sun install and sets things >up for you in alternatives so that you can begin using your shiny new >non-GNU java. How can I be sure of the dependencies? What yum command would I run afterwards? How do I get updates to this rpm over time? thanks!

4 3

Mailing List Etiquette
by Johnny Hughes 18 Sep '06

18 Sep '06

OK guys and gals ... can we please stop all the fighting? When technical questions are asked, they should be answered. I lot of people on this list have something that a lot of newbies need ... experience. So answering a question with "RTFM" or "JFGI" is not going to impart any of your experience ... which is one of the things they need and want. Also ... if someone attacks you, you should not respond in kind, but should try not to flame or bait people. It take more than one person to get these things going, and just a little restraint on both people's parts could prevent problems. Can everyone who is a member of this list please read this document: http://www.gweep.ca/~edmonds/usenet/ml-etiquette.html Especially the section "I've been insulted! How should I respond?" Please, please, please ... can we be civil and not attack people personally. ALSO There is a forum at http://www.centos.org/modules/newbb/ It would be very good if people would post questions and answers there as well. Thanks, Johnny Hughes

10 11

Bug: lvchange delayed until re-boot. System lock up experienced.
by William L. Maltby 06 Sep '06

06 Sep '06

Did a search for LVM at the CentOS bugzilla. Nothing seems to match this scenario. If no one contradicts me, I'll also post this in the bug reporting system. Wanted to a) get confirmation, if possible before bugging it and b) warn other souls that may be adventurous too! Summary: failings in LVM and kernel(?) seem to make a "freeze" possible. 1) Lvchange --permission=r seems to not take effect until re-boot even though lvdisplay says it has taken effect; 2) Prior to reboot, mount will mount a read-only LV and give no warning that it is read-only and will mount it r/w. The opposite also occurs: if the LV was ro and it is changed to r/w, mount still acts as if read-only is in effect. 3) If these steps are done, *ALL* commands work as if everything is normal *except* "ro" seems to have no effect: - lvchange --permission=r # Seems OK - lvdisplay # Seems OK, says "r" - mount <normal mount args> # Only "t -ext2" extra, no "read # only" warning from mount command - >/mnt/the_mount_point/test # Seems OK, ls shows it - rm /mnt/the_mount_point/test # Seems OK, ls doesn't show it What would happen if I did not umount it here? I guess it would run for at least some time without problem. Then, if LVM truly has it ro, when buffer flush time came there should be some undesirable results. At this point, I issued a umount for the volume and the system froze with blinking keyboard LED. Subsequent re-boot and investigation added the knowledge that the change in lv status was delayed until reboot. Can/will anyone confirm/deny this for me? Thx. Node: Athalon, CentOS-4.3. fully updated, all normal components from base (wine and a few odds and ends from rpmforge). ============ Gory Details Below ====================================== Progressing on LVM education and simplified b/u procedure using it. Covered my butt by setting the lv to read only. Got the hare-brained idea to see what would happen if... >>:-( # Protect fools from themselves. # umount /dev/VolGroupAA/lvol1 # lvchange --permission r VolGroupAA/lvol1 Logical volume "lvol1" changed # lvdisplay VolGroupAA/lvol1 # Edited below to items of interest --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV Write Access read only LV Status available # open 0 LV Size 9.31 GB Current LE 298 Block device 253:3 # Notice: no read-only this mount & no warning from mount command # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 # > /mnt/VolGroupAA_lvol1/test # ls show file created # rm /mnt/VolGroupAA_lvol1/test # ls shows file gone # umount /dev/VolGroupAA/lvol1 # Instant petrification! Purgatory entered: flashing keyboard LED and the usual three-fingered salute and destructive pounding on attached peripherals had the expected results! NADA! Googled here (it wrapped, sorry) http://groups.google.com/groups/search?hl=en&lr=&q=read-only+mount +write+LVM2+kernel+2.6+2006+lock+OR+crash&qt_s=Search Didn't see anything that looks like it. Saw a drbd related elsewhere that might come close... but NOPE! Anyway, since it seems (according to the HOWTO) that only mailing list activities report and address bugs (didn't see a bugzilla: did I look too casually?) I would like to confirm this is not peculiar to my node. I prefer not to subscribe to another list just to belatedly discover nothing of value after searching their archives too! If anyone else has a test machine and time, I will take the trouble to report this if it is confirmed. Subsequent reboot and test from the console gave this surprise. # lvchange --permission rw VolGroupAA/lvol1 Logical volume "lvol1" changed # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 mount: block device /dev/VolGroupAA/lvol1 is write-protected, mounting read-only # There I realized that the status change was not propagated to the system until a re-boot. Later I tried adding a "lvchange --refresh" although the docs didn't seem promising. It had no effect. Confiming again, re-booted and did this. Note the read/write access. # lvdisplay /dev/VolGroupAA/lvol1 --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV UUID jDoW7T-e7IS-Z5Zd-F1lG-3E6S-DvDl-bxYq7d LV Write Access read/write LV Status available # open 0 LV Size 9.31 GB Current LE 298 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:3 # lvchange --permission r VolGroupAA/lvol1 Logical volume "lvol1" changed # lvdisplay /dev/VolGroupAA/lvol1 --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV UUID jDoW7T-e7IS-Z5Zd-F1lG-3E6S-DvDl-bxYq7d LV Write Access read only LV Status available # open 0 LV Size 9.31 GB Current LE 298 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:3 # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 # Note: no warning about read-only issued. # mount <snip uninteresting stuff> /dev/mapper/VolGroupAA-lvol1 on /mnt/VolGroupAA_lvol1 type ext2 (rw) # >/mnt/VolGroupAA_lvol1/test # ls -ltr /mnt/VolGroupAA_lvol1 total 6486852 -rw-r--r-- 1 <snip> 290155835 Jul 25 12:25 ImportedHardDisks.tar.bz2 drwx------ 2 <snip> 16384 Jul 25 16:53 lost+found -rw-r--r-- 1 <snip> 6345862846 Jul 25 20:49 TestDisk_Test.tar.bz2 -rw-r--r-- 1 root root 0 Jul 27 11:56 test # umount here will lock machine. I'll finish mail first. TIA -- Bill

2 1

TARPIT target in iptables
by Barry Brimer 04 Sep '06

04 Sep '06

Has anyone been successful at using the TARPIT target in iptables under CentOS 4? I am using CentOS 4.3, fully updated with iptables-1.2.11-3.1.RHEL4 and kernel-2.6.9-34.107.plus.c4 Doing a locate on TARPIT returns: # locate TARPIT /lib/iptables/libipt_TARPIT.so This makes me think that the TARPIT target would be valid, however when I try to use it, I get the following reponse: # iptables -A INPUT -p tcp -m tcp --dport 80 -j TARPIT iptables: No chain/target/match by that name I am following the example located at the Netfilter website for rule creation: http://www.netfilter.org/patch-o-matic/pom-extra.html#pom-extra-TARPIT I have *NOT* rebuilt my kernel, or any tools because on the surface, as it does not appear necessary. Any help would be greatly appreciated. Thanks, Barry

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2006