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

goesproc: Assertion 'rv == 0' failed #114

Open
reykowski opened this issue Sep 2, 2021 · 2 comments
Open

goesproc: Assertion 'rv == 0' failed #114

reykowski opened this issue Sep 2, 2021 · 2 comments

Comments

@reykowski
Copy link

Hi Pieter,
I helped a friend of mine to set up goes tools on an R-Pi.
He had his setup running for over 6 months, then something strange was happening.
After starting goesproc, the software was running for several minutes, displaying
mkdir: Permission deniedcounter=15492799
Then the code terminated with the following message:
Assertion 'rv == 0' failed at /home/pi/goestools/src/util/fs.cc:23
I think it is also important to mention that he uses an external USB drive to store the data.
Thanks in advance,
Arne

@ThePhotoChemist
Copy link

I'm not 100% sure if this is the answer, but I'm hoping this helps someone.

I had a similar issue. I had a setup that ran for about 8 months. At some point the computer shut down, and I was receiving this error message. I wasn't able to figure it out, updated Ubuntu, couldn't compile, etc etc and I just let it sit idle for another 6 months.

Recently I did a fresh install and got everything working again... until I got this same error message after a few minutes. But this time I realized, the way I had my script setup, goesproc was trying to write the files to whatever my current directory was... which at the time, was root. Goesproc would run happily long enough until it needed to write, and then it would crash.

Once I changed back to my home directory and made sure the goes16 directory had adequate permissions, I haven't had any issues since.

@mbruski
Copy link

mbruski commented Dec 27, 2022

I had this issue last evening when out of the blue I received the same error. Turned out the partition I was saving all my files and images to had saturated. After moving a bunch of stuff off to another drive I was back in business.

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

3 participants