-
Notifications
You must be signed in to change notification settings - Fork 8
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
Segmentation fault (core dumped) #9
Comments
Hi @alexbogus, no inconvenience mate, good to hear from you again. Firstly, is your underlying host still this?:
Secondly, was this a once off or does it happen over and over continually? Lastly, can you please post the output of Please sanitise this output by censoring your Thanks. -Mike |
Hi Mike, Output of my
Output of my rbfeeder container:
Thank you for taking the time to help me |
Is the segfault a once off or does it happen over and over continually? |
It happen over and over continually |
Are you able to post the output of You may need to censor some of the information in this file... I'm looking for more information on what is causing the segfault. Thanks. |
This is the output of
|
Hmm. I can’t see any helpful information in there. The next time you see a segfault could you capture the last 100 lines of |
I'm currently reviewing the logs, but I cannot not see any useful information This is the output:
Maybe those file can be useful to debug? |
Yes please, I’d like to have a look at them. Any way I can get hold of them? Do you need me to set up a drop box? You probably don’t want to post them publicly as they may contain sensitive info. |
I'll send you an email with the details to download the Regards |
Core analysis:
It looks like I can see from your "Mounts": [
{
"Type": "bind",
"Source": "/home/docker/adsb/radarbox/rbfeeder.ini",
"Destination": "/etc/rbfeeder.ini",
"Mode": "rw",
"RW": true,
"Propagation": "rprivate"
}
], Could you please post the contents of this file (censor Thanks. |
Could you also try running the container without the bind mount for |
Could I also please have the output of |
Volume lines commented in
And this is the output, another
|
My system It's working dockerized in a VM inside a ESXi Server (v6.5) |
Could you SSH into the VM and run the command |
Here is the output of
SSh into the VM, and I can't see
But doing a recursive search, I cannot find any temp files |
Hi @alexbogus, I think the problem is with the missing Looking at the rbfeeder source code, searching the files for ...
thermal = fopen("/sys/class/thermal/thermal_zone0/temp", "r");
n = fscanf(thermal, "%f", &millideg);
... I think what's happenning is because this code is designed to be run on an RPi (RadarBox don't make binaries for other platforms), I'm using On my Linux host that I run this on (physical), I have a kernel module loaded called
Could you run the If not, you could try loading it with |
Alternatively, you could try running the commands: mkdir -p /sys/class/thermal/thermal_zone0
echo 24000 > /sys/class/thermal/thermal_zone0/temp ...which will "spoof" a temperature of 24 degrees C and hopefully fool |
Ups, I'm trying to pass from host to virtual machine information about temperature. |
OK try this. echo 24000 > /home/docker/adsb/radarbox/faketemp Then add a bind mount to your under - /home/docker/adsb/radarbox/faketemp:/sys/class/thermal/thermal_zone0/temp:ro Then recreate the container with |
Trying the workaround:
|
Can you share your updated Outside of the suggested workarounds, I'm not sure how to solve this problem without either:
Sorry Alex. :( |
Thanks Mike, I really appreciate your effort to help me with the issue. No problem if we cannot solve this issue. This is my docker-compose.yml
|
Consider this issue closed as no further resolution is possible until Radarbox releases new code. |
Hi Mike,
Me again, sorry for the inconvenience.
After a few days of working the docker, I appreciate in the logs a
segmentation fault
.These are the logs
My apologies for the inconvenience
Thanks again four your support
Kind regards
Alex
The text was updated successfully, but these errors were encountered: