[MDEV-24501] mariadbd fails to start: addr2line: 'linux-gate.so.1': No such file Created: 2020-12-30  Updated: 2020-12-30  Resolved: 2020-12-30

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.5.9
Fix Version/s: N/A

Type: Bug Priority: Trivial
Reporter: Otto Kekäläinen Assignee: Sergei Golubchik
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

While checking that my own PRs don't break anything on buildbot I noticed this which nobody seems to have reported so far:

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-sid-x86/builds/11587/steps/minor-upgrade-columnstore/logs/stdio

Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: 2020-12-27 17:32:41 0 [Note] /usr/sbin/mariadbd: ready for connections.
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: Version: '10.5.8-MariaDB-1:10.5.8+maria~sid'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: ??:0(my_print_stacktrace)[0x1149078]
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: ??:0(handle_fatal_signal)[0xb5985f]
Dec 27 17:32:41 debian-sid-i386 systemd[1]: Started MariaDB 10.5.8 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit mariadb.service has finished successfully.
-- 
-- The job identifier is 1939.
Dec 27 17:32:41 debian-sid-i386 mariadbd[5291]: addr2line: 'linux-gate.so.1': No such file
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: linux-gate.so.1(__kernel_sigreturn+0x0)[0xb7f3c1d8]
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: Printing to addr2line failed
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: linux-gate.so.1(__kernel_vsyscall+0x9)[0xb7f3c1cd]
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: linux/raise.c:51(__GI_raise)[0xb75558e2]
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: stdlib/abort.c:81(__GI_abort)[0xb753e309]
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: posix/libc_fatal.c:183(__libc_message)[0xb7598a6c]
Dec 27 17:32:41 debian-sid-i386 mariadbd[5269]: posix/libc_fatal.c:191(__GI___libc_fatal)[0xb7598aac]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: nptl/unwind-forcedunwind.c:65(pthread_cancel_init)[0xb79efec3]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: nptl/unwind-forcedunwind.c:127(_Unwind_ForcedUnwind)[0xb79f0045]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: nptl/unwind.c:125(__GI___pthread_unwind)[0xb79edc0a]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: :0(__pthread_exit)[0xb79e4426]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: ??:0(void std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_construct<char*>(char*, char*, std::forward_iterator_tag))[0xefdafa]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: ??:0(std::_Rb_tree<unsigned int, unsigned int, std::_Identity<unsigned int>, std::less<unsigned int>, std::allocator<unsigned int> >::_M_erase(std::_Rb_tree_node<unsigned int>*))[0xfa6bbf]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: nptl/pthread_create.c:479(start_thread)[0xb79e3082]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: i386/clone.S:110(__GI___clone)[0xb7622f86]
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: information that should help you find out what is causing the crash.
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: Writing a core file...
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: Working directory at /var/lib/mysql
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: Resource Limits:
Dec 27 17:32:42 debian-sid-i386 mariadbd[5269]: Fatal signal 11 while backtracing

Library linux-gate.so.1 is not a physical file and one should not try to read it.

https://web.archive.org/web/20170128060623/http://www.trilithium.com/johan/2005/08/linux-gate/



 Comments   
Comment by Sergei Golubchik [ 2020-12-30 ]

it's just the best effort attempt of resolving the stack trace.
if addr2line fails to read a file, stack trace will still be resolved, it just won't have the file name and line number for the corresponding library.
Normally the server should not crash at all.

Generated at Thu Feb 08 09:30:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.