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 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • 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
  • Crown
  • crown-corecrown-core
  • Issues
  • #253

Closed
Open
Created Oct 26, 2018 by Mark Brooker@walkjiveflyMaintainer

daemon stops processing blocks 1 before a superblock

Summary

MNs and SNs "hanging" one block before a superblock. They are responsive to crown-cli rpc requests, and actually keep talking to the network but they stop accepting new blocks.

Steps to reproduce

Just run a RC3 MN/SN/wallet.

Expected behavior

daemon should keep running normally.

Problematic behavior

daemon stops accepting new blocks one block before a superblock.

Crown-core environment info

Ubuntu 16.04

Crown-core application info

v0.12.5.2 RC3

Relevant logs, dumps and/or screenshots

Added 2 bzip2 compressed tar archives at https://nextcloud.crown.tech/nextcloud/s/znd8HiiAsRX3C6B

20181026_walkjivefly_neb08_MN_hang
20181026_walkjivefly_neb10_SN_hang

Each contains a core dump, debug.log and short README.

/cc @artem

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking