monitorix-general — Help and general discussion

[Monitorix-general] Monitorix 3.16.0 released

[Jordi S. <jo...@fi...>]

Monitorix 3.16.0 has been released!

This Monitorix version comes with small changes and just a few fixes. 
The mature of this tool and mainly my lack of spare time to include new 
features resulted in a short list of changes.

The most noticeable change in this version is the new size of the 
graphs. Until now the option global_zoom was set to 1, which meant 100%. 
Now it is set to 1.5 which means 150%. As a result, all graphs are 50% 
bigger than before.

The rest of new features, changes and bugs fixed are, as always, 
reflected in the Changes file.

Please, check the monitorix.conf(5) man page for all the details.

NOTICE: The configuration file monitorix.conf has been extended with 
important changes.

All users still using older versions are encouraged to upgrade to this 
version.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

[Monitorix-general] :Trouble with disk monitor

[Ken M. <kma...@gm...>]

I just installed Monitorix on Ubuntu 23.04. The install with the default 
config worked fine, and the graphs look ok. However, my immediate 
motivation is disk temperature, so I enabled disk in the config file and 
restarted the service.


Now I get

ERROR: while graphing /var/lib/monitorix/www//imgs/disk01.1day.png: 
opening '/var/lib/monitorix/disk.rrd': No such file or directory ERROR: 
while graphing /var/lib/monitorix/www//imgs/disk01z.1day.png: opening 
'/var/lib/monitorix/disk.rrd': No such file or direct

How do I fix this?

By the way I know that the disk temperature is not available using 
sensors or hddtemp, it is available by smartctl which is installed. 
Don't know if thats related to the failure.

(This may be a repost, I just realized the first time I didn't use the 
email address I subscribed with)

[Monitorix-general] Monitorix 3.15.0 released

[Jordi S. <jo...@fi...>]

Monitorix 3.15.0 has been released!

This new version introduces two new modules: intelrapl.pm, for 
monitoring the power consumption of Intel-RAPL capable devices, and 
amdenergy.pm to monitor also AMD CPU power consumption.

Another important change in this new version is the total rewrite of 
serv.pm. Its configuration has also changed completely and now it allows 
a lot of customization. The default configuration should give the same 
results as with the previous version, although the graph layout will 
change. The only service that will be affected is Samba. This service 
needs a complex parsing to get the current Samba use and that's the 
reason why you need an external script to deal with it.

Due to massive change in serv.pm, the following options: secure_log, 
imap_log, hylafax_log, cups_log and cg_logdir have been deprecated and 
will be removed in the next Monitorix version.

The rest of new features, changes and bugs fixed are, as always, 
reflected in the Changes file.

Please, check the monitorix.conf(5) man page for all the details.

NOTICE: The configuration file monitorix.conf has been extended with 
important changes.

All users still using older versions are encouraged to upgrade to this 
version.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

Re: [Monitorix-general] Strange output and I have no clue

[Jordi S. <jo...@fi...>]

Hi,


On 7/7/22 11:52, lut...@gm... wrote:
> I am on my way to set up monitorix and something in the configuration is broken.  In the Mail Graph it shows
> 
> http://10.211.103.131:8080/monitorix-cgi/%3Cbr and then to the right the graphics for greylisting.  So you can read the link which does not work.  This should be the link to greylisting and should not be visible and should not contain the "<br" at the end.

I've copied the whole <mail> section from your configuration file and I 
don't see such error. All graphs are shown, with no data of course, but 
the graphs look fine.



> When I set fs=n everything is fine again.  When I delete my second bind entry, everything is ok.  When I set net and netstat to n, everything is ok again.
> 
> As far as I can see it is only this one Mail link that gets destroyed.  And I cannot find why.  Ok, the configuration is not complete but I cannot find the error in the config file.  Maybe more eyes are able to see what's wrong.
> 

This is really strange. I was unable to compare your configuration file 
because it has converted all tabs to spaces. Maybe you can send it again 
as an attachment?

What Monitorix version are you using?
What RRDtool version are you using?
What's your OS, and how did you install Monitorix?

Also, you might want to check in the log file to see if there are some 
error messages.

Regards.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

[Monitorix-general] Strange output and I have no clue

[<lut...@gm...>]

Hi,

could anyone please help.

I am on my way to set up monitorix and something in the configuration is broken.  In the Mail Graph it shows

http://10.211.103.131:8080/monitorix-cgi/%3Cbr and then to the right the graphics for greylisting.  So you can read the link which does not work.  This should be the link to greylisting and should not be visible and should not contain the "<br" at the end.

When I set fs=n everything is fine again.  When I delete my second bind entry, everything is ok.  When I set net and netstat to n, everything is ok again.

As far as I can see it is only this one Mail link that gets destroyed.  And I cannot find why.  Ok, the configuration is not complete but I cannot find the error in the config file.  Maybe more eyes are able to see what's wrong.

I thnak you very much.

-lutzn



# Monitorix - configuration file
#
# See monitorix.conf(5) manpage for a detailed description of each option.
#

title = MONITORIX - memox
hostname = memox
theme_color = black
refresh_rate = 150
iface_mode = graph
enable_zoom = y
netstats_in_bps = n
disable_javascript_void = n
temperature_scale = c
show_gaps = n
global_zoom = 1
max_historic_years = 1
accept_selfsigned_certs = y
image_format = PNG
enable_parallelizing = y
include_dir = /etc/monitorix/conf.d

ipv6_disabled = y

base_dir = /var/lib/monitorix/www/
base_lib = /var/lib/monitorix/
base_url = /monitorix
base_cgi = /monitorix-cgi

<httpd_builtin>
        enabled = y
        host =
        port = 8080
        user = nobody
        group = nobody
        log_file = /var/log/monitorix-httpd
        hosts_deny =
        hosts_allow =
        autocheck_responsiveness = y
        <auth>
                enabled = n
                msg = Monitorix: Restricted access
                htpasswd = /var/lib/monitorix/htpasswd
        </auth>
</httpd_builtin>


# Log files pathnames
# -----------------------------------------------------------------------------
log_file        = /var/log/monitorix
secure_log      = /var/log/secure
mail_log        = /var/log/mail.log
milter_gl       = /var/milter-greylist/greylist.db
imap_log        = /var/log/imap
hylafax_log     = /var/spool/hylafax/etc/xferfaxlog
cups_log        = /var/log/cups/page_log
ftp_log         = /var/log/proftpd/access.log # Check monitorix.conf(5) manpage how to edit your ProFTPD server.
fail2ban_log    = /var/log/fail2ban.log
spamassassin_log        = /var/log/mail.log
clamav_log      = /var/log/clamav/clamav.log
cg_logdir       = /var/CommuniGate/SystemLogs/
squid_log       = /var/log/squid/access.log

imap_log_date_format = %b %d
secure_log_date_format = %b %e


<piwik_tracking>
        enabled = n
        url = "://example.com/piwik/"
        sid = "1"
        img = "http://example.com/piwik/piwik.php?idsite=1"
</piwik_tracking>


# Graphs (de)activation
# -----------------------------------------------------------------------------
<graph_enable>
        system          = y
        kern            = y
        proc            = y
        hptemp          = n
        lmsens          = n
        gensens         = y
        ipmi            = y
        ambsens         = n
        nvidia          = n
        disk            = y
        fs              = y
        zfs             = n
        du              = n
        net             = y
        netstat         = y
        tc              = n
        libvirt         = y
        process         = n
        serv            = y
        mail            = y
        port            = y
        user            = y
        ftp             = n
        apache          = n
        nginx           = n
        lighttpd        = n
        mysql           = n
        mongodb         = n
        varnish         = n
        pagespeed       = n
        squid           = n
        nfss            = n
        nfsc            = n
        bind            = y
        unbound         = n
        ntp             = n
        chrony          = n
        fail2ban        = y
        icecast         = n
        raspberrypi     = n
        phpapc          = n
        memcached       = n
        phpfpm          = n
        apcupsd         = n
        nut             = n
        wowza           = n
        int             = y
        verlihub        = n
</graph_enable>


# SYSTEM graph
# -----------------------------------------------------------------------------
<system>
        <alerts>
                loadavg_enabled = n
                loadavg_timeintvl = 3600
                loadavg_threshold = 5.0
                loadavg_script = /path/to/script.sh
        </alerts>
        rigid = 1, 0, 0, 0, 0
        limit = 1, 1000, 1000, 1000, 1000
</system>


# KERN graph
# -----------------------------------------------------------------------------
<kern>
        graph_mode = r
        <list>
                user    = y
                nice    = y
                sys     = y
                iow     = y
                irq     = y
                sirq    = y
                steal   = y
                guest   = y
        </list>
        rigid = 2, 1, 2
        limit = 100, 1000, 100
</kern>


# PROC graph
# -----------------------------------------------------------------------------
<proc>
        max = 4
        graphs_per_row = 2
        size = medium
        data = y
        rigid = 2
        limit = 100
</proc>


# HPTEMP graph
# -----------------------------------------------------------------------------
<hptemp>
        graph_0 = 2, 3
        graph_1 = 1, 6
        graph_2 = 16, 18, 19, 20, 21, 22
        <alerts>
        </alerts>
</hptemp>


# LMSENS graph
# -----------------------------------------------------------------------------
<lmsens>
        <list>
                core0   = Core 2
                core1   = Core 4
                core2   = Core 6
                core3   = Core 8
                cpu0    = Package id 0
#               mb0     = M/B Temp
#               cpu0    = CPU Temp
#               fan0    = fan1
#               fan1    = fan2
#               fan2    = fan3
#               volt0   = VCore 1
#               volt1   = VCore 2
#               volt2   = \+3.3V
#               volt3   = \+5V
#               volt4   = \+12V
#               volt5   = \-12V
#               volt6   = \-5V
#               volt7   = Battery
#               gpu0    = nvidia
        </list>
        <desc>
        </desc>
        <alerts>
        </alerts>
</lmsens>


# GENSENS graph
# -----------------------------------------------------------------------------
<gensens>
        <list>
                0 = temp0
                1 = cpu0
#               2 = bat0
        </list>
        <title>
                0 = Temperatures
                1 = CPU frequency
#               2 = Battery status
        </title>
        <desc>
                temp0 = /sys/devices/virtual/thermal/thermal_zone0/temp
                cpu0 = /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
#               bat0 = /sys/class/power_supply/BAT0/capacity
        </desc>
        <unit>
                temp0 = 1000
                cpu0 = 0.001
#               bat0 = 1
        </unit>
        <map>
                temp0 = Temperature Zone 0
                cpu0 = CPU0 frequency
#               bat0 = Battery 0
        </map>
        <alerts>
        </alerts>
        rigid = 0, 0, 2
        limit = 100, 100, 100
</gensens>


# IPMI graph
# -----------------------------------------------------------------------------
<ipmi>
        list = Temperatures, Fans, Voltages
        <desc>
                0 = CPU Temp, System Temp, Peripheral Temp, DIMMA1 Temp, DIMMB1 Temp
                1 = FAN1, FAN2, FAN3
                2 = Vcpu, 3.3VCC, 12V, VDIMM, 5VCC, 5VSB, 3.3VSB, VBAT, 1.2V BMC
        </desc>
        <units>
                0 = degrees C
                1 = RPM
                2 = Volts
        </units>
        <map>
                FAN1 = FAN1 (CPU)
                FAN2 = FAN2 (RAM)
                FAN3 = FAN3 (PCI-NVME)
        </map>
        <alerts>
        </alerts>
        graphs_per_row = 2
        rigid = 0
        limit = 100
</ipmi>


# AMBSENS graph
# -----------------------------------------------------------------------------
<ambsens>
        list = Ambient Temperature
        <desc>
                0 = at1
        </desc>
        <units>
                0 = Celsius
        </units>
        <cmd>
                at1 = /path/to/script.sh
        </cmd>
        <map>
                at1 = Gold TEMPer PC USB
        </map>
        <alerts>
        </alerts>
        graphs_per_row = 2
        rigid = 0
        limit = 100
</ambsens>


# NVIDIA graph
# -----------------------------------------------------------------------------
<nvidia>
        max = 1
        <alerts>
        </alerts>
        rigid = 1, 2, 2
        limit = 50, 100, 100
</nvidia>


# DISK graph
# -----------------------------------------------------------------------------
<disk>
        <list>
                0 = /dev/sda, /dev/sdb, /dev/nvme1n1, /dev/nvme0n1
        </list>
        <alerts>
                realloc_enabled = n
                realloc_timeintvl = 0
                realloc_threshold = 1
                realloc_script = /path/to/script.sh
                pendsect_enabled = n
                pendsect_timeintvl = 0
                pendsect_threshold = 1
                pendsect_script = /path/to/script.sh
        </alerts>
</disk>


# FS graph
# -----------------------------------------------------------------------------
<fs>
        <list>
                0 = /, swap, /boot, /mnt/DATA, /mnt/BIGBACKUP
        </list>
        <desc>
        </desc>
        <devmap>
        </devmap>
        rigid = 2, 0, 2, 0
        limit = 100, 1000, 100, 1000
        <alerts>
        </alerts>
</fs>


# ZFS graph
# -----------------------------------------------------------------------------
<zfs>
        max_pools = 5
        list = pool1, pool2
        rigid = 0, 0, 0, 0, 2, 0, 0, 0, 2, 0, 0
        limit = 1000, 1000, 1000, 1000, 100, 1000, 1000, 1000, 100, 1000, 1000
</zfs>


# DU graph
# -----------------------------------------------------------------------------
<du>
        list = System, Users
        <desc>
                0 = /var/spool/mail, /var/spool/mqueue, /etc, /var/ftp, /tmp
                1 = /home/ace, /home/gene, /home/paul, /home/peter
        </desc>
        <type>
                0 = size
                1 = files
        </type>
        <dirmap>
                /var/spool/mail = Mail boxes
                /var/spool/mqueue = Mail queue
        </dirmap>
        graphs_per_row = 2
        rigid = 0
        limit = 100
</du>


# NET graph
# -----------------------------------------------------------------------------
<net>
        max = 10
        list = eth0
        <desc>
                eth0 = FastEthernet LAN, 0, 10000000
        </desc>
        gateway = eth0
</net>


# NETSTAT graph
# -----------------------------------------------------------------------------
<netstat>
        cmd = ss
        rigid = 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100
</netstat>


# TC graph
# -----------------------------------------------------------------------------
<tc>
        list = eth0
        <desc>
                eth0 = cbq 1, sfq 10, sfq 20, sfq 30, ingress ffff
        </desc>
        <map>
        </map>
        rigid = 0, 0, 0, 0
        limit = 1000, 1000, 1000, 1000
</tc>


# LIBVIRT graph
# -----------------------------------------------------------------------------
<libvirt>
        cmd = virsh
        <list>
                0 = centos6, winxp
        </list>
        <desc>
                centos6 = CentOS 6, vda, 52:54:00:45:d0:e7
                winxp = MS Windows XP, hda, 52:54:00:97:1c:e5
        </desc>
        rigid = 2, 0, 0, 0
        limit = 100, 1000, 1000, 1000
</libvirt>


# PROCESS graph
# -----------------------------------------------------------------------------
<process>
        <list>
                0 = httpd, sshd, ntpd, mysqld, proftpd, clamd, imap, sendmail, named, smbd
        </list>
        <desc>
                httpd = Apache
                imap = Dovecot
                named = Bind
        </desc>
        rigid = 2, 0, 0, 0, 0, 0, 0, 0
        limit = 100, 1000, 1000, 1000, 1000, 1000, 1000, 1000
</process>


# SERV graph
# -----------------------------------------------------------------------------
<serv>
        mode = i
        rigid = 0, 0, 0
        limit = 1000, 1000, 1000
</serv>


# MAIL graph
# -----------------------------------------------------------------------------
<mail>
        mta = postfix
        greylist = postgrey
        stats_rate = real
        rigid = 0, 0, 0, 0, 0
        limit = 1, 1000, 1000, 1000, 1000
        <alerts>
                delvd_enabled = n
                delvd_timeintvl = 60
                delvd_threshold = 100
                delvd_script = /path/to/script.sh
                mqueued_enabled = n
                mqueued_timeintvl = 3600
                mqueued_threshold = 100
                mqueued_script = /path/to/script.sh
        </alerts>
</mail>


# PORT graph
# -----------------------------------------------------------------------------
<port>
        max = 9
        rule = 24000
        list = 25, 21, 80, 22, 110, 139, 3306, 53, 143
        <desc>
                25      = SMTP,    tcp, in, 0, 1000, L
                21      = FTP,     tcp, in, 0, 1000, L
                80      = HTTP,    tcp, in, 0, 1000, L
                22      = SSH,     tcp, in, 0, 1000, L
                110     = POP3,    tcp, in, 0, 1000, L
                139     = NETBIOS, tcp, in, 0, 1000, L
                3306    = MYSQL,   tcp, in, 0, 1000, L
                53      = DNS,     udp, in, 0, 1000, L
                143     = IMAP,    tcp, in, 0, 1000, L
        </desc>
        graphs_per_row = 3
</port>


# USER graph
# -----------------------------------------------------------------------------
<user>
        rigid = 0, 0, 0
        limit = 1000, 1000, 1000
</user>


# FTP graph
# -----------------------------------------------------------------------------
<ftp>
        server = proftpd
        anon_user = anonymous, ftp
        rigid = 0, 0, 0
        limit = 1000, 1000, 1000
</ftp>


# APACHE graph
# -----------------------------------------------------------------------------
<apache>
        list = http://localhost/server-status?auto
        <alerts>
        </alerts>
        rigid = 0, 0, 2, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100
</apache>


# NGINX graph
# -----------------------------------------------------------------------------
<nginx>
        url = http://localhost/nginx_status
        port = 80
        rule = 24100
        rigid = 0, 0, 0
        limit = 100, 100, 100
</nginx>


# LIGHTTPD graph
# -----------------------------------------------------------------------------
<lighttpd>
        list = http://localhost/server-status?auto
        rigid = 0, 0, 0
        limit = 100, 100, 100
</lighttpd>


# MYSQL graph
# -----------------------------------------------------------------------------
<mysql>
        conn_type = host
        list = localhost
#       list = /var/lib/mysql/mysql.sock
        <desc>
                localhost = 3306, user, secret
        </desc>
        rigid = 0, 2, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100
</mysql>


# MONGODB graph
# -----------------------------------------------------------------------------
<mongodb>
        list = localhost
        max_db = 1
        <desc>
                <localhost>
                        host = 127.0.0.1
                        db_list = mydb
                </localhost>
        </desc>
        rigid = 0, 0, 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100, 100, 100
</mongodb>


# VARNISH graph
# -----------------------------------------------------------------------------
<varnish>
        rigid = 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100
</varnish>


# PAGESPEED graph
# -----------------------------------------------------------------------------
<pagespeed>
        list = http://modpagespeed.com/mod_pagespeed_statistics
        rigid = 0, 0, 2, 0, 0, 0, 0, 0
        limit = 1000, 1000, 100, 1000, 1000, 1000, 1000, 1000
</pagespeed>


# SQUID graph
# -----------------------------------------------------------------------------
<squid>
        cmd = squidclient -h 127.0.0.1
        graph_0 = TCP_MISS, TCP_DENIED, TCP_REFRESH_HIT, TCP_IMS_HIT, TCP_HIT, TCP_REFRESH_MISS, TCP_MEM_HIT, TCP_NEGATIVE_HIT, TCP_CLIENT_REFRESH_MISS
        graph_1 = 200, 403, 304, 204, 302, 000, 404, 301, 206
        rigid = 0, 0, 0, 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100, 100, 100, 100
</squid>


# NFSS graph
# -----------------------------------------------------------------------------
<nfss>
        version = 3
        graph_0 = readlink, create, mkdir, symlink, rmdir, remove, rename, link, readdir
        graph_1 = mknod, readdirplus, fsstat, fsinfo, pathconf, access, lookup, commit, null
        graph_2 = read, write, getattr, setattr
        rigid = 0, 0, 0, 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100, 100, 100, 100
</nfss>


# NFSC graph
# -----------------------------------------------------------------------------
<nfsc>
        version = 3
        graph_0 = readlink, create, mkdir, symlink, rmdir, remove, rename, link, readdir
        graph_1 = mknod, readdirplus, fsstat, fsinfo, pathconf
        graph_2 = read, write
        graph_3 = getattr, setattr
        graph_4 = access, lookup, commit, null
        rigid = 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100
</nfsc>


# BIND graph
# -----------------------------------------------------------------------------
<bind>
        list = http://localhost:8053/,http://10.211.100.1:8053/
#       list = http://localhost:8053/
        <in_queries_list>
                http://localhost:8053/ = A, AAAA, ANY, DS, MX, NS, PTR, SOA, SRV, TXT, NAPTR, A6, CNAME, SPF, KEY, DNSKEY, HINFO, WKS, PX, NSAP
                http://10.211.100.1:8053/ = A, AAAA, ANY, DS, MX, NS, PTR, SOA, SRV, TXT, NAPTR, A6, CNAME, SPF, KEY, DNSKEY, HINFO, WKS, PX, NSAP
        </in_queries_list>
        <out_queries_list>
                http://localhost:8053/ = A, AAAA, ANY, DS, MX, NS, PTR, SOA, SRV, TXT, NAPTR, A6, CNAME, SPF, KEY, DNSKEY, HINFO, WKS, PX, NSAP
                http://10.211.100.1:8053/ = A, AAAA, ANY, DS, MX, NS, PTR, SOA, SRV, TXT, NAPTR, A6, CNAME, SPF, KEY, DNSKEY, HINFO, WKS, PX, NSAP
        </out_queries_list>
        <server_stats_list>
                http://localhost:8053/ = Requestv4, ReqEdns0, ReqBadEDNSVer, ReqTSIG, ReqSIG0, ReqBadSIG, ReqTCP, Response, QrySuccess, QryAuthAns, QryNoauthAns, QryReferral, QryNxrrset, QrySERVFAIL, QryNXDOMAIN, QryRecursion, QryDuplicate, QryDropped, QryFailure, -nan
                http://10.211.100.1:8053/ = Requestv4, ReqEdns0, ReqBadEDNSVer, ReqTSIG, ReqSIG0, ReqBadSIG, ReqTCP, Response, QrySuccess, QryAuthAns, QryNoauthAns, QryReferral, QryNxrrset, QrySERVFAIL, QryNXDOMAIN, QryRecursion, QryDuplicate, QryDropped, QryFailure, -nan
        </server_stats_list>
        <resolver_stats_list>
                http://localhost:8053/ = Queryv4, Responsev4, NXDOMAIN, SERVFAIL, FORMERR, OtherError, EDNS0Fail, Truncated, Lame, Retry, QueryTimeout, GlueFetchv4, GlueFetchv4Fail, ValAttempt, ValOk, ValNegOk
                http://10.211.100.1:8053/ = Queryv4, Responsev4, NXDOMAIN, SERVFAIL, FORMERR, OtherError, EDNS0Fail, Truncated, Lame, Retry, QueryTimeout, GlueFetchv4, GlueFetchv4Fail, ValAttempt, ValOk, ValNegOk
        </resolver_stats_list>
        <cache_rrsets_list>
                http://localhost:8053/ = A, !A, AAAA, !AAAA, DLV, !DLV, DS, !DS, MX, NS, CNAME, !CNAME, SOA, !SOA, !ANY, PTR, RRSIG, NSEC, DNSKEY, NXDOMAIN
                http://10.211.100.1:8053/ = A, !A, AAAA, !AAAA, DLV, !DLV, DS, !DS, MX, NS, CNAME, !CNAME, SOA, !SOA, !ANY, PTR, RRSIG, NSEC, DNSKEY, NXDOMAIN
        </cache_rrsets_list>
        rigid = 0, 0, 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100, 100, 100
</bind>


# UNBOUND graph
# -----------------------------------------------------------------------------
<unbound>
        queries_type = A, AAAA, ANY, DS, MX, NS, PTR, SOA, SRV, TXT, NAPTR, A6, CNAME, SPF, KEY, DNSKEY, HINFO, WKS, PX, NSAP
        rigid = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100, 100, 100, 100, 100
</unbound>


# NTP graph
# -----------------------------------------------------------------------------
<ntp>
        list = localhost
        <desc>
                localhost = AUTH, AUTO, CRYP, DENY, GPS, INIT, NKEY, RATE, RMOT, RSTR
        </desc>
        rigid = 0, 0, 0
        limit = 100, 100, 100
</ntp>


# CHRONY graph
# -----------------------------------------------------------------------------
<chrony>
        list = localhost
        rigid = 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100
</chrony>


# FAIL2BAN graph
# -----------------------------------------------------------------------------
<fail2ban>
        list = Security, Overload / Abuse
        <desc>
                0 = [apache], [apache-mod-security], [apache-overflows], [courierauth], [sshd], [pam-generic], [php-url-fopen], [vsftpd]
                1 = [apache-evasive], [apache-badbots], [named-refused-udp], [named-refused-tcp]
        </desc>
        graphs_per_row = 2
        rigid = 0
        limit = 100
</fail2ban>


# ICECAST graph
# -----------------------------------------------------------------------------
<icecast>
        list = http://localhost:8000/status.xsl
        <desc>
                http://localhost:8000/status.xsl = stream1, stream2, stream3
        </desc>
        graph_mode = r
        rigid = 0, 0
        limit = 100, 100
</icecast>


# RASPBERRYPI graph
# -----------------------------------------------------------------------------
<raspberrypi>
        cmd = /opt/vc/bin/vcgencmd
        clocks = arm, core, h264, isp, v3d, uart, emmc, pixel, hdmi
        volts = core, sdram_c, sdram_i, sdram_p
        rigid = 0, 0, 0
        limit = 100, 100, 100
</raspberrypi>


# PHPAPC graph
# -----------------------------------------------------------------------------
<phpapc>
        list = http://localhost/apc.php?auto
        rigid = 2, 2, 0
        limit = 100, 100, 100
</phpapc>


# MEMCACHED graph
# -----------------------------------------------------------------------------
<memcached>
        list = localhost:11211
        rigid = 0, 0, 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100, 100
</memcached>


# PHP-FPM graph
# -----------------------------------------------------------------------------
<phpfpm>
        <group>
                0 = First group of domains
        </group>
        <list>
                0 = example1, example2, example3
        </list>
        <desc>
                example1 = http://www.example1.com/php_fpm_status
                example2 = http://www.example2.com/php_fpm_status
                example3 = http://www.example3.com/php_fpm_status
        </desc>
        <map>
        </map>
        rigid = 0, 0, 2, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100
</phpfpm>


# APCUPSD graph
# -----------------------------------------------------------------------------
<apcupsd>
        cmd = apcaccess
        list = localhost:3551
        rigid = 0, 2, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100, 100
</apcupsd>


# NUT graph
# -----------------------------------------------------------------------------
<nut>
        list = ups@localhost
        rigid = 0, 2, 0, 0, 0, 0
        limit = 100:0, 100, 100:0, 100:0, 100:0, 100:0
</nut>


# WOWZA graph
# -----------------------------------------------------------------------------
<wowza>
        list = http://localhost:8086/connectioncounts
        <desc>
                http://localhost:8086/connectioncounts = channel1, channel2
        </desc>
        rigid = 0, 0, 0, 0, 0
        limit = 100, 100, 100, 100, 100
</wowza>


# INT graph
# -----------------------------------------------------------------------------
<int>
        rigid = 0, 0, 0
        limit = 100, 100, 100
</int>


# VERLIHUB graph
# -----------------------------------------------------------------------------
<verlihub>
        host = localhost
        port = 3306
        user = verlihub_user
        password = verlihub_password
        database = verlihub_database
        rigid = 0, 0, 0
        limit = 1000, 1000, 1000
</verlihub>


# TRAFFACCT graph
# -----------------------------------------------------------------------------
<traffacct>
        enabled = n
        max = 10
        graphs_per_row = 2
        list = pc101, pc102, pc103, pc104
        <desc>
                0 = 192.168.1.101/32, ac...@ex...
                1 = 192.168.1.102/32, ge...@ex...
                2 = 192.168.1.103/32, pa...@ex...
                3 = 192.168.1.104/32, pe...@ex...
        </desc>
        <reports>
                enabled = n
                language = en
                default_mail = root@localhost
                url_prefix = http://localhost:8080
                smtp_hostname = localhost
                from_address = no...@ex...
        </reports>
        rigid = 0
        limit = 100
</traffacct>


# Multihost
# -----------------------------------------------------------------------------
<multihost>
        enabled = n
        footer_url = y
        graphs_per_row = 2
        default_option_when_all = "System load"
        remotehost_list = server 1, server 2, server 3
        <remotehost_desc>
                0 = http://www.example.com,/monitorix,/monitorix-cgi
                1 = http://10.0.0.1,/monitorix,/monitorix-cgi
                2 = http://192.168.0.100:8080,/,/
        </remotehost_desc>
        groups = n
        remotegroup_list = My Group
        <remotegroup_desc>
                0 = server 2, server 3
        </remotegroup_desc>
</multihost>


# Email Reports
# -----------------------------------------------------------------------------
<emailreports>
        enabled = n
        url_prefix = http://localhost:8080
        smtp_hostname = localhost
        from_address = no...@ex...
        hour = 0
        minute = 0
        <daily>
                enabled = n
                graphs = system, fs
                to = ac...@ex...
        </daily>
        <weekly>
                enabled = n
                graphs = system, fs
                to = ge...@ex...
        </weekly>
        <monthly>
                enabled = n
                graphs = system, fs
                to = pa...@ex...
        </monthly>
        <yearly>
                enabled = n
                graphs = system, fs
                to = pe...@ex...
        </yearly>
</emailreports>


# ========================================================================
# ======  Probably you don't need to touch anything below this line ======
# ========================================================================

timeout = 15

imgs_dir = imgs/
usage_dir = usage/
report_dir = reports/
favicon = monitorixico.png
logo_top = logo_top.png
logo_top_url = http://www.monitorix.org/
logo_bottom = logo_bot.png

<theme>
        <white>
                main_bg         = FFFFFF
                main_fg         = 000000
                title_bg        = 777777
                title_fg        = CCCC00
                graph_bg        = CCCCCC
                gap             = 000000
        </white>
        <black>
                canvas          = 000000
                back            = 101010
                font            = C0C0C0
                mgrid           = 80C080
                grid            = 808020
                frame           = 808080
                arrow           = FFFFFF
                shadea          = 404040
                shadeb          = 404040
                axis            = 101010
                main_bg         = 000000
                main_fg         = FFFFFF
                title_bg        = 333333
                title_fg        = 888800
                graph_bg        = 888888
                gap             = FFFFFF
        </black>
</theme>

<graph_size>
        main    = 450x150
        medium  = 325x150
        medium2 = 325x70
        small   = 200x66
        mini    = 183x66
        tiny    = 110x40
        zoom    = 800x300
        remote  = 300x100
</graph_size>

graph_name = system, kern, proc, hptemp, lmsens, gensens, ipmi, ambsens, nvidia, disk, fs, zfs, du, net, netstat, tc, libvirt, process, serv, mail, port, user, ftp, apache, nginx, lighttpd, mysql, mongodb, varnish, pagespeed, squid, nfss, nfsc, bind, unbound, ntp, chrony, fail2ban, icecast, raspberrypi, phpapc, memcached, phpfpm, apcupsd, nut, wowza, int, verlihub

<graph_title>
        system          = System load average and usage
        kern            = Global kernel usage
        proc            = Kernel usage per processor
        hptemp          = HP ProLiant System Health
        lmsens          = LM-Sensors and GPU temperatures
        gensens         = Generic sensor statistics
        ipmi            = IPMI sensor statistics
        ambsens         = Ambient sensor statistics
        nvidia          = NVIDIA temperatures and usage
        disk            = Disk drive temperatures and health
        fs              = Filesystem usage and I/O activity
        zfs             = ZFS statistics
        du              = Directory usage
        net             = Network traffic and usage
        netstat         = Netstat statistics
        tc              = Traffic Control statistics
        libvirt         = Libvirt statistics
        process         = Processes statistics
        serv            = System services demand
        mail            = Mail statistics
        port            = Network port traffic
        user            = Users using the system
        ftp             = FTP statistics
        apache          = Apache statistics
        nginx           = Nginx statistics
        lighttpd        = Lighttpd statistics
        mysql           = MySQL statistics
        mongodb         = MongoDB statistics
        varnish         = Varnish statistics
        pagespeed       = PageSpeed statistics
        squid           = Squid statistics
        nfss            = NFS server statistics
        nfsc            = NFS client statistics
        bind            = BIND statistics
        unbound         = Unbound statistics
        ntp             = NTP statistics
        chrony          = Chrony statistics
        fail2ban        = Fail2ban statistics
        icecast         = Icecast Streaming Media Server
        raspberrypi     = Raspberry Pi sensor statistics
        phpapc          = Alternative PHP Cache statistics
        memcached       = Memcached statistics
        phpfpm          = PHP-FPM statistics
        apcupsd         = APC UPS statistics
        nut             = Network UPS Tools statistics
        wowza           = Wowza Media Server
        int             = Devices interrupt activity
        verlihub        = VerliHub statistics
</graph_title>

<graphs>
        _system1        = System load
        _system2        = Memory allocation
        _system3        = Active processes
        _system4        = Entropy
        _system5        = Uptime
        _kern1          = Kernel usage
        _kern2          = Context switches and forks
        _kern3          = VFS usage
        _proc           = Processor
        _hptemp1        = Temperatures 1
        _hptemp2        = Temperatures 2
        _hptemp3        = Temperatures 3
        _lmsens1        = Core temperatures
        _lmsens2        = Voltages
        _lmsens3        = MB and CPU temperatures
        _lmsens4        = Fan speeds
        _lmsens5        = GPU temperatures
        _gensens        = Generic sensors
        _ipmi           = IPMI sensors
        _ambsens        = Ambient sensors
        _nvidia1        = NVIDIA temperatures
        _nvidia2        = CPU usage
        _nvidia3        = Memory usage
        _disk1          = Disk drives temperatures
        _disk2          = Reallocated sector count
        _disk3          = Current pending sector
        _fs1            = Filesystems usage
        _fs2            = Disk I/O activity
        _fs3            = Inode usage
        _fs4            = Time spent in I/O activity
        _zfs1           = ARC usage
        _zfs2           = ARC cache
        _zfs3           = L2ARC cache
        _zfs4           = Pool data usage
        _zfs5           = Pool usage
        _zfs6           = Operations
        _zfs7           = Bandwidth
        _du             = Directory usage
        _net1           = Network traffic
        _net2           = Network packets
        _net3           = Network errors
        _netstat1       = IPv4 states
        _netstat2       = IPv6 states
        _netstat3       = Active close
        _netstat4       = Passive close
        _netstat5       = UDP statistics
        _tc1            = Traffic
        _tc2            = Dropped
        _tc3            = Overlimits
        _tc4            = Requeues
        _libvirt1       = CPU time usage
        _libvirt2       = Memory usage
        _libvirt3       = Disk usage
        _libvirt4       = Network usage
        _process1       = CPU time usage
        _process2       = Memory usage
        _process3       = Disk usage
        _process4       = Network usage
        _process5       = Opened files
        _process6       = Number of threads
        _process7       = Context switches
        _process8       = Number of processes
        _serv1          = System services demand
        _serv2          = IMAP and POP3 services
        _serv3          = SMTP service
        _mail1          = Mail statistics
        _mail2          = Network traffic
        _mail3          = Mails in queue
        _mail4          = Queue size
        _mail5          = SPF
        _mail6          = Greylisting
        _port           = Port
        _user1          = Users logged in
        _user2          = Samba users
        _user3          = Netatalk users
        _ftp1           = Commands usage
        _ftp2           = New sessions
        _ftp3           = FTP traffic
        _apache1        = Apache workers
        _apache2        = Apache workers
        _apache3        = Apache CPU usage
        _apache4        = Apache requests
        _apache5        = Apache workers
        _apache6        = Apache open slots
        _nginx1         = Nginx connections
        _nginx2         = Nginx requests
        _nginx3         = Nginx traffic
        _lighttpd1      = Lighttpd workers
        _lighttpd2      = Lighttpd traffic
        _lighttpd3      = Lighttpd requests
        _mysql1         = MySQL query types
        _mysql2         = MySQL overall stats
        _mysql3         = Table saturation and MyISAM
        _mysql4         = MySQL queries
        _mysql5         = MySQL connections
        _mysql6         = MySQL traffic
        _mongodb1       = MongoDB operations
        _mongodb2       = MongoDB metrics document
        _mongodb3       = MongoDB write performance
        _mongodb4       = MongoDB connections
        _mongodb5       = MongoDB requests & asserts
        _mongodb6       = MongoDB traffic
        _varnish1       = Varnish statistics
        _varnish2       = Backend usage
        _varnish3       = Client connections
        _varnish4       = Cache performance
        _varnish5       = Objects
        _varnish6       = Traffic
        _pagespeed1     = Cache overview
        _pagespeed2     = HTML optimization
        _pagespeed3     = Saved ratio
        _pagespeed4     = Memcached
        _pagespeed5     = Pcache cohorts
        _pagespeed6     = Rewrite & SHM cache
        _pagespeed7     = LRU & File cache
        _pagespeed8     = Cache time
        _squid1         = Squid statistics 1
        _squid2         = Squid statistics 2
        _squid3         = Overall I/O
        _squid4         = Memory usage
        _squid5         = Store directory stats
        _squid6         = IP cache stats
        _squid7         = Network protocols usage
        _squid8         = Client traffic
        _squid9         = Server traffic
        _nfss1          = NFS server stats 1
        _nfss2          = NFS server stats 2
        _nfss3          = NFS server stats 3
        _nfss4          = Overall I/O
        _nfss5          = Network layer
        _nfss6          = RPC
        _nfss7          = Thread utilization
        _nfss8          = Read cache
        _nfss9          = File handle cache
        _nfsc1          = NFS client stats 1
        _nfsc2          = NFS client stats 2
        _nfsc3          = NFS client stats 3
        _nfsc4          = NFS client stats 4
        _nfsc5          = NFS client stats 5
        _nfsc6          = RPC client stats
        _bind1          = Incoming queries
        _bind2          = Outgoing queries (_default)
        _bind3          = Name server statistics
        _bind4          = Resolver statistics (_default)
        _bind5          = Cache DB RRsets (_default)
        _bind6          = Memory usage
        _bind7          = Task manager
        _unbound1       = Queries and cache
        _unbound2       = Queries by type
        _unbound3       = Recursion time
        _unbound4       = Uptime
        _unbound5       = Specific traffic
        _unbound6       = Memory usage
        _unbound7       = Answers by type
        _unbound8       = Queries by flags
        _unbound9       = Less than 1s resolving time
        _unbound10      = More than 1s resolving time
        _ntp1           = NTP timing stats
        _ntp2           = Stratum level
        _ntp3           = Codes
        _chrony1        = Chrony timing stats
        _chrony2        = Network path delays
        _chrony3        = Stratum level
        _chrony4        = System's clock drift
        _chrony5        = Estimated error in frequency
        _chrony6        = Update interval
        _fail2ban       = Fail2ban jails
        _icecast1       = Current listeners
        _icecast2       = Bitrate
        _raspberrypi1   = Clock frequency
        _raspberrypi2   = Temperatures
        _raspberrypi3   = Voltages
        _phpapc1        = Memory usage
        _phpapc2        = Hits & misses
        _phpapc3        = File cache
        _memcached1     = Memcached statistics 1
        _memcached2     = Memcached statistics 2
        _memcached3     = Cache usage
        _memcached4     = Items in cache
        _memcached5     = Objects I/O
        _memcached6     = Connections
        _memcached7     = Memcached traffic
        _phpfpm1        = Accepted connections
        _phpfpm2        = Active processes
        _phpfpm3        = Listen queue
        _phpfpm4        = Total processes
        _phpfpm5        = Max. children reached
        _phpfpm6        = Slow requests
        _apcupsd1       = Line voltage
        _apcupsd2       = Battery charge
        _apcupsd3       = Temperatures
        _apcupsd4       = Battery voltage
        _apcupsd5       = Time left
        _apcupsd6       = Line frequency
        _nut1           = Line voltage
        _nut2           = Battery charge
        _nut3           = Temperatures
        _nut4           = Battery voltage
        _nut5           = Time left
        _nut6           = Line frequency
        _wowza1         = Current connections
        _wowza2         = Messages bytes rate
        _wowza3         = Connections accepted
        _wowza4         = Connections rejected
        _wowza5         = Streams
        _int1           = Interrupt activity
        _int2           = Core activity
        _int3           = Interrupt activity
        _verlihub1      = Users in hub
        _verlihub2      = Total hub upload
        _verlihub3      = Total hub share
</graphs>

Re: [Monitorix-general] lmsensors configuration

[Jordi S. <jo...@fi...>]

Hello,

On 4/22/22 14:42, Steve Valliere wrote:
> Sorry for being a pest, but I'm trying to figure out what I've done wrong.  After this I promise to shut up and go away. (smile)

Steve, you are very welcome :-), this list has a very low activity, 
almost only used for version announcements.

Nowadays, most people seem to prefer GitHub to ask for issues, 
questions, etc. Anyway, it's fine to see someone writing here.



> I enabled the hourly graphs and got this for the last hour's CPU Core temperatures (image attached). When I've seen a missing/zero value, there has always been a (near) vertical line drawn between the X axis and the 'actual' values. The attached graph doesn't show any of that and yet did not auto scale.  If you look closely, you can see that all five tracks are plotted in the very narrow 'track blob' at the top.
> 
> So, how did I defeat the auto-scaling feature? Or is the graph /using/ a zero value (that it invented, since 'sensors' never outputs 0C for a CPU Core temp!) and electing not to draw the associated line segment(s)?

I'm sorry, now I realized that the option 'use_nan_for_missing_data' was 
already recently included in the 'lmsens.pm' module. See here 
<https://github.com/mikaku/Monitorix/pull/406>.

So you only need to add the following options in your <lmsens> section:

use_nan_for_missing_data = y
limit = 100, 100, 100, 100, 100

and wait until all data plotted (in your selected time frame) is changed 
to use NaN for all zero values. That is, your graph will start 
autoscaling correctly after an hour in the hourly graph and after a day 
in the daily graph and so on.

Check the following issue <https://github.com/mikaku/Monitorix/pull/403> 
to read a similar problem a user had but with a different graph.



> [Side note:  I tried switching to text mode output to look at the values, but all of the selections I have tried fail with messages like "ERROR: while fetching /var/lib/monitorix/lmsens.rrd: resolution: value must be (suffixed) positive number" on the HOURLY setting -- text mode seems to work fine for daily and above]

Yes, text version might well support only standard time frames (daily, 
weekly, etc.), hourly is a 'tricky' time frame.

Regards.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

Re: [Monitorix-general] lmsensors configuration

[Steve V. <nu...@ho...>]

Sorry for being a pest, but I'm trying to figure out what I've done wrong.  After this I promise to shut up and go away. (smile)

I enabled the hourly graphs and got this for the last hour's CPU Core temperatures (image attached). When I've seen a missing/zero value, there has always been a (near) vertical line drawn between the X axis and the 'actual' values. The attached graph doesn't show any of that and yet did not auto scale.  If you look closely, you can see that all five tracks are plotted in the very narrow 'track blob' at the top.

So, how did I defeat the auto-scaling feature? Or is the graph /using/ a zero value (that it invented, since 'sensors' never outputs 0C for a CPU Core temp!) and electing not to draw the associated line segment(s)?

[Side note:  I tried switching to text mode output to look at the values, but all of the selections I have tried fail with messages like "ERROR: while fetching /var/lib/monitorix/lmsens.rrd: resolution: value must be (suffixed) positive number" on the HOURLY setting -- text mode seems to work fine for daily and above]



-----Original Message-----
From: Jordi Sanfeliu via Monitorix-general <mon...@li...> 
Sent: Friday, April 22, 2022 3:54 AM
To: mon...@li...
Cc: Jordi Sanfeliu <jo...@fi...>
Subject: Re: [Monitorix-general] lmsensors configuration

Hello,

On 4/21/22 20:08, Steve Valliere wrote:
> Re #2 (setting Y-axis ranges)... I do not understand the need to add the use nan setting, since to set a sensible range for the bulk of the values on my graph.  For example, the core (and GPU) temps on my system are just about always 55C +/- 2C, so why am I required to have a graph whose scale goes from 0 to 60?  I was hoping it might auto-adjust the low limit on the scale once the graph filled, but it did not.

> It looks like both the min and max values for the Y axis are settable parameters for the graphics package, so I'm requesting that we be allowed to set them without hacking into the perl script on our own.  But I think I can figure that out if you don't think there's any value to graphs that aren't generally a flat line, um, sorry, I mean if you don't see the value in this option.
> 

The graphs do autoscaling automatically, this is an RRDtool feature. The problem is that some graphs plot a zero value when there is not value to plot and that forces the graph to scale from 0 to the maximum value represented.

This behavior is accepted in the majority of cases. That's the reason why not all the graphs include the option 'use_nan_for_missing_data' 
which forces to use the value NaN when there is no value to represent.

Regards.

--
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat


_______________________________________________
Monitorix-general mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/monitorix-general

Re: [Monitorix-general] lmsensors configuration

[Jordi S. <jo...@fi...>]

Hello,

On 4/21/22 20:08, Steve Valliere wrote:
> Re #2 (setting Y-axis ranges)... I do not understand the need to add the use nan setting, since to set a sensible range for the bulk of the values on my graph.  For example, the core (and GPU) temps on my system are just about always 55C +/- 2C, so why am I required to have a graph whose scale goes from 0 to 60?  I was hoping it might auto-adjust the low limit on the scale once the graph filled, but it did not.

> It looks like both the min and max values for the Y axis are settable parameters for the graphics package, so I'm requesting that we be allowed to set them without hacking into the perl script on our own.  But I think I can figure that out if you don't think there's any value to graphs that aren't generally a flat line, um, sorry, I mean if you don't see the value in this option.
> 

The graphs do autoscaling automatically, this is an RRDtool feature. The 
problem is that some graphs plot a zero value when there is not value to 
plot and that forces the graph to scale from 0 to the maximum value 
represented.

This behavior is accepted in the majority of cases. That's the reason 
why not all the graphs include the option 'use_nan_for_missing_data' 
which forces to use the value NaN when there is no value to represent.

Regards.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

Re: [Monitorix-general] lmsensors configuration

[Steve V. <nu...@ho...>]

Re #2 (setting Y-axis ranges)... I do not understand the need to add the use nan setting, since to set a sensible range for the bulk of the values on my graph.  For example, the core (and GPU) temps on my system are just about always 55C +/- 2C, so why am I required to have a graph whose scale goes from 0 to 60?  I was hoping it might auto-adjust the low limit on the scale once the graph filled, but it did not.

It looks like both the min and max values for the Y axis are settable parameters for the graphics package, so I'm requesting that we be allowed to set them without hacking into the perl script on our own.  But I think I can figure that out if you don't think there's any value to graphs that aren't generally a flat line, um, sorry, I mean if you don't see the value in this option.

Thanks,

SteveV.

-----Original Message-----
From: Jordi Sanfeliu via Monitorix-general <mon...@li...> 
Sent: Thursday, April 21, 2022 10:43 AM
To: mon...@li...
Cc: Jordi Sanfeliu <jo...@fi...>
Subject: Re: [Monitorix-general] lmsensors configuration

Hello Steve,

On 4/21/22 15:05, Steve Valliere wrote:

> I’m hoping there is a way to do a few things:
> 
>  1. Sensibly map all (I hope) of my sensors output to the graphs

This is out of scope of Monitorix, you need to modify lm_sensors to output different names.

Please read this FAQ <https://www.monitorix.org/faq.html#Q125>, which will guide you to <https://github.com/mikaku/Monitorix/issues/131>.



>  2. Find the setting for the min/max values for the various graphs (e.g.
>     the core temps only need 30-70 or so)

This would need to introduce the option 'use_nan_for_missing_data' like 
some other graphs already have 
(<https://github.com/mikaku/Monitorix/issues/401>).

Please, open a new issue in GitHub to help to track this change.



>  3. Remove graphs with no data points from the display.

That's not possible as the majority of graph layouts in Monitorix are fixed.

Regards.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat


_______________________________________________
Monitorix-general mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/monitorix-general

Re: [Monitorix-general] lmsensors configuration

[Steve V. <nu...@ho...>]

Thanks, IPMI sounded great, but it seems that my system (a Dell Precision WorkStation R5500, circa 2013)  does not support it (Dell appears to have an IPMI driver, but not for linux and/or not for my device.)  All of the IPMI detection methods suggested by the freeipmi documentation fail and the ipmi-sensors program runs for a couple minutes and then fails with an internal error (no more detail than that.)  Oh well.

Using the other suggestion for renaming the lmsensors in the 'sensors' output, I've been able to get all four case temps into the MP and CPU temps graph, and I added my radeon GPU temp to the Core Temperatures graph as well.  So voltages and GPU Temps are empty, oh well.

Thanks for the help!


-----Original Message-----
From: Jordi Sanfeliu via Monitorix-general <mon...@li...> 
Sent: Thursday, April 21, 2022 10:43 AM
To: mon...@li...
Cc: Jordi Sanfeliu <jo...@fi...>
Subject: Re: [Monitorix-general] lmsensors configuration

Hello Steve,

On 4/21/22 15:05, Steve Valliere wrote:

> I’m hoping there is a way to do a few things:
> 
>  1. Sensibly map all (I hope) of my sensors output to the graphs

This is out of scope of Monitorix, you need to modify lm_sensors to output different names.

Please read this FAQ <https://www.monitorix.org/faq.html#Q125>, which will guide you to <https://github.com/mikaku/Monitorix/issues/131>.



>  2. Find the setting for the min/max values for the various graphs (e.g.
>     the core temps only need 30-70 or so)

This would need to introduce the option 'use_nan_for_missing_data' like 
some other graphs already have 
(<https://github.com/mikaku/Monitorix/issues/401>).

Please, open a new issue in GitHub to help to track this change.



>  3. Remove graphs with no data points from the display.

That's not possible as the majority of graph layouts in Monitorix are fixed.

Regards.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat


_______________________________________________
Monitorix-general mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/monitorix-general

Re: [Monitorix-general] lmsensors configuration

[Jordi S. <jo...@fi...>]

Hello Steve,

On 4/21/22 15:05, Steve Valliere wrote:

> I’m hoping there is a way to do a few things:
> 
>  1. Sensibly map all (I hope) of my sensors output to the graphs

This is out of scope of Monitorix, you need to modify lm_sensors to 
output different names.

Please read this FAQ <https://www.monitorix.org/faq.html#Q125>, which 
will guide you to <https://github.com/mikaku/Monitorix/issues/131>.



>  2. Find the setting for the min/max values for the various graphs (e.g.
>     the core temps only need 30-70 or so)

This would need to introduce the option 'use_nan_for_missing_data' like 
some other graphs already have 
(<https://github.com/mikaku/Monitorix/issues/401>).

Please, open a new issue in GitHub to help to track this change.



>  3. Remove graphs with no data points from the display.

That's not possible as the majority of graph layouts in Monitorix are fixed.

Regards.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

Re: [Monitorix-general] lmsensors configuration

[mr2dave <mr...@gm...>]

Welcome Steve.

I don't know what hardware you've got, but I've had better luck with
ipmi than lmsens on hardware with a BMC.
Try installing a freeipmi package and run "sudo ipmi-sensors" to see if
it detects anything.

-Dave


On Thu, 2022-04-21 at 13:05 +0000, Steve Valliere wrote:
> Hello, I am new to monitorix, having learned of and installed it only
> yesterday, so please forgive my ignorance.
>  
> I have managed to get most of the graphs configured the way I want
> them and configured the server to listen on only aninternal network
> address. I have had some trouble with the LMSENSORS graph for two
> reasons:  My system doesn’t have any of the sensors required for some
> of the graphs and uses the same name for multiple sensor values. 
> Here’s the output from a sensors command on my machine:
>  
> steve@mail:/etc/monitorix$ sensors
> dell_smm-virtual-0
> Adapter: Virtual device
> Other Fan:     3114 RPM
> Processor Fan: 3148 RPM
> Processor Fan: 3137 RPM
> Ambient:        +25.0°C
> Ambient:        +24.0°C
> Ambient:        +27.0°C
> Ambient:        +24.0°C
>  
> radeon-pci-0200
> Adapter: PCI adapter
> temp1:        +56.0°C
>  
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:       +54.0°C  (high = +87.0°C, crit = +103.0°C)
> Core 1:       +55.0°C  (high = +87.0°C, crit = +103.0°C)
> Core 2:       +55.0°C  (high = +87.0°C, crit = +103.0°C)
> Core 3:       +56.0°C  (high = +87.0°C, crit = +103.0°C)
>  
> And here’s what the graph looks like:
>  
>  
> And finally, here’s what I’ve got for configuration:
>  
> # LMSENS graph
> # -------------------------------------------------------------------
> ----------
> <lmsens>
>         <list>
>                 core0   = Core 0
>                 core1   = Core 1
>                 core2   = Core 2
>                 core3   = Core 3
>                 mb0     = Ambient
>                 #cpu0   = CPU Temp
>                 fan0    = Other Fan
>                 fan1    = Processor Fan
>                 #fan2   = Processor Fan
>                 #volt0  = VCore 1
>                 #volt1  = VCore 2
>                 #volt2  = \+3.3V
>                 #volt3  = \+5V
>                 #volt4  = \+12V
>                 #volt5  = \-12V
>                 #volt6  = \-5V
>                 #volt7  = Battery
>                 gpu0    = temp1
>         </list>
>         <desc>
>                 mb0     = Case Ambient
>                 fan0    = Case Fan
>                 fan1    = CPU Fan
>                 gpu0    = Radeon GPU
>         </desc>
>         <alerts>
>         </alerts>
> </lmsens>
>  
> I’m hoping there is a way to do a few things:
> 1. Sensibly map all (I hope) of my sensors output to the graphs
> 2. Find the setting for the min/max values for the various graphs
> (e.g. the core temps only need 30-70 or so)
> 3. Remove graphs with no data points from the display.
>  
> Hopefully someone here will be able and willing to help!  (smile) 
> Thanks in advance.
> _______________________________________________
> Monitorix-general mailing list
> Mon...@li...
> https://lists.sourceforge.net/lists/listinfo/monitorix-general

[Monitorix-general] lmsensors configuration

[Steve V. <nu...@ho...>]

Hello, I am new to monitorix, having learned of and installed it only yesterday, so please forgive my ignorance.

I have managed to get most of the graphs configured the way I want them and configured the server to listen on only an internal network address. I have had some trouble with the LMSENSORS graph for two reasons:  My system doesn't have any of the sensors required for some of the graphs and uses the same name for multiple sensor values.  Here's the output from a sensors command on my machine:

steve@mail:/etc/monitorix$ sensors
dell_smm-virtual-0
Adapter: Virtual device
Other Fan:     3114 RPM
Processor Fan: 3148 RPM
Processor Fan: 3137 RPM
Ambient:        +25.0°C
Ambient:        +24.0°C
Ambient:        +27.0°C
Ambient:        +24.0°C

radeon-pci-0200
Adapter: PCI adapter
temp1:        +56.0°C

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +54.0°C  (high = +87.0°C, crit = +103.0°C)
Core 1:       +55.0°C  (high = +87.0°C, crit = +103.0°C)
Core 2:       +55.0°C  (high = +87.0°C, crit = +103.0°C)
Core 3:       +56.0°C  (high = +87.0°C, crit = +103.0°C)

And here's what the graph looks like:

[cid:image001.png@01D8555D.FED04090]

And finally, here's what I've got for configuration:

# LMSENS graph
# -----------------------------------------------------------------------------
<lmsens>
        <list>
                core0   = Core 0
                core1   = Core 1
                core2   = Core 2
                core3   = Core 3
                mb0     = Ambient
                #cpu0   = CPU Temp
                fan0    = Other Fan
                fan1    = Processor Fan
                #fan2   = Processor Fan
                #volt0  = VCore 1
                #volt1  = VCore 2
                #volt2  = \+3.3V
                #volt3  = \+5V
                #volt4  = \+12V
                #volt5  = \-12V
                #volt6  = \-5V
                #volt7  = Battery
                gpu0    = temp1
        </list>
        <desc>
                mb0     = Case Ambient
                fan0    = Case Fan
                fan1    = CPU Fan
                gpu0    = Radeon GPU
        </desc>
        <alerts>
        </alerts>
</lmsens>

I'm hoping there is a way to do a few things:

  1.  Sensibly map all (I hope) of my sensors output to the graphs
  2.  Find the setting for the min/max values for the various graphs (e.g. the core temps only need 30-70 or so)
  3.  Remove graphs with no data points from the display.

Hopefully someone here will be able and willing to help!  (smile)  Thanks in advance.

Re: [Monitorix-general] Reports no longer working

[Michael B. <mb...@br...>]

Hi,



No problem, I'm just glad that you could fix the problem so fast.



Yes, you can include my name and email address.



Micke Test is just my nickename, my real name is Michael Bronzini.





Regards



/Michael






Hi,

Thank you very much for your feedback, and sorry for the inconveniences 
of this bug.

Do you give me permission to include your name and email address in the 
Changes file, as the person who found this bug?

Regards.



On 1/30/22 09:44, Micke Test via Monitorix-general wrote:
> Hi,
> 
> 
> Yes, your patch works!
> 
> I sent a report at 09:40 local time, and it looks like this.
> 
> 
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/du0.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/du1.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port0i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port1i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port2i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port3i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port4i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port5i.1day.png - libwww-perl/6.52"
> 
> 
> Thank you for your help.
> 
> 
> Regards
> 
> 
> /Michael
> 

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat



_______________________________________________
Monitorix-general mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/monitorix-general

Re: [Monitorix-general] Reports no longer working

[Jordi S. <jo...@fi...>]

Hi,

Thank you very much for your feedback, and sorry for the inconveniences 
of this bug.

Do you give me permission to include your name and email address in the 
Changes file, as the person who found this bug?

Regards.



On 1/30/22 09:44, Micke Test via Monitorix-general wrote:
> Hi,
> 
> 
> Yes, your patch works!
> 
> I sent a report at 09:40 local time, and it looks like this.
> 
> 
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/du0.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/du1.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port0i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port1i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port2i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port3i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port4i.1day.png - libwww-perl/6.52"
> Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/port5i.1day.png - libwww-perl/6.52"
> 
> 
> Thank you for your help.
> 
> 
> Regards
> 
> 
> /Michael
> 

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

Re: [Monitorix-general] Reports no longer working

[Micke T. <mb...@br...>]

Hi,



Yes, your patch works!

I sent a report at 09:40 local time, and it looks like this.



Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/du0.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:01 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/du1.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/port0i.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/port1i.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/port2i.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/port3i.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/port4i.1day.png - libwww-perl/6.52"
Sun Jan 30 09:40:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/port5i.1day.png - libwww-perl/6.52"



Thank you for your help.



Regards



/Michael



-----Original message-----
From: Jordi Sanfeliu via Monitorix-general <mon...@li...>
Sent: Sunday 30th January 2022 8:07
To: Micke Test via Monitorix-general <mon...@li...>
Cc: Jordi Sanfeliu <jo...@fi...>
Subject: Re: [Monitorix-general] Reports no longer working


Hi,

Good news!, I finally was able to reproduce this and indeed there is a bug.

This is the log with the current version:

Sun Jan 30 07:49:00 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:01 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sun Jan 30 07:49:01 2022 - OK - [127.0.0.1] "GET /monitorix - 
libwww-perl/6.60"


and this is the log once patched:

Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system1.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system2.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system3.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system4.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system5.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs01.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs02.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs03.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs04.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET /monitorix - 
libwww-perl/6.60"

The problem is in line 138 of the 'emailreports.pm' module. During the 
parsing of the HTML, the current code is trying find the URLs of the 
images enclosed with single quotes, but they are now enclosed with 
double quotes.

The line 138 should be changed by the following code:

($url) = $_ =˜ m/<img src=['"](.*?)['"] /;

which covers both single or double quotes.

Michael, please, patch manually your file in 
/usr/lib/monitorix/emailreports.pm, then restart Monitorix and let us 

know if that really fixed it.

Thanks.




On 1/29/22 22:21, Micke Test via Monitorix-general wrote:
> Hi,
> 
> 
> OS versions are Debian 10 & Debian 11.
> 
> 
> Using this repository
> 
> deb https://apt.izzysoft.de/ubuntu <https://apt.izzysoft.de/ubuntu> 

> generic universe
> 
> 
> I have a script running every night updating all servers.
> 
> apt-get update && apt-get full-upgrade -y
> 
> 
> I checked the /var/log/monitorix-httpd
> 
> My automated reports are sent at midnight,
> 
> and it looks like this the day before and the day after the 3.14.0 update
> 
> 
> Tue Jan 18 00:00:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
> Fri Jan 19 00:00:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Sat Jan 20 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> 
> 
> Regards
> 
> 
> /Michael
> 
> 
>     Hi,
> 
>     I've updated dozens of servers without any problem so far. If you can
>     bring more information about the OS you are using and how did you update
>     Monitorix, perhaps I could give some help.
> 
>     Just let me know.
>     Regards.
> 
> 
> 
>     On 1/29/22 15:22, Micke Test via Monitorix-general wrote:
>     > Hi,
>     > 
>     > 
>     > I've been using Monitorix for about a year now and everything has been 
>     > working great.
>     > 
>     > But after the update January 18 2022, my reports no longer contain any 
>     > graphs.
>     > 
>     > 
>     > Is this feature broken in 3.14.0 or is there a workaround?
>     > 
>     > 
>     > 
>     > Thanks,
>     > 
>     > 
>     > /Michael
> 


-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat


_______________________________________________
Monitorix-general mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/monitorix-general

Re: [Monitorix-general] Reports no longer working

[Jordi S. <jo...@fi...>]

Hi,

Good news!, I finally was able to reproduce this and indeed there is a bug.

This is the log with the current version:

Sun Jan 30 07:49:00 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:00 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:01 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:01 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
Sun Jan 30 07:49:01 2022 - OK - [127.0.0.1] "GET /monitorix - 
libwww-perl/6.60"


and this is the log once patched:

Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system1.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system2.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system3.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system4.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/system5.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix-cgi/monitorix.cgi - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs01.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs02.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs03.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET 
/monitorix/imgs/fs04.1day.png - libwww-perl/6.60"
Sun Jan 30 07:55:01 2022 - OK - [127.0.0.1] "GET /monitorix - 
libwww-perl/6.60"

The problem is in line 138 of the 'emailreports.pm' module. During the 
parsing of the HTML, the current code is trying find the URLs of the 
images enclosed with single quotes, but they are now enclosed with 
double quotes.

The line 138 should be changed by the following code:

($url) = $_ =~ m/<img src=['"](.*?)['"] /;

which covers both single or double quotes.

Michael, please, patch manually your file in 
/usr/lib/monitorix/emailreports.pm, then restart Monitorix and let us 
know if that really fixed it.

Thanks.




On 1/29/22 22:21, Micke Test via Monitorix-general wrote:
> Hi,
> 
> 
> OS versions are Debian 10 & Debian 11.
> 
> 
> Using this repository
> 
> deb https://apt.izzysoft.de/ubuntu <https://apt.izzysoft.de/ubuntu> 
> generic universe
> 
> 
> I have a script running every night updating all servers.
> 
> apt-get update && apt-get full-upgrade -y
> 
> 
> I checked the /var/log/monitorix-httpd
> 
> My automated reports are sent at midnight,
> 
> and it looks like this the day before and the day after the 3.14.0 update
> 
> 
> Tue Jan 18 00:00:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
> Fri Jan 19 00:00:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Sat Jan 20 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> 
> 
> Regards
> 
> 
> /Michael
> 
> 
>     Hi,
> 
>     I've updated dozens of servers without any problem so far. If you can
>     bring more information about the OS you are using and how did you update
>     Monitorix, perhaps I could give some help.
> 
>     Just let me know.
>     Regards.
> 
> 
> 
>     On 1/29/22 15:22, Micke Test via Monitorix-general wrote:
>     > Hi,
>     > 
>     > 
>     > I've been using Monitorix for about a year now and everything has been 
>     > working great.
>     > 
>     > But after the update January 18 2022, my reports no longer contain any 
>     > graphs.
>     > 
>     > 
>     > Is this feature broken in 3.14.0 or is there a workaround?
>     > 
>     > 
>     > 
>     > Thanks,
>     > 
>     > 
>     > /Michael
> 


-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

Re: [Monitorix-general] Reports no longer working

[Jordi S. <jo...@fi...>]

Hi,

The permission bits in the imgs/ directory could have changed during the 
update procedure.

Check the permissions in the /var/lib/monitorix/www/imgs/ directory, and 
make sure that Monitorix can write images there.

Regards.



On 1/29/22 22:21, Micke Test via Monitorix-general wrote:
> Hi,
> 
> 
> OS versions are Debian 10 & Debian 11.
> 
> 
> Using this repository
> 
> deb https://apt.izzysoft.de/ubuntu <https://apt.izzysoft.de/ubuntu> 
> generic universe
> 
> 
> I have a script running every night updating all servers.
> 
> apt-get update && apt-get full-upgrade -y
> 
> 
> I checked the /var/log/monitorix-httpd
> 
> My automated reports are sent at midnight,
> 
> and it looks like this the day before and the day after the 3.14.0 update
> 
> 
> Tue Jan 18 00:00:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
> Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
> Fri Jan 19 00:00:01 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
> Sat Jan 20 00:00:02 2022 - OK - [127.0.0.1] "GET 
> /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
> 
> 
> Regards
> 
> 
> /Michael
> 

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

Re: [Monitorix-general] Reports no longer working

[Baptiste B. <ly...@ci...>]

On January 29, 2022 10:21:00 PM GMT+01:00, Micke Test via Monitorix-general <mon...@li...> wrote:
>Hi,
>
>
>
>OS versions are Debian 10 & Debian 11.
>
>
>
>Using this repository
>
>deb https://apt.izzysoft.de/ubuntu generic universe
>
>
>
>I have a script running every night updating all servers.
>
>apt-get update && apt-get full-upgrade -y
>
>
>
>I checked the /var/log/monitorix-httpd
>
>My automated reports are sent at midnight,
>
>and it looks like this the day before and the day after the 3.14.0 update
>
>
>
>Tue Jan 18 00:00:01 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
>Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
>Fri Jan 19 00:00:01 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /
>
>Sat Jan 20 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
>
>
>
>Regards
>
>
>
>/Michael
>
>
>
>Hi,
>
>I've updated dozens of servers without any problem so far. If you can 
>
>bring more information about the OS you are using and how did you update 
>Monitorix, perhaps I could give some help.
>
>Just let me know.
>Regards.
>
>
>
>On 1/29/22 15:22, Micke Test via Monitorix-general wrote:
>> Hi,
>> 
>> 
>> I've been using Monitorix for about a year now and everything has been 
>> working great.
>> 
>> But after the update January 18 2022, my reports no longer contain any 
>> graphs.
>> 
>> 
>> Is this feature broken in 3.14.0 or is there a workaround?
>> 
>> 
>> 
>> Thanks,
>> 
>> 
>> /Michael
>
>

Hi Micke,

Could you share the relevant part of /var/log/apt/history.log so we know the exact version you upgraded from (for both Debian version)?

That might help to reproduce the issue.

Best,
-- 
Baptiste BEAUPLAT

Re: [Monitorix-general] Reports no longer working

[Micke T. <mb...@br...>]

Hi,



OS versions are Debian 10 & Debian 11.



Using this repository

deb https://apt.izzysoft.de/ubuntu generic universe



I have a script running every night updating all servers.

apt-get update && apt-get full-upgrade -y



I checked the /var/log/monitorix-httpd

My automated reports are sent at midnight,

and it looks like this the day before and the day after the 3.14.0 update



Tue Jan 18 00:00:01 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system1.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system2.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system3.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system4.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/system5.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs01.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs02.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs03.1day.png - libwww-perl/6.52"
Tue Jan 18 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix/imgs/fs04.1day.png - libwww-perl/6.52"
Fri Jan 19 00:00:01 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"
Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Fri Jan 19 00:00:02 2022 - NOTEXIST - [127.0.0.1] File does not exist: /

Sat Jan 20 00:00:02 2022 - OK - [127.0.0.1] "GET /monitorix-cgi/monitorix.cgi - libwww-perl/6.52"



Regards



/Michael



Hi,

I've updated dozens of servers without any problem so far. If you can 

bring more information about the OS you are using and how did you update 
Monitorix, perhaps I could give some help.

Just let me know.
Regards.



On 1/29/22 15:22, Micke Test via Monitorix-general wrote:
> Hi,
> 
> 
> I've been using Monitorix for about a year now and everything has been 
> working great.
> 
> But after the update January 18 2022, my reports no longer contain any 
> graphs.
> 
> 
> Is this feature broken in 3.14.0 or is there a workaround?
> 
> 
> 
> Thanks,
> 
> 
> /Michael


-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat


_______________________________________________
Monitorix-general mailing list
Mon...@li...
https://lists.sourceforge.net/lists/listinfo/monitorix-general

Re: [Monitorix-general] Reports no longer working

[Jordi S. <jo...@fi...>]

Hi,

I've updated dozens of servers without any problem so far. If you can 
bring more information about the OS you are using and how did you update 
Monitorix, perhaps I could give some help.

Just let me know.
Regards.



On 1/29/22 15:22, Micke Test via Monitorix-general wrote:
> Hi,
> 
> 
> I've been using Monitorix for about a year now and everything has been 
> working great.
> 
> But after the update January 18 2022, my reports no longer contain any 
> graphs.
> 
> 
> Is this feature broken in 3.14.0 or is there a workaround?
> 
> 
> 
> Thanks,
> 
> 
> /Michael


-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
https://www.fibranet.cat

[Monitorix-general] Reports no longer working

[Micke T. <mb...@br...>]

Hi,



I've been using Monitorix for about a year now and everything has been working great.

But after the update January 18 2022, my reports no longer contain any graphs.



Is this feature broken in 3.14.0 or is there a workaround?





Thanks,



/Michael

[Monitorix-general] Monitorix 3.14.0 released

[Jordi S. <jo...@fi...>]

Monitorix 3.14.0 has been released!

This new version introduces three new modules: nvme.pm, which is capable 
of monitoring an unlimited number of NVM Express (NVMe) devices, the 
amdgpu.pm, to monitor also an unlimited number of AMD GPU graphic cards, 
and nvidiagpu.pm which can be seen as an extended version of the current 
module nvidia.pm, as it comes with more detailed statistics.

The rest of new features, changes and bugs fixed are, as always, 
reflected in the Changes file.

Please, check the monitorix.conf(5) man page for all the details.

NOTICE: The configuration file monitorix.conf has been extended with 
important changes.

All users still using older versions are encouraged to upgrade to this 
version.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

[Monitorix-general] Monitorix 3.13.1 released

[Jordi S. <jo...@fi...>]

Monitorix 3.13.1 has been released!

This new version fixes a security bug introduced in the 3.13.0 version 
that lead the HTTP built-in server to bypass the Basic Authentication 
when the option hosts_deny is not defined, which is the default.

Besides this fix, this version also updates the main configuration file 
to add the option hosts_deny = all by default inside the auth 
subsection, in an attempt to make the default behavior more clear.

All users using the 3.13.0 version are advised and encouraged to upgrade 
to this new version, which resolves the security issue.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat

[Monitorix-general] Monitorix 3.13.0 released

[Jordi S. <jo...@fi...>]

Monitorix 3.13.0 has been released!

This new version introduces three new modules: the long-awaited pgsql.pm 
capable of monitoring up to 9 databases of an unlimited number of 
PostgreSQL servers, the redis.pm and tinyproxy.pm which are both also 
capable of monitoring an unlimited number of Redis and Tinyproxy servers 
respectively.

This version also includes some interesting new features. The new CSS 
theming support will allow people to create their own color themes. The 
new support for the ss command in port.pm and nginx.pm modules. The 
ability to map the device names and also to include a title name in 
disk.pm module. The new stacked visualization of network stats available 
on a number of modules, and more.

Also with this new version, Monitorix is able to be executed as a 
regular user instead of root. This is of course subject to the 
capabilities of each module to get statistics without using the superuser.

The rest of new features, changes and bugs fixed are, as always, 
reflected in the Changes file.

Please, check the monitorix.conf(5) man page for all the details.

NOTICE: The configuration file monitorix.conf has been extended with 
important changes.

All users still using older versions are encouraged to upgrade to this 
version.

-- 
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.cat