Page MenuHomePhabricator

restbase1030: Cassandra crashing (signal 11)
Closed, ResolvedPublic

Description

After the Cassandra upgrade to 4.1.1, the cassandra-a instance of restbase1030 continues to crash with sigsegv. The following output is observed in dmesg after each crash.

[ 2042.187996] ata5.00: exception Emask 0x0 SAct 0xf880440f SErr 0x0 action 0x0
[ 2042.195050] ata5.00: irq_stat 0x40000008
[ 2042.198995] ata5.00: failed command: READ FPDMA QUEUED
[ 2042.204147] ata5.00: cmd 60/00:b8:a8:72:c1/01:00:9b:00:00/40 tag 23 ncq dma 131072 in
                        res 51/40:00:a8:72:c1/00:01:9b:00:00/40 Emask 0x409 (media error) <F>
[ 2042.220222] ata5.00: status: { DRDY ERR }
[ 2042.224240] ata5.00: error: { UNC }
[ 2042.228286] ata5.00: configured for UDMA/133
[ 2042.228360] sd 4:0:0:0: [sdc] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2042.228365] sd 4:0:0:0: [sdc] tag#23 Sense Key : Medium Error [current] 
[ 2042.228371] sd 4:0:0:0: [sdc] tag#23 Add. Sense: Unrecovered read error - auto reallocate failed
[ 2042.228376] sd 4:0:0:0: [sdc] tag#23 CDB: Read(10) 28 00 9b c1 72 a8 00 01 00 00
[ 2042.228379] print_req_error: I/O error, dev sdc, sector 2613146280
[ 2042.234633] ata5: EH complete
[ 2042.363986] ata5.00: exception Emask 0x0 SAct 0x1202fff8 SErr 0x0 action 0x0
[ 2042.371045] ata5.00: irq_stat 0x40000008
[ 2042.374992] ata5.00: failed command: READ FPDMA QUEUED
[ 2042.380151] ata5.00: cmd 60/08:e0:60:73:c1/00:00:9b:00:00/40 tag 28 ncq dma 4096 in
                        res 51/40:08:60:73:c1/00:00:9b:00:00/40 Emask 0x409 (media error) <F>
[ 2042.396050] ata5.00: status: { DRDY ERR }
[ 2042.400068] ata5.00: error: { UNC }
[ 2042.404049] ata5.00: configured for UDMA/133
[ 2042.404078] sd 4:0:0:0: [sdc] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2042.404080] sd 4:0:0:0: [sdc] tag#28 Sense Key : Medium Error [current] 
[ 2042.404082] sd 4:0:0:0: [sdc] tag#28 Add. Sense: Unrecovered read error - auto reallocate failed
[ 2042.404084] sd 4:0:0:0: [sdc] tag#28 CDB: Read(10) 28 00 9b c1 73 60 00 00 08 00
[ 2042.404086] print_req_error: I/O error, dev sdc, sector 2613146464
[ 2042.410275] ata5: EH complete

See also: T344259: hw troubleshooting: Failing SSD for restbase1030.eqiad.wmnet

Event Timeline

Eevans renamed this task from restbase1030 crashing (signal 11) to restbase1030: Cassandra crashing (signal 11).Aug 15 2023, 2:30 AM
eevans@restbase1030:~$ sudo smartctl -a /dev/sdc
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-25-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     THNSF81D92CSE
Serial Number:    994S101WTCWQ
LU WWN Device Id: 5 00080d 9111f6151
Add. Product Id:  DELL(tm)
Firmware Version: DACB
User Capacity:    1,920,383,410,176 bytes [1.92 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-3 (minor revision not indicated)
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Aug 15 14:02:02 2023 UTC
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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		(   30) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control 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     0x000a   100   100   000    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0013   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       28682
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       21
 13 Read_Soft_Error_Rate    0x000a   100   100   000    Old_age   Always       -       0
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0012   100   100   000    Old_age   Always       -       100
181 Program_Fail_Cnt_Total  0x0032   100   100   000    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   075   070   000    Old_age   Always       -       25 (Min/Max 21/30)
195 Hardware_ECC_Recovered  0x0032   100   100   000    Old_age   Always       -       155
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   100   100   000    Old_age   Always       -       12
201 Unknown_SSD_Attribute   0x0023   100   100   004    Pre-fail  Always       -       0
202 Unknown_SSD_Attribute   0x0003   100   100   099    Pre-fail  Always       -       0
233 Media_Wearout_Indicator 0x0012   100   100   000    Old_age   Always       -       13127301
245 Unknown_Attribute       0x0012   096   096   000    Old_age   Always       -       96

SMART Error Log Version: 1
ATA Error Count: 155 (device log contains only the most recent five errors)
	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 155 occurred at disk power-on lifetime: 28682 hours (1195 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 38 60 73 c1 40  Error: UNC at LBA = 0x00c17360 = 12677984

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 28 90 d0 b4 40 08  21d+05:04:42.280  READ FPDMA QUEUED
  60 10 20 70 d0 b4 40 08  21d+05:04:42.280  READ FPDMA QUEUED
  60 08 08 60 d0 b4 40 08  21d+05:04:42.280  READ FPDMA QUEUED
  60 10 f8 48 d0 b4 40 08  21d+05:04:42.280  READ FPDMA QUEUED
  60 a0 00 20 a0 30 40 08  21d+05:04:42.279  READ FPDMA QUEUED

Error 154 occurred at disk power-on lifetime: 28682 hours (1195 days + 2 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 40 60 73 c1 40  Error: UNC at LBA = 0x00c17360 = 12677984

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 40 68 72 c1 40 08  21d+05:04:42.046  READ FPDMA QUEUED
  60 10 08 58 82 cb 40 08  21d+05:04:42.046  READ FPDMA QUEUED
  60 08 00 48 82 cb 40 08  21d+05:04:42.046  READ FPDMA QUEUED
  60 18 f0 70 52 fd 40 08  21d+05:04:42.046  READ FPDMA QUEUED
  60 08 e8 60 52 fd 40 08  21d+05:04:42.046  READ FPDMA QUEUED

Error 153 occurred at disk power-on lifetime: 28681 hours (1195 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 a8 60 73 c1 40  Error: UNC at LBA = 0x00c17360 = 12677984

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 b0 88 40 5f 40 08  21d+04:03:38.100  READ FPDMA QUEUED
  60 08 a8 60 73 c1 40 08  21d+04:03:38.095  READ FPDMA QUEUED
  60 08 a0 58 73 c1 40 08  21d+04:03:38.095  READ FPDMA QUEUED
  60 08 98 50 73 c1 40 08  21d+04:03:38.095  READ FPDMA QUEUED
  60 08 90 48 73 c1 40 08  21d+04:03:38.095  READ FPDMA QUEUED

Error 152 occurred at disk power-on lifetime: 28681 hours (1195 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 30 60 73 c1 40  Error: UNC at LBA = 0x00c17360 = 12677984

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 30 90 72 c1 40 08  21d+04:03:37.900  READ FPDMA QUEUED
  60 00 f0 50 70 02 40 08  21d+04:03:37.900  READ FPDMA QUEUED
  60 00 28 70 f4 88 40 08  21d+04:03:37.892  READ FPDMA QUEUED
  60 00 08 90 1c 3a 40 08  21d+04:03:37.891  READ FPDMA QUEUED
  60 00 00 88 8f 2f 40 08  21d+04:03:37.891  READ FPDMA QUEUED

Error 151 occurred at disk power-on lifetime: 28680 hours (1195 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 40 60 73 c1 40  Error: UNC at LBA = 0x00c17360 = 12677984

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 c8 f0 47 eb 40 08  21d+03:03:31.553  READ FPDMA QUEUED
  60 08 20 c8 69 cd 40 08  21d+03:03:31.553  READ FPDMA QUEUED
  60 08 18 b0 69 cd 40 08  21d+03:03:31.553  READ FPDMA QUEUED
  60 08 40 60 73 c1 40 08  21d+03:03:31.552  READ FPDMA QUEUED
  60 80 98 c0 c2 ec 40 08  21d+03:03:31.551  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%         1         -
# 2  Short offline       Completed without error       00%         1         -

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.

eevans@restbase1030:~$
Eevans triaged this task as High priority.Aug 15 2023, 2:42 PM
Eevans added a project: ops-eqiad.

I think the upgrade to 4.1.1 is a red herring. This seems to be limited to a single instance (one of three), and each sig 11 corresponds with the device errors above. Do we have spare SSDs for this machine? Can we get sdc replaced?

I think the upgrade to 4.1.1 is a red herring. This seems to be limited to a single instance (one of three), and each sig 11 corresponds with the device errors above. Do we have spare SSDs for this machine? Can we get sdc replaced?

See T344259

KOfori renamed this task from restbase1030: Cassandra crashing (signal 11) to Urgent: restbase1030: Cassandra crashing (signal 11).Aug 22 2023, 5:41 PM
KOfori renamed this task from Urgent: restbase1030: Cassandra crashing (signal 11) to restbase1030: Cassandra crashing (signal 11).Aug 22 2023, 5:46 PM

Mentioned in SAL (#wikimedia-operations) [2023-08-29T08:26:21Z] <claime> downtiming cassandra-a alerts on restbase1030.eqiad.wmnet for 14 days T344210 T344259

Status update:

The Cassandra instances on this host have net yet been brought online; Attempts to bootstrap Cassandra are resulting in client exceptions, and elevated error rates. A solution to this is still TBD.

However, the issue for which this ticket was opened has been resolved (the failing SSD), so I will close this issue and open a separate one to track the bootstrapping issues.

Status update:

The Cassandra instances on this host have net yet been brought online; Attempts to bootstrap Cassandra are resulting in client exceptions, and elevated error rates. A solution to this is still TBD.

However, the issue for which this ticket was opened has been resolved (the failing SSD), so I will close this issue and open a separate one to track the bootstrapping issues.

See: T346803: Unable to bootstrap restbase1030-{a,b,c}