Re: CORE creation is not working

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The hang is on the .48 version and hence our issue of not being able to get a CORE file.

 

From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Rich Megginson
Sent: Wednesday, February 18, 2015 10:25 AM
To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: CORE creation is not working

 

On 02/18/2015 09:12 AM, Jordan, Phillip wrote:

So a few weeks back we installed the CORE RPM and we were able to get a test core file on our Dev environment, but dev is 1.2.11.15-32, and in prod we are unable to get the core to generate with version 1.2.11.15-48.


That's a good thing, right?  That is, perhaps the crash has been fixed in -48?


We have had two failure where the dirsrv hangs and becomes unresponsive and need to get a CORE to see what is causing the issues.


AFAIK, there is nothing about debugging crashes (i.e. getting core files), or debugging hangs other than what's here: http://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes


 

When we installed the CORE RPM here are the additional setting we put in place:

 

sysctl -w fs.suid_dumpable=1

and ulimit -u unlimited


Right.  See above.


 

Can anyone suggest a reason for the CORE file not getting generated or why we can do a test core in Dev and not in prod?  Also any know issues with the dirsrv service stopping or hanging with the -48 version?


It's possible that the -48 version has a problem with hanging.  See the Debugging Hangs section in the link above and provide stack traces.


 

 

Phillip Jordan

Lead Engineer, Web Hosting

 

                      

555 W. Adams

Chicago, IL 60661

 

This email including, without limitation, the attachments, if any, accompanying this email, may contain information which is confidential or privileged and exempt from disclosure under applicable law. The information is for the use of the intended recipient. If you are not the intended recipient, be aware that any disclosure, copying, distribution, review or use of the contents of this email, and/or its attachments, is without authorization and is prohibited. If you have received this email in error, please notify us by reply email immediately and destroy all copies of this email and its attachments. 

 




--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

 

Attachment: PGP.sig
Description: PGP signature

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux