Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-07-03T20:00:19.299574+00:00
Window starts 2026-07-03T08:00:19.299540+00:00
Uptime
up 6 weeks, 6 days, 10 hours, 47 minutes
Load
1.15 1.10 1.09
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
189

Security

SSH activity
Failed logins: 189
Top IPs
  • 116.99.171.144 · 86 hits
  • 116.99.175.122 · 60 hits
Recent auth events
  • Jul 3 19:57:09 srv1675884 sshd-session[2575757]: Invalid user user1 from 116.99.175.122 port 33444
  • Jul 3 19:57:09 srv1675884 sshd-session[2575757]: pam_unix(sshd:auth): check pass; user unknown
  • Jul 3 19:57:09 srv1675884 sshd-session[2575757]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.175.122
  • Jul 3 19:57:12 srv1675884 sshd-session[2575757]: Failed password for invalid user user1 from 116.99.175.122 port 33444 ssh2
  • Jul 3 19:59:10 srv1675884 sshd-session[2575834]: Invalid user db2inst2 from 116.99.171.144 port 48036
  • Jul 3 19:59:10 srv1675884 sshd-session[2575834]: pam_unix(sshd:auth): check pass; user unknown
  • Jul 3 19:59:10 srv1675884 sshd-session[2575834]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.171.144
  • Jul 3 19:59:13 srv1675884 sshd-session[2575834]: Failed password for invalid user db2inst2 from 116.99.171.144 port 48036 ssh2

Web

HTTP status mix
200: 28301: 2400: 3404: 10
Top IPs
  • 216.73.217.87 · 20 hits
  • 69.55.61.114 · 4 hits
  • 107.150.97.4 · 3 hits
  • 137.184.64.244 · 2 hits
  • 34.31.31.195 · 2 hits
Recent access highlights
  • 2a06:4883:3000::32 - - [03/Jul/2026:14:40:30 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; InternetMeasurement/1.0; +https://internet-measurement.com/)" "-"
  • 154.242.137.250 - - [03/Jul/2026:15:08:39 +0000] "POST /HNAP1/ HTTP/1.0" 404 153 "-" "-" "-"
  • 189.121.109.193 - - [03/Jul/2026:15:30:04 +0000] "SSH-2.0-PuTTY_Release_0.79" 400 157 "-" "-" "-"
  • 103.24.95.51 - - [03/Jul/2026:17:22:33 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 18_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.5 Mobile/15E148 Safari/604.1" "-"
  • 107.150.97.4 - - [03/Jul/2026:17:25:33 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0" "-"
  • 107.150.97.4 - - [03/Jul/2026:17:25:35 +0000] "GET /favicon.ico HTTP/1.1" 404 153 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:120.0) Gecko/20100101 Firefox/120.0" "-"
  • 107.150.97.4 - - [03/Jul/2026:17:33:02 +0000] "GET /favicon.ico HTTP/1.1" 404 555 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36" "-"
  • 3.250.241.142 - - [03/Jul/2026:17:55:19 +0000] "HEAD / HTTP/1.0" 404 0 "-" "Mozilla/5.0 (compatible; NetcraftSurveyAgent/1.0; +info@netcraft.com)" "-"

System

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

Maintenance

Cron
  • Jul 3 18:01:01 srv1675884 CROND[2571073]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 3 18:01:01 srv1675884 run-parts[2571076]: (/etc/cron.hourly) starting 0anacron
  • Jul 3 18:01:01 srv1675884 run-parts[2571082]: (/etc/cron.hourly) finished 0anacron
  • Jul 3 18:01:01 srv1675884 CROND[2571072]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jul 3 19:01:01 srv1675884 CROND[2573391]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 3 19:01:01 srv1675884 run-parts[2573394]: (/etc/cron.hourly) starting 0anacron
  • Jul 3 19:01:01 srv1675884 run-parts[2573400]: (/etc/cron.hourly) finished 0anacron
  • Jul 3 19:01:01 srv1675884 CROND[2573390]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-07-03T18:42:51+0000 DEBUG baseos: using metadata from Thu 02 Jul 2026 09:24:54 AM UTC.
  • 2026-07-03T18:42:52+0000 DEBUG reviving: 'crb' can be revived - repomd matches.
  • 2026-07-03T18:42:52+0000 DEBUG crb: using metadata from Thu 02 Jul 2026 09:25:20 AM UTC.
  • 2026-07-03T18:42:53+0000 DEBUG reviving: 'extras' can be revived - repomd matches.
  • 2026-07-03T18:42:53+0000 DEBUG extras: using metadata from Thu 02 Jul 2026 09:25:12 AM UTC.
  • 2026-07-03T18:42:53+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-07-03T18:42:55+0000 DEBUG epel: using metadata from Fri 03 Jul 2026 12:35:56 AM UTC.
  • 2026-07-03T18:42:55+0000 INFO Metadata cache created.

Highlights

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