Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Tom Bradshaw
  • crown-corecrown-core
  • Issues
  • #6

Closed
Open
Created Jan 05, 2019 by Mark Brooker@walkjivefly

coredump when starting MN with jumpstart=1

Summary

Attempted to start MN with jumpstart=1 (discussed in https://gitlab.crown.tech/presstab/crown-core/issues/4). MN almost immediately SIGSEGV'd

Steps to reproduce

Shutdown a MN. Attempt to restart with either -jumpstart flag or jumpstart=1 in the config

Expected behavior

Node should start and sync as normal.

Problematic behavior

daemon crashes almost immediately.

Crown-core environment info

Ubuntu 16.04

Crown-core application info

Crown version v0.12.5.1-492e309f pipeline 869 build

Relevant logs and/or screenshots

2019-01-05 12:36:34 Crown version v0.12.5.1-492e309 (2019-01-03 10:18:53 -0700)
2019-01-05 12:36:34 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015
2019-01-05 12:36:34 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
...
2019-01-05 12:36:37 CBudgetManager::CheckAndRemove
2019-01-05 12:36:37 CBudgetManager::CheckAndRemove - mapBudgetDrafts cleanup - size: 0
2019-01-05 12:36:37 CBudgetManager::CheckAndRemove - mapProposals cleanup - size: 0
2019-01-05 12:36:37 CBudgetManager::CheckAndRemove - PASSED
2019-01-05 12:36:37      Proposals: 0, Budgets: 0, Seen Budgets: 1, Seen Budget Votes: 1, Seen Final Budgets: 2, Seen Final Budget Votes: 2

A quick gdb of the core file shows

crown@2093:~/.crown/testnet3$ gdb /usr/local/bin/crownd core
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/bin/crownd...(no debugging symbols found)...done.
[New LWP 16829]
[New LWP 16830]
[New LWP 16831]
[New LWP 16832]
[New LWP 16833]
[New LWP 16834]
[New LWP 16835]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `crownd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000699750 in BudgetDraft::ResetSync() ()
[Current thread is 1 (Thread 0x7f568bf00740 (LWP 16829))]
(gdb) quit

Possible fixes

(Any comments on what you think might be responsible for the problem, if you have particular insight.)

/cc @finjosh

Edited Jan 05, 2019 by Mark Brooker
Assignee
Assign to
Time tracking