Hi. I'm also on RPI 4 v 9.2.1. I don't even have the option to upgrade in the GUI
Posts by anand0412
-
-
Hi. Sorry. I think top only shows one one core. I installed htop and the results makes more sense. I guess my system is okay afterall
-
Hi guys. I'm running libreelec 9.2.1 on raspberry pi 4b 4GB. I also have the docker addon installed with home assistant and nginx letsencrypt. when i run the top command, i get this results.
When idle, kodi.bin cpu usage is about 40 - 50%
Code
Display Moretop - 09:51:45 up 1 day, 16:55, 2 users, load average: 1.02, 1.60, 1.20 Tasks: 140 total, 1 running, 139 sleeping, 0 stopped, 0 zombie %Cpu(s): 11.1 us, 0.8 sy, 0.0 ni, 87.5 id, 0.6 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3662.4 total, 815.2 free, 499.6 used, 2347.5 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 2954.2 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 685 root 20 0 1127352 293188 50628 S 44.9 7.8 828:06.92 kodi.bin 511 root 20 0 2924 1728 1484 S 0.7 0.0 0:00.94 top 642 root 20 0 2948 1816 1400 R 0.7 0.0 0:00.09 top 1075 root 20 0 218416 100432 20432 S 0.7 2.7 39:18.39 python3 23 root 0 -20 0 0 0 I 0.3 0.0 0:04.91 kworker/2:0H-kblockd 84 root 1 -19 0 0 0 S 0.3 0.0 8:17.18 vchiq-slot/0 352 root 20 0 963768 48704 34436 S 0.3 1.3 10:39.87 dockerd 377 root 20 0 970832 25616 19492 S 0.3 0.7 8:05.82 containerd 501 root 20 0 5244 4004 3608 S 0.3 0.1 0:00.22 sshd 18736 root 20 0 24368 11128 4800 S 0.3 0.3 9:03.62 f2b/server 22626 root 20 0 0 0 0 I 0.3 0.0 0:05.04 kworker/2:1-events_power_efficient 31658 root 0 -20 0 0 0 I 0.3 0.0 0:00.18 kworker/0:2H-mmc_complete 32509 root 20 0 0 0 0 I 0.3 0.0 0:00.93 kworker/0:3-events 1 root 20 0 25572 5592 4656 S 0.0 0.1 0:04.34 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.12 kthreadd 3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp 8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq 9 root 20 0 0 0 0 S 0.0 0.0 0:07.93 ksoftirqd/0 10 root 20 0 0 0 0 I 0.0 0.0 1:52.29 rcu_sched 11 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_bh 12 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/0 13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0 14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1 15 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/1 16 root 20 0 0 0 0 S 0.0 0.0 0:01.51 ksoftirqd/1 19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/2 20 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/2 21 root 20 0 0 0 0 S 0.0 0.0 0:01.49 ksoftirqd/2 24 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/3 25 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/3 26 root 20 0 0 0 0 S 0.0 0.0 0:01.35 ksoftirqd/3 29 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs 30 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns 35 root 20 0 0 0 0 S 0.0 0.0 0:00.00 oom_reaper 36 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 writeback 37 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kcompactd0 38 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 crypto 39 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kblockd 40 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdogd 41 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rpciod 42 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/u9:0-hci0 43 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 xprtiod 48 root 20 0 0 0 0 S 0.0 0.0 0:03.18 kswapd0 49 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nfsiod 50 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 cifsiod 51 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 cifsoplockd 80 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 iscsi_eh
When playing a video from local library, the kodi.bin's cpu usage drops to about 20% - 30%
Code
Display Moretop - 10:00:10 up 1 day, 17:03, 2 users, load average: 2.28, 1.80, 1.48 Tasks: 143 total, 1 running, 142 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.4 us, 1.7 sy, 0.0 ni, 72.2 id, 22.7 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3662.4 total, 788.1 free, 511.3 used, 2363.0 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 2950.4 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 685 root 20 0 1198456 304212 50628 D 21.6 8.1 831:23.38 kodi.bin 84 root 1 -19 0 0 0 S 0.7 0.0 8:19.56 vchiq-slot/0 1075 root 20 0 218056 100280 20432 S 0.7 2.7 39:25.63 python3 10 root 20 0 0 0 0 I 0.3 0.0 1:53.54 rcu_sched 88 root 10 -10 0 0 0 S 0.3 0.0 1:04.18 SMIO 97 root -2 0 0 0 0 S 0.3 0.0 0:03.74 v3d_bin 98 root -2 0 0 0 0 S 0.3 0.0 0:04.96 v3d_render 352 root 20 0 963768 48704 34436 S 0.3 1.3 10:41.82 dockerd 377 root 20 0 970832 25616 19492 S 0.3 0.7 8:07.36 containerd 511 root 20 0 2924 1728 1484 S 0.3 0.0 0:04.53 top 1 root 20 0 25572 5592 4656 S 0.0 0.1 0:04.34 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.12 kthreadd 3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp 8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq 9 root 20 0 0 0 0 S 0.0 0.0 0:07.98 ksoftirqd/0 11 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_bh 12 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/0 13 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0 14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1 15 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/1 16 root 20 0 0 0 0 S 0.0 0.0 0:01.53 ksoftirqd/1 19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/2 20 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/2 21 root 20 0 0 0 0 S 0.0 0.0 0:01.51 ksoftirqd/2 23 root 0 -20 0 0 0 I 0.0 0.0 0:04.93 kworker/2:0H-kblockd 24 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/3 25 root rt 0 0 0 0 S 0.0 0.0 0:00.01 migration/3 26 root 20 0 0 0 0 S 0.0 0.0 0:01.35 ksoftirqd/3 29 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs 30 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns 35 root 20 0 0 0 0 S 0.0 0.0 0:00.00 oom_reaper 36 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 writeback 37 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kcompactd0 38 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 crypto 39 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kblockd 40 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdogd 41 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rpciod 42 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/u9:0-hci0 43 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 xprtiod 48 root 20 0 0 0 0 S 0.0 0.0 0:03.18 kswapd0 49 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 nfsiod 50 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 cifsiod 51 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 cifsoplockd 80 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 iscsi_eh 83 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 DWC Notificatio 85 root 1 -19 0 0 0 S 0.0 0.0 0:08.22 vchiq-recy/0 86 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 vchiq-sync/0
When the video stops playing, it bumps back up to about 40 % ?
I'm not sure how this works. Is that how it should be? is 40% cpu usage on idle too high?
Best regards,
Anand
-
Hi, aptalca , thanks for the detailed explanation.
Docker addons are not the same as docker containers you manually create. Addons use systemd to manage the containers in an automated fashion.
I did not know that.
"started for the first time" refers to starting it with no existing persistent data. The persistent data (including the certs) reside in the userdata addon_data folder by default. As long as it's there, certs are not regenerated until they get close to expiration.
thanks for clarifying.
In any case, it sounds like this is a case of the xy problem. Let's focus on the boot delay. I assure you I'm running plenty of docker addons here on an rpi4 with no noticeable delay. The only delay I'm observing is "waiting for network" before kodi starts.
Check the kodi log to see what's holding things up during boot. Also check the addon logs with journalctl -u docker.linuxserver.letsencrypt and journalctl -u docker.linuxserver.duckdns (you can also try journalctl -u docker.linuxserver.updater).
---
EDIT: As a test, I set up all three containers in question, two as addons and one manually. I even created homeassistant with the same docker run from your other thread, all on an rpi4 with le 9.2.3 and I experience no boot delay at all.
Since my earlier setup was unusable, i uninstalled the linux io addons. then, I manually created a contained for nginx/letsencrypt with this command
docker create --name=letsencrypt --cap-add=NET_ADMIN --net=host -e PUID=1000 -e PGID=1000 -e TZ=Asia/Kuala_Lumpur -e URL=subdomain.duckdns.org -e SUBDOMAINS=www,ha -e VALIDATION=http -e [email protected] -p 443:443 -p 80:80 -v /storage/letsencrypt:/config --restart unless-stopped linuxserver/letsencrypt
I ran duckdns as an integration with HA. i guess i dont need another docker for it.
Its all working great now with no problems. Just that I dont know if this is a best practice case.
Having said that, i feel like i owe you a test. I didn't expect you to do so much to help me out. really appreciate it. Thank you alot.
With that said, make sure you update your addons and refresh the repos. There was a brief period of time where the addon updater caused a boot delay of about 10 minutes due to a bug in its systemd config. It was fixed shortly after.
This could have been my problem. But then, i also experienced extreme system lag while using kodi.
Will update
In the meantime, not sure if this log is any helpful.
-
My suspicion seems to be further supported by this article at Let's Encrypt, Nginx & Reverse Proxy Starter Guide - 2019 Edition .
"The validation is performed when the container is started for the first time. Nginx won't be up until ssl certs are successfully generated."
If that's the case, ssl validation will be performed on every restart crippling libreelec for a long time. Any way i can get around this?
-
Hi. thanks for the reply.
Something must be wrong with my setup then. Libreelec with kodi and home assistant in a docker runs fine and smooth. When I restart libreelec, the HA docker (which I installed using command line) does not get destroyed and recreated.
Nginx letsencrypt and duck dns gets destroyed and recreated.
Without nginx letsencrypt and duckdns, i can restart my libreelec (with HA) in about 30 seconds. With nginx letsencrypt and duckdns, its about 10 to 15 mins and kodi appears laggy. I suspect nginx is trying to create ssl certificare on every boot.
I have now uninstalled nginx letsencrypt and duckdns and not sure how to find the relevant logs. If you can guide me I will provide it. The system becomes unusable with those addons.
Just to clarify, i did let it run overnight the first time with nginx letsencrypt installed to allow it to process the certificates.
-
Hi. I did some reading and came across this
LinuxServer.io docker addons and general docker info .
Updater:
The updater addon is a dependency for all linuxserver docker addons and is responsible for refreshing the docker images in the background. By doing so, it ensures that when Libreelec is restarted, the new container is created based on the latest image, but it doesn't have to download the image, potentially holding up the start process.
Is there a way for me to turn this off?
-
Hi. I am new to libreelec, docker and linux.
I have 3 docker container installed. One for home assistant via docker run -d command. Another 2 through the linux io repo ( duck dns and nginx letsencrypt).
When i restart libreelec, it took a very long time to boot up . A good 10 mins. I ran docker -ps command. It shows that duck dns and nginx letsencrypt comtainer was just created when it booted up.
Home assistant docker on the other hand just started the existing container.
I can see this by the difference in created vs status.
Is it supposed to be like this or am i doing something wrong.
Also, is these setup too heavy for a raspberry pi 4 4gb?
-
Hi. Thanks. Got it resolved.
Used this command i got from HA forum.
docker run -d --name="home-assistant" -v /storage/hass-config:/config -v /etc/localtime:/etc/localtime:ro -p 8123:8123/tcp --restart=unless-stopped homeassistant/raspberrypi3-homeassistant
Works perfectly now.
Thanks
-
Identified the problem. The command above sends it into a restart loop. Now i dont know why that is happening
-
Hi. Im trying to use home assistant in libreelec.
Device : Raspberry pi4 4gb
Libreelec v. 9.2.1
Installed docker.
Installed home assistant with this command:-
docker run --init -d --name="home-assistant" -e "TZ=Asia/Kuala_Lumpur/" -v /storage/dockerconfig/home-assistant/:/config --net=host --restart=unless-stopped homeassistant/home-assistant:stable
Installed without any error. I get a Docker notification in the corner stating name:home-assistant | action:start.
My problem is i have no idea how to access home assistant web interface.
Tried :-
http://ip address:8123
Any help is much appreciated.
Thanks.
-
Thanks guys. Looks like its some trial and error time
-
Does your TV have an IR remote? If it does, it should be able to be "LEARNT" You don't need a smart TV
Just to clarify, the IR blaster for the Pi will not be able to control the TV, particularly if it's not a network tv. You can however get remotes, that can learn various TV functions, like TV volume control
Not sure if im missing out on something. The remote you suggested doesn't have an ir blaster right? How could it control my tv?
I apologize again. I have lost focus from what i originally intended to do. The ultimate goal would be :-
When libreelec is idle (when the black screen saver comes up) i want rpi to send a turn off signal to the tv via ir. (my tv doesnt have a cec). When i try to watch something in kodi, press any key / wake up - i want the pi to send a turn on signal.
Am i too ambitious?
-
Hi. Sorry i forgot to mention. My tv is not a smart tv. Its a older hd tv. So that remote wouldnt work.
-
Hi. I'm new here. I have setup latest libreelec on a Raspberry pi4. I would like to add a IR blaster to the pi 4 to control my tv.
Thinking of getting this Infrared IR Wireless Remote Control Kits for Arduino & Raspberry | Online Shopping Lazada .
However i cant find a recent guide on how to do it.
Infrared Remotes [LibreELEC.wiki] this link says nothing about transmitting at all.
https://openelec.tv/documentation/…irc-ir-blasting this is exactly what i want to do. Wondering if it will work in libreelec. And any specific instructions available?