Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

n2kd crashes when connecting to caching server #28

Closed
stevepmitchell opened this issue Jan 11, 2015 · 4 comments
Closed

n2kd crashes when connecting to caching server #28

stevepmitchell opened this issue Jan 11, 2015 · 4 comments

Comments

@stevepmitchell
Copy link

Using the most recent version of canboat.
Have an Actisense serial NGT-1, not USB.

Running actisense-serial /dev/ttyS1 | analyzer -json | n2kd to try to debug why n2kd_monitor was restarting constantly.

When connecting to the caching server on port 2597, n2kd exits with the below. This can be reproduced every time I try to connect to the caching server. I suspect it's a device on my network (very busy) that is throwing crappy data, but I can't be 100% sure:

FATAL 2015-01-11 11:07:01.504 [n2kd] Stream 0 contains invalid fd 976629818

Connecting to the non-caching json server on 2598, and the NMEA0183 server on 2599 work fine for long periods of time.

@keesverruijt
Copy link
Collaborator

Can you check whether the latest commit d0a4c4a fixes this? I couldn't find the issue exactly, but there was some fishy stuff going on in closeStream. Also, if it does still happen, run n2kd in debug mode and check the output.

@stevepmitchell
Copy link
Author

Well things are more stable with the checkin above, but now port 2597 is completely blank when I request any data from it. I get a TCP connect, and then the session is closed.

@keesverruijt
Copy link
Collaborator

@stevepmitchell did commit 8cdad67 fix it? That cleared up some remaining issues that I found. Port 2597 worked for me in that version.

@keesverruijt
Copy link
Collaborator

Assuming this worked as I received no further feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants