Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Failed to write core dump
-
Hello
Now and then production Mango solution is found "crashed"! With this I mean that MANGO Stops once we can get access to Webmin.
Looking to the generated logs I found a common message about Java than says: "Failed to write core dump. Core dumps have been disabled. To enable core dumping, try ulimit -c unlimited before starting Java again"
My question is: Is it or not recommended to issue the specified command?
ulimit -c unlimitedIf you does not recommend it what should I try to solve the MANGO crashing issues?
Thanks in advance,
José -
Hi José,
I do not believe that is the cause. If it were, you would see messages in your ma.log files about not having enough available file descriptors. (Probably, IOException: Too many open files)
It sounds like Java is having an error. Do you have any hs_err files in your Mango/ directory? If so, they should have information as to the cause. If not, what is occurring in your ma.log when it ends?
-
Yes Phil I do have hs_err files.
I upload the last ones hope it may help [1_1515084790078_hs_err_pid592.log](Uploading 100%) [0_1515084790077_hs_err_pid568.log](Uploading 100%)Thanks,
José -
Hmm, doesn't look like the upload worked. You can email them to us, or try the upload again. I find the buttons above the post body work best, and that I need to wait for it to present a blue link in the preview section of the post, which typically takes several seconds after it says
(Uploading 100%) -
The problem to upload it seems
Error You do not have enough privileges for this action.I will send to you by email
-
Your hs_err files contain,
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xb3f3d7cc, pid=592, tid=1828779104 #One of the two hs_err files shows it was deep in the JVM when this happened. The first thing I would do in seeking resolution is update Java, as you appear to be on u33 when the latest are u151 and u152
-
Is there a special upgrade process for Java/MANGO that I have to pay attention once this is in a production environment or is that straight forward?
Thanks in advance,
José -
You need to have Mango (and any other Java program) stopped when you do the update to Java, and then restart Mango with the new Java.
