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

Stat: File or directory not found goesproc #111

Open
zeke800 opened this issue Aug 5, 2021 · 1 comment
Open

Stat: File or directory not found goesproc #111

zeke800 opened this issue Aug 5, 2021 · 1 comment

Comments

@zeke800
Copy link

zeke800 commented Aug 5, 2021

Hi

This is a wonderful piece of software, but I am getting one error on Raspberry pi 3. I am getting from goesproc, when I run the command goesproc -c /usr/share/goestools/goesproc-goesr.conf -m packet – subscribe tcp://127.0.0.1:5004 – out /home/pi/goes, I get the error "stat: no such file or directory. I have no 'stat' file anywhere, and I have no idea what this means. I am getting around 100 vit avg and the demodulator works perfectly. Config for demodulator:

[demodulator]
mode = "hrit"
source = "rtlsdr"

[rtlsdr]
frequency = 1694100000
sample_rate = 2000000
gain = 42
bias_tee = true

[costas]
max_deviation = 200e3

[decoder.packet_publisher]
bind = "tcp://0.0.0.0:5004"
send_buffer = 1048576

[monitor]
statsd_address = "udp4://localhost:8125"
For decoder:
https://drive.google.com/file/d/10B1cr4ji0qMi9frQdC_bJKbfVa0k27Fj/view?usp=sharing
How can I solve this issue? It the decoder worked fine before the pi crashed. Thanks in advance!!

@Volas171
Copy link

Volas171 commented Jan 24, 2022

I had the same issue, solved it by not using -

log into your pi
create a goes folder
mkdir goes && cd goes
then open a screen session and execute goesproc
screen -mS goesproc
(inside the screen)
goesproc --config /usr/share/goestools/goesproc-goesr.conf --mode packet --subscribe tcp://127.0.0.1:5004 --out /home/pi/goes
that should fix the issue and store everything into /home/pi/goes

tl;dr: I'm pretty sure the source issue is because its piping stuff into - which isn't meant to be permanent (using - as a pipe for a long time eats a lot of ram)

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