[DRE-maint] Bug#1000140: ruby-moneta: FTBFS: mysqld fails to start
Antonio Terceiro
terceiro at debian.org
Thu Nov 18 14:55:29 GMT 2021
Source: ruby-moneta
Version: 1.0.0-9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
X-Debbugs-CC: debian-ruby at lists.debian.org
Hi,
ruby-moneta fails to build from source. This is a recurring problem. We
have a ton of scritps to start mysql for running tests, they are all
slightly different, and they all break from time to time. :-/
Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
>
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rb │
> └──────────────────────────────────────────────────────────────────────────────┘
>
> RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-moneta/usr/lib/ruby/vendor_ruby:. GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-moneta/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 ruby2.7 debian/ruby-tests.rb
> 2021-11-18 14:48:53 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
> 2021-11-18 14:48:53 0 [ERROR] InnoDB: Write to file ./ibdata1 failed at offset 0, 1048576 bytes should have been written, only 0 were written. Operating system error number 22. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
> 2021-11-18 14:48:53 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument'
> 2021-11-18 14:48:53 0 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space
> 2021-11-18 14:48:53 0 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
> 2021-11-18 14:48:53 0 [ERROR] InnoDB: Operating system error number 22 in a file operation.
> 2021-11-18 14:48:53 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument'
> 2021-11-18 14:48:53 0 [ERROR] InnoDB: File (unknown): 'close' returned OS error 222. Cannot continue operation
> 211118 14:48:53 [ERROR] mysqld got signal 6 ;
> This could be because you hit a bug. It is also possible that this binary
> or one of the libraries it was linked against is corrupt, improperly built,
> or misconfigured. This error can also be caused by malfunctioning hardware.
>
> To report this bug, see https://mariadb.com/kb/en/reporting-bugs
>
> We will try our best to scrape up some info that will hopefully help
> diagnose the problem, but since we have already crashed,
> something is definitely wrong and this may fail.
>
> Server version: 10.6.4-MariaDB-1+b1
> key_buffer_size=134217728
> read_buffer_size=131072
> max_used_connections=0
> max_threads=153
> thread_count=0
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467956 K bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>
> Thread pointer: 0x0
> Attempting backtrace. You can use the following information to find out
> where mysqld died. If you see no messages after this, something went
> terribly wrong...
> stack_bottom = 0x0 thread_stack 0x49000
> ??:0(my_print_stacktrace)[0x55f65c52e8fe]
> ??:0(handle_fatal_signal)[0x55f65c07d2f8]
> ??:0(__restore_rt)[0x7ffa991ac8e0]
> ??:0(gsignal)[0x7ffa98cb7e71]
> ??:0(abort)[0x7ffa98ca1536]
> ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55f65bd31214]
> ??:0(std::unique_lock<std::mutex>::unlock())[0x55f65c38bc05]
> ??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x55f65c499e68]
> ??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x55f65c499ed1]
> ??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x55f65c49c530]
> ??:0(void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long&&))[0x55f65c49d651]
> ??:0(void std::this_thread::sleep_for<long, std::ratio<1l, 1l> >(std::chrono::duration<long, std::ratio<1l, 1l> > const&))[0x55f65c3fa717]
> ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55f65c33aa95]
> ??:0(ha_initialize_handlerton(st_plugin_int*))[0x55f65c08042e]
> ??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*, st_plugin_int*, st_mysql_sys_var*))[0x55f65be7ae06]
> ??:0(plugin_init(int*, char**, int))[0x55f65be7bdc8]
> ??:0(unireg_abort)[0x55f65bda783a]
> ??:0(mysqld_main(int, char**))[0x55f65bdad3b2]
> ??:0(__libc_start_main)[0x7ffa98ca2e4a]
> ??:0(_start)[0x55f65bda29ca]
> The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
> information that should help you find out what is causing the crash.
> Writing a core file...
> Working directory at /tmp/moneta20211118-1022140-17wcxol
> Resource Limits:
> Limit Soft Limit Hard Limit Units
> Max cpu time unlimited unlimited seconds
> Max file size unlimited unlimited bytes
> Max data size unlimited unlimited bytes
> Max stack size 8388608 unlimited bytes
> Max core file size 0 unlimited bytes
> Max resident set unlimited unlimited bytes
> Max processes 127325 127325 processes
> Max open files 32186 32186 files
> Max locked memory 4181245952 4181245952 bytes
> Max address space unlimited unlimited bytes
> Max file locks unlimited unlimited locks
> Max pending signals 127325 127325 signals
> Max msgqueue size 819200 819200 bytes
> Max nice priority 0 0
> Max realtime priority 0 0
> Max realtime timeout unlimited unlimited us
> Core pattern: |/lib/systemd/systemd-coredump %P %u %g %s %t 9223372036854775808 %h
>
> Aborted (core dumped)
>
> Installation of system tables failed! Examine the logs in
> /tmp/moneta20211118-1022140-17wcxol for more information.
>
> The problem could be conflicting information in an external
> my.cnf files. You can ignore these by doing:
>
> shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf
>
> You can also try to start the mysqld daemon with:
>
> shell> /usr/sbin/mariadbd --skip-grant-tables --general-log &
>
> and use the command line tool /usr/bin/mariadb
> to connect to the mysql database and look at the grant tables:
>
> shell> /usr/bin/mysql -u root mysql
> mysql> show tables;
>
> Try 'mysqld --help' if you have problems with paths. Using
> --general-log gives you a log in /tmp/moneta20211118-1022140-17wcxol that may be helpful.
>
> The latest information about mysql_install_db is available at
> https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
> You can find the latest source at https://downloads.mariadb.org and
> the maria-discuss email list at https://launchpad.net/~maria-discuss
>
> Please check all of the above before submitting a bug report
> at https://mariadb.org/jira
>
> Unable to start the test MySQL server.
> ERROR: Test "ruby2.7" failed.
The full build log is attached.
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ruby-moneta_amd64-2021-11-18T14:48:34Z.log.gz
Type: application/gzip
Size: 21151 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20211118/d9b12f59/attachment-0001.gz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20211118/d9b12f59/attachment-0001.sig>
More information about the Pkg-ruby-extras-maintainers
mailing list