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

./rippled --unittest failed output #5024

Closed
Xtinc-T opened this issue May 21, 2024 · 4 comments
Closed

./rippled --unittest failed output #5024

Xtinc-T opened this issue May 21, 2024 · 4 comments

Comments

@Xtinc-T
Copy link

Xtinc-T commented May 21, 2024

Issue Description

I am building the rippled release repo on my VM (Ubuntu 22.04) and when I ran ran test, initially they were going as expected. But at the end the output was something else and I am not sure what should I make of it, did the testing went well? did it gave out errors and stopped the testing?

Steps to Reproduce

Expected Result

Absolutely no idea what to expect as this is my first time working with Rippled.

Actual Result

I am attaching some of the final output lines, I literally have no clue what happened and I am learning.
Screenshot 2024-05-21 174625

Environment

Ubuntu 22.04 Jammy everything else is above the requirements.

Supporting Files

@dangell7
Copy link
Collaborator

"Address already in use". Are you running other services on that computer?

@Xtinc-T
Copy link
Author

Xtinc-T commented May 22, 2024

Yes I checked these is nothing running, I even killed the running service which was rippled itself but everytime i killed it, it just gets assigned with different PID and goes to (LISTEN). I killed the process, then I kill again so at time I get no process running as expect but when I lsof, I see its created automatically as if it is binded.
Screenshot 2024-05-22 124449

@legleux
Copy link
Collaborator

legleux commented May 23, 2024

Yes I checked these is nothing running,

How'd you do that? You must have missed it because 51235 is the example config's peer port.

How are you "killing the service"? It wont restart if you ask it nicely.
Although if you built it from source, I'd expect you probably didn't install it as a service.

@Xtinc-T
Copy link
Author

Xtinc-T commented May 23, 2024

I see, I got it resolved though. Turns out just needed to end the rippled service instead of service running on that port. Thanks for the help

@mvadari mvadari closed this as completed May 23, 2024
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

4 participants