stn icon indicating copy to clipboard operation
stn copied to clipboard

feat: check ports on startup / .env file validation

Open safeina86 opened this issue 1 year ago • 13 comments

Screenshot_2024-02-06_205716

How can I fix this?

safeina86 avatar Feb 06 '24 22:02 safeina86

@safeina86 what operating system is this?

dionysuzx avatar Feb 07 '24 05:02 dionysuzx

@safeina86 also can i have your rustc and cargo version? rustc -V && cargo -V

dionysuzx avatar Feb 07 '24 05:02 dionysuzx

@safeina86 can you try it again? i just pushed it a fix :)

dionysuzx avatar Feb 07 '24 05:02 dionysuzx

@safeina86 what operating system is this?

ubuntu

safeina86 avatar Feb 07 '24 09:02 safeina86

@safeina86 also can i have your rustc and cargo version? rustc -V && cargo -V

rustc 1.72.1 (d5c2e9c34 2023-09-13) (built from a source tarball) cargo 1.72.1

safeina86 avatar Feb 07 '24 09:02 safeina86

@safeina86 can you try it again? i just pushed it a fix :)

I will try again and let you know

safeina86 avatar Feb 07 '24 09:02 safeina86

How can I deal with this situation?? Screenshot 2024-02-07 142233

safeina86 avatar Feb 07 '24 12:02 safeina86

How can I deal with this situation?? Screenshot 2024-02-07 142233

are you already using port 8548 for something? you can check with lsof -i tcp:8548. it seems like that port is already being used. if you do have a process there, i would kill the pid with kill <pid> (insert pid from lsof command).

please let me know if this works. thx

dionysuzx avatar Feb 07 '24 16:02 dionysuzx

nothing appears for me when I type lsof -i tcp:8548

There is a note that I would like to draw your attention to: I am running a Shardeum node on the same VPS but the Shardeum node is not running until I change port 3001 to 3002 from the .env file.

Screenshot 2024-02-08 010004

safeina86 avatar Feb 07 '24 23:02 safeina86

I will move the node from the VPS to a local machine... but I have a question: Can the Proposer node be run on 8 GB RAM??

safeina86 avatar Feb 07 '24 23:02 safeina86

There is a note: - When I run the node from within stn, there is a conflict between the ports, but when I entered the .env file and I changed the ports, as shown in the attached image, and restarted the node from inside stn, the node ran without problems.

Screenshot 2024-02-08 163059

When I said a conflict between ports, I meant something like what happened in this case shown in the image below

11111111111111111111111

safeina86 avatar Feb 08 '24 14:02 safeina86

@d1onys1us you here ??

safeina86 avatar Feb 09 '24 23:02 safeina86

@d1onys1us you here ??

Got it, sounds like I need to check for allocated ports before startup. Will do that to close this bug report, thank you.

dionysuzx avatar Feb 14 '24 22:02 dionysuzx