Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.4.16, 10.5.7
Description
While starting a MariaDB Galera 10.5.7 node on machine in a production environment it failed to start with error message:
...
|
mariadbd[48385]: 2020-11-07 17:26:12 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 100663296 bytes
|
mariadbd[48385]: 2020-11-07 17:26:12 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
|
mariadbd[48385]: 2020-11-07 17:26:12 0 [Note] InnoDB: New log file created, LSN=1273138439286
|
mariadbd[48385]: 2020-11-07 17:26:13 0 [Note] InnoDB: 128 rollback segments are active.
|
mariadbd[48385]: 2020-11-07 17:26:13 0 [Note] InnoDB: Creating sys_virtual system tables.
|
mariadbd[48385]: 2020-11-07 17:26:13 0 [Note] InnoDB: Creating shared tablespace for temporary tables
|
mariadbd[48385]: 2020-11-07 17:26:13 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
|
mariadbd[48385]: 2020-11-07 17:26:13 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
|
mariadbd[48385]: 2020-11-07 17:26:13 0 [Note] InnoDB: 10.5.7 started; log sequence number 0; transaction id 8895517680547275320
|
mariadbd[48385]: 2020-11-07 17:26:13 0x7f5c5effd700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.5.7/storage/innobase/include/fut0lst.h line 127
|
mariadbd[48385]: InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
|
mariadbd[48385]: 201107 17:26:13 [ERROR] mysqld got signal 6 ;
|
This seems very odd. Why are there buildbot paths embedded in the released binary?
The lines in fut0lst.h around 127 look like:
/** @return a file address */
|
inline fil_addr_t flst_read_addr(const byte *faddr)
|
{
|
fil_addr_t addr= { mach_read_from_4(faddr + FIL_ADDR_PAGE),
|
mach_read_from_2(faddr + FIL_ADDR_BYTE) };
|
ut_a(addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA);
|
ut_a(ut_align_offset(faddr, srv_page_size) >= FIL_PAGE_DATA);
|
return addr;
|
}
|
The commits around this section were:
- February 2020: 7ae21b18a6b73bbc3bf1ff448faf60c29ac1d386
- November 2019: a6e8a7df82f8434fc522470a8b7ffd45160cef71
- May 2009: 3945d5e5549187a18c64a112899f90a7f6a320d6
Does marko have any idea what might be going on here?
Attachments
Issue Links
- duplicates
-
MDEV-24096 Server crash, InnoDB fatal error, Assertion `first_free <= srv_page_size - 8' failed in trx_undo_page_report_modify
- Closed
-
MDEV-24155 Database not starting
- Closed
- is caused by
-
MDEV-23672 Assertion `v.v_indexes.empty()' failed in dict_table_t::instant_column
- Closed
- relates to
-
MDEV-24578 MariaDB 10.5 fails to join Galera cluster of MariaDB 10.1, root cause SST failure, symptom is InnoDB: Assertion failure
- Closed