Graphs (collectd) stopped being updated after auto update

Software SW bugs discussion
1

After the latest automated update, graphs in LUCI are not updated anymore.

turris-collectd-error
turris-collectd-error1036×335 66.4 KB

The graph stopped being updated on 18-Apr-2019 which exactly corresponds to the email sent by Turris updater (see below).

When trying to restart collecd, I get:

root@turris:~# /etc/init.d/collectd restart
configfile: stat (/etc/collectd.conf) failed: No such file or directory
Unable to read config file /etc/collectd.conf.
Error: Reading the config file failed!
Read the syslog for details.
root@turris:~# ls /etc/collectd.conf
ls: /etc/collectd.conf: No such file or directory

The /etc/collectd.conf just disappeared during the update, which I assume is a bug.

Corresponding email notification from Turris updater:

Restart is needed

The system was updated, but some changes will take effect only after reboot. Please reboot the device.

The device will be restarted automatically on Thursday, April 18 at 03:30 AM.

News announcements

• mosquitto, libatsha204, libssh2, dovecot: security updates
• unbound, netdata, youtube-dl, ca-certificates, czmq: update
• python3-certifi, python3-urllib3: new packages
• pakon: minor fixes
• kernel: update

Update notifications

• Installed version 20190110-1 of package ca-certificates
• Installed version 20190110-1 of package ca-bundle
• Installed version 59 of package create_notification
• Installed version 4.4.178-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kernel
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-ipt
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-conntrack
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-nat
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-nathelper
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-base
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-uhci
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb3
• Installed version 4.4.178+2017-01-31-5-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-cfg80211
• Installed version 4.4.178+2017-01-31-5-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-mac80211
• Installed version 4.4.178+2017-01-31-5-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ath
• Installed version 4.4.178+2017-01-31-5-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ath10k
• Installed version 4.4.178+2017-01-31-5-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ath9k-common
• Installed version 4.4.178+2017-01-31-5-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ath9k
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-libphy
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-swconfig
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-switch-mvsw61xx
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-i2c-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-i2c-mv64xxx
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-serial
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-serial-wwan
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-serial-qualcomm
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-hwmon-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-thermal
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-thermal-armada
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-mmc
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-mvsdio
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-wdt-orion
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-default-on
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-gpio
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-heartbeat
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-morse
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-netdev
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ipt-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-netfilter
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-oneshot
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-timer
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-transient
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ledtrig-usbdev
• Installed version 1.9.1-1 of package libunbound
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ipt-nat
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ipt-conntrack
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-llc
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-stp
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-bridge
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ebtables
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-crc-ccitt
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-slhc
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ppp
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-pppox
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-pppoe
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-conntrack6
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-ipt6
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ip6tables
• Installed version 29.2-3.6-1 of package libatsha204
• Installed version 59 of package user-notify
• Installed version git-19.101.33375-d8558fd-1 of package luci-proto-ipv6
• Installed version git-19.101.33375-d8558fd-1 of package luci-proto-ppp
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-firewall
• Installed version git-19.101.33375-d8558fd-1 of package luci-theme-bootstrap
• Installed version git-19.101.33375-d8558fd-1 of package luci-lib-jsonc
• Installed version git-19.101.33375-d8558fd-1 of package luci-lib-ip
• Installed version git-19.101.33375-d8558fd-1 of package luci-lib-nixio
• Installed version git-19.101.33375-d8558fd-10 of package luci-base
• Installed version git-19.101.33375-d8558fd-3 of package luci-mod-admin-full
• Installed version git-19.101.33375-d8558fd-1 of package luci
• Installed version 0.4-1 of package crypto-wrapper
• Installed version 1.5.8-1 of package mosquitto-ssl
• Installed version 0.9.9-3.6-1 of package foris-client-python3
• Installed version 99.7.5-3.6-1 of package foris-common
• Installed version 99.7.5-3.6-1 of package foris-config
• Installed version 99.7.5-3.6-1 of package foris
• Installed version 0.9.9-3.6-1 of package foris-client-bin
• Installed version 5 of package turris-cagen
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ipt-conntrack-extra
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ipt-ipopt
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ifb
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-sched-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-sched
• Installed version 0.11.11-3.6-1 of package foris-controller-app
• Installed version 0.11.11-3.6-1 of package foris-controller-hotplug
• Installed version 0.11.11-3.6-1 of package foris-controller
• Installed version 3.11.4 of package turris-version
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nfnetlink
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-conntrack-netlink
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-commands
• Installed version git-19.101.33375-d8558fd-10 of package luci-i18n-base-en
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-commands-en
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-tun
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-atm
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-pppoa
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-pcompress
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-hash
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-null
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-aead
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-manager
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-ecb
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-sha1
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-mppe
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-iptunnel
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-gre
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-iptunnel6
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ip6-tunnel
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-iptunnel4
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-sit
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-textsearch
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nf-nathelper-extra
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-mii
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-net
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-net-cdc-ether
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-net-rndis
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-wdm
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-net-qmi-wwan
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-serial-option
• Installed version git-19.101.33375-d8558fd-1 of package luci-proto-3g
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-scsi-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ata-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ata-ahci
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-fscache
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-dnsresolver
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-fcrypt
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-pcbc
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-rxrpc
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-afs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-autofs4
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-xor
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-raid6
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-zlib
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-lzo
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-crc32c
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-crc32c
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-btrfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-sha256
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-des
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-md4
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-md5
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-hmac
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-cifs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-configfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-cramfs
• Installed version 4.4.178+git-20151121-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-exfat
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-exportfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-crc16
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-ext4
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-f2fs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-hfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-utf8
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-hfsplus
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-isofs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-jfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-minix
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-vfat
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-msdos
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-nfs-common
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-nfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-oid-registry
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-nfs-common-v4
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-nfsd
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-ntfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-lib-crc-itu-t
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-udf
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fs-xfs
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp1250
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp1251
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp437
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp775
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp850
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp852
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp862
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp864
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp866
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-cp932
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-iso8859-1
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-iso8859-13
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-iso8859-15
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-iso8859-2
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-iso8859-6
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-iso8859-8
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-nls-koi8r
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-md-mod
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-md-linear
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-md-multipath
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-md-raid0
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-md-raid1
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-md-raid10
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-md-raid456
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-storage
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-storage-extras
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb2
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-usb-storage-uas
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ata-ahci-platform
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-ata-mvebu-ahci
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-marvell-cesa
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-dm
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-fuse
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-hd-idle
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-input-core
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-sound-core
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-minidlna
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-samba
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-hd-idle-en
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-minidlna-en
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-samba-en
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-authenc
• Installed version 4.4.178+1.8-mvebu-2 of package kmod-cryptodev
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-user
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-cbc
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-wq
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-rng
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-iv
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-seqiv
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-ctr
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-gf128
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-xts
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-cmac
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-sha512
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-ccm
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-crypto-deflate
• Installed version 4.4.178+0-1-7bc33afbb1b35f5830b2b1b42c9cd8a0-0 of package kmod-veth
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-ahcp
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-mjpg-streamer
• Installed version git-19.101.33375-d8558fd-4 of package luci-app-statistics
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-tinyproxy
• Installed version git-19.101.33375-d8558fd-2 of package luci-app-transmission
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-upnp
• Installed version git-19.101.33375-d8558fd-1 of package luci-app-wol
• Installed version git-19.101.33375-d8558fd-1 of package luci-proto-openconnect
• Installed version git-19.101.33375-d8558fd-1 of package luci-proto-relay
• Installed version 1.12-1 of package libgpg-error
• Installed version 1.6.1-1 of package libgcrypt
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-ahcp-en
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-firewall-en
• Installed version git-19.101.33375-d8558fd-4 of package luci-i18n-statistics-en
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-tinyproxy-en
• Installed version git-19.101.33375-d8558fd-2 of package luci-i18n-transmission-en
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-upnp-en
• Installed version git-19.101.33375-d8558fd-1 of package luci-i18n-wol-en
• Installed version 1.8.1-1 of package libssh2

2

Bug reported to tech.support@turris.cz per https://doc.turris.cz/doc/en/howto/error_reporting.

3

There is UCI(LUCI) config in /etc/config/luci_statistics which generates /etc/collectd.conf. So if you do not have that one, it means final config was not generated.

In some cases individual 'plugins" can cause that you do not have graphs or/and data collected. Check if “rrrd” tool is running/creating files and you have entries for each active plugin. If not, restart it as well.

My experience from past with “no-graphs” is that you have collection active, but rendering part is not working. Solution (in most situation it worked for me) stop service for collecting, delete “luci_statistics-opkg” config, check via LUCI that your config is loaded correctly, ensure all path are valid under collectd (and rrrd). Check your setup of each plugin in same manner. Save and apply and check in terminal if you have /etc/collectd.conf created. If so, you can start collectd/rrrd services.

Around the forum, there are several post (very oldish i believe), regarding issue “no-graphs” “stats-not-working” and so on. There were some glitches in plugin lua files, (for example “ping” plugin has “ts” instead “ds” due oldish collectd vs newer ping-plugin version), which needed manual fix. Lot of them are fixed already. So if you added some plugin before updater brings new version of TOS, it might be the situation, that new plugin is causing no-graphs/no-data issue.

4

Thanks for reply Maxmilian. My point was that the config just disappeared (in fact, it was deleted and replaced by a broken symlink to some path under /var), which is definitely not a correct behavior.

I was able to recreate that config, the rrd data files are created correctly (for some time), they even contain meaningful data as can be seen by running rrdtool dump <path_to_rrd_file>.

Now there is another problem after the upgrade, the collectd itself runs for some time (typically few seconds) after restarting it by /etc/initd.d/collectd restart, but then the service dies (no collectd process found after a minute or so). The service itself runs /usr/sbin/collectd which seems to be in pretty bad shape. Running the binary with -h is fine:

root@turris:~# /usr/sbin/collectd -h
Usage: collectd [OPTIONS]

Available options:
  General:
    -C <file>       Configuration file.
                    Default: /etc/collectd.conf
    -t              Test config and exit.
    -T              Test plugin read and exit.
    -P <file>       PID-file.
                    Default: /var/run/collectd.pid
    -f              Don't fork to the background.
    -h              Display help (this message)

Builtin defaults:
  Config file       /etc/collectd.conf
  PID file          /var/run/collectd.pid
  Plugin directory  /usr/lib/collectd
  Data directory    /var/lib/collectd

collectd 4.10.8.git, http://collectd.org/
by Florian octo Forster <octo@verplant.org>
for contributions see `AUTHORS'

Running it as non-forked to debug it however results in segfault:

root@turris:~# /usr/sbin/collectd -f
Initialization complete, entering read-loop.
uc_update: Value too old: name = turris/df/df-tmpfs; value time = 1556568824; last cache update = 
1556568824;
Segmentation fault
root@turris:~#

My asumption so far is that it has problems with some of the plugins, I’ll be enabling them one-by-one in the config to see which one causes the issues.

Regarding the lua codes for rendering, I’ve found the one for the df plugin at /usr/lib/lua/luci/statistics/rrdtool/definitions/df.lua was totally broken and had to be fixed per Email notifications and graphs broken after latest package upgrade.

5

Another problem with collectd on Turris (perhaps the OpenWrt itself, haven’t checked yet) is that there are just a few plugins and the most importnant, LogFile plugin, is not packaged. The only available collectd plugins are:

root@turris:~# opkg list collectd-mod-*
collectd-mod-cpu - 4.10.8-4
collectd-mod-df - 4.10.8-4
collectd-mod-disk - 4.10.8-4
collectd-mod-interface - 4.10.8-4
collectd-mod-iwinfo - 4.10.8-4
collectd-mod-load - 4.10.8-4
collectd-mod-memory - 4.10.8-4
collectd-mod-network - 4.10.8-4
collectd-mod-processes - 4.10.8-4
collectd-mod-rrdtool - 4.10.8-4
collectd-mod-thermal - 4.10.8-4
collectd-mod-uptime - 4.10.8-4
collectd-mod-wireless - 4.10.8-4
6

I am checking below listed files when update broke my graphs …

list of files

/usr/lib/lua/luci/controller/luci_statistics/luci_statistics.lua
/usr/lib/lua/luci/model/cbi/luci_statistics/thermal.lua
/usr/lib/lua/luci/statistics/rrdtool/definitions/thermal.lua
/usr/lib/lua/luci/statistics/rrdtool/definitions/ping.lua
/usr/lib/lua/luci/statistics/rrdtool/definitions/interface.lua
/usr/bin/stat-genconfig

7

Thanks for the list - now I see you got there ping.lua which is used to render data collected by the ping plugin. Do you use this plugin? I wasn’t able to find any package that would provide ping.so in /usr/lib/collectd. I have only plugins provided by the packages mentioned above, i.e.:

root@turris:~# ls /usr/lib/collectd
cpu.so        interface.so  memory.so     rrdtool.so    wireless.so
df.so         iwinfo.so     network.so    thermal.so
disk.so       load.so       processes.so  uptime.so
8

I am using only provided default plugins. Any try with something new ended with broken stats/graphs. Ping and Interface were causing most of the issues.The list is from like three users reporting some issues. So i am not using all listed ones.

9

Ok, cheers. I was wondering if you were even able to get the ping plugin to work when it’s not packaged. It could be crosscompiled, but definitely not worth the hassle with setting up the toolchain etc.

10

Maybe i install it some times ago. It is working for some time. I 've tried thermal (but horribly failed) :)) The issue with ping one was with “%ti”(wrong) “%di”(correct) in code in ping.lua file.
stats

11

Could you please provide me with the output of the following commands?

 ls -l /usr/lib/collectd/ping.so

and

opkg search /usr/lib/collectd/ping.so

This should be the shared lib that implements the ping plugin. For example, for other plugins (e.g., df), I have:

root@turris:~# ls -l /usr/lib/collectd/df.so
-rwxr-xr-x    1 root     root         13532 Jan 14 16:38 /usr/lib/collectd/df.so
root@turris:~# opkg search /usr/lib/collectd/df.so
collectd-mod-df - 4.10.8-4

As I said above, it’s possible the ping plugin was available some time ago, but was then removed from the opkg repository.

Regarding my problem, I got the graphs back (at least, cpu, thermal and df (after a complete df.lua script replacement)), now I’m finding which plugin causes the segfault to close this.

12
here it is

ls -l /usr/lib/collectd/ping.so
-rwxr-xr-x 1 root root 13460 Mar 5 2018 /usr/lib/collectd/ping.so

opkg search /usr/lib/collectd/ping.so
collectd-mod-ping - 4.10.8-4

13

Ah, I didn’t have the list of packages refreshed. Running opkg update solved the missing ping plugin package, thanks! Now I see there is a huge bundle of new collectd plugins, compared to my list above, including the LogFile plugin. Good.

I’ll be back with the conclulsion of which plugin causes the collectd to segfault soon.

14

Now I got the offending plugin. It’s the collectd processes plugin, provided by collectd-mod-processes - 4.10.8-4.

Whenever I enable the following line in the /etc/collectd.conf, the collectd immediately segfaults:

LoadPlugin processes

The command line:

root@turris:~# /usr/sbin/collectd -f
Initialization complete, entering read-loop.
Segmentation fault

For completeness, it’s config later in the config is just:

<Plugin processes>
        Process "lxc-start"
</Plugin>

Conclusion

To wrap up, there were two issues combined in one that caused the graphs to not being updated anymore:

  1. The /etc/collectd.conf was deleted and replaced by a broken symlink that lead somewhere to /var (didn’t note the exact destination)
  2. The processes plugin provided by package collectd-mod-processes - 4.10.8-4 is probably broken as enabling it causes the collectd to segfault immediately.