rw-r-r- 1 root root 7107 Mar 5 01:19 dpinstall.log I’ve put together a selection from the 100’s of log lines …Īny help or suggestions would be very doesn’t exist. Mar 5 10:16:31 emonpi-node-13 lwrfd: Failed to connect to MQTT, return code -1 Mar 5 10:16:31 emonpi-node-13 run-parts: run-parts: executing /etc/redis//00_example Mar 5 10:16:31 emonpi-node-13 lwrfd: Reconnecting to MQTT. Mar 5 10:16:31 emonpi-node-13 systemd: Starting Advanced key-value store. Mar 5 10:16:31 emonpi-node-13 systemd: Stopped Advanced key-value store. Mar 5 10:16:31 emonpi-node-13 systemd: rvice: Service hold-off time over, scheduling restart. Mar 5 10:16:31 emonpi-node-13 systemd: rvice: Failed with result 'exit-code'. Mar 5 10:16:31 emonpi-node-13 systemd: rvice: Unit entered failed state. Mar 5 10:16:31 emonpi-node-13 systemd: Failed to start Advanced key-value store. Mar 5 10:16:31 emonpi-node-13 systemd: rvice: Control process exited, code=exited status=1 Mar 5 10:16:31 emonpi-node-13 redis-server: Can't open the log file: No such file or directory Mar 5 10:16:31 emonpi-node-13 redis-server: > 'logfile /var/log/redis/redis-server.log' Mar 5 10:16:31 emonpi-node-13 redis-server: Reading the configuration file, at line 163

One caught my eye – Mar 5 10:16:31 emonpi-node-13 redis-server: *** FATAL CONFIG FILE ERROR *** Now on the edge of my ‘comfort/knowledge zone’, I saw many reports – error, fatal, warn, warning, etc I downloaded /var/log to my Windows PC (winSCP) and examined it (Notepad++). But now I could not browse to the emonTx/RPi instance which was running but now only controllable via SSH. Everything seemed fine so I powered down and examined the USB HDD on my windows PC. I then commented out (in fstab) the tmpfs for /var/log and re-booted. I started over – burned a fresh image, copied rootfs & data partitions to USB HDD and ran from that. So watchman (also running the emonSD image) has a duplicate of all inputs. The emonTx/RPi’s each with a different Node number communicate with watchman via an EmonHubEmoncmsHTTPInterfacer.

Given the same problem is on identical instances then – SDHC, hardware & power supply issues can be ruled out? And as rootfs and data partitions are run from a USB spinning hard drive, space is not a problem.

HTTP, 403 Forbidden (Apache httpd 2.4.25)Īnd, I also could not connect via ssh/puTTy – connection refused. Using a network scanner, I could see an instance and its IP address. This time it was on two different (but identical) instances of emonTx/RPi running emonSD image Oct 2018. Server unable to read htaccess file, denying access to be safeĪpache/2.4.25 (Raspbian) Server at 192.168.0.167 Port 80 You don’t have permission to access / on this server. Darn it! Just days after my last post (Recurring problem 23 Feb), it’s happened again … twice … when trying to browse

Phpmyadmin not found raspberry pi