statistics is pretty binary for many modules... if they are not installed or the config is incorrect the service will fail to start... it will usually tell you in the log... but you left those lines out... (edit: my bad.. with a 'uci parse error' you probably wouldn't get far enough for a 'module load' error)
prime cantidates are: disk iptables irq... just keep restarting... checking the log.... and removing sections until you find the culprit...
(quite possibly I have a setup bug - i.e. if you've unplugged a disk recently that could do it...)
i do my best to give a default 'full featured' config... but anything specific is really up to the end user to tweak... it's way too difficult to predict or accomodate for all setups... that said... if i've got a bug... i'd rather remove a section than have it work half the time...
totally understable. i do not expect you to solve my misconfigurations. my knowledge to track down such things is...narrow. i am very grateful for your work. for completeness-reasons here is mine.
please feel free to ignore. i really dont want to waste your time.
/etc/config/luci_statistics
/etc/config/luci_statistics: line 2: config: command not found
/etc/config/luci_statistics: line 3: option: command not found
...
/etc/config/luci_statistics: line 188: config: command not found
/etc/config/luci_statistics: line 190: config: command not found
/etc/config/luci_statistics: line 191: option: command not found
/etc/config/luci_statistics: line 192: list: command not found
/etc/config/luci_statistics: line 193: list: command not found
/etc/config/luci_statistics: line 195: config: command not found
/etc/config/luci_statistics: line 196: option: command not found
/etc/config/luci_statistics: line 197: option: command not found
/etc/config/luci_statistics: line 199: config: command not found
/etc/config/luci_statistics: line 200: option: command not found
/etc/config/luci_statistics: line 201: list: command not found
/etc/config/luci_statistics: line 202: list: command not found
Sat Jul 3 02:50:37 2021 daemon.err collectd[22313]: Configuration file /tmp/collectd.conf is empty.
Sat Jul 3 02:50:37 2021 daemon.err collectd[22313]: Error: Parsing the config file failed!
Sat Jul 3 02:50:37 2021 daemon.info procd: Instance collectd::instance1 s in a crash loop 6 crashes, 0 seconds since last crash
line 190 is near the bottom ( good think phpeditor shows lline numbers ) and is near the first 'disk' section which there should not be two of?
(do does look like a bug with 'disk' being added)... remove that disk section and see how it goes...
lines-to-remove
config statistics 'collectd_disk'
option enable '1'
list Disks 'mmcblk0p1'
list Disks 'mmcblk0p2'
I just wanted to report, that I have upgraded to 3.2 once again and can confirm, that the mac changes do apply properly, if a valid mac is being used. As I had used multiple different mac generators would say, that it made sense to add a check for invalid mac before setting it, so others cannot run into this issue again.
Not sure if this is the right place to ask but I want to try. - I am just installing dockerd, docker-compose, docker and luci-app-dockerman. On installing luci-app-dockerman I get this one:
Collected errors:
* check_data_file_clashes: Package libwebsockets-full wants to install file /usr/lib/libwebsockets.so
But that file is already provided by package * libwebsockets-openssl
* check_data_file_clashes: Package libwebsockets-full wants to install file /usr/lib/libwebsockets.so.17
But that file is already provided by package * libwebsockets-openssl
* opkg_install_cmd: Cannot install package luci-app-dockerman.
Is it safe to have luci-app-dockermans installation overwrite libwebsockes.so?
I have been looking for a configuration option in lucy, that allows to set the WIFI to 2.4ghz (some older devices dont support 5ghz) or optimally to run it in dual band, can you eventually hint me where to look for it?
Im have been searching for the past 15 minutes, I cant seem to find it. I went through all links trying to find 'index' in them but I didnt find it - searched the thread for 'ac mode' '2.4 ghz' 'ac mode' and so on, ill keep searching.
Ah darn, I should have seen that one, thank you for helping out.
EDIT: Alright I have now changed operating frequency to Legacy with 2.4ghz but as it seems (if I haven't forgotten something) the change is not reflected in config-wifi-device:
G'Day all, newbie here. Got a rpi4b on the way and want to give Openwrt a crack to use as my router, and relegate my ERX-SFP to poe switch status. Got a UE300 ethernet dongle to accompany. Just wanted to confirm if I should use 3.1 vs 3.2 branch? Is there a stability difference? Have a fairly basic config, just a separate VLAN for IoT devices, a few extra firewall rules as applicable and use Wireguard for remote access/managment. Wireless won't be used, access points in house are powered via switch.
Any tips appreciated. Looking forward to giving it all a crack.