openldap 2.4.23 exited on signal 6
Hi all, I am experiencing the same problem below. Do you have a solution for this? I am running on FreeBSD 8.1. - Hi list, I'm experiencing some problems with and LDAP box which used to run 2.4.21 and has been upgraded to 2.4.22 The box act as a pam_ldap/nsswitch login server for a bunch of boxes, let's say 20, and serve the mail server and web proxy server as a user base. The box has 2G of RAM and has an average load very low, let's say top/systat shows 0.40. The issue is that it happens from time to time every 2/4 days that the slapd daemon exits on signal 6: May 12 01:00:00 polido kernel: pid 27153 (slapd), uid 389: exited on signal 6 Then i restart the process everything looks fine and no corruption seems to happen in the DB. The box is a FreeBSD 8 Any clue is really appreciated. Regards, Alyd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: uid 80: exited on signal 6
Zbigniew Szalbot wrote: szalbot.homedns.org kernel log messages: +++ /tmp/security.BfIqepKO Fri Oct 12 03:08:35 2007 +pid 82543 (httpd), uid 80: exited on signal 6 +pid 82542 (httpd), uid 80: exited on signal 6 +pid 82541 (httpd), uid 80: exited on signal 6 +pid 82537 (httpd), uid 80: exited on signal 6 +pid 82533 (httpd), uid 80: exited on signal 6 +pid 82536 (httpd), uid 80: exited on signal 6 +pid 82535 (httpd), uid 80: exited on signal 6 +pid 82534 (httpd), uid 80: exited on signal 6 +pid 3653 (httpd), uid 80: exited on signal 6 This means that the httpd child processes are crashing, most likely in response to a request. Because apache creates child processes dynamically to handle load (at least, with the default MPM) these crashed processes are automatically replaced, and the server continues happily servicing requests. It might be a good idea to go through your access and error logs and see if there are any suspicious-looking or unusually long requests that might be trying to exploit a buffer overflow vulnerability in apache or a module thereof. If you are using mod_php, though, it's more likely that it's a bug in PHP or a PHP extension that's being flushed out by some rarely used script on your server. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
uid 80: exited on signal 6
Hello, With each (daily) log rotation I get this in /var/log/messages file. szalbot.homedns.org kernel log messages: +++ /tmp/security.BfIqepKO Fri Oct 12 03:08:35 2007 +pid 82543 (httpd), uid 80: exited on signal 6 +pid 82542 (httpd), uid 80: exited on signal 6 +pid 82541 (httpd), uid 80: exited on signal 6 +pid 82537 (httpd), uid 80: exited on signal 6 +pid 82533 (httpd), uid 80: exited on signal 6 +pid 82536 (httpd), uid 80: exited on signal 6 +pid 82535 (httpd), uid 80: exited on signal 6 +pid 82534 (httpd), uid 80: exited on signal 6 +pid 3653 (httpd), uid 80: exited on signal 6 This seems to be saying to me that httpd died but it works and I do not have to start apache by hand. I know this may be caused by extensions. Currently I have a few of them commented out. When I enable them, apache crashes for good. $ cat /usr/local/etc/php/extensions.ini extension=calendar.so extension=ctype.so extension=zlib.so extension=imap.so extension=xml.so extension=exif.so extension=bcmath.so extension=sockets.so #extension=ftp.so extension=mbstring.so extension=mcrypt.so #extension=posix.so extension=dbase.so extension=gettext.so extension=xmlrpc.so extension=simplexml.so extension=session.so extension=pdo.so extension=pdo_sqlite.so extension=hash.so extension=gmp.so extension=gd.so extension=bz2.so #extension=pspell.so extension=openssl.so #extension=pdf.so extension=pcre.so extension=filter.so extension=curl.so extension=fileinfo.so #extension=zip.so extension=mhash.so extension=iconv.so extension=mysql.so extension=spl.so extension=sqlite.so extension=dom.so extension=xmlwriter.so #extension=json.so extension=mysqli.so extension=soap.so extension=tokenizer.so extension=xmlreader.so For example, if I uncomment json.so, apache will crash when restarted. I do not need this extension so I keep it commented out. My question is a bit general. Should I worry about the warning of apache exiting on signal 6? How best to debug it further? Thanks! -- Zbigniew Szalbot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
+pid 48635 (squid), uid 100: exited on signal 6 (core dumped)
I'm seeing 4 Current servers that were running squid with no problems now dumping core with the following error in the log file. +pid 48635 (squid), uid 100: exited on signal 6 (core dumped) I have no idea where to begin looking. I went to the squid list and saw where it was caused by persistent connections on some platforms so I turned them off and there was no change. All the machines are running up to date ports, with kernel and userland no more that a week old and it includes Intel and amd processors. Two boxes have multiple processors so it doesn't seem to be a hardware problem. Any help or suggestions are appreciated. ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
exited on signal 6
Pointed pan2-0.14.2 at a newsgroup with over 750,000 messages. Watching the process in top I see it gets up to 470M and about 425M in core. Have seen the size over 525M. In any case for this particular newsgroup pan core dumps on signal 6. An abort? Where is this signal coming from? Have done nothing to /etc/login.conf, the field is blank in my account so default should be in effect. Default is unlimited. KDE is my window manager. System is an Athlon 800 with 640MB and about 1.7G of swap in 3 partitions and disks. At the time of the core dump only 150MB of swap is being used but there was about 100MB of swap activity in the moments before. The filesystem hosting my account has 63G free. Archive search didn't turn up anything of use but that may be due to my skills at forming a search expression, or limits of the search engine. -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: exited on signal 6
On Friday 16 January 2004 16:55, David Kelly wrote: Have seen the size over 525M. In any case for this particular newsgroup pan core dumps on signal 6. An abort? Where is this signal coming from? From malloc() most probably. Check the value of MAXDSIZ in your kernel config, or use limits -d to find out that the default maximum data size for any process is 512Megs. -- Melvyn === FreeBSD sarevok.idg.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Tue Dec 30 14:31:47 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
Re: exited on signal 6
On Jan 16, 2004, at 10:09 AM, Melvyn Sopacua wrote:
On Friday 16 January 2004 16:55, David Kelly wrote:
Have seen the size over 525M. In any case for this particular
newsgroup
pan core dumps on signal 6. An abort? Where is this signal coming
from?
From malloc() most probably.
Check the value of MAXDSIZ in your kernel config, or use limits -d to
find out
that the default maximum data size for any process is 512Megs.
Sure enough, limits -d says 512M. The core dump was 480M so maybe it
blew up on attempt to allocate a bunch more.
Didn't find any mention of these limits mentioned in
/usr/src/sys/i386/conf/ but
find /usr/src/sys -type f -exec grep -l MAXDSIZ {} \; turned up
/usr/src/sys/conf/NOTES which had more stuff that I had not seen
including examples of how to set the default and the absolute max.
So have launched a build with limits set to 1GB and will see how that
fares.
Thanks!
--
David Kelly N4HHE, [EMAIL PROTECTED]
Whom computers would destroy, they must first drive mad.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
