Re: Starting redis fails with 'Bus error (core dumped)'
On Nov 17, 2019 3:21 PM, Consus wrote: > > On 22:05 Sun 17 Nov, Unicorn wrote: > > On Sun, 2019-11-17 at 23:22 +0300, Consus wrote: > > > On 16:25 Sun 17 Nov, Unicorn wrote: > > > > After installing redis (and rspamd), before having modified any > > > > part of > > > > redis, starting redis with 'rcctl start redis' fails. I then tried > > > > running the binary itself in /usr/local/sbin/redis-server, which > > > > only > > > > returns 'Bus error (core dumped)'. > > > > > > > > I changed the log level in the '/etc/redis/redis.conf' to debug, > > > > but do > > > > not get any more information about the reason for failure. Running > > > > 'grep -R redis /var/log/' did not give me any information either, > > > > and > > > > after changing the log level to debug, the only thing that changed > > > > is > > > > an unreadable 'redis-server.core' file appearing in '/var/log'. > > > > > > Please, post the output of > > > > > > # gdb /usr/local/sbin/redis-server /var/log/redis-server.core > > > > > > > Output: > > > > GNU gdb 6.3 > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and > > you are > > welcome to change it and/or distribute copies of it under certain > > conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for > > details. > > This GDB was configured as "arm-unknown-openbsd6.6"...(no debugging > > symbols found) > > > > Core was generated by `redis-server'. > > Program terminated with signal 10, Bus error. > > (no debugging symbols found) > > Loaded symbols for /usr/local/sbin/redis-server > > Reading symbols from /usr/lib/libm.so.10.1...done. > > Loaded symbols for /usr/lib/libm.so.10.1 > > Reading symbols from /usr/lib/libpthread.so.26.1...done. > > Loaded symbols for /usr/lib/libpthread.so.26.1 > > Reading symbols from /usr/local/lib/liblua5.1.so.5.1...done. > > Loaded symbols for /usr/local/lib/liblua5.1.so.5.1 > > Reading symbols from /usr/lib/libc.so.95.1...done. > > Loaded symbols for /usr/lib/libc.so.95.1 > > Reading symbols from /usr/libexec/ld.so...Error while reading shared > > library symbols: > > Dwarf Error: wrong version in compilation unit header (is 4, should be > > 2) [in module /usr/libexec/ld.so] May need to install egdb from ports. Not sure what the deal is with the damn Dwarf but using egdb generally works for me. > > #0 0x133f3834 in SHA1Final () from /usr/local/sbin/redis-server > > (gdb) > > Damn it, on Linux it prints backtrace by default. Type `bt' in the gdb > prompt and post the output. >
Re: Starting redis fails with 'Bus error (core dumped)'
On 22:05 Sun 17 Nov, Unicorn wrote: > On Sun, 2019-11-17 at 23:22 +0300, Consus wrote: > > On 16:25 Sun 17 Nov, Unicorn wrote: > > > After installing redis (and rspamd), before having modified any > > > part of > > > redis, starting redis with 'rcctl start redis' fails. I then tried > > > running the binary itself in /usr/local/sbin/redis-server, which > > > only > > > returns 'Bus error (core dumped)'. > > > > > > I changed the log level in the '/etc/redis/redis.conf' to debug, > > > but do > > > not get any more information about the reason for failure. Running > > > 'grep -R redis /var/log/' did not give me any information either, > > > and > > > after changing the log level to debug, the only thing that changed > > > is > > > an unreadable 'redis-server.core' file appearing in '/var/log'. > > > > Please, post the output of > > > > # gdb /usr/local/sbin/redis-server /var/log/redis-server.core > > > > Output: > > GNU gdb 6.3 > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "arm-unknown-openbsd6.6"...(no debugging > symbols found) > > Core was generated by `redis-server'. > Program terminated with signal 10, Bus error. > (no debugging symbols found) > Loaded symbols for /usr/local/sbin/redis-server > Reading symbols from /usr/lib/libm.so.10.1...done. > Loaded symbols for /usr/lib/libm.so.10.1 > Reading symbols from /usr/lib/libpthread.so.26.1...done. > Loaded symbols for /usr/lib/libpthread.so.26.1 > Reading symbols from /usr/local/lib/liblua5.1.so.5.1...done. > Loaded symbols for /usr/local/lib/liblua5.1.so.5.1 > Reading symbols from /usr/lib/libc.so.95.1...done. > Loaded symbols for /usr/lib/libc.so.95.1 > Reading symbols from /usr/libexec/ld.so...Error while reading shared > library symbols: > Dwarf Error: wrong version in compilation unit header (is 4, should be > 2) [in module /usr/libexec/ld.so] > #0 0x133f3834 in SHA1Final () from /usr/local/sbin/redis-server > (gdb) Damn it, on Linux it prints backtrace by default. Type `bt' in the gdb prompt and post the output.
Re: Starting redis fails with 'Bus error (core dumped)'
On Sun, 2019-11-17 at 23:22 +0300, Consus wrote: > On 16:25 Sun 17 Nov, Unicorn wrote: > > After installing redis (and rspamd), before having modified any > > part of > > redis, starting redis with 'rcctl start redis' fails. I then tried > > running the binary itself in /usr/local/sbin/redis-server, which > > only > > returns 'Bus error (core dumped)'. > > > > I changed the log level in the '/etc/redis/redis.conf' to debug, > > but do > > not get any more information about the reason for failure. Running > > 'grep -R redis /var/log/' did not give me any information either, > > and > > after changing the log level to debug, the only thing that changed > > is > > an unreadable 'redis-server.core' file appearing in '/var/log'. > > Please, post the output of > > # gdb /usr/local/sbin/redis-server /var/log/redis-server.core > Output: GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "arm-unknown-openbsd6.6"...(no debugging symbols found) Core was generated by `redis-server'. Program terminated with signal 10, Bus error. (no debugging symbols found) Loaded symbols for /usr/local/sbin/redis-server Reading symbols from /usr/lib/libm.so.10.1...done. Loaded symbols for /usr/lib/libm.so.10.1 Reading symbols from /usr/lib/libpthread.so.26.1...done. Loaded symbols for /usr/lib/libpthread.so.26.1 Reading symbols from /usr/local/lib/liblua5.1.so.5.1...done. Loaded symbols for /usr/local/lib/liblua5.1.so.5.1 Reading symbols from /usr/lib/libc.so.95.1...done. Loaded symbols for /usr/lib/libc.so.95.1 Reading symbols from /usr/libexec/ld.so...Error while reading shared library symbols: Dwarf Error: wrong version in compilation unit header (is 4, should be 2) [in module /usr/libexec/ld.so] #0 0x133f3834 in SHA1Final () from /usr/local/sbin/redis-server (gdb)
Re: Starting redis fails with 'Bus error (core dumped)'
On 16:25 Sun 17 Nov, Unicorn wrote: > Hello again, > > I am currently setting up redis with rspamd for my mail setup, but I am > encountering an issue when trying to just start redis. > For the record, I am following the guide at > https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/ > > After installing redis (and rspamd), before having modified any part of > redis, starting redis with 'rcctl start redis' fails. I then tried > running the binary itself in /usr/local/sbin/redis-server, which only > returns 'Bus error (core dumped)'. > > I changed the log level in the '/etc/redis/redis.conf' to debug, but do > not get any more information about the reason for failure. Running > 'grep -R redis /var/log/' did not give me any information either, and > after changing the log level to debug, the only thing that changed is > an unreadable 'redis-server.core' file appearing in '/var/log'. > > I'd very much appreciate your help, thanks in advance! Please, post the output of # gdb /usr/local/sbin/redis-server /var/log/redis-server.core
Re: Starting redis fails with 'Bus error (core dumped)'
On Sun, 2019-11-17 at 16:25 +0100, Unicorn wrote: > Hello again, > > I am currently setting up redis with rspamd for my mail setup, but I > am > encountering an issue when trying to just start redis. > For the record, I am following the guide at > https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/ > > After installing redis (and rspamd), before having modified any part > of > redis, starting redis with 'rcctl start redis' fails. I then tried > running the binary itself in /usr/local/sbin/redis-server, which only > returns 'Bus error (core dumped)'. > > I changed the log level in the '/etc/redis/redis.conf' to debug, but > do > not get any more information about the reason for failure. Running > 'grep -R redis /var/log/' did not give me any information either, and > after changing the log level to debug, the only thing that changed is > an unreadable 'redis-server.core' file appearing in '/var/log'. > > I'd very much appreciate your help, thanks in advance! > > Best, > > Unicorn > I forgot to mention that I am running redis on ARMv7, and I think the issue is that something is broken with ARMv7 and Redis, since it worked just fine inside a VM on x86_64. Is there anything I can do to fix this or diagnose it further? Would really appreciate any suggestions. :) Best, Unicorn
Starting redis fails with 'Bus error (core dumped)'
Hello again, I am currently setting up redis with rspamd for my mail setup, but I am encountering an issue when trying to just start redis. For the record, I am following the guide at https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/ After installing redis (and rspamd), before having modified any part of redis, starting redis with 'rcctl start redis' fails. I then tried running the binary itself in /usr/local/sbin/redis-server, which only returns 'Bus error (core dumped)'. I changed the log level in the '/etc/redis/redis.conf' to debug, but do not get any more information about the reason for failure. Running 'grep -R redis /var/log/' did not give me any information either, and after changing the log level to debug, the only thing that changed is an unreadable 'redis-server.core' file appearing in '/var/log'. I'd very much appreciate your help, thanks in advance! Best, Unicorn
