Re: debugging segmentation fault

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

 



Niltze, deva-



On Sun, Jul 26, 2015 at 9:33 PM, deva seetharam
<tagsense@xxxxxxxxx.invalid> wrote:
> hello
>
> we are running debian linux stable (Jessie) with apache 2.4.10 and mod_wsgi
> 4.3.0-1 on a x86_64 machine.
> our application is written in python 2.7 and django 1.8.
>
> the list of modules as reported by apachectl -M are:
> Loaded Modules:
>  core_module (static)
>  so_module (static)
>  watchdog_module (static)
>  http_module (static)
>  log_config_module (static)
>  logio_module (static)
>  version_module (static)
>  unixd_module (static)
>  access_compat_module (shared)
>  alias_module (shared)
>  auth_basic_module (shared)
>  authn_core_module (shared)
>  authn_file_module (shared)
>  authz_core_module (shared)
>  authz_host_module (shared)
>  authz_user_module (shared)
>  autoindex_module (shared)
>  cgi_module (shared)
>  deflate_module (shared)
>  dir_module (shared)
>  env_module (shared)
>  filter_module (shared)
>  mime_module (shared)
>  mpm_worker_module (shared)
>  negotiation_module (shared)
>  perl_module (shared)
>  rewrite_module (shared)
>  setenvif_module (shared)
>  socache_shmcb_module (shared)
>  status_module (shared)
>  wsgi_module (shared)
>
> we were getting segmentation faults when rest api clients were making
> requests. the apache error log has the following messages:
>
> [Mon Jul 27 09:04:38.375433 2015] [core:notice] [pid 32693:tid
> 140315326191488] AH00052: child pid 32700 exit signal Segmentation fault
> (11)
> [Mon Jul 27 09:04:38.375556 2015] [core:notice] [pid 32693:tid
> 140315326191488] AH00052: child pid 32701 exit signal Segmentation fault
> (11)
>
> i have enabled core dumps by setting ulimit to unlimited and adding core
> dump config directive in the apache2.conf file.
>
> but the core dumps are not happening.
>
> when i tried to debug using gdb (gdb /usr/sbin/apache2), the environment
> variables are not getting read.
>
> any clues on how to go about this? thanks in advance.
>
>
>
>
>

Indeed, the Debian Jessie repos lists apache2 (2.4.10-10) <
https://packages.debian.org/jessie/apache2 >;
however, the current HTTPD (from where debian Apache2 derives) is at
2.4.16 < http://httpd.apache.org/ >

If for whatever reason you don't want to build HTTPD 2.4.16 for
Jessie, I would suggest to use the Debian Stretch Apache2 repo <
https://packages.debian.org/stretch/apache2  > in a test instance to
find out if your seg fault issue disappears.

Good luck!


Best Professional Regards.

-- 
Jose R R
http://metztli.it
---------------------------------------------------------------------------------------------
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
---------------------------------------------------------------------------------------------
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx




[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux