Discuss

discuss@lists.centos.org

34753 discussions

cmd line import of certificates
by Phil Savoie 22 Sep '06

22 Sep '06

Hi All, Would anyone know of a way to import certificates into netscape/mozilla on the command line? Thanks in advance, Phil

1 0

RE: [CentOS] Problem deleting an active route
by Alex Palenschat 22 Sep '06

22 Sep '06

> The big difference between mine and yours is that the > 169.254.0.0 route > is showing up on eth0 - which is the only port connected. I > can get into > the box, but the box can not get out to anyplace. I could be > looking in > the wrong place for the solution, I figured that this looks wrong to > have this apparent self-assigned IP on my only active ethernet port. What do you mean the box cannot get out to anyplace? What apps etc. Are you certain it is not a firewall or DNS issue? What are you trying and are there any errors? Simple stuff but sometimes overlooked. alex

1 0

rgmanager Hanging at shutdown
by Sherwyn Greene 22 Sep '06

22 Sep '06

HI All I'm working on a test cluster system with two computer system, both are almost the same spec... the problem i'm having is the service I create in the services are not shown in the cluster manager tab on the cluster configuration, and when I go to reboot the systems the rgmanager service hangs and I need to push the reset button on the system to reboot. How can i fix this prob??? Thanks Sherwyn Greene Planner / I.T. Technician Project Controls Dept. Kentz-OJ's E&I Services J.V. +1 (868) 648-0876

1 0

RE: [CentOS] Hard drive errors
by Bowie Bailey 22 Sep '06

22 Sep '06

Karanbir Singh wrote: > Jordi Espasa Clofent wrote: > > > > The ideal should be to use the SmartTools utilities, but, if I'm > > right, there're problems with SATA support. > > smartctl on CentOS >= 4.3, supports SATA just fine. Sounds good. I'll give it a try. > > At least, you can boot with liveCD-util (like UltimateBootCD, for > > example) and check the HD integrity. > > why not use the CentOS-4 LiveCD ? I downloaded the CentOS-4 LiveCD last night. The system is running from the hard drives at the moment, but if it dies again, I'll try the LiveCD. -- Bowie

1 0

RE: [CentOS] Re: Hard drive errors
by Bowie Bailey 22 Sep '06

22 Sep '06

Peter Farrow wrote: > This can be caused by overheating. If the drives are mounted close > together as some chassis configurations permit, then it make sense > they may both exhibit the same problem, but not necessarily > simultaneously. > > Are this log entries adjacent to each other? The drives have an open slot between them and a 120mm fan right in front of them, so I don't think overheating is an issue. At one point, I shut the machine down and let it sit for an hour or so. The errors started back up immediately during the boot process when I turned it back on. The log entries are adjacent...usually with the exact same timestamp. There are no other errors mixed in with them. I was able to get the system to boot yesterday. It triggered a raid rebuild which finished last night. The last batch of errors happened at 4am and the system appears to be running normally now. Here's a snip from the logs showing the errors and the rebuild: (I've cut out a few columns to shorten the lines) ---------------------------------- 22:36:21 kernel: ata3: command 0x25 timeout, stat 0x50 host_stat 0x24 22:36:21 kernel: ata3: status=0x50 { DriveReady SeekComplete } 22:36:21 kernel: Current sda: sense key No Sense 22:36:21 kernel: ata4: command 0x35 timeout, stat 0x50 host_stat 0x24 22:36:21 kernel: ata4: status=0x50 { DriveReady SeekComplete } 22:36:21 kernel: Current sdb: sense key No Sense 22:37:09 kernel: ata3: command 0x25 timeout, stat 0x50 host_stat 0x24 22:37:09 kernel: ata3: status=0x50 { DriveReady SeekComplete } 22:37:09 kernel: Current sda: sense key No Sense 22:38:03 kernel: md: md1: sync done. 22:38:03 kernel: RAID1 conf printout: 22:38:03 kernel: --- wd:2 rd:2 22:38:03 kernel: disk 0, wo:0, o:1, dev:sda2 22:38:03 kernel: disk 1, wo:0, o:1, dev:sdb2 23:25:39 kernel: ata3: command 0xca timeout, stat 0x50 host_stat 0x24 23:25:39 kernel: ata3: status=0x50 { DriveReady SeekComplete } 23:25:39 kernel: Info fld=0x662270, Current sda: sense key No Sense 23:25:39 kernel: ata4: command 0xca timeout, stat 0x50 host_stat 0x24 23:25:39 kernel: ata4: status=0x50 { DriveReady SeekComplete } 23:25:39 kernel: Info fld=0x662270, Current sdb: sense key No Sense ---------------------------------- These errors are showing ata3 and ata4 because I switched the drives to different SATA connections on the MB. These are the same drives that I showed previously with errors on ata1 and ata2. -- Bowie

1 0

RE: [CentOS] Re: Hard drive errors
by Bowie Bailey 22 Sep '06

22 Sep '06

Scott Silva wrote: > Bowie Bailey spake the following on 9/21/2006 12:56 PM: > > One of my CentOS boxes has started giving me errors. The box is > > CentOS-4.4 (i386) fully updated. It has a pair of SATA drives in a > > software raid 1 configuration. > > > > The errors I see are: > > > > ata1: command 0xca timeout, stat 0x50 host_stat 0x24 > > ata1: status=0x50 { DriveReady SeekComplete } > > Info fld=0x1e22b8, Current sda: sense key No Sense > > ata2: command 0xca timeout, stat 0x50 host_stat 0x24 > > ata2: status=0x50 { DriveReady SeekComplete } > > Info fld=0x1e2598, Current sdb: sense key No Sense > > > > If it was just coming from one drive, I would say it was a bad > > drive, but this is happening on both drives. > > > > Can anyone give me a starting place to diagnose this? > > Cables? Connections? Power supply going bad? Already reseated all of the cables. I even moved the drives to two different SATA ports on the MB. Power supply...maybe, but not my first guess. I may swap it out later if I can't find any other cause. -- Bowie

1 0

Lost path to root directory!
by Ted Miller 22 Sep '06

22 Sep '06

I'll admit I am new to LVM2, but I have got myself in a bad spot. I renamed the LVM volume and volume group so that I can keep track of what is in them. I have changed grub's menu.lst, /etc/fstab, and /etc/mtab, but somewhere else there is still something telling lvm that my root drive is on VolGroup00. Where is it, and how do I convince it that VolGroup00/Volume00 (or whatever the defaults are) is now DriveC/Centos? I suspect it may be hiding in initrd (compressed). Wherever it is, it brings the boot process to a screeching halt with a kernel panic when it tries to pivot mount the root drive. Until I get this figured out, my Centos install is dead, and I am back on my old Mandrake install. Ted Miller

2 6

FreeNX on 64-bit success
by Adam Huffman 22 Sep '06

22 Sep '06

I know a few people have been asking about running FreeNX on x86_64 machines. I've just installed the i386 versions of FreeNX and NX from Extras, and the openssl.i686 package, and it seems to be running happily on an x86_64 CentOS 4.4 machine. Adam

2 2

Hard drive errors
by Bowie Bailey 22 Sep '06

22 Sep '06

One of my CentOS boxes has started giving me errors. The box is CentOS-4.4 (i386) fully updated. It has a pair of SATA drives in a software raid 1 configuration. The errors I see are: ata1: command 0xca timeout, stat 0x50 host_stat 0x24 ata1: status=0x50 { DriveReady SeekComplete } Info fld=0x1e22b8, Current sda: sense key No Sense ata2: command 0xca timeout, stat 0x50 host_stat 0x24 ata2: status=0x50 { DriveReady SeekComplete } Info fld=0x1e2598, Current sdb: sense key No Sense If it was just coming from one drive, I would say it was a bad drive, but this is happening on both drives. Can anyone give me a starting place to diagnose this? Thanks. -- Bowie

5 5

Help with dhclient.conf & vendor options
by Plant, Dean 22 Sep '06

22 Sep '06

I have a test CentOS 4.4 workstation that I am trying to configure to use vendor options from a W2003 DHCP server. A vendor class with the custom options has been created on the windoze box and I seem to be receiving the info in the vendor-encapsulated-options shown in the lease file. What I don't know is how to decode these options so that the CentOS client uses them. I have searched the web and read the man pages and come up with a configuration for the /etc/dhclient.conf but as yet I am unable to get the extra options to work and to be honest I don't fully understand how the dhclient.conf should be written. Can anyone shed some light on what I am doing wrong or missing. /var/lib/dhcp/dhclient-eth0.leases lease { interface "eth0"; fixed-address 192.168.80.10; option subnet-mask 255.255.255.0; option dhcp-lease-time 691200; option dhcp-message-type 5; option dhcp-server-identifier 192.168.80.1; option dhcp-renewal-time 345600; option dhcp-rebinding-time 604800; option vendor-encapsulated-options 28:a:70:75:62:6c:69:63:6e:65:74:0:29:8:c1:76:c0:21:c1:76:c0:18:2a:8:c1:7 6:c0:18:c1:76:c5:5e:77:1e:63:6f:6d:6d:2e:61:64:2e:72:6f:6b:65:2e:63:6f:2 e:75:6b:20:72:6f:6b:65:2e:63:6f:2e:75:6b:0; renew 1 2006/9/25 12:41:13; rebind 5 2006/9/29 10:32:59; expire 6 2006/9/30 10:32:59; } /etc/dhclient-eth0.conf send host-name "test"; send vendor-class-identifier "CentOS"; vendor option space "CentOS"; request CentOS.nis-domain; request CentOS.nis-servers; request CentOS.ntp-servers; request CentOS.domain-search-list; Thanks Dean

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss