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
Pid1944
Parent pid1
Uid0
Effective uid0
Gid0
Uptime16h 16m
Threads51
Children0
Cpu0.1%
Cpu total0.1%
Memory0.1% [39.6 MB]
Memory total0.1% [39.6 MB]
Security attributeunconfined
Filedescriptors9 [0.9% of 1024 limit]
Total filedescriptors9
Read bytes13.8 kB/s [682.1 MB total]
Disk read bytes0 B/s [13.3 MB total]
Disk read operations49.5 reads/s [2379024 reads total]
Write bytes43.9 kB/s [2.5 GB total]
Disk write bytes2.2 kB/s [330.9 MB total]
Disk write operations11.0 writes/s [658595 writes total]
Unix socket response time0.080 ms to /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT
Unix socket response time0.068 ms to /var/run/fail2ban/fail2ban.sock type TCP protocol DEFAULT
Data collectedFri, 12 Jun 2026 12:52:55
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'