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
Pid3189
Parent pid1
Uid0
Effective uid0
Gid0
Uptime9d 15h 21m
Threads59
Children0
Cpu0.1%
Cpu total0.1%
Memory0.1% [45.4 MB]
Memory total0.1% [45.4 MB]
Security attributeunconfined
Filedescriptors9 [0.9% of 1024 limit]
Total filedescriptors9
Read bytes13.3 kB/s [14.1 GB total]
Disk read bytes0 B/s [24.9 MB total]
Disk read operations40.3 reads/s [49506467 reads total]
Write bytes59.4 kB/s [47.1 GB total]
Disk write bytes9.8 kB/s [7.1 GB total]
Disk write operations14.9 writes/s [12608806 writes total]
Unix socket response time0.083 ms to /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT
Unix socket response time0.050 ms to /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT
Data collectedSun, 11 Oct 2026 02:42:20
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'