Just a follow-up on this bug report:
opened 05:51PM - 01 Nov 19 UTC
I noticed in top that `tallow` was consuming 100% of a cpu thread.
A `gdb` at… tach shows its stack as:
```
(gdb) where
#0 0x00007fa3ae02fd4c in ?? () from /usr/lib64/libsystemd.so.0
#1 0x00007fa3ae0301be in ?? () from /usr/lib64/libsystemd.so.0
#2 0x00007fa3ae03e057 in sd_journal_get_data () from /usr/lib64/libsystemd.so.0
#3 0x0000555ba651b775 in ?? ()
#4 0x00007fa3ae1472c3 in __libc_start_main () from /usr/lib64/haswell/libc.so.6
#5 0x0000555ba651baee in ?? ()
```
A continue/stop then showed it as:
```
(gdb) where
#0 0x00007fa3ae0ca578 in ?? () from /usr/lib64/libpcre.so.1
#1 0x00007fa3ae0db08b in pcre_exec () from /usr/lib64/libpcre.so.1
#2 0x0000555ba651b801 in ?? ()
#3 0x00007fa3ae1472c3 in __libc_start_main () from /usr/lib64/haswell/libc.so.6
#4 0x0000555ba651baee in ?? ()
```
The tallow journal looks like:
```
# journalctl -u tallow
-- Logs begin at Thu 2019-10-31 10:18:08 GMT, end at Fri 2019-11-01 17:28:18 GMT. --
Oct 31 13:57:04 skull tallow[216312]: Journal was rotated, resetting
Oct 31 18:00:40 skull systemd[1]: Stopping Tallow Service...
Oct 31 18:00:40 skull systemd[1]: tallow.service: Succeeded.
Oct 31 18:00:40 skull systemd[1]: Stopped Tallow Service.
-- Reboot --
Nov 01 09:53:49 skull systemd[1]: Started Tallow Service.
Nov 01 09:53:49 skull tallow[397]: /usr/share/tallow/sshd.json: 10 patterns
Nov 01 09:53:49 skull tallow[397]: Skipped reading /etc/tallow: No such file or directory
Nov 01 09:53:49 skull tallow[397]: Loaded 10 patterns total
Nov 01 09:53:49 skull tallow[397]: tallow 18 Started
Nov 01 10:06:34 skull tallow[397]: Journal was rotated, resetting
Nov 01 10:46:00 skull systemd[1]: Stopping Tallow Service...
Nov 01 10:46:00 skull systemd[1]: tallow.service: Succeeded.
Nov 01 10:46:00 skull systemd[1]: Stopped Tallow Service.
Nov 01 10:46:00 skull systemd[1]: Started Tallow Service.
Nov 01 10:46:00 skull tallow[134447]: /usr/share/tallow/sshd.json: 10 patterns
Nov 01 10:46:00 skull tallow[134447]: Skipped reading /etc/tallow: No such file or directory
Nov 01 10:46:00 skull tallow[134447]: Loaded 10 patterns total
Nov 01 10:46:00 skull tallow[134447]: tallow 18 Started
Nov 01 14:44:35 skull tallow[134447]: Journal was rotated, resetting
```
The only 'interesting' thing on this machine is that it is running a single node k8s cluster.
The machine is:
```
# cat /etc/os-release
NAME="Clear Linux OS"
VERSION=1
ID=clear-linux-os
ID_LIKE=clear-linux-os
VERSION_ID=31460
PRETTY_NAME="Clear Linux OS"
ANSI_COLOR="1;35"
HOME_URL="https://clearlinux.org"
SUPPORT_URL="https://clearlinux.org"
BUG_REPORT_URL="mailto:dev@lists.clearlinux.org"
PRIVACY_POLICY_URL="http://www.intel.com/privacy"
```
In my case I’m not sure why it would do that, I’m not seeing a very high rate of IP bans in the tallow log, and I had just recently rebooted the server when I noticed the problem.