Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Node crashed multiple times without any error #3353

Closed
ManuGowda opened this issue Apr 15, 2019 · 2 comments
Closed

Node crashed multiple times without any error #3353

ManuGowda opened this issue Apr 15, 2019 · 2 comments
Assignees

Comments

@ManuGowda
Copy link
Contributor

Expected behavior

  • Node should log errors before crashing for tracability
  • Since the issue is unknow due to no log info, we need to fix the issue once identified

Actual behavior

2019-04-14 01:04:10 272: [dbg] 2019-04-14 01:04:10 | Transport->broadcastHeaders: Failed to notify peer about self - {"peer":"104.238.145.120:7001","err":"Error: Unable to match an address to the peer"}
2019-04-14 01:26:12 604: [inf] 2019-04-14 01:26:12 | Initializing controller
2019-04-14 01:50:40 593: [dbg] 2019-04-14 01:50:40 | Updated peer 46.101.111.1:7001 - {"state":2}
2019-04-14 01:53:01 985: [inf] 2019-04-14 01:53:01 | Initializing controller

Steps to reproduce

Which version(s) does this affect? (Environment, OS, etc...)

1.6.0-rc.3, Binary release

@michielmulders
Copy link
Contributor

Investigations currently suspended as the exact cause can be related to the application, pm2, or even external influence. If this happens again, further research is definitely needed to assure quality.

@shuse2
Copy link
Collaborator

shuse2 commented Apr 17, 2019

Closing because not reproducible

@shuse2 shuse2 closed this as completed Apr 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants