Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-30T20:00:09.910753+00:00
Window starts 2026-06-30T08:00:09.910689+00:00
Uptime
up 6 weeks, 3 days, 10 hours, 47 minutes
Load
1.10 1.06 1.00
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
106

Security

SSH activity
Failed logins: 106
Top IPs
  • 120.79.141.71 · 64 hits
  • 167.233.60.71 · 30 hits
Recent auth events
  • Jun 30 19:11:58 srv1675884 sshd-session[2404344]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.233.60.71 user=root
  • Jun 30 19:12:00 srv1675884 sshd-session[2404344]: Failed password for root from 167.233.60.71 port 41406 ssh2
  • Jun 30 19:14:17 srv1675884 sshd-session[2404437]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.233.60.71 user=root
  • Jun 30 19:14:18 srv1675884 sshd-session[2404437]: Failed password for root from 167.233.60.71 port 48452 ssh2
  • Jun 30 19:16:39 srv1675884 sshd-session[2404536]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.233.60.71 user=root
  • Jun 30 19:16:42 srv1675884 sshd-session[2404536]: Failed password for root from 167.233.60.71 port 35956 ssh2
  • Jun 30 19:19:07 srv1675884 sshd-session[2404633]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.233.60.71 user=root
  • Jun 30 19:19:08 srv1675884 sshd-session[2404633]: Failed password for root from 167.233.60.71 port 60528 ssh2

Web

HTTP status mix
200: 67400: 1404: 17
Top IPs
  • 136.66.151.214 · 30 hits
  • 216.73.216.111 · 20 hits
  • 34.62.103.217 · 9 hits
  • 34.155.75.24 · 5 hits
  • 35.195.60.93 · 5 hits
Recent access highlights
  • 34.62.103.217 - - [30/Jun/2026:09:02:11 +0000] "OPTIONS / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"
  • 2a06:4884:d000::ec - - [30/Jun/2026:11:24:42 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; InternetMeasurement/1.0; +https://internet-measurement.com/)" "-"
  • 168.144.147.26 - - [30/Jun/2026:13:23:15 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0" "-"
  • 168.144.147.26 - - [30/Jun/2026:13:23:16 +0000] "GET /favicon.ico HTTP/1.1" 404 153 "http://77.37.47.24/" "Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0" "-"
  • 5.89.48.92 - - [30/Jun/2026:14:11:30 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"
  • 206.81.31.86 - - [30/Jun/2026:15:57:18 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"
  • 66.249.79.4 - - [30/Jun/2026:16:03:41 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"
  • 146.70.179.198 - - [30/Jun/2026:16:32:23 +0000] "GET / HTTP/1.1" 404 153 "-" "Apache-HttpClient/4.5.13 (Java/17.0.17-internal)" "-"

System

Recent service / journal activity
  • Jun 30 20:00:02 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 30 20:00:02 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 30 20:00:06 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 766291.
  • Jun 30 20:00:06 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 30 20:00:06 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 30 20:00:06 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 30 20:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 766292.
  • Jun 30 20:00:09 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 30 20:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 30 20:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jun 30 18:01:01 srv1675884 CROND[2401260]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 30 18:01:01 srv1675884 run-parts[2401263]: (/etc/cron.hourly) starting 0anacron
  • Jun 30 18:01:01 srv1675884 run-parts[2401269]: (/etc/cron.hourly) finished 0anacron
  • Jun 30 18:01:01 srv1675884 CROND[2401259]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 30 19:01:02 srv1675884 CROND[2403904]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 30 19:01:02 srv1675884 run-parts[2403907]: (/etc/cron.hourly) starting 0anacron
  • Jun 30 19:01:02 srv1675884 run-parts[2403913]: (/etc/cron.hourly) finished 0anacron
  • Jun 30 19:01:02 srv1675884 CROND[2403903]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-30T18:25:07+0000 DEBUG baseos: using metadata from Tue 30 Jun 2026 03:38:21 PM UTC.
  • 2026-06-30T18:25:08+0000 DEBUG reviving: failed for 'crb', mismatched repomd.
  • 2026-06-30T18:25:09+0000 DEBUG crb: using metadata from Tue 30 Jun 2026 03:38:53 PM UTC.
  • 2026-06-30T18:25:10+0000 DEBUG reviving: failed for 'extras', mismatched repomd.
  • 2026-06-30T18:25:10+0000 DEBUG extras: using metadata from Tue 30 Jun 2026 03:38:45 PM UTC.
  • 2026-06-30T18:25:11+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-30T18:25:14+0000 DEBUG epel: using metadata from Tue 30 Jun 2026 01:27:40 AM UTC.
  • 2026-06-30T18:25:17+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.