node process hits 100% CPU every few minutes
Hi folks,
since a few weeks the node.js process uses 100% CPU performance every few minutes (sawtooth graph in system sensor)
Webfrontend is very slow then indeed. Any hints to analyse this are highly welcome 
running:
Linux pimatic 4.4.21+ #911 Thu Sep 15 14:17:52 BST 2016 armv6l GNU/Linux
node.js v4.6.2
Thank you in advance.
Kind Regards,
Paule
@cybolord Did you inspect the mobile frontend with Chrome Developer?
Load page in Chrome and press F12, what does it say?
@gleno0h said in node process hits 100% CPU every few minutes:
@cybolord Did you inspect the mobile frontend with Chrome Developer?
Load page in Chrome and press F12, what does it say?
Mmmh, I am not an HTML expert and IMO nothing special to see - for what especially should I watch out please?
@cybolord well, anything that is written in a red font lol! You should see what the page is loading and if anything is causing error’s.
Nope - nothing special in Chrome devtools console…
Just to clarify: no Access from any device to the webfrontend BUT Node process Runs high every few minutes…
Groetjes uit Keulen
@cybolord please try this:
sudo wget https://transfer.sh/Pr2wZ/PimaticLog.sh
sudo chmod +x PimaticLog.sh
sudo ./PimaticLog.sh
Post the output here.
@gleno0h …here we go - the console output…
pi@pimatic:~ $ sudo ./PimaticLog.sh
JQ is needed but not installed. Installing...
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
libunbound2 unbound-anchor
Verwenden Sie »apt-get autoremove«, um sie zu entfernen.
Die folgenden NEUEN Pakete werden installiert:
jq
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 128 nicht aktualisiert.
Es müssen 97,2 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 237 kB Plattenplatz zusätzlich benutzt.
WARNUNG: Die folgenden Pakete können nicht authentifiziert werden!
jq
E: Es gab Probleme und -y wurde ohne --force-yes verwendet.
./PimaticLog.sh: Zeile 17: jq: Kommando nicht gefunden.
sudo: gpio: Kommando nicht gefunden
./PimaticLog.sh: Zeile 24: jq: Kommando nicht gefunden.
./PimaticLog.sh: Zeile 25: jq: Kommando nicht gefunden.
./PimaticLog.sh: Zeile 26: jq: Kommando nicht gefunden.
Copy the output from here to the forum!
___ _ _ _
/ _ (_)_ __ ___ __ _| |_(_) ___
/ /_)/ | |_ \ _ \ / _/ | __| |/ __|
/ ___/| | | | | | | (_| | |_| | (__
\/ |_|_| |_| |_|\__,_|\__|_|\___|
Status of Pimatic :
Process running with pid 1381.
Kernel version: 4.4.21+
Node version: v4.6.2
Node location: node: /usr/local/bin/node
NPM version: 2.15.11
WiringPI
GCC++ version: gcc (Raspbian 4.9.2-10) 4.9.2
Checking service script location: /etc/init.d/pimatic
Validating config.json:
Config is valid!
Loading plugins(from config.json):
Homeduino version:
Homeduino config:
@cybolord seems your system is outdated as it cant install the application JQ. Try it again but first run sudo apt-get update. Then run it again and on the last question press Y to output log file.
The output should be similar to this;
root@raspberrypi:/home/pi# ./PimaticLog.sh
JQ is installed. Resuming...
Copy the output from here to the forum!
___ _ _ _
/ _ (_)_ __ ___ __ _| |_(_) ___
/ /_)/ | |_ \ _ \ / _/ | __| |/ __|
/ ___/| | | | | | | (_| | |_| | (__
\/ |_|_| |_| |_|\__,_|\__|_|\___|
Status of Pimatic 0.9.39:
Process running with pid 624.
Kernel version: 4.1.18+
Node version: v4.4.5
Node location: node: /usr/local/bin/node
NPM version: 2.15.5
WiringPI gpio version: 2.32
GCC++ version: gcc (Raspbian 4.9.2-10) 4.9.2
Checking service script location: /etc/init.d/pimatic
Validating config.json:
Config is valid!
Loading plugins(from config.json):
"shell-execute" "ping" "sunrise" "cron" "homeduino" "sysinfo" "mobile-frontend" "knmi-weather" "pushover" "pushbullet" "dimmer-proxy" "angular-material-frontend"
Homeduino version: 0.9.11
Homeduino config: { "plugin": "homeduino", "driver": "serialport", "driverOptions": { "serialDevice": "/dev/ttyUSB0", "baudrate": 115200 }, "receiverPin": 0, "transmitterPin": 4, "debug": true, "enableReceiving": true, "active": true, "rfrepeats": 7 }
Do you want to add pimatic-daemon reports (Y/N)?y
15:13:10.017 [pimatic-homeduino] debug: data: "PING" 15:18:30.035 [pimatic-homeduino] debug: data: "PING" 15:23:50.050 [pimatic-homeduino] debug: data: "PING" 15:29:10.066 [pimatic-homeduino] debug: data: "PING" 15:34:30.096 [pimatic-homeduino] debug: data: "PING" 15:39:50.109 [pimatic-homeduino] debug: data: "PING" 15:44:50.130 [pimatic-homeduino] debug: data: "PING" 15:50:10.149 [pimatic-homeduino] debug: data: "PING" 15:51:45.508 [pimatic-homeduino] debug: Sending Protocol: dimmer1 id:10 unit:1 dimlevel:11 all:false Pin:4 Repeats:7 15:51:45.633 [pimatic-homeduino] debug: data: "ACK" 15:51:46.263 [pimatic-homeduino] debug: data: "11959565{"buckets":{"0":"260","1":"1300","2":"2700","3":"10400","4":"0","5":"0","6":"0","7":"0"},"repeats":"7","pulse":"0200010001000100010001000100010001000100010001000100010001000100010001000100010001000100010100000101000001000100000001000100010100010000010100010003","protocol":"dimmer1","unit":"3","id":"10"}" unknown message received: 11959565{"buckets":{"0":"260","1":"1300","2":"2700","3":"10400","4":"0","5":"0","6":"0","7":"0"},"repeats":"7","pulse":"0200010001000100010001000100010001000100010001000100010001000100010001000100010001000100010100000101000001000100000001000100010100010000010100010003","protocol":"dimmer1","unit":"3","id":"10"} 15:51:46.284 [pimatic-homeduino] debug: data: "UDP Packet 0 done" unknown message received: UDP Packet 0 done 15:51:46.308 [pimatic-homeduino] debug: data: "UDP Packet 1 done" unknown message received: UDP Packet 1 done 15:51:46.356 [pimatic-homeduino] debug: data: "UDP Packet 2 done" unknown message received: UDP Packet 2 done 15:51:46.407 [pimatic-homeduino] debug: data: "UDP Packet 3 done" unknown message received: UDP Packet 3 done 15:51:47.188 [pimatic-homeduino] debug: Sending Protocol: dimmer1 id:10 unit:1 dimlevel:15 all:false Pin:4 Repeats:7 15:51:47.241 [pimatic-homeduino] debug: data: "ACK" 100 15:51:47.893 [pimatic-homeduino] debug: data: "10337140{"buckets":{"0":"260","1":"1300","2":"2700","3":"10400","4":"0","5":"0","6":"0","7":"0"},"repeats":"7","pulse":"0200010001000100010001000100010001000100010001000100010001000100010001000100010001000100010100000101000001000100000001000100010100010001000100010003","protocol":"dimmer1","unit":"3","id":"10"}" unknown message received: 10337140{"buckets":{"0":"260","1":"1300","2":"2700","3":"10400","4":"0","5":"0","6":"0","7":"0"},"repeats":"7","pulse":"0200010001000100010001000100010001000100010001000100010001000100010001000100010001000100010100000101000001000100000001000100010100010001000100010003","protocol":"dimmer1","unit":"3","id":"10"} 15:51:47.906 [pimatic-homeduino] debug: data: "UDP Packet 0 done" unknown message received: UDP Packet 0 done 15:51:47.933 [pimatic-homeduino] debug: data: "UDP Packet 1 done" unknown message received: UDP Packet 1 done 15:51:47.982 [pimatic-homeduino] debug: data: "UDP Packet 2 done" unknown message received: UDP Packet 2 done 15:51:48.030 [pimatic-homeduino] debug: data: "UDP Packet 3 done" unknown message received: UDP Packet 3 done 15:56:50.160 [pimatic-homeduino] debug: data: "PING" 16:02:10.173 [pimatic-homeduino] debug: data: "PING" 16:07:30.191 [pimatic-homeduino] debug: data: "PING" 16:12:50.208 [pimatic-homeduino] debug: data: "PING" 16:18:10.224 [pimatic-homeduino] debug: data: "PING" 16:23:30.238 [pimatic-homeduino] debug: data: "PING" 16:28:50.256 [pimatic-homeduino] debug: data: "PING" 16:34:10.269 [pimatic-homeduino] debug: data: "PING" 16:39:10.294 [pimatic-homeduino] debug: data: "PING" 16:44:30.313 [pimatic-homeduino] debug: data: "PING" 16:49:50.331 [pimatic-homeduino] debug: data: "PING" 16:54:50.368 [pimatic-homeduino] debug: data: "PING" 16:59:50.392 [pimatic-homeduino] debug: data: "PING" 17:05:10.410 [pimatic-homeduino] debug: data: "PING" 17:10:30.424 [pimatic-homeduino] debug: data: "PING" 17:15:50.439 [pimatic-homeduino] debug: data: "PING" 17:21:10.458 [pimatic-homeduino] debug: data: "PING"
End of copy
…maybe this is the “main issue”?! should I re-install the whole thing on a new SDCARD ?!
@cybolord do a integrity check, https://forum.pimatic.org/topic/14/database-tips/2
@gleno0h said in node process hits 100% CPU every few minutes:
@cybolord do a integrity check, https://forum.pimatic.org/topic/14/database-tips/2
Do I understand this right? it is necessary for DB integrity check to use a WINDOWS based PC?! 
@cybolord ill asume everything is installed like the tutorial, if not, replace paths;
pimatic.js stop
sqlite3 /home/pi/pimatic-app/pimatic-database.sqlite "PRAGMA integrity_check"
@cybolord said in node process hits 100% CPU every few minutes:
…maybe this is the “main issue”?! should I re-install the whole thing on a new SDCARD ?!
…a few weeks after: and YES !
–> all Errors and misbehaviours were resulting from a bad SDCARD indeed!
–> pimatic is running absolutely fine now since 8 weeks on new SD - no SQLITE errors nor bad event log entries nor high CPU utilization anymore
P.S.: how can I mark this topic as “RESOLVED” plz?