An issue with piler export/reindex segmentation fault.

[rajesh]

Hi jsuto,

We are facing piler DB corrupt issue to access adn also unable to reindex/export getting sementation fault error.

kinldy help me here to resolve the issue.

InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. InnoDB: Ending processing because of a corrupt database page. 150128 15:13:26 mysqld_safe Number of processes running now: 0 150128 15:13:26 mysqld_safe mysqld restarted 150128 15:13:26 InnoDB: Initializing buffer pool, size = 8.0M 150128 15:13:26 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 2 3412787418 150128 15:13:26 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 2 3412815089 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 1 row operations to undo InnoDB: Trx id counter is 0 12151296 150128 15:13:26 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Starting in background the rollback of uncommitted transactions 150128 15:13:27 InnoDB: Rolling back trx with id 0 12147397, 1 rows to undo 150128 15:13:27 InnoDB: Started; log sequence number 2 3412815089 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 65189. InnoDB: You may have to recover from a backup. 150128 15:13:27 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex da0aa12d0000fea5000050c8000045d9000000021449e43f45bf000000000000000000000000002c3e5280cd000000003e0a0002000100cb00000000008883070000000000000000059d0000000000000000000000000000000000000000010002001b696e66696d756d0007000b000073757072656d756d40000010004e35623230373938663932366135323862303133613232616466373037303734643666346262303438633137366332366661623432313566363731636334356536000000000000709940000018004e35623231363239653236363966313065306463626562386135616437613366636461303766393737623635343932376438373166396533366130623032363934000000000007fe1540000020004e35623231363239653236363966313065306463626562386135616437613366636461303766393737623635343932376438373166396533366130623032363934000000000008232e40040028004e35623231363239653236363966313065306463626562386135616437613366636461303766393737623635343932376438373166396533366130623032363934000000000008233540000030004e356232313863363730623237323936633731333932633966303139623636353365343035306265663364396538373963633365333465616565373237326163380000000000046ea140000038004e35623231386336373062323732393663373133393263396630313962363635336534303530626566336439653837396363336533346561656537323732616338000000000004d459400000402d1835623231386336373062323732393663373133393263396630313962363635336534303530626566336439653837396363336533346561656537323732616338000000000004d47340060048004e3562323538336162666539336434316165323030373733333037363863376530663636383230343564333863313336396263326638383430373861663133333300000000000832f140000050004e3562323538336162666539336434316165323030373733333037363863376530663636383230343564333863313336396263326638383430373861663133333300000000000837a840000058004e35623235383361626665393364343161653230303737333330373638633765306636363832303435643338633133363962633266383834303738616631333333000000000008381f40000060004e356232353833616266653933643431616532303037373333303736386337653066363638323034356433386331333639626332663838343037386166313333330000000000083ee440040068004e35623236323961150128 15:13:27 [Note] Event Scheduler: Loaded 0 events

we have approval to reindexing if its an issue with database corrupt.

but it should be resolve.

[Janos SUTO]

What version is this? What commands give you segfault error? Btw. I'm not sure how a corrupt mysql table is a major piler bug.

[eXtremeSHOK]

InnoDB: the corrupt table is a MySQL error, generally caused by unpatched/misconfigured mysql.. Are you running mysql 5.1 ?

[eXtremeSHOK]

Database page corruption on disk or a failed InnoDB: file read of page 65189. InnoDB: You may have to recover from a backup

MySQL error.. fix the crashed database..

Reindexing piler will not fix the crashed database..

[Janos SUTO]

No news is good news.