Sort:  

Bus error (core dumped)

That usually means you ran out of available space on whatever file system is holding the shared data file. If you are following @abit's directions that would be /dev/shm. You need to make sure you have enough RAM and/or swap space and have used the remount command to enlarge it.

BTW, on Ubuntu Linux (and probably others) /dev/shm is not a mounted file system, it is a symlink to /run/shm. I don't think remount on /dev/shm will work, but I'm not 100% sure. I do the remount on /run/shm instead. EDIT: remount on /dev/shm appears to be okay; mount follows the link.

I guess it's OK to remount /dev/shm, from my test:

$ df -h /dev/shm
Filesystem      Size  Used Avail Use% Mounted on
none             10G  144K   10G   1% /run/shm

$ sudo mount -o remount,size=11G /dev/shm
$ df -h /dev/shm
Filesystem      Size  Used Avail Use% Mounted on
none             11G  144K   11G   1% /run/shm

I guess mount follows the link. I will edit.

Thank you.

I tried a few different sizes for RAM and swap.

I will try to remount /run/shm/ instead.

Could this also be related to this ?:

so Linux users may need to tweak kernel settings in order to run the latest version of steemd.

source: https://steemit.com/steem/@steemitblog/steem-0-16-0-official-release

It is related in that the settings given there are trying to address some of the same issues. The approach outlined by abit here works better.

I have:

  • enable-plugin = witness (without the rest )
  • changed the shared-file-size
  • tried with 14 G, 10G and 8G RAM
  • changed the size of the swap (tried various settings)

Still crashes with Bus error.

I appreciate the help.
Didn't work so far.

I also tried the kernel settings @steemitblog suggested ...
Didn't change the error.

After you changed the enable-plugin settings in config.ini, you need to run with --replay like follows:

./steemd --shared-file-dir /dev/shm/ --replay

Also you can check if the disk is full:

df -h /dev/shm/

//Update: after further investigation, we found that @felixxx's issue is caused by a typo when running the mount command, so the size of /dev/shm remained unchanged (too small), so unable to allocate new space. Here is the tip: no space after the comma, and, just copy & paste.