Discuss November 2009

discuss@lists.centos.org

311 participants
291 discussions

Automatical resync of MD, why?
by happymaster23 02 Nov '09

02 Nov '09

Hello, I have three MDs on two HDDs in RAID 1. In last days, thanks to my monitoring (which is installed longer time), I have recognized, that one of these MDs is automatically started resync. First was at 25th October and second resync of the same MD was today. It started in same daytime (about 4:00 AM). Now is MD resynced and working well. Can someone tell me what means this automatic resync? Is it standard? Is it means some possible problems with one HDD (but other two MDs are working without resync)? Thank you Martin Šťastný

4 4

CentOS Mirrored On RapidShare [Links Here]
by James Bensley 02 Nov '09

02 Nov '09

5 6

DoveCot and Postfix Setup? or Zimbra?
by ML 01 Nov '09

01 Nov '09

Hi All, I have not really setup e-mail serving on Linux before by myself. I have a setup now where it was setup for me running Dovecot and postfix. The setup works. I want to set this up again on my own system. Does anyone have a good tutorial? Zimbra...does it replace dovecot and postfx setup? Best, -Jason

5 4

loading a program in memory for faster startup
by Jerry Geis 01 Nov '09

01 Nov '09

After searching for a way to load a program in memory for fast start time I found preload.sourceforge.net I then kept looking and found CentOS 5 has readahead_early and readahead_later. I have (2) questions. 1) the /etc/readahead.d/default.later file has firefox 1.5 preloads mentioned. That seems REALLY old. shouldnt that be updated? 2) can I just add the path to oowriter to /etc/readahead.d/default.later and oowriter will be ready all the time to just run from memory and wont have to load from disk? Is there a /etc/readahead.d/local type file to add oowriter to instead of default.later? Thanks, Jerry

1 1

No entry in /var/log/boot.log
by Rod Rook 01 Nov '09

01 Nov '09

I installed CentOS 5.3 on Oct 27, 2009 and immediately updated it to 5.4. I had not paid attention to this boot log until yesterday when I decided to take a look to do some trouble shooting. Oct 27 13:16:24 localhost NET[3797]: /sbin/dhclient-script : updated >> /etc/resolv.conf > > Oct 27 13:16:29 localhost NET[4059]: >> /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf > > This entry was probably made right after the fresh installation. I've done searches on the Internet for answers for this problem and the only thing I've found is that I am not the only one with this problem. But no body has offered any definite solution for it. I even posted the same question in the CentOS forum and haven't got any reply. >From what I have read, this problem may be caused by a bug or bugs in CentOS 5.x, but I hope it is not because I am in the process of switching from Fedora 10 to CentOS 5.4 and I don't want to get disappointed. Trivial as this may be, this does not give me confidence in CentOS distribution. Can anyone come up with a solution?

6 10

Disk error (kicking from MD) during smartctl -t short
by happymaster23 01 Nov '09

01 Nov '09

Hello, I started smartctl -t short of disk in RAID1, but during this operation this disk was kicked from RAID (only from one MD of three). /var/log/messages: Nov 1 16:45:45 server kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 1 16:45:45 server kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Nov 1 16:45:45 server kernel: res 51/04:00:38:df:f7/00:00:00:00:00/a7 Emask 0x1 (device error) Nov 1 16:45:45 server kernel: ata1.00: status: { DRDY ERR } Nov 1 16:45:45 serve kernel: ata1.00: error: { ABRT } Nov 1 16:45:45 server kernel: ata1.00: configured for UDMA/133 Nov 1 16:45:45 server kernel: ata1: EH complete Nov 1 16:45:45 server kernel: SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) Nov 1 16:45:45 server kernel: sda: Write Protect is off Nov 1 16:45:45 server kernel: SCSI device sda: drive cache: write back Nov 1 16:45:52 server kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 1 16:45:52 server kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Nov 1 16:45:52 server kernel: res 51/04:00:38:df:f7/00:00:00:00:00/a7 Emask 0x1 (device error) Nov 1 16:45:52 server kernel: ata1.00: status: { DRDY ERR } Nov 1 16:45:52 server kernel: ata1.00: error: { ABRT } Nov 1 16:45:52 server kernel: ata1.00: configured for UDMA/133 Nov 1 16:45:52 server kernel: ata1: EH complete Nov 1 16:45:52 server kernel: SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) Nov 1 16:45:52 server kernel: sda: Write Protect is off Nov 1 16:45:52 server kernel: SCSI device sda: drive cache: write back Nov 1 16:47:43 server kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 1 16:47:43 server kernel: ata1.00: BMDMA stat 0x25 Nov 1 16:47:43 server kernel: ata1.00: cmd ca/00:08:1f:41:1e/00:00:00:00:00/e1 tag 0 dma 4096 out Nov 1 16:47:43 server kernel: res 51/10:08:1f:41:1e/00:00:00:00:00/e1 Emask 0x81 (invalid argument) Nov 1 16:47:43 server kernel: ata1.00: status: { DRDY ERR } Nov 1 16:47:43 server kernel: ata1.00: error: { IDNF } Nov 1 16:47:43 server kernel: ata1.00: configured for UDMA/133 Nov 1 16:47:43 server kernel: sd 0:0:0:0: SCSI error: return code = 0x08000002 Nov 1 16:47:43 server kernel: sda: Current [descriptor]: sense key: Aborted Command Nov 1 16:47:43 server kernel: Add. Sense: Recorded entity not found Nov 1 16:47:43 server kernel: Nov 1 16:47:44 server kernel: Descriptor sense data with sense descriptors (in hex): Nov 1 16:47:44 server kernel: 72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 1 16:47:44 server kernel: 01 1e 41 1f Nov 1 16:47:44 server kernel: end_request: I/O error, dev sda, sector 18759967 Nov 1 16:47:44 server kernel: raid1: Disk failure on sda1, disabling device. Nov 1 16:47:44 server kernel: Operation continuing on 1 devices Nov 1 16:47:44 server kernel: ata1: EH complete Nov 1 16:47:44 server kernel: SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) Nov 1 16:47:44 server kernel: sda: Write Protect is off Nov 1 16:47:44 server kernel: SCSI device sda: drive cache: write back Nov 1 16:47:44 server kernel: RAID1 conf printout: Nov 1 16:47:44 server kernel: --- wd:1 rd:2 Nov 1 16:47:44 server kernel: disk 0, wo:1, o:0, dev:sda1 Nov 1 16:47:44 server kernel: disk 1, wo:0, o:1, dev:sdb1 Nov 1 16:47:44 server kernel: RAID1 conf printout: Nov 1 16:47:44 server kernel: --- wd:1 rd:2 Nov 1 16:47:44 server kernel: disk 1, wo:0, o:1, dev:sdb1 And output of smarctl -all: === START OF INFORMATION SECTION === Device Model: WDC WD3201ABYS-01B9A0 Serial Number: Firmware Version: 13.01C02 User Capacity: 320 072 933 376 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Nov 1 19:26:47 2009 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (8400) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 100) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 156 156 021 Pre-fail Always - 5183 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 82 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14329 10 Spin_Retry_Count 0x0012 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 82 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 58 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 82 194 Temperature_Celsius 0x0022 123 106 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 5 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 5 occurred at disk power-on lifetime: 14329 hours (597 days + 1 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 08 a7 4a 1e e1 Error: IDNF at LBA = 0x011e4aa7 = 18762407 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ca 00 08 a7 4a 1e e1 0a 45d+04:44:26.835 WRITE DMA ca 00 08 3f 14 00 e2 0a 45d+04:44:26.816 WRITE DMA Error 4 occurred at disk power-on lifetime: 14326 hours (596 days + 22 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 08 1f 41 1e e1 Error: IDNF at LBA = 0x011e411f = 18759967 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ca 00 08 1f 41 1e e1 0a 45d+02:30:44.518 WRITE DMA ca 00 08 3f 14 00 e2 0a 45d+02:30:44.504 WRITE DMA SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 14329 - # 2 Short offline Completed without error 00% 14329 - # 3 Extended offline Completed without error 00% 14328 - # 4 Short offline Completed without error 00% 14326 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. This device was kicked from MD during #4 and #2 short test. Second HDD (same as this problematic) is without errors. Thank you for you help

1 0

relatime in plus kernel
by Yuji Tsuchimoto 01 Nov '09

01 Nov '09

Dear CentOS lovers, Is someone interested in the linux-2.6-smarter-relatime.patch for centosplus kernel? This patch solves disk I/O performance dramatically on servers, And recent distributions (fedora9 and later, etc.) and official kernel applies it. RHEL6 may include it, but RHEL5 is not. How about the linux-2.6-smarter-relatime.patch? Best Regards, Yuji

3 5

CentOS 5.4: yum-priorities seems to be MIA
by Boris Epstein 01 Nov '09

01 Nov '09

Hi all, I just installed 5.4 on a machine here... All seems running fine, except I decided to put on the extra repositories - and as usual I decided to install yum-priorities (as directed here: http://wiki.centos.org/AdditionalResources/Repositories/RPMForge ) but it seems like this package is nowhere to be found. Does anybody know why this would be? Thanks. Boris.

3 3

iptables -d fqdn instead of IP
by Marcus Moeller 01 Nov '09

01 Nov '09

Hi all, does it work to define iptables rules with a fqdn as destination instead of an IP address? Or is it useful to resolve the name first using e.g. nslookup, writing the result to a variable which is then used within the -d statement? Best Regards Marcus

5 8

Interrupting Yum Update
by Lee Perez 01 Nov '09

01 Nov '09

Hi All, Quick question, I just finished googling and found the thread that is dealing with the rpmdup_remover.sh script, and thanks to everyone that was involved in this. I followed the following threads: http://www.opensubscriber.com/message/centos@centos.org/11086209.html http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=17… Which lead me to the following link and the script: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=10139&forum=27&p… I started an update at about 5pm on the 30th and here it is 2:30 in the morning on the 31st. I want to kill this update and start over. I usually get around 155 KB/s now I'm getting 455 B/s. I do believe it is the mirror that I am connected to. I just want to make sure that by using the above mentioned script that I am going the right way. Just looking for a little reassurance before I do it. If I don't I don't think this thing will finish until sometime next week :-) and that is a bit long. Thanks!! Lee Perez

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2009