K2LL33D SHELL

 Apache/2.4.7 (Ubuntu)
 Linux sman1baleendah 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64
 uid=33(www-data) gid=33(www-data) groups=33(www-data)
 safemode : OFF
 MySQL: ON | Perl: ON | cURL: OFF | WGet: ON
  >  / usr / share / doc / apache2 /
server ip : 172.67.156.115

your ip : 172.69.214.17

H O M E


Filename/usr/share/doc/apache2/README.backtrace
Size1.18 kb
Permissionrw-r--r--
Ownerroot : root
Create time27-Apr-2025 10:07
Last modified26-Nov-2018 20:08
Last accessed07-Jul-2025 00:05
Actionsedit | rename | delete | download (gzip)
Viewtext | code | image
If apache crashes or freezes, it is helpful if you include a backtrace in the
bug report.



In case of a crash, do the following:

1) Install the packages apache2-dbg libapr1-dbg libaprutil1-dbg gdb.

2) Add "CoreDumpDirectory /var/cache/apache2" to your apache configuration.

3) Execute as root:
/etc/init.d/apache2 stop
ulimit -c unlimited
/etc/init.d/apache2 start

4) Do whatever it takes to reproduce the crash. There should now be the file
/var/cache/apache2/core .

5) If you use a forking MPM (e.g. mod_prefork), execute:

gdb /usr/sbin/apache2 /var/cache/apache2/core
(gdb) bt full
...
(gdb) quit

If you use a threaded mpm (mod_worker, mod_event), execute:

gdb /usr/sbin/apache2 /var/cache/apache2/core
(gdb) thread apply all bt full
...
(gdb) quit

Include the backtrace in the bug report.

6) Undo the change to your configuration, uninstall the debug packages, remove
/var/cache/apache2/core



In case of a hanging process, you don't need a core dump and you can skip steps 2 and 3.

4) Reproduce the problem. Get the pid of a hanging process.

5) Start gdb with

gdb -p pid

and continue as described above. It may also be helpful to include the output of

strace -p pid