• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
High cpu usage in 433gpio thread after rpi-update
#21
The name of the protocol has been changed in the nightly.
Check the wiki for any more changes.
 
Reply
#22
HA! I have fixed with the stable Version of pilight!!

Only downgrade the firmware Smile

Code:
rpi-update 2ef601a50b68eebeeb4dc3c6c525855961891be6
 
Reply
#23
@n3ro: You made my day! I also struggled with high cpu usage of the 433gpio module since I upgraded. Downgrade of the firmware solved the issue. Thank you very much for sharing.
 
Reply
#24
Hello,

I have installed pilight stable on a Pi2, but it will not work...

After Reboot the Pi 2 the Web-Gui is shown with the message " Connection lost, touch to reload " But the Surface will not load.

tail -f / var/log/pilight.log

Output Log :
Code:
[Feb 22 22:38:56:433097] pilight-daemon: INFO: client connected, ip 192.168.10.2, port 44715
[Feb 22 22:38:56:433762] pilight-daemon: NOTICE: caching /usr/local/share/pilight/default/pilight.css
[Feb 22 22:38:56:689562] pilight-daemon: INFO: client connected, ip 192.168.10.2, port 44716
[Feb 22 22:38:56:690269] pilight-daemon: NOTICE: caching /usr/local/share/pilight/default/pilight.jquery.theme.css
[Feb 22 22:38:56:837567] pilight-daemon: INFO: client connected, ip 192.168.10.2, port 44717
[Feb 22 22:38:56:838162] pilight-daemon: NOTICE: caching /usr/local/share/pilight/default/favicon.ico
[Feb 22 22:38:57:620600] pilight-daemon: INFO: client connected, ip 192.168.10.2, port 44717
[Feb 22 22:38:57:622142] pilight-daemon: NOTICE: caching /usr/local/share/pilight/default/images/ajax-loader.gif
[Feb 22 22:38:57:781554] pilight-daemon: INFO: client connected, ip 192.168.10.2, port 44718
[Feb 22 22:38:57:782086] pilight-daemon: NOTICE: caching /usr/local/share/pilight/default/apple-touch-icon-iphone-retina-display-hr.png

The log stopps after that...

Checking pilight Status on the Commandline :
Code:
pi@kowalsky ~ $ service pilight status
[FAIL] pilight is not running ... failed!

It seems the pilight daemon crashed ?!

After restarting pilight " service pilight start " the daemon is running but the Web-Gui is still unreachable.

Output pilight Log after restart :

Code:
[Feb 22 23:16:58:975660] pilight-daemon: INFO: version 5.0, commit v5.0
[ Feb 22 23:16:59:76755] pilight-daemon: NOTICE: a pilight daemon was found, clientizing
[ Feb 22 23:16:59:78236] pilight-daemon: INFO: daemon started with pid: 2358

Output pilight-daemon :
Code:
pi@kowalsky ~ $ sudo pilight-daemon -D
[Feb 22 22:58:36:252466] pilight-daemon: DEBUG: ssdp sent search
[Feb 22 22:58:36:346831] pilight-daemon: NOTICE: a pilight daemon was found, clientizing
[Feb 22 22:58:36:348793] pilight-daemon: DEBUG: new thread lirc, 1 thread running
[Feb 22 22:58:36:349295] pilight-daemon: DEBUG: new thread node, 2 threads running
[Feb 22 22:58:36:349856] pilight-daemon: DEBUG: ssdp sent search
[Feb 22 22:58:36:350330] pilight-daemon: DEBUG: new thread sender, 3 threads running
[Feb 22 22:58:36:351690] pilight-daemon: DEBUG: new thread broadcaster, 4 threads running
[Feb 22 22:58:36:364406] pilight-daemon: DEBUG: new thread 433gpio, 5 threads running
[Feb 22 22:58:36:364962] pilight-daemon: DEBUG: new thread receive parser, 6 threads running
[Feb 22 22:58:36:365664] pilight-daemon: DEBUG: new thread firmware upgrader, 7 threads running
[Feb 22 22:58:36:448696] pilight-daemon: DEBUG: socket write succeeded: {"message":"client node","uuid":"0000-00-00-33-95c6f4"}

[Feb 22 22:58:36:451032] pilight-daemon: DEBUG: socket recv: {"message":"accept client"}
[Feb 22 22:58:36:451294] pilight-daemon: DEBUG: socket write succeeded: {"message":"request config"}

[Feb 22 22:58:36:487981] pilight-daemon: DEBUG: socket recv: {"config":{"living":{"name":"Wohnzimmer","order":1,"stehlampe":{"name":"Stehlampe","order":1,"type":1,"uuid":"0000-00-00-60-976529","origin":"0000-00-00-60-976529","timestamp":0,"protocol":[ "kaku_switch" ],"id":[ {"id":1234,"unit":1} ],"state":"off","gui-readonly":0},"relais":{"name":"Relais AnAus","order":2,"type":4,"uuid":"0000-00-00-60-976529","origin":"0000-00-00-60-976529","timestamp":1424559242,"protocol":[ "relay" ],"id":[ {"gpio":0} ],"state":"off","gui-readonly":0,"default-state":"off"},"weather":{"name":"Wetter Abstatt","order":3,"type":3,"uuid":"0000-00-00-60-976529","origin":"0000-00-00-60-976529","timestamp":1424645720,"protocol":[ "openweathermap" ],"id":[ {"location":"abstatt","country":"de"} ],"humidity":8700,"temperature":-100,"poll-interval":900,"sunrise":717,"sunset":1754,"update":1,"sun":"set","gui-show-update":0,"gui-show-sunriseset":1,"gui-show-humidity":1,"gui-show-temperature":1,"min-interval":600,"gui-decimals":2,"device-decimals":2}},"work":{"name":"Büro","order":2,"leselampe":{"name":"Leselampe","order":1,"type":1,"uuid":"0000-00-00-60-976529","origin":"0000-00-00-60-976529","timestamp":0,"protocol":[ "kaku_switch" ],"id":[ {"id":1234,"unit":0} ],"state":"off","gui-readonly":0}},"music":{"name":"Musik","order":3,"Openelec":{"name":"Openelec","order":1,"type":1,"uuid":"0000-00-00-60-976529","origin":"0000-00-00-60-976529","timestamp":0,"protocol":[ "kaku_switch" ],"id":[ {"id":1235,"unit":0} ],"state":"off","gui-readonly":0}}},"version":[ "5.0", "5.0", "v5.0" ],"firmware":{"version":0,"hpf":0,"lpf":0}}

After another reboot pilight crash in the same way as above described.

What have I done wrong ?

Greetings from Germany
 
Reply
#25
Indeed pilight 5 stable does not support Pi2.

You can try the latest development version or
wait for pilight 6 which will be released soon.
If you try the next higher version please read
the wiki carefully before.
Many things have changed since pilight 5.
Terrarium:  RPi Model B Rev 2 / pilight 8.1.2 / stretch
Aquarium: RPi Model B Plus Rev 1.2 / pilight 8.0.6 / jessie
 
Reply
#26
Thanks for your reply.

So i am looking forward to the release of pilight v.6 Big Grin
 
Reply
#27
Hi!

I am running pilight v6 (self compiled from the development sources of the 26. February) on a newly installed Pi2. My pilight-daemon process takes always 20% CPU load! Followed by kworker with 14%. Crying

Code:
16476 root      20   0  125m 3360 1804 S  20,5  0,3   1:38.00 pilight-daemon
16179 root      20   0     0    0    0 S  13,9  0,0  14:28.75 kworker/0:1

And again with pilight daemon stopped:

Code:
16976 root      20   0  5228 2516 2132 R   0,7  0,3   0:00.23 top
    1 root      20   0  2152 1332 1228 S   0,0  0,1   0:04.56 init
    2 root      20   0     0    0    0 S   0,0  0,0   0:00.03 kthreadd
    3 root      20   0     0    0    0 S   0,0  0,0   0:08.94 ksoftirqd/0
 
Reply
#28
And the problem is?
 
Reply
#29
I was wondering if >20% CPU load are normal or not.
 
Reply
#30
If you aren't using a filter yes.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 133 08-13-2019, 05:43 PM
Last Post: curlymo
  Increased CPU usage with version 8.1.5 wimThoelke 13 405 08-07-2019, 08:38 PM
Last Post: curlymo
  High cpu usage Dergo 1 269 02-23-2019, 04:31 PM
Last Post: curlymo
  Update to 8.1.3-18-gab88dcf3 Traeumer 10 1,244 11-01-2018, 10:42 PM
Last Post: Oliver
  Update Error latest Nightly Alex 13 4,026 09-11-2016, 02:51 PM
Last Post: Alex
  pilight Error : default_sa_restorer_v2 & CPU High Tommybear1979 5 2,531 06-30-2016, 07:36 AM
Last Post: pilino1234
Bug Bug report: gpio_switch does not accept high pin numbers woutput 2 2,366 10-12-2015, 03:54 PM
Last Post: woutput
Question pilight-send or pilight-control --> update config.json terrar 3 3,229 10-23-2014, 07:52 PM
Last Post: curlymo
  webgui/ssh very slow .. high cpu usage gneandr 1 2,423 10-01-2014, 06:43 PM
Last Post: creamers
  [Fixed] usage of log-level rien 3 3,630 05-15-2014, 02:52 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)