Skip to content
This repository has been archived by the owner on May 3, 2020. It is now read-only.

Bug : fail2ban status on systemd OSs #4

Closed
nocternology opened this issue Sep 20, 2015 · 2 comments
Closed

Bug : fail2ban status on systemd OSs #4

nocternology opened this issue Sep 20, 2015 · 2 comments
Labels

Comments

@nocternology
Copy link
Contributor

Hi there,

I just tried the dashboard, and i had a strange bug : when launching the webserver and going to localhost:5000, i get a :

UnicodeDecodeError
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)

I tracked down the problem to the variable status before the rendering of the homepage (line 32 of home.py), and i think it comes from the fact that on systemd OSs, the "service" command is translated to "systemctl" command; with systemctl, the output is this :

screenshot_2015-09-20_22-44-58

it has the little green led to indicate that the service is up, and that cannot be parsed by Jinja.

I will try to fix this problem and give a PR to make the fail2ban status checking more universal.

@oussemos
Copy link
Owner

Hi @nocternology, this tool was developed with Debian Wheezy (based on sysvinit) and wasn't tested with systemd.
Thanks and i'm waiting for your fix 👍 :)

@oussemos
Copy link
Owner

Good fix @nocternology 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants