-
Notifications
You must be signed in to change notification settings - Fork 213
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
Occassional Segmentation Faults #3
Comments
Hi mceyzar Thank you for your report, could you tell us for which purpose you use Hi There, I've built and installed Mona Server in Centos 7 (latest from GIT — |
Hi, I am only using the RTMP. HTTP and RTMFP are being used by Apache and Cumulus (will eventually replace Cumulus with Mona). However, it behave itself today, it is still running stable on debug mode under GDB and has not crashed. The only difference with last week is that I have now installed and enabled SE Linux. Regards Mirza Ceyzar |
Hi, i'm not sure for SELinux, it's not a firewall so it should not alter If it comes from HTTP like I think you can first change the port used by For this issue we are currently working on. If you're interested in using
|
Hmmm, I'm not using HTTP for that Mona instance. Only RTMP. are you saying it is still possible for the segmentation fault to happen due to HTTP request being falsely triggered to Mona ? At the moment our setup is: I will try the maximum log (8) to see if anything. shows up. So far it has not crashed since Friday, but then again, there was no requests to it during the weekend. Regards Mirza Ceyzar |
It just crashed now, not much info: Program received signal SIGSEGV, Segmentation fault. |
Ok it crashed again with --log=8 sources/FlashStream.cpp[38] FlashStream 0 deleted |
Ok, now I don't think it comes from a HTTP problem. |
Do you have some news? If you can send me your files we will correct the Thomas 2014-11-17 8:29 GMT+01:00 mceyzar notifications@github.com:
|
Hi, sorry I have been sick in the past week. I will clean up log as it is very big, re run Mona and when it crash i will attach fresh Logfile, Corefile and main.lua. There is also a crash report mailed to sys admin, do you want that too ? |
Hi! Sorry for your illness! No I don't need the crash report, thank you for your help! Thomas
|
We have take a look at yout GDB output, I wonder if you have compiled Mona with debug info. If you don't please clean projects (with "make clean") and re-compile with debug info : "make debug" (for MonaBase/MonaCore/MonaServer). Thank you. |
I'm pretty sure it was compiled with debug (I do not mind rebuilding), anyway, it just crashed again: the lest things printed out are: how do you want me to pass the log.0, main.lua and core file ? |
Ok, just send me a mail at jammetthomas@gmail.com. -- Thomas JAMMET 2014-11-21 8:37 GMT+01:00 mceyzar notifications@github.com:
|
ok, sent :) |
let me know if i can be of any assistance |
…ertion to avoid crashes. - Correction of LUAXML::Index, a key not found was returning the key itself (may cause an infinite loop with ipairs) - Added a test of ipairs(mona:fromXML(...)) - Added tests RTMPLoad and RTMFPLoad to test several successive connections - Deleting directories data and www from UnitTests, duplicate
I've commited a correction for your issue, can you confirm that the problem is resolved? Thank you for your assistance! |
Hi There, I've built and installed Mona Server in Centos 7 (latest from GIT as of 7/11/2014).
I do get occasional SEGFAULT and could not pin point of why it is doing it.
It is quiet random although the more connections/disconnection I make the more likelihood of it happening.
I'm running it under GDB at the moment with debug build (make debug on all, base, core and server) When the crash happens (which could happen in 2 seconds or 2 days)
I will paste what i can find here.
The text was updated successfully, but these errors were encountered: