there may have been a section added for interface 'gether' in networking...
but it should not really cause problems unless you have other 'usbX' (tethering/modem) devices in use or use 10.11.12.x as a subnet... [another not-so-smart idea of mine]
Sat Jul 3 00:00:25 2021 daemon.err collectd[16650]: Configuration file /tmp/collectd.conf is empty.
Sat Jul 3 00:00:25 2021 daemon.err collectd[16650]: Error: Parsing the config file failed!
Sat Jul 3 00:00:25 2021 daemon.info procd: Instance collectd::instance1 s in a crash loop 6 crashes, 0 seconds since last crash
/:
i recognised it earlier in syslog but thought it worked before, didnt touched it, so cant be it, just ignore. i am failure. still wonder why it makes the whole menu gone.
also noticed this before in syslog when it error-stated when updating pkg's (iirc) 'last time was bla and new timestamp is older' (likewise).
pheditor is nice to have, didnt knew it before.
tty links to 'rpi-ip/ttyd' which then gets forwarded to 'ttyd.router' and (at least for me) cant be resolved.
maybe dns-problem on my side, but atm it has no usecase for me as long as ssh is reliable, which it has been since forever. seems like pheditor also has a 'terminal' in the bottom-part. strange times.
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?