Didi Posted June 30, 2018 Posted June 30, 2018 Hi Everyone After several weeks (maybe months) seeking for a solution for my problem I decide to post it here and hope to get a fix for it. At first I still run an Cubietruck with Armbian (everytime the latest Version) with just a few services (Pi-Hole, RPi-Monitor) and for future use Apache, MariaDB and PHPmyadmin (just installed and running, but with no content). Now to the problem itself: The Cubietruck runs approximatly 6 to 10 days and then it's get stuck. Only a reset solve the problem for the next 6 to 10 days. On every crash I checked the syslog and it always show the following lines as latest entries: Jun 29 15:17:28 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes... Jun 29 15:17:28 localhost systemd[1]: Started Update UTMP about System Runlevel Changes. Jun 29 15:17:28 localhost systemd[1]: Startup finished in 9.355s (kernel) + 29.863s (userspace) = 39.218s. Jun 29 15:17:29 localhost ntpd[1280]: Soliciting pool server 46.163.88.237 Jun 29 15:17:29 localhost ntpd[1280]: Soliciting pool server 144.76.3.142 Jun 29 15:17:29 localhost ntpd[1280]: Soliciting pool server 78.47.184.132 Jun 29 15:17:29 localhost ntpd[1280]: Soliciting pool server 81.7.16.52 Jun 29 15:17:30 localhost ntpd[1280]: Soliciting pool server 129.70.132.37 Jun 29 15:17:30 localhost ntpd[1280]: Soliciting pool server 31.172.86.173 Jun 29 15:17:30 localhost ntpd[1280]: Soliciting pool server 131.234.137.64 Jun 29 15:17:30 localhost ntpd[1280]: Soliciting pool server 80.151.151.109 Jun 29 15:17:31 localhost ntpd[1280]: Soliciting pool server 2a02:c207:2010:9464::3 Every further entry were made after the reset. Have anybody else the same problem or a possible solution for me ?? Thank you in advance. P.S.: The Cubietruck is not reachable via internet
guidol Posted June 30, 2018 Posted June 30, 2018 Did you check the space of /var/log because of the limitations of log2ram? 2nd: sometimesyou could have problems between the Pihole Webserver and the apache if you didnt change the port numbers and do only start apache. But by 6-10 days I will bet on a log2ram problem
Didi Posted June 30, 2018 Author Posted June 30, 2018 Sorry, I haven't mentioned that the Pi-Hole port is changed to 8080 and port 80 is for Apache (even for further use). I checked my logs twice and there is no logs of log2ram. /usr/share/log2ram /usr/sbin/log2ram /etc/cron.daily/log2ram /etc/default/log2ram This is the complete result of find
Recommended Posts