Hi James.
At this time, with the latest build of Apache as mentioned in my last
post, I'm not seeing this issue any more. I'll open a new issue if I do
see it again.
Cheers,
Paul.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop):
Public bug reported:
Binary package hint: apache2
Expected behaviour: no problems, Apache to serve web pages for the
college's VLE.
Actual behaviour: very slow serving pages for ~30 seconds,
/var/log/apache2/error.log shows:
*** glibc detected *** /usr/sbin/apache2: double free or corruption
** Attachment added: Apache 2 error log entry relating to the glibc crash
https://bugs.launchpad.net/bugs/675965/+attachment/1735170/+files/log.log
--
Apache crashes with glibc detected and stack trace
https://bugs.launchpad.net/bugs/675965
You received this bug notification because you are
Hi Mathias.
You are correct, the server runs PHP scripts, but as part of the open
source VLE Moodle: http://moodle.org/
Moodle is a complex application and I would have no idea what aspect of
it might have caused apache to crash. I develop code for Moodle, but
plugins only, I have little to do
In Apache's error.log, the error happened at some point between 10:00:39
and 10:01:18, so I have included a much-reduced access.log with all PHP
files executed between those time points on that day, appropriately
sanitised. Hopefully it will prove useful.
** Attachment added: Apache access.log
It may be worth mentioning that I filed a very similar bug to this one
within the last month or so, but as it was closed as 'cannot reproduce'
or similar and I cannot locate it to link to. It definitely had 'glibc'
in the title of the report.
--
Apache crashes with glibc detected and stack trace
Public bug reported:
Binary package hint: apache2
Expected: no errors.
Actual: Maybe crashes isn't quite the right phrase, as the server itself
is still servings pages, however we've seen the below error and
backtrace regularly since we upgraded our server and once Apache stopped
responding.
** Attachment added: Bug as found in /var/log/apache2/error.log
https://bugs.launchpad.net/bugs/651134/+attachment/1653329/+files/apache2_glibc_error.txt
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
Have run apport-collect on the server via a remote ssh session but
despite trying to sign in with my email address and password (good text
interface by the way), the continue text is inactive. I can get a
forgotten password, create a new account or cancel (all work) but I
cannot continue.
Have
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: apache2
Expected: no errors.
Actual: Maybe crashes isn't quite the right phrase, as the server itself
is still servings pages, however we've seen the below error and
backtrace
Got around the issue by using the solution found here:
https://bugs.launchpad.net/launchpad-foundations/+bug/556927
apport-collect report sent successfully.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
Followed the instructions on DebuggingProgramCrash as far as:
$ sudo apt-get install apache2.2-bin-dbgsym
Received:
The following packages have unmet dependencies.
apache2.2-bin-dbgsym: Depends: apache2.2-bin (= 2.2.14-5ubuntu8.3) but
2.2.14-5ubuntu8 is to be installed
E: Broken packages
I have just realised that having updated/upgraded, I may have 1. solved
the problem (you never know) and 2. I may have now changed the version
numbers of key apps and libraries as reported earlier.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption
Thanks for the above, it worked successfully.
I will keep a close eye on Apache today (a normal day's use, basically)
and report back.
Regards.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
After approximately 2 days of normal use, the error has not reoccurred
(whereas normally we'd see it approximately 3-5 times in a 24 hour
period).
I guess we can consider this issue 'gone'.
Cheers.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption
I spoke too soon. 21 of the 'glibc detected' reports in the Apache error
log. Please see attached. I'll work on the backtrace this afternoon.
** Attachment added: Indications of the error (again) from
/var/log/apache2/error.log
I have gdb running on the server, but as I have no idea what causes the
error I'll just watch Apache's error log until I see it print out the
backtrace and memory map.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
Hi Christine.
Since upgrading Apache to 2.2.14-5ubuntu8.2 we haven't seen this issue
resurface in over a week. I've also noticed that 2.2.14-5ubuntu8.3 is
available so may tentatively upgrade to that. I hope that's of some use.
Paul.
--
apache crashes with *** glibc detected ***
Hi Christine.
Since upgrading Apache to 2.2.14-5ubuntu8.2 we haven't seen this issue
resurface in over a week. I've also noticed that 2.2.14-5ubuntu8.3 is
available so may tentatively upgrade to that. I hope that's of some use.
Paul.
--
apache crashes with *** glibc detected ***
Hi James.
At this time, with the latest build of Apache as mentioned in my last
post, I'm not seeing this issue any more. I'll open a new issue if I do
see it again.
Cheers,
Paul.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop):
Public bug reported:
Binary package hint: apache2
Expected behaviour: no problems, Apache to serve web pages for the
college's VLE.
Actual behaviour: very slow serving pages for ~30 seconds,
/var/log/apache2/error.log shows:
*** glibc detected *** /usr/sbin/apache2: double free or corruption
** Attachment added: Apache 2 error log entry relating to the glibc crash
https://bugs.launchpad.net/bugs/675965/+attachment/1735170/+files/log.log
--
Apache crashes with glibc detected and stack trace
https://bugs.launchpad.net/bugs/675965
You received this bug notification because you are
Hi Mathias.
You are correct, the server runs PHP scripts, but as part of the open
source VLE Moodle: http://moodle.org/
Moodle is a complex application and I would have no idea what aspect of
it might have caused apache to crash. I develop code for Moodle, but
plugins only, I have little to do
In Apache's error.log, the error happened at some point between 10:00:39
and 10:01:18, so I have included a much-reduced access.log with all PHP
files executed between those time points on that day, appropriately
sanitised. Hopefully it will prove useful.
** Attachment added: Apache access.log
It may be worth mentioning that I filed a very similar bug to this one
within the last month or so, but as it was closed as 'cannot reproduce'
or similar and I cannot locate it to link to. It definitely had 'glibc'
in the title of the report.
--
Apache crashes with glibc detected and stack trace
Public bug reported:
Binary package hint: apache2
Expected: no errors.
Actual: Maybe crashes isn't quite the right phrase, as the server itself
is still servings pages, however we've seen the below error and
backtrace regularly since we upgraded our server and once Apache stopped
responding.
** Attachment added: Bug as found in /var/log/apache2/error.log
https://bugs.launchpad.net/bugs/651134/+attachment/1653329/+files/apache2_glibc_error.txt
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
Have run apport-collect on the server via a remote ssh session but
despite trying to sign in with my email address and password (good text
interface by the way), the continue text is inactive. I can get a
forgotten password, create a new account or cancel (all work) but I
cannot continue.
Have
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: apache2
Expected: no errors.
Actual: Maybe crashes isn't quite the right phrase, as the server itself
is still servings pages, however we've seen the below error and
backtrace
Got around the issue by using the solution found here:
https://bugs.launchpad.net/launchpad-foundations/+bug/556927
apport-collect report sent successfully.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
After approximately 2 days of normal use, the error has not reoccurred
(whereas normally we'd see it approximately 3-5 times in a 24 hour
period).
I guess we can consider this issue 'gone'.
Cheers.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption
I spoke too soon. 21 of the 'glibc detected' reports in the Apache error
log. Please see attached. I'll work on the backtrace this afternoon.
** Attachment added: Indications of the error (again) from
/var/log/apache2/error.log
I have gdb running on the server, but as I have no idea what causes the
error I'll just watch Apache's error log until I see it print out the
backtrace and memory map.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
Followed the instructions on DebuggingProgramCrash as far as:
$ sudo apt-get install apache2.2-bin-dbgsym
Received:
The following packages have unmet dependencies.
apache2.2-bin-dbgsym: Depends: apache2.2-bin (= 2.2.14-5ubuntu8.3) but
2.2.14-5ubuntu8 is to be installed
E: Broken packages
I have just realised that having updated/upgraded, I may have 1. solved
the problem (you never know) and 2. I may have now changed the version
numbers of key apps and libraries as reported earlier.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption
Thanks for the above, it worked successfully.
I will keep a close eye on Apache today (a normal day's use, basically)
and report back.
Regards.
--
apache crashes with *** glibc detected *** /usr/sbin/apache2: double free or
corruption (fasttop): 0x7f8b5c8fdac0 ***
Public bug reported:
Was using Chromium as a second browser when it closed down unexpectedly.
Restarting the browser results in a brief flicker as the browser starts
up and then immediately closes again.
Steps to reproduce the problem:
1. Go to this web page:
I got this error after installing nginx on a system that already had
Apache2 running on port 80. When I changed the nginx default site config
to run on an unused port, it started up just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
38 matches
Mail list logo
