feat: check ports on startup / .env file validation
How can I fix this?
@safeina86 what operating system is this?
@safeina86 also can i have your rustc and cargo version? rustc -V && cargo -V
@safeina86 can you try it again? i just pushed it a fix :)
@safeina86 what operating system is this?
ubuntu
@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 can you try it again? i just pushed it a fix :)
I will try again and let you know
How can I deal with this situation??
How can I deal with this situation??
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
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.
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??
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.
When I said a conflict between ports, I meant something like what happened in this case shown in the image below
@d1onys1us you here ??
@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.
