Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-07-06T08:00:16.991236+00:00
Window starts 2026-07-05T20:00:16.991182+00:00
Uptime
up 7 weeks, 1 day, 22 hours, 47 minutes
Load
1.16 1.09 1.07
Memory
1.5Gi used / 3.8Gi total
Disk /
22G used / 49G total (44% used)
Kernel
6.12.0-124.52.3.el10_1.x86_64
Failed SSH logins
158

Security

SSH activity
Failed logins: 158
Top IPs
  • 202.10.47.135 · 75 hits
  • 116.110.210.97 · 55 hits
Recent auth events
  • Jul 6 02:25:01 srv1675884 sshd-session[2702771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.210.97 user=root
  • Jul 6 02:25:03 srv1675884 sshd-session[2702771]: Failed password for root from 116.110.210.97 port 42032 ssh2
  • Jul 6 02:27:00 srv1675884 sshd-session[2702870]: Invalid user user100 from 116.110.210.97 port 49264
  • Jul 6 02:27:07 srv1675884 sshd-session[2702870]: pam_unix(sshd:auth): check pass; user unknown
  • Jul 6 02:27:07 srv1675884 sshd-session[2702870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.210.97
  • Jul 6 02:27:09 srv1675884 sshd-session[2702870]: Failed password for invalid user user100 from 116.110.210.97 port 49264 ssh2
  • Jul 6 02:27:11 srv1675884 sshd-session[2702816]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.210.97 user=root
  • Jul 6 02:27:14 srv1675884 sshd-session[2702816]: Failed password for root from 116.110.210.97 port 49840 ssh2

Web

HTTP status mix
200: 4400: 2404: 9405: 1
Top IPs
  • 152.89.209.121 · 5 hits
  • 165.245.223.222 · 2 hits
  • 47.76.123.141 · 2 hits
  • 47.238.253.152 · 2 hits
  • 34.76.209.17 · 2 hits
Recent access highlights
  • 116.139.30.25 - - [06/Jul/2026:03:03:51 +0000] "GET / HTTP/1.1" 404 555 "http://77.37.47.24:80" "Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1)" "-"
  • 34.31.31.195 - - [06/Jul/2026:05:11:42 +0000] "\x05\x01\x00" 400 157 "-" "-" "-"
  • 47.76.123.141 - - [06/Jul/2026:05:34:15 +0000] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0;" "-"
  • 47.76.123.141 - - [06/Jul/2026:05:34:15 +0000] "GET /favicon.ico HTTP/1.1" 404 555 "-" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0;" "-"
  • 35.189.245.162 - - [06/Jul/2026:05:42:11 +0000] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36" "-"
  • 34.76.209.17 - - [06/Jul/2026:05:42:52 +0000] "\x16\x03\x00\x00i\x01\x00\x00e\x03\x03U\x1C\xA7\xE4random1random2random3random4\x00\x00\x0C\x00/\x00" 400 157 "-" "-" "-"
  • 34.76.209.17 - - [06/Jul/2026:05:42:52 +0000] "\x16\x03\x00\x00i\x01\x00\x00e\x03\x03U\x1C\xA7\xE4random1random2random3random4\x00\x00\x0C\x00/\x00" 400 157 "-" "-" "-"
  • 34.76.209.17 - - [06/Jul/2026:05:42:52 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"

System

Recent service / journal activity
  • Jul 6 08:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 6 08:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jul 6 08:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 912362.
  • Jul 6 08:00:12 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jul 6 08:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 6 08:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jul 6 08:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 912363.
  • Jul 6 08:00:15 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jul 6 08:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 6 08:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jul 6 06:01:01 srv1675884 CROND[2711204]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 6 06:01:01 srv1675884 run-parts[2711207]: (/etc/cron.hourly) starting 0anacron
  • Jul 6 06:01:01 srv1675884 run-parts[2711213]: (/etc/cron.hourly) finished 0anacron
  • Jul 6 06:01:01 srv1675884 CROND[2711203]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jul 6 07:01:01 srv1675884 CROND[2713502]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 6 07:01:01 srv1675884 run-parts[2713505]: (/etc/cron.hourly) starting 0anacron
  • Jul 6 07:01:01 srv1675884 run-parts[2713511]: (/etc/cron.hourly) finished 0anacron
  • Jul 6 07:01:01 srv1675884 CROND[2713501]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-07-06T05:05:07+0000 DEBUG crb: using metadata from Thu 02 Jul 2026 09:25:20 AM UTC.
  • 2026-07-06T05:05:07+0000 DEBUG reviving: 'extras' can be revived - repomd matches.
  • 2026-07-06T05:05:07+0000 DEBUG extras: using metadata from Thu 02 Jul 2026 09:25:12 AM UTC.
  • 2026-07-06T05:05:08+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-07-06T05:05:11+0000 DEBUG epel: using metadata from Sun 05 Jul 2026 12:35:46 AM UTC.
  • 2026-07-06T05:05:11+0000 INFO Metadata cache created.
  • 2026-07-06T06:37:03+0000 INFO --- logging initialized ---
  • 2026-07-06T06:37:03+0000 INFO Metadata cache refreshed recently.

Highlights

Data sources: /var/log/cron, /var/log/secure, /var/log/messages, /var/log/nginx/access.log, /var/log/dnf.log.