Process status

ParameterValue
Namefail2ban
Pid file/run/fail2ban/fail2ban.pid
StatusOK
Groupservices
Monitoring statusMonitored
Monitoring modeactive
On rebootstart
Start program'/bin/systemctl start fail2ban' timeout 2 m
Stop program'/bin/systemctl stop fail2ban' timeout 2 m
Pid2228604
Parent pid1
Uid0
Effective uid0
Gid0
Uptime3d 16h 26m
Threads59
Children0
Cpu0.1%
Cpu total0.1%
Memory0.1% [42.7 MB]
Memory total0.1% [42.7 MB]
Security attributeunconfined
Filedescriptors9 [0.9% of 1024 limit]
Total filedescriptors9
Read bytes15.7 kB/s [5.4 GB total]
Disk read bytes0 B/s [3.0 MB total]
Disk read operations49.0 reads/s [18449869 reads total]
Write bytes66.6 kB/s [19.0 GB total]
Disk write bytes10.1 kB/s [2.8 GB total]
Disk write operations16.7 writes/s [5133422 writes total]
Unix socket response time0.080 ms to /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT
Unix socket response time0.052 ms to /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT
Data collectedTue, 11 Aug 2026 02:34:49
TimeoutIf restarted 5 times within 5 cycle(s) then unmonitor
ExistenceIf doesn't exist then restart
Unix SocketIf failed /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT with timeout 5 s for 6 cycles then restart
Unix SocketIf failed /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT with timeout 5 s for 3 cycles then exec '/usr/bin/fail2ban-client reload'