* [ISSUE] fail2ban-1.0.2_3 does not start on fresh void installation
@ 2023-12-10 20:22 c0m4r
2023-12-11 6:52 ` [ISSUE] [CLOSED] " sgn
0 siblings, 1 reply; 2+ messages in thread
From: c0m4r @ 2023-12-10 20:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
New issue by c0m4r on void-packages repository
https://github.com/void-linux/void-packages/issues/47682
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.13_1 x86_64 AuthenticAMD/KVM uptodate rF
### Package(s) Affected
fail2ban-1.0.2_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
none
### Expected behaviour
\# /var/log/messages (rsyslogd)
```2023-12-10 21:02:59,080 fail2ban.server [1662]: INFO Starting Fail2ban v1.0.2```
\~$ /usr/sbin/fail2ban-server -V
```1.1.0.1```
### Actual behaviour
\# /var/log/messages (rsyslogd)
```
2023-12-10T20:58:18.883956+01:00 blackhole xbps-install: Installed `python3-pyasyncore-1.0.2_1' successfully (rootdir: /).
2023-12-10T20:58:18.888076+01:00 blackhole xbps-install: Installed `python3-pyasynchat-1.0.2_1' successfully (rootdir: /).
2023-12-10T20:58:18.896471+01:00 blackhole xbps-install: Installed `fail2ban-1.0.2_3' successfully (rootdir: /).
2023-12-10T20:58:38.194494+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:39.196279+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:40.198119+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:41.199980+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:42.202225+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:43.204392+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:44.206706+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:45.208749+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
```
\~$ /usr/bin/fail2ban-server -V
```/usr/bin/fail2ban-server: cannot execute: required file not found```
### Steps to reproduce
1. Void Linux installed from https://repo-default.voidlinux.org/live/current/void-x86_64-ROOTFS-20230628.tar.xz
2. xbps-install -Su xbps
3. xbps-install -u
4. xbps-install fail2ban
---
I was able to workaround this by manually installing fail2ban:
```
git clone https://github.com/fail2ban/fail2ban.git
cd fail2ban
sudo python setup.py install
```
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ISSUE] [CLOSED] fail2ban-1.0.2_3 does not start on fresh void installation
2023-12-10 20:22 [ISSUE] fail2ban-1.0.2_3 does not start on fresh void installation c0m4r
@ 2023-12-11 6:52 ` sgn
0 siblings, 0 replies; 2+ messages in thread
From: sgn @ 2023-12-11 6:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]
Closed issue by c0m4r on void-packages repository
https://github.com/void-linux/void-packages/issues/47682
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.13_1 x86_64 AuthenticAMD/KVM uptodate rF
### Package(s) Affected
fail2ban-1.0.2_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
none
### Expected behaviour
\# /var/log/messages (rsyslogd)
```2023-12-10 21:02:59,080 fail2ban.server [1662]: INFO Starting Fail2ban v1.0.2```
\~$ /usr/sbin/fail2ban-server -V
```1.1.0.1```
### Actual behaviour
\# /var/log/messages (rsyslogd)
```
2023-12-10T20:58:18.883956+01:00 blackhole xbps-install: Installed `python3-pyasyncore-1.0.2_1' successfully (rootdir: /).
2023-12-10T20:58:18.888076+01:00 blackhole xbps-install: Installed `python3-pyasynchat-1.0.2_1' successfully (rootdir: /).
2023-12-10T20:58:18.896471+01:00 blackhole xbps-install: Installed `fail2ban-1.0.2_3' successfully (rootdir: /).
2023-12-10T20:58:38.194494+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:39.196279+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:40.198119+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:41.199980+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:42.202225+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:43.204392+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:44.206706+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
2023-12-10T20:58:45.208749+01:00 blackhole fail2ban: ./run: 5: exec: fail2ban-server: not found
```
\~$ /usr/bin/fail2ban-server -V
```/usr/bin/fail2ban-server: cannot execute: required file not found```
### Steps to reproduce
1. Void Linux installed from https://repo-default.voidlinux.org/live/current/void-x86_64-ROOTFS-20230628.tar.xz
2. xbps-install -Su xbps
3. xbps-install -u
4. xbps-install fail2ban
---
I was able to workaround this by manually installing fail2ban:
```
git clone https://github.com/fail2ban/fail2ban.git
cd fail2ban
sudo python setup.py install
```
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-12-11 6:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-12-10 20:22 [ISSUE] fail2ban-1.0.2_3 does not start on fresh void installation c0m4r
2023-12-11 6:52 ` [ISSUE] [CLOSED] " sgn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).