profile
viewpoint
Plamen Vasilev PVasileff BGDNS Sofia, Bulgaria https://bgdns.eu

PVasileff/ABVNet-cyrillic-seenserv 0

Atheme + patch for cyrillic nicks and SeenServ module

PVasileff/BGDNS 0

BGDNS

PVasileff/bluetooth-lock 0

Lock/unlock computer based on proximity of bluetooth device

PVasileff/check_smart 0

Monitoring Plugin to check hard drives, solid state drives and NVMe drives using SMART

PVasileff/dhcp_failover 0

k-level DHCP failover scripts that work with keepalived

PVasileff/ispconfig3_roundcube 0

ISPConfig3 Plugins for Roundcube

PVasileff/librenms-agent 0

LibreNMS Agent & Scripts

PVasileff/main-nagios-plugins 0

Main collection of nagios checks

PVasileff/mysql4.1.22 0

Instructions on installation MySQL 4.1.22 on CentOS 6 / 7

PR opened librenms/librenms-agent

fix occasionally random ordering for fail2ban

If

    $j->canonical(1);

need another changes, please fix that. I get this from: https://github.com/librenms/librenms-agent/pull/240

+1 -1

0 comment

1 changed file

pr created time in 6 days

push eventPVasileff/librenms-agent

Plamen Vasilev

commit sha ce48efcc18a6727fbdceb1fa04d6c0510c2814c5

fix occasionally random ordering for fail2ban If $j->canonical(1); need another changes, please fix that. I get this from: https://github.com/librenms/librenms-agent/pull/240

view details

push time in 6 days

fork PVasileff/librenms-agent

LibreNMS Agent & Scripts

fork in 6 days

issue closedlibrenms/librenms-agent

fail2ban: output data format wrong on RPI4

I've open that because ISSUE 283 is closed.

I have configured librenms to monitoring few servers. On two of them I have installed fail2ban and configured that snmp extend. On VM with Debian 11 and on rasberry pi 4 with rasbian 11.

I have installed libjson-perl and configured on both server on snmpd.conf:

extend fail2ban '/usr/bin/sudo /opt/snmp/fail2ban -c -U -f /usr/local/bin/fail2ban-client'

and in /etc/sudoers:

Debian-snmp ALL = NOPASSWD: /opt/snmp/fail2ban

When I have run with root on cli:

sudo -u Debian-snmp /usr/bin/sudo /opt/snmp/fail2ban -c -U -f /usr/local/bin/fail2ban-client

on VM with Debian 11 - reported:

{"data":{"jails":{"nginx-forbidden":"0","ssh":"206"},"total":206},"error":"0","errorString":"fail2ban-client exited with 0","version":"1"} on RPI 4 with Rasbian - reported:

{"data":{"jails":{"openvpn":"0","ssh":"0"},"total":0},"error":"0","errorString":"fail2ban-client exited with 0","version":"1"}

BUT on librenms graphs for VM with Debian 11:

  • graphs are OK

Debian 11 Graphs

debian11

On RPI 4 - with rasbian 11 - NOT:

RPI4

rpi4

Any Ideas how to fix that on RPI 4?

closed time in 6 days

PVasileff

issue commentlibrenms/librenms-agent

fail2ban: output data format wrong on RPI4

Problem solved.

On RPI4 when I run Capture - Poller - I see:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:

Fixed with:

export LANG="en_US.UTF-8"
export LANGUAGE="en_US.UTF-8"
export LC_CTYPE="en_US.UTF-8"
export LC_NUMERIC="en_US.UTF-8"
export LC_TIME="en_US.UTF-8"
export LC_COLLATE="en_US.UTF-8"
export LC_MONETARY="en_US.UTF-8"
export LC_MESSAGES="en_US.UTF-8"
export LC_PAPER="en_US.UTF-8"
export LC_NAME="en_US.UTF-8"
export LC_ADDRESS="en_US.UTF-8"
export LC_TELEPHONE="en_US.UTF-8"
export LC_MEASUREMENT="en_US.UTF-8"
export LC_IDENTIFICATION="en_US.UTF-8"

and in /etc/locale.gen just enabled:

en_US.UTF-8 UTF-8 and then run:

locale-gen; reboot

PVasileff

comment created time in 6 days

issue commentlibrenms/librenms-agent

fail2ban: output data format wrong

I have configured librenms to monitoring few servers. On two of them I have installed fail2ban and configured that snmp extend. On VM with Debian 11 and on rasberry pi 4 with rasbian 11.

I have installed libjson-perl and configured on both server on snmpd.conf:

extend fail2ban '/usr/bin/sudo /opt/snmp/fail2ban -c -U -f /usr/local/bin/fail2ban-client'

and in /etc/sudoers:

Debian-snmp ALL = NOPASSWD: /opt/snmp/fail2ban

When I have run with root on cli:

sudo -u Debian-snmp /usr/bin/sudo /opt/snmp/fail2ban -c -U -f /usr/local/bin/fail2ban-client

on VM with Debian 11 - reported:

{"data":{"jails":{"nginx-forbidden":"0","ssh":"206"},"total":206},"error":"0","errorString":"fail2ban-client exited with 0","version":"1"} on RPI 4 with Rasbian - reported:

{"data":{"jails":{"openvpn":"0","ssh":"0"},"total":0},"error":"0","errorString":"fail2ban-client exited with 0","version":"1"}

BUT on librenms graphs for VM with Debian 11 - graphs are OK

Debian 11 Graphs RPI4

Any Ideas how to fix that on RPI 4?

markuspachali

comment created time in 7 days

issue commentlibrenms/librenms

Missing graphics and problem with daily.sh

As additional information, after I dist-upgrade from debian 10 to 11 rrdcached is missing. I have installed again, and copy original /etc/default/rrdcached to another place, and put on it:

DAEMON=/usr/bin/rrdcached
WRITE_TIMEOUT=1800
WRITE_JITTER=1800
WRITE_THREADS=4
BASE_PATH=/opt/librenms/rrd/
JOURNAL_PATH=/var/lib/rrdcached/journal/
PIDFILE=/var/run/rrdcached.pid
SOCKFILE=/run/rrdcached.sock
SOCKGROUP=librenms
DAEMON_GROUP=librenms
DAEMON_USER=librenms
BASE_OPTIONS="-B -F -R"

chown librenms:librenms /var/lib/rrdcached/journal/

and

systemctl restart rrdcached.service Process is running but graphics not shown..

PVasileff

comment created time in 2 months

issue openedlibrenms/librenms

Missing graphics and problem with daily.sh

The problem

Graphics not shown correctly in my installation.

Using Debian 11 x64:

$ uname -a
Linux nms 5.10.0-8-amd64 #1 SMP Debian 5.10.46-5 (2021-09-23) x86_64 GNU/Linux

RRDTool is installed:

dpkg --list |grep rrdtool
ii  rrdtool                           1.7.2-3+b7                                                               amd64        time-series data storage and display system (programs)

but /var/run/rrdcached.sock is missing.

After I run daily.sh I see:

su - librenms
librenms@nms:~$ ./daily.sh 



Updating to latest codebase                       ./daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
./daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
./daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK


Updating Composer packages                        /opt/librenms/daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK
Updating SQL-Schema                               /opt/librenms/daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK
Updating submodules                               /opt/librenms/daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK
Cleaning up DB                                    /opt/librenms/daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK
Fetching notifications                            /opt/librenms/daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK
Caching PeeringDB data                            /opt/librenms/daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK
Caching Mac OUI data                              /opt/librenms/daily.sh: line 62: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 65: 
/opt/librenms/logs/daily.log: No such file or directory
/opt/librenms/daily.sh: line 66: 
/opt/librenms/logs/daily.log: No such file or directory
 OK
$ ls -lah /opt/librenms/logs/daily.log 
-rw-rw-r-- 1 librenms librenms 0 Sep 27 17:33 /opt/librenms/logs/daily.log

Output of ./validate.php

$ ./validate.php
====================================
Component | Version
--------- | -------
LibreNMS  | 21.9.0-24-gb934d0c92
DB Schema | 2021_08_26_093522_config_value_to_medium_text (217)
PHP       | 7.4.24
Python    | 3.9.2
MySQL     | 10.5.11-MariaDB-1
RRDTool   | 1.7.2
SNMP      | NET-SNMP 5.9
====================================

[OK]    Composer Version: 2.1.8
[OK]    Dependencies up-to-date.

[OK]    Database connection successful
[OK]    Database schema correct

What was the last working version of LibreNMS?

No response

Anything in the logs that might be useful for us?

No response

created time in 2 months

issue openedfail2ban/fail2ban

[BR]: ERROR: No module named 'ConfigParser'

Environment:

fail2ban version:master os:debian11.0 platform:amd64 python:3.9.2

The issue:

Sep 26 18:34:57 mail fail2ban-server[8335]: ERROR: No module named 'ConfigParser'

Steps to reproduce

git clone https://github.com/fail2ban/fail2ban.git /opt/fail2ban cd /opt/fail2ban python setup.py install

When I run python setup install I see:

byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/filtertestcase.py to filtertestcase.cpython-39.pyc
  File "/usr/local/lib/python3.9/dist-packages/fail2ban/tests/filtertestcase.py", line 1715
                                   % m for m in 53, 54, 57, 58])
                                                  ^
SyntaxError: invalid syntax

byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/utils.py to utils.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/action_d/__init__.py to __init__.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/action_d/test_smtp.py to test_smtp.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/__init__.py to __init__.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/datedetectortestcase.py to datedetectortestcase.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/dummyjail.py to dummyjail.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/failmanagertestcase.py to failmanagertestcase.cpython-39.pyc
byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/tests/misctestcase.py to misctestcase.cpython-39.pyc
  File "/usr/local/lib/python3.9/dist-packages/fail2ban/tests/misctestcase.py", line 265
                                print deep_function(3)
                                      ^
SyntaxError: invalid syntax

byte-compiling /usr/local/lib/python3.9/dist-packages/fail2ban/server/ipdns.py to ipdns.cpython-39.pyc
  File "/usr/local/lib/python3.9/dist-packages/fail2ban/server/ipdns.py", line 333
                                        mask = ~(0xFFFFFFFFL >> cidr)
                                                           ^
SyntaxError: invalid syntax

When I run manualy:

/usr/local/bin/fail2ban-server -xf start

I see:

ERROR: No module named 'ConfigParser'

created time in 2 months

more