I am using the Docker addon to run Logitech Media Server in the background.
I have done this for some time now with Coreelec, and prior to that Libreelec, without any troubles.
However, with Coreelec V19, I am noticing that after switching Kodi profiles, I am getting a series of Docker notifications, saying ‘Kill’ - these go on for some time after the profile switch and pop up every few minutes…quite irritating. I can turn the notifications off of course, but that doesn’t seem like a solution as such.
I can still browse LMS while this is happening, so the Docker appears to continue running (as it should). I don’t really understand why a ‘kill’ is happening here at all? The whole point of Docker is to run things like services in the background, and a Kodi profile switch should have no effect on that, right? (And, with Coreelec 18, it didn’t).
Yep so looking at logs it is clear that on profile changes that the system is attempting to stop docker:
2021-04-17 14:41:12.364 T:5147 DEBUG <general>: CServiceAddonManager: stopping service.system.docker.
…and then start it again:
021-04-17 14:41:57.682 T:5399 DEBUG <general>: CServiceAddonManager: starting service.system.docker
…on each profile change.
And, presumably it is finding a container that has not actually exited, so is then trying to re-start it by first killing it:
2021-04-17 14:42:34.569 T:5855 DEBUG <general>: ## service.system.docker ## Name: logitech-media-server | Action: kill
…
2021-04-17 14:43:04.593 T:5855 DEBUG <general>: ## service.system.docker ## Name: logitech-media-server | Action: kill
…
…and many more from then on…
Given what Docker is, and is used for, surely it should stay running at all times, and not be associated with profiles? I’m fairly sure this is what happened with Kodi 18 - at least I never got on screen kill notifications and the containers appeared to run continuously in the background).
Anyone have any thoughts/ideas on this? In terms of running background containers, this is undesirable behaviour (either, if it must kill containers when switching, it needs to do so more reliably and not in a way that results in 20 kill messages popping up, or it should leave containers running and regard docker as a background-to-Kodi service to be left alone once started?
(Not sure this is the right place to ask, but I can’t find who/where this addon comes from/where it is developed? Is it a LibreElec thing I should ask about there?)
CoreELEC doesn’t do anything special how addons are handled. If addon is really restarted then this is just Kodi issue.
But I tried installing ProFTPd addon and it is not restarted on profile switch.
I’m going slightly off topic here but I hope you’ll see the relevance. I’ve tried running Plex Server via Docker on a clean install on SD with version RC2 on my N2. I get regular kill messages from Docker and can’t get to the webpage.
I only use the default profile, so that’s where I’m off topic. That said, it seems something is going on with docker in RC2.
Post kodi.log with debug option enabled.
Will do but it will be tomorrow.
Hmm, that’s a hint. Perhaps something about changing profiles is helping trigger a condition that causes docker to think it needs to kill/restart a container (mem use or similar).
The docker LMS I am using I have changed (to the new official one: Docker Hub) - perhaps it is using more memory than what I was using previously.
I have 4GB of RAM on the N2 though (for precisely this sort of reason as 2GB is ample for Kodi), though, so would expect in general for their to be ample memory, really. And the LMS in question is doing literally nothing at the time, no squeezebox players are even connected at this point.
I’ll do some testing (and post debug logs) as soon as I can.
@vpeter - to be clearm you’re not seeing these in your logs when you switch profiles? I can’t think of a reason why I would, and others wouldn’t, really - doesn’t make sense - either Kodi is stopping services on profile switch (which, to be honest, it mostly should - indeed I am not sure there is a mechanism in Kodi to stop this…hmmm) - or its not.
The Kodi wiki says (https://kodi.wiki/view/Service_add-ons) say:
Service addons will be automatically started when a user profile logs in or on Kodi startup, and stopped when the user profile logs out. These addons must offer the xbmc.service extension point.
…which indeed implies a service addon like Docker should be being killed on profile switches. Yet I am 99% sure that did not happen with Kodi 18…I have left machines running for a week plus, with many profile switches, and never seen the container stop. This is you are not seeing these docker start and stop messages, that doesn’t actually seem right/intended (especially as I am).
Indeed, it begs the question - is there in fact a way to stop this, at all? Can docker run in the background and stay running? As, obviously, would be the general usecase for background services…
Anyone know who/where the docker addon is actually developed?
@vpeter Here’s my log running Plex Server thro Docker on N2 4GB and using the default profile. I’ve double checked the dtb before preparing this.
Until the “kill” at 7.49, I could get to the plex webpage.
http://ix.io/2Wsx
Try removing service extension point
<extension point="xbmc.service" library="default.py">
<provides></provides>
</extension>
from /storage/.kodi/addons/service.system.docker/addon.xml or other addon which restarts. To see if it helps.
But this means Kodi will not stop service on update.
Sorry for the slow response, I have to wait until I’ve got solo use of the telly.
Removing extension point from docker (the location you gave) did nothing- still had the “kills”.
Removing extension point from /storage/.kodi/addons/docker.linuxserver.plex/addon.xml did nothing- still had the “kills”.
Removing extension point from /storage/.kodi/addons/docker.linuxserver.updater/addon.xml did nothing- still had the “kills”.
In all cases all I did was remove the 3 lines you specified using a text editor. The original files were renamed addon.xmlold before the edited versions were copied back into the directory. After that, I rebooted for the change to be effective.
What I’ve noticed:
- The kill does not kill the server. I can still use the web interface.
- The kill notifications could be triggered by using other addons. This is just conjecture but I noticed it when opening Iplayer while waiting for a kill.
- I’ve set up a library in plex and the official plex client. Kill messages appear when watching but do not interrupt video playback.
Hope this helps.
Then I don’t know what is going on.
You can use ps command in SSH console to see if those processes were really restated - they should have different pid value.
Will do but it’ll be a few hours before I get a chance.
This is a big showstopper for me with Matrix. I’m so glad I tried it on SD before making the jump.
I’m assuming that you can’t recreate the issue.
No, I didn’t saw anything in kodi log and also processes used same pid so they were not restarted.
I wonder why removing service extension point didn’t do anything. Because this means Kodi didn’t saw this addon as service and there is no reason to restart them. I hope you did restart Kodi after changing addon.xml.
Definitely did the reboots. Definitely deleted the 3 lines you specified. Puzzling isn’t it?
I’ll be back later.
Ran the os command twice. Second time after seeing a kill notification. Does this mean anything to you?
##############################################
# CoreELEC #
# https://coreelec.org #
##############################################
CoreELEC (official): 19.1-Matrix_rc2 (Amlogic-ng.arm)
CoreELEC19:~ # ps
PID USER TIME COMMAND
1 root 0:01 /usr/lib/systemd/systemd
2 root 0:00 [kthreadd]
3 root 0:00 [ksoftirqd/0]
4 root 0:00 [kworker/0:0]
5 root 0:00 [kworker/0:0H]
6 root 0:00 [kworker/u12:0]
7 root 0:00 [rcu_preempt]
8 root 0:00 [rcu_sched]
9 root 0:00 [rcu_bh]
10 root 0:00 [migration/0]
11 root 0:00 [lru-add-drain]
12 root 0:00 [watchdog/0]
13 root 0:00 [cpuhp/0]
14 root 0:00 [cpuhp/1]
15 root 0:00 [watchdog/1]
16 root 0:00 [migration/1]
17 root 0:00 [ksoftirqd/1]
18 root 0:00 [kworker/1:0]
19 root 0:00 [kworker/1:0H]
20 root 0:00 [cpuhp/2]
21 root 0:00 [watchdog/2]
22 root 0:00 [migration/2]
23 root 0:00 [ksoftirqd/2]
24 root 0:00 [kworker/2:0]
25 root 0:00 [kworker/2:0H]
26 root 0:00 [cpuhp/3]
27 root 0:00 [watchdog/3]
28 root 0:00 [migration/3]
29 root 0:00 [ksoftirqd/3]
30 root 0:00 [kworker/3:0]
31 root 0:00 [kworker/3:0H]
32 root 0:00 [cpuhp/4]
33 root 0:00 [watchdog/4]
34 root 0:00 [migration/4]
35 root 0:00 [ksoftirqd/4]
36 root 0:00 [kworker/4:0]
37 root 0:00 [kworker/4:0H]
38 root 0:00 [cpuhp/5]
39 root 0:00 [watchdog/5]
40 root 0:00 [migration/5]
41 root 0:00 [ksoftirqd/5]
42 root 0:00 [kworker/5:0]
43 root 0:00 [kworker/5:0H]
44 root 0:00 [kdevtmpfs]
45 root 0:00 [netns]
46 root 0:00 [kworker/u12:1]
51 root 0:00 [kworker/u12:2]
278 root 0:00 [kworker/u12:3]
1192 root 0:00 [khungtaskd]
1193 root 0:00 [oom_reaper]
1194 root 0:00 [writeback]
1196 root 0:00 [kcompactd0]
1197 root 0:00 [crypto]
1198 root 0:00 [bioset]
1200 root 0:00 [kblockd]
1210 root 0:00 [ata_sff]
1235 root 0:00 [devfreq_wq]
1275 root 0:00 [cfg80211]
1276 root 0:00 [kworker/2:1]
1280 root 0:00 [watchdogd]
1366 root 0:00 [gp_pll]
1372 root 0:00 [kworker/3:1]
1373 root 0:00 [rpciod]
1374 root 0:00 [xprtiod]
1411 root 0:00 [kswapd0]
1412 root 0:00 [vmstat]
1498 root 0:00 [nfsiod]
1503 root 0:00 [cifsiod]
1504 root 0:00 [cifsoplockd]
1564 root 0:00 [hwrng]
1569 root 0:00 [bioset]
1572 root 0:00 [bioset]
1575 root 0:00 [bioset]
1578 root 0:00 [bioset]
1581 root 0:00 [bioset]
1584 root 0:00 [bioset]
1587 root 0:00 [bioset]
1590 root 0:00 [bioset]
1615 root 0:00 [eth_moniter_tx_]
1708 root 0:00 [null]
1709 root 0:00 [null]
1710 root 0:00 [cpu_hogplug_thr]
1723 root 0:00 [vmalloc_ion]
1724 root 0:00 [codec_mm_ion]
1728 root 0:00 [ge2d_monitor]
1744 root 0:00 [kworker/0:1]
1746 root 0:00 [kthread_hdcp]
1756 root 0:00 [kthread_di]
1784 root 0:00 [irq/48-meson-am]
1786 root 0:00 [irq/49-meson-am]
1788 root 0:00 [kworker/0:2]
1798 root 0:00 [cec_work]
1823 root 0:00 [irq/18-meson-g1]
1828 root 0:00 [cma_task0]
1829 root 0:00 [cma_task1]
1830 root 0:00 [cma_task2]
1831 root 0:00 [cma_task3]
1832 root 0:00 [cma_task4]
1833 root 0:00 [cma_task5]
1893 root 0:00 [bioset]
1895 root 0:00 [mmcqd/0]
1896 root 0:00 [bioset]
1897 root 0:00 [mmcqd/0boot0]
1898 root 0:00 [bioset]
1899 root 0:00 [mmcqd/0boot1]
1900 root 0:00 [bioset]
1901 root 0:00 [mmcqd/0rpmb]
1912 root 0:00 [kworker/2:2]
1913 root 0:00 [kworker/5:1]
1920 root 0:00 [ipv6_addrconf]
1922 root 0:00 [kworker/5:2]
1935 root 0:00 [kworker/0:1H]
1936 root 0:00 [dwc_otg]
1937 root 0:00 [kworker/2:3]
1976 root 0:00 [kworker/0:3]
1980 root 0:00 [bioset]
1981 root 0:00 [mmcqd/1]
2008 root 0:00 [kworker/3:2]
2014 root 0:00 [kworker/1:1]
2022 root 0:00 [loop0]
2038 root 0:00 [kworker/u12:4]
2052 root 0:00 [kworker/4:1]
2053 root 0:00 [jbd2/mmcblk1p2-]
2054 root 0:00 [ext4-rsv-conver]
2089 root 0:00 [kworker/3:1H]
2093 root 0:00 [scsi_eh_0]
2094 root 0:00 [scsi_tmf_0]
2095 root 0:00 [usb-storage]
2106 root 0:00 [kworker/5:1H]
2212 root 0:00 [kworker/2:1H]
2261 root 0:00 [bioset]
2290 root 0:00 /bin/sh
2315 root 0:00 [kworker/4:1H]
2368 root 0:00 [kworker/1:1H]
2451 root 0:00 /usr/lib/systemd/systemd-journald
2500 root 0:00 [kauditd]
2908 root 0:00 [kworker/3:3]
3348 root 0:00 [kworker/4:2]
3384 root 0:00 [irq/42-vdec-0]
3385 root 0:00 [irq/43-vdec-1]
3386 root 0:01 [vdec-core]
3387 root 0:00 [kworker/u13:0]
3388 root 0:00 [vdec-work]
3439 root 0:00 [kworker/1:2]
3511 root 0:00 /usr/sbin/rpcbind -f
3707 root 0:00 /usr/sbin/rpc.idmapd
3733 root 0:00 /usr/lib/systemd/systemd-udevd
3807 root 0:00 /usr/sbin/connman-vpnd -n
3848 dbus 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --n
3871 root 0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/r
3912 root 0:00 /usr/bin/pulseaudio --system --disallow-exit --exit-idle-time
3933 root 0:00 /usr/lib/systemd/systemd-logind
4037 root 0:00 [kworker/4:3]
4098 root 0:00 [kworker/u13:1]
4099 root 0:00 [kbase_job_fault]
4119 root 0:00 [kworker/u13:2]
4267 root 0:00 /usr/sbin/connmand -nr --config=/etc/connman/main.conf
4448 root 0:00 [jbd2/mmcblk0p2-]
4453 root 0:00 [ext4-rsv-conver]
4501 avahi 0:00 avahi-daemon: running [CoreELEC19.local]
4628 root 0:00 /usr/bin/wpa_supplicant -u
4643 root 0:00 [kworker/u12:5]
4743 root 0:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
4828 root 0:12 mount.ntfs /dev/sda1 /media/TOSHIBA EXT -o big_writes,fmask=0
4994 root 0:00 /sbin/crond -f -S
5013 root 0:01 /storage/.kodi/addons/service.system.docker/bin/dockerd --exe
5043 root 0:00 /bin/sh /storage/.kodi/addons/docker.linuxserver.plex/bin/doc
5117 root 0:00 /usr/sbin/rpc.statd
5126 root 0:00 /usr/sbin/rpc.mountd
5199 root 0:00 containerd --config /var/run/docker/containerd/containerd.tom
5213 root 0:00 /usr/sbin/nmbd
5236 root 0:00 /usr/sbin/smbd
5245 root 0:00 {smbd-notifyd} /usr/sbin/smbd
5250 root 0:00 {cleanupd} /usr/sbin/smbd
5270 root 0:00 [rc0]
5372 root 0:00 {lpqd} /usr/sbin/smbd
5401 root 0:00 [kworker/1:3]
5435 root 0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs
5458 root 0:30 /usr/lib/kodi/kodi.bin --standalone -fs
5670 root 0:00 [kbase_event]
5877 root 0:00 docker run --name=plex --rm --net=host --hostname=Plex-LibreE
5897 root 0:00 containerd-shim -namespace moby -workdir /storage/.kodi/userd
5921 root 0:00 s6-svscan -t0 /var/run/s6/services
5980 root 0:00 s6-supervise s6-fdholderd
6265 root 0:00 s6-supervise plex
6268 nobody 0:02 /usr/lib/plexmediaserver/Plex Media Server
6303 nobody 0:04 {Plex Script Hos} Plex Plug-in [com.plexapp.system] /usr/lib/
6350 nobody 0:00 /usr/lib/plexmediaserver/Plex Tuner Service /usr/lib/plexmedi
6372 nobody 0:03 {Plex Script Hos} Plex Plug-in [com.plexapp.agents.imdb] /usr
6481 root 0:04 /usr/sbin/smbd
6540 root 0:00 [tb_detect]
6541 root 0:00 [ppmgr]
6542 root 0:00 [irq/29-ff642000]
6615 root 0:00 sshd: root@pts/0
6619 root 0:00 -sh
6625 root 0:00 ps
CoreELEC19:~ # ps
PID USER TIME COMMAND
1 root 0:01 /usr/lib/systemd/systemd
2 root 0:00 [kthreadd]
3 root 0:00 [ksoftirqd/0]
4 root 0:00 [kworker/0:0]
5 root 0:00 [kworker/0:0H]
6 root 0:00 [kworker/u12:0]
7 root 0:00 [rcu_preempt]
8 root 0:00 [rcu_sched]
9 root 0:00 [rcu_bh]
10 root 0:00 [migration/0]
11 root 0:00 [lru-add-drain]
12 root 0:00 [watchdog/0]
13 root 0:00 [cpuhp/0]
14 root 0:00 [cpuhp/1]
15 root 0:00 [watchdog/1]
16 root 0:00 [migration/1]
17 root 0:00 [ksoftirqd/1]
18 root 0:00 [kworker/1:0]
19 root 0:00 [kworker/1:0H]
20 root 0:00 [cpuhp/2]
21 root 0:00 [watchdog/2]
22 root 0:00 [migration/2]
23 root 0:00 [ksoftirqd/2]
24 root 0:00 [kworker/2:0]
25 root 0:00 [kworker/2:0H]
26 root 0:00 [cpuhp/3]
27 root 0:00 [watchdog/3]
28 root 0:00 [migration/3]
29 root 0:00 [ksoftirqd/3]
30 root 0:00 [kworker/3:0]
31 root 0:00 [kworker/3:0H]
32 root 0:00 [cpuhp/4]
33 root 0:00 [watchdog/4]
34 root 0:00 [migration/4]
35 root 0:00 [ksoftirqd/4]
36 root 0:00 [kworker/4:0]
37 root 0:00 [kworker/4:0H]
38 root 0:00 [cpuhp/5]
39 root 0:00 [watchdog/5]
40 root 0:00 [migration/5]
41 root 0:00 [ksoftirqd/5]
42 root 0:00 [kworker/5:0]
43 root 0:00 [kworker/5:0H]
44 root 0:00 [kdevtmpfs]
45 root 0:00 [netns]
46 root 0:00 [kworker/u12:1]
51 root 0:00 [kworker/u12:2]
278 root 0:00 [kworker/u12:3]
1192 root 0:00 [khungtaskd]
1193 root 0:00 [oom_reaper]
1194 root 0:00 [writeback]
1196 root 0:00 [kcompactd0]
1197 root 0:00 [crypto]
1198 root 0:00 [bioset]
1200 root 0:00 [kblockd]
1210 root 0:00 [ata_sff]
1235 root 0:00 [devfreq_wq]
1275 root 0:00 [cfg80211]
1276 root 0:00 [kworker/2:1]
1280 root 0:00 [watchdogd]
1366 root 0:00 [gp_pll]
1372 root 0:00 [kworker/3:1]
1373 root 0:00 [rpciod]
1374 root 0:00 [xprtiod]
1411 root 0:00 [kswapd0]
1412 root 0:00 [vmstat]
1498 root 0:00 [nfsiod]
1503 root 0:00 [cifsiod]
1504 root 0:00 [cifsoplockd]
1564 root 0:00 [hwrng]
1569 root 0:00 [bioset]
1572 root 0:00 [bioset]
1575 root 0:00 [bioset]
1578 root 0:00 [bioset]
1581 root 0:00 [bioset]
1584 root 0:00 [bioset]
1587 root 0:00 [bioset]
1590 root 0:00 [bioset]
1615 root 0:00 [eth_moniter_tx_]
1708 root 0:00 [null]
1709 root 0:00 [null]
1710 root 0:00 [cpu_hogplug_thr]
1723 root 0:00 [vmalloc_ion]
1724 root 0:00 [codec_mm_ion]
1728 root 0:00 [ge2d_monitor]
1744 root 0:00 [kworker/0:1]
1746 root 0:00 [kthread_hdcp]
1756 root 0:00 [kthread_di]
1784 root 0:00 [irq/48-meson-am]
1786 root 0:00 [irq/49-meson-am]
1788 root 0:00 [kworker/0:2]
1798 root 0:00 [cec_work]
1823 root 0:00 [irq/18-meson-g1]
1828 root 0:00 [cma_task0]
1829 root 0:00 [cma_task1]
1830 root 0:00 [cma_task2]
1831 root 0:00 [cma_task3]
1832 root 0:00 [cma_task4]
1833 root 0:00 [cma_task5]
1893 root 0:00 [bioset]
1895 root 0:00 [mmcqd/0]
1896 root 0:00 [bioset]
1897 root 0:00 [mmcqd/0boot0]
1898 root 0:00 [bioset]
1899 root 0:00 [mmcqd/0boot1]
1900 root 0:00 [bioset]
1901 root 0:00 [mmcqd/0rpmb]
1912 root 0:00 [kworker/2:2]
1913 root 0:00 [kworker/5:1]
1920 root 0:00 [ipv6_addrconf]
1922 root 0:00 [kworker/5:2]
1935 root 0:00 [kworker/0:1H]
1936 root 0:00 [dwc_otg]
1937 root 0:00 [kworker/2:3]
1976 root 0:00 [kworker/0:3]
1980 root 0:00 [bioset]
1981 root 0:00 [mmcqd/1]
2008 root 0:00 [kworker/3:2]
2014 root 0:00 [kworker/1:1]
2022 root 0:00 [loop0]
2038 root 0:00 [kworker/u12:4]
2052 root 0:00 [kworker/4:1]
2053 root 0:00 [jbd2/mmcblk1p2-]
2054 root 0:00 [ext4-rsv-conver]
2089 root 0:00 [kworker/3:1H]
2093 root 0:00 [scsi_eh_0]
2094 root 0:00 [scsi_tmf_0]
2095 root 0:00 [usb-storage]
2106 root 0:00 [kworker/5:1H]
2212 root 0:00 [kworker/2:1H]
2261 root 0:00 [bioset]
2290 root 0:00 /bin/sh
2315 root 0:00 [kworker/4:1H]
2368 root 0:00 [kworker/1:1H]
2451 root 0:00 /usr/lib/systemd/systemd-journald
2500 root 0:00 [kauditd]
2908 root 0:00 [kworker/3:3]
3348 root 0:00 [kworker/4:2]
3384 root 0:00 [irq/42-vdec-0]
3385 root 0:01 [irq/43-vdec-1]
3386 root 0:01 [vdec-core]
3387 root 0:00 [kworker/u13:0]
3388 root 0:00 [vdec-work]
3439 root 0:00 [kworker/1:2]
3511 root 0:00 /usr/sbin/rpcbind -f
3707 root 0:00 /usr/sbin/rpc.idmapd
3733 root 0:00 /usr/lib/systemd/systemd-udevd
3807 root 0:00 /usr/sbin/connman-vpnd -n
3848 dbus 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --n
3871 root 0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/r
3912 root 0:00 /usr/bin/pulseaudio --system --disallow-exit --exit-idle-time
3933 root 0:00 /usr/lib/systemd/systemd-logind
4037 root 0:00 [kworker/4:3]
4098 root 0:00 [kworker/u13:1]
4099 root 0:00 [kbase_job_fault]
4119 root 0:00 [kworker/u13:2]
4267 root 0:00 /usr/sbin/connmand -nr --config=/etc/connman/main.conf
4448 root 0:00 [jbd2/mmcblk0p2-]
4453 root 0:00 [ext4-rsv-conver]
4501 avahi 0:00 avahi-daemon: running [CoreELEC19.local]
4628 root 0:00 /usr/bin/wpa_supplicant -u
4643 root 0:00 [kworker/u12:5]
4743 root 0:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
4828 root 0:12 mount.ntfs /dev/sda1 /media/TOSHIBA EXT -o big_writes,fmask=0
4994 root 0:00 /sbin/crond -f -S
5013 root 0:02 /storage/.kodi/addons/service.system.docker/bin/dockerd --exe
5043 root 0:00 /bin/sh /storage/.kodi/addons/docker.linuxserver.plex/bin/doc
5117 root 0:00 /usr/sbin/rpc.statd
5126 root 0:00 /usr/sbin/rpc.mountd
5199 root 0:01 containerd --config /var/run/docker/containerd/containerd.tom
5213 root 0:00 /usr/sbin/nmbd
5236 root 0:00 /usr/sbin/smbd
5245 root 0:00 {smbd-notifyd} /usr/sbin/smbd
5250 root 0:00 {cleanupd} /usr/sbin/smbd
5270 root 0:00 [rc0]
5372 root 0:00 {lpqd} /usr/sbin/smbd
5401 root 0:00 [kworker/1:3]
5435 root 0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs
5458 root 0:42 /usr/lib/kodi/kodi.bin --standalone -fs
5670 root 0:00 [kbase_event]
5877 root 0:00 docker run --name=plex --rm --net=host --hostname=Plex-LibreE
5897 root 0:00 containerd-shim -namespace moby -workdir /storage/.kodi/userd
5921 root 0:00 s6-svscan -t0 /var/run/s6/services
5980 root 0:00 s6-supervise s6-fdholderd
6265 root 0:00 s6-supervise plex
6268 nobody 0:03 /usr/lib/plexmediaserver/Plex Media Server
6303 nobody 0:04 {Plex Script Hos} Plex Plug-in [com.plexapp.system] /usr/lib/
6350 nobody 0:00 /usr/lib/plexmediaserver/Plex Tuner Service /usr/lib/plexmedi
6372 nobody 0:03 {Plex Script Hos} Plex Plug-in [com.plexapp.agents.imdb] /usr
6615 root 0:00 sshd: root@pts/0
6619 root 0:00 -sh
6779 root 0:00 ps
CoreELEC19:~ #
I’ve reverted all add-on xmls back to the originals and have set custom notifications in the docker settings so that the kills do not show. I want to confirm that they have no effect on media playback.
As you can see all PID values (first column) are the same so nothing got restarted.
Can you repeat the same steps (switch profile) and after that run this command and post url.
journalctl -l | paste
Sorry for this @vpeter, I’ve confused you by hijacking this thread. I only run the default profile. I’m the one having Docker Plex Kill notifications.
I can turn kill notifications back on and run the journal thingy once I’ve seen a kill message. Give me a few mins to set it up.
In this case you need to debug this plex docker container. Maybe it has some log file.