diodechain / diode_client

Diode client written in GO that runs the Blockquick™ algorithm and a socks server to transmit data through diodechain.
https://diode.io/download
Other
65 stars 23 forks source link

Raspberry Pi Executable Command Returning No Output #102

Closed gallitim closed 1 year ago

gallitim commented 1 year ago

Hello, I had been using diode cli for a while on my raspberry pi. Although I'm not sure if this is the right place to ask this question, I was wondering why after a fresh restart, the diode terminal commands return no output for some reason. Am I possibly missing a dependancy? Here is an example of a command that I'd run that produces no output:

pi@raspberrypi:~ $ ./diode publish -public 8000:80 pi@raspberrypi:~ $

The diode file is in my home directory, so this command should theoretically work. Any help is much appreciated.

dominicletz commented 1 year ago

Hey @gallitim , this looks indeed pretty weird. Did you download the binary from our site or did you build it locally?

Indeed it's strange that there is not even an error message. You could check whether sudo dmesg shows any recent message about diode crashing.

gallitim commented 1 year ago

I had to download and unzip the zip folder to download it, since I am running on 64 bit bullseye OS, the curl command says it doesn't work properly on 64 bit, but I've gotten it to work on another pi running bullseye. After running dmesg I get this: [ 381.369179] process '/home/pi/diode' started with executable stack It seems like it's working, but I'm getting no visual output in the terminal.

dominicletz commented 1 year ago

Yeah indeed looks like something is wrong with the executable if it's not even printing an error message. You could try to download it again from our page - maybe it got corrupted during the restart?

gallitim commented 1 year ago

Do you reccomend the arm64 zip file on your website?

gallitim commented 1 year ago

I tried redownloading the arm64 file but no success. Long story short though, a few days ago I had a pi running 64 bit OS and diode worked just fine, I accidentally wiped the sd card and reinstalled the 64 os, and thats when I started experiencing this issue which is why I feel like I'm missing a dependancy or something, since I tried installing it on a separate sd card on a fresh 64 bit install but had the same issue as well.

dominicletz commented 1 year ago

hm it might be some compatibility issue. The safe way is to clone the source code repo and build it on your pi -- even though that is some work...

If I've got around to it I'm going to try the newest Raspberry PI OS and see if I run into any issues - Are you running on a PI4?

gallitim commented 1 year ago

I thought of that too, but which repo do I need to clone? All I want is to run the diode publish command to make my localhost publicly accessible. I've tried to clone this repo before I believe, but there was no makefile. How would I go about building it and running the command in console? And yes I am on a pi4, with a fresh install of 64 bit bullseye.

dominicletz commented 1 year ago

There definitely is a Makefile https://github.com/diodechain/diode_client/blob/master/Makefile -

1) Install go sudo apt install golang 1) Clone the repo git clone https://github.com/diodechain/diode_client.git 2) Go ino the directory and build openssl & diode:

cd diode_client
make openssl
make
jimthedj65 commented 1 year ago

I did exactly this on MAC M1 MAX, and it compiled very very very fast after Dominic resolved the Cloudflare dependency. I also had to downgrade golang to 18.09

dominicletz commented 1 year ago

Closed, because stale and can't reproduce :-(