Posts by ajiratech

Nevermind this, I restored to an older backup of LE with docker and it seems to work fine again. I've disabled auto-update for docker.

journalctl -r gets me the following logs for docker:

--------- start of logs ------------

Jul 07 05:36:30 libreElec nmbd[2851]: This response was from IP 192.168.222.41, reporting an IP address of 192.168.222.41.

Jul 07 05:36:30 libreElec nmbd[2851]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.222.160 for name WORKGROUP<1d>.

Jul 07 05:36:30 libreElec nmbd[2851]: [2019/07/07 05:36:30.533454, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)

Jul 07 05:31:30 libreElec nmbd[2851]: This response was from IP 192.168.222.41, reporting an IP address of 192.168.222.41.

Jul 07 05:31:30 libreElec nmbd[2851]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.222.160 for name WORKGROUP<1d>.

Jul 07 05:31:30 libreElec nmbd[2851]: [2019/07/07 05:31:30.903969, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)

Jul 07 05:28:32 libreElec connmand[2760]: ntp: adjust (slew): +0.014074 sec

Jul 07 05:26:30 libreElec nmbd[2851]: This response was from IP 192.168.222.41, reporting an IP address of 192.168.222.41.

Jul 07 05:26:30 libreElec nmbd[2851]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.222.160 for name WORKGROUP<1d>.

Jul 07 05:26:30 libreElec nmbd[2851]: [2019/07/07 05:26:30.968947, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)

Jul 07 05:26:25 libreElec systemd[1]: Started Cleanup of Temporary Directories.

Jul 07 05:26:25 libreElec systemd[1]: Starting Cleanup of Temporary Directories...

Jul 07 05:25:10 libreElec dockerd[3546]: time="2019-07-07T05:25:10.916821000-04:00" level=info msg="API listen on /var/run/docker.sock"

Jul 07 05:25:10 libreElec systemd[1]: Started Docker Application Container Engine.

Jul 07 05:25:10 libreElec dockerd[3546]: time="2019-07-07T05:25:10.849477000-04:00" level=info msg="Docker daemon" commit=1.13.1 graphdriver=overlay2 version=1.13.1

Jul 07 05:25:10 libreElec dockerd[3546]: time="2019-07-07T05:25:10.849314000-04:00" level=info msg="Daemon has completed initialization"

Jul 07 05:25:10 libreElec dockerd[3546]: time="2019-07-07T05:25:10.824833000-04:00" level=warning msg="Not using native diff for overlay2: opaque flag erroneously copied up, consider update to kernel 4.8 or later to fix"

Jul 07 05:25:10 libreElec dockerd[3546]: time="2019-07-07T05:25:10.610251000-04:00" level=info msg="Loading containers: done."

Jul 07 05:25:09 libreElec dockerd[3546]: time="2019-07-07T05:25:09.184144000-04:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"

Jul 07 05:25:08 libreElec dockerd[3546]: time="2019-07-07T05:25:08.797745000-04:00" level=warning msg="Could not load necessary modules for IPSEC rules: Running modprobe xfrm_user failed with message: `modprobe: WARNING: Module xfrm_user not found in directory /lib/modules/3.14.29`, error: exit status 1"

Jul 07 05:25:08 libreElec dockerd[3546]: time="2019-07-07T05:25:08.695033000-04:00" level=info msg="Firewalld running: false"

Jul 07 05:25:08 libreElec dockerd[3546]: time="2019-07-07T05:25:08.023889000-04:00" level=error msg="Failed to load container mount 1889d5fc421e3d2de52191371d2a500a05a59a12cadf4462b9b40d73e05eb77c: mount does not exist"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.960196000-04:00" level=info msg="Loading containers: start."

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.959342000-04:00" level=warning msg="mountpoint for pids not found"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.959063000-04:00" level=warning msg="Your kernel does not support cgroup blkio weightt_device"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.959009000-04:00" level=warning msg="Your kernel does not support cgroup blkio weightt"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.958960000-04:00" level=warning msg="Your kernel does not support cgroup rt runtime"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.958914000-04:00" level=warning msg="Your kernel does not support cgroup rt period"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.958864000-04:00" level=warning msg="Your kernel does not support cgroup cfs quotas"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.958761000-04:00" level=warning msg="Your kernel does not support cgroup cfs period"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.958047000-04:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"

Jul 07 05:25:07 libreElec dockerd[3546]: time="2019-07-07T05:25:07.563168000-04:00" level=warning msg="Using pre-4.0.0 kernel for overlay2, mount failures may require kernel update"

Jul 07 05:25:06 libreElec dockerd[3546]: time="2019-07-07T05:25:06.527650000-04:00" level=info msg="libcontainerd: new containerd process, pid: 3553"

Jul 07 05:25:06 libreElec systemd[1]: Starting Docker Application Container Engine...

Jul 07 05:25:06 libreElec systemd[1]: Stopped Docker Application Container Engine.

Jul 07 05:25:06 libreElec kodi.sh[3171]: EOFError: socket closed

Jul 07 05:25:06 libreElec kodi.sh[3171]: raise EOFError('socket closed')

Jul 07 05:25:06 libreElec kodi.sh[3171]: File "/storage/.kodi/addons/service.system.docker/lib/dockermon.py", line 94, in watch

Jul 07 05:25:06 libreElec kodi.sh[3171]: dockermon.watch(print_notification)

Jul 07 05:25:06 libreElec kodi.sh[3171]: File "/storage/.kodi/addons/service.system.docker/default.py", line 266, in run

Jul 07 05:25:06 libreElec kodi.sh[3171]: File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner

Jul 07 05:25:06 libreElec kodi.sh[3171]: Traceback (most recent call last):

Jul 07 05:25:06 libreElec kodi.sh[3171]: Exception in thread Thread-1:

Jul 07 05:25:06 libreElec dockerd[2790]: time="2019-07-07T05:25:06.321981000-04:00" level=error msg="libcontainerd: failed to receive event from containerd: rpc error: code = 13 desc = transport is closing"

Jul 07 05:25:06 libreElec systemd[1]: Stopping Docker Application Container Engine...

Jul 07 05:25:06 libreElec dockerd[2790]: time="2019-07-07T05:25:06.312042000-04:00" level=info msg="Processing signal 'terminated'"

Jul 07 05:25:06 libreElec dockerd[2790]: time="2019-07-07T05:25:06.311994-04:00" level=info msg="stopping containerd after receiving terminated"

------------ end of log --------------

I'm running LE 8.x with Kodi 17.6 and have installed docker from LE Add-on Services. I run some custom Server applications inside that docker and it had been running quite well for several months.

Since last month or two docker has stopped running properly. Even after a reboot my script that connected to docker is no longer able to do so:

docker -H tcp://0.0.0.0:2900 run -v <some_parameters> node myAppServer.js

This command throws an error :

docker: Cannot connect to the Docker daemon at tcp://0.0.0.0:2900. Is the docker daemon running?.

I have confirmed that docker is running via 'systemctl status docker' command

systemctl status docker returns:

---------------- start of status -----------------

service.system.docker.service - Docker Application Container Engine

Loaded: loaded (/storage/.kodi/addons/service.system.docker/system.d/service.system.docker.service; enabled; vendor preset: disa

bled)

Active: active (running) since Sun 2019-07-07 05:25:10 EDT; 7min ago

Docs: Docker Documentation | Docker Documentation

Process: 3543 ExecStartPre=/storage/.kodi/addons/service.system.docker/bin/docker-config (code=exited, status=0/SUCCESS)

Main PID: 3546 (dockerd)

CGroup: /system.slice/service.system.docker.service

3546 /storage/.kodi/addons/service.system.docker/bin/dockerd --exec-opt native.cgroupdriver=systemd --log-driver=j

ournald --group=root --graph=/storage/.kodi/userdata/addon_data/service.system.docker/docker --storage-driver=overlay2 --storage-op

t overlay2.override_kernel_check=1

3553 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start

-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --shim docker-containerd-shim --runtime docker-runc --runtime-args

--systemd-cgroup=true

Jul 07 05:25:08 libreelec dockerd[3546]: time="2019-07-07T05:25:08.023889000-04:00" level=error msg="Failed to load container mount 1889

d5fc421e3d2de52191371d2a500a05a59a12cadf4462b9b40d73e05eb77c: mount does not exist"

Jul 07 05:25:08 libreelec dockerd[3546]: time="2019-07-07T05:25:08.695033000-04:00" level=info msg="Firewalld running: false"

Jul 07 05:25:08 libreelec dockerd[3546]: time="2019-07-07T05:25:08.797745000-04:00" level=warning msg="Could not load necessary modules

for IPSEC rules: Running modprobe xfrm_user failed with message: `modprobe: WARNING: Module xfrm_user not found in directory /lib/m

odules/3.14.29`, error: exit status 1"

Jul 07 05:25:09 libreelec dockerd[3546]: time="2019-07-07T05:25:09.184144000-04:00" level=info msg="Default bridge (docker0) is assigned

with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"

Jul 07 05:25:10 libreelec dockerd[3546]: time="2019-07-07T05:25:10.610251000-04:00" level=info msg="Loading containers: done."

Jul 07 05:25:10 libreelec dockerd[3546]: time="2019-07-07T05:25:10.824833000-04:00" level=warning msg="Not using native diff for overlay

2: opaque flag erroneously copied up, consider update to kernel 4.8 or later to fix"

Jul 07 05:25:10 libreelec dockerd[3546]: time="2019-07-07T05:25:10.849314000-04:00" level=info msg="Daemon has completed initialization"

Jul 07 05:25:10 libreelec dockerd[3546]: time="2019-07-07T05:25:10.849477000-04:00" level=info msg="Docker daemon" commit=1.13.1 graphdr

iver=overlay2 version=1.13.1

Jul 07 05:25:10 libreelec systemd[1]: Started Docker Application Container Engine.

Jul 07 05:25:10 libreelec dockerd[3546]: time="2019-07-07T05:25:10.916821000-04:00" level=info msg="API listen on /var/run/docker.sock"

---------------- end of status. -----------------

I have uninstalled and reinstalled docker and it still doesn't work.

I did notice one odd thing though - I left the system running for several days and then tried to start my custom application in docker and it WORKED! so it is almost as if upon reboot it fails for some reason and takes a while (could be several minutes, hours or days - no idea) and will then allow me to connect. This happened once, I have since rebooted the box and am yet to connect successfully.

Please advice on how to resolve this. also is there any change that happened to docker that would have caused this to stop working ?
My first install of docker add-on had "auto-update" enabled, so it may have updated docker automatically causing some incompatibility that broke this. I did not keep track of docker version that was first installed vs one that I have now so I don't know for sure if an upgrade caused this broken functionality.

Thanks in advance.

Thanks vpeter . I'll give it a shot and report back.

I'm working on an Add-on to drive a custom GUI on a LibreELEC system on Linux. The add-on works fine and is able to drive the GUI as needed.

At the linux level - LE has udev rules that detect when an SD card is inserted and it works fine, KODI interface generates a notification on bottom right corner as device is added or removed.

I want my Python add-on to react to the SD card addition or removal event and make changes to the GUI. Users on Kodi forum suggested I use PyUdev module. But as LE does not come with PIP, I cannot install that module.

Please advice on how to detect/react to SD Card insertion/removal in a Python add-on.

Thanks in advance.

Thanks vpeter .

I did take a look line by line and there is nothing in there that could be resetting the DB.

Thank you for checking and confirming that audit wouldn't work. Since Audit is no longer an option, I'll see what I can do, maybe if needed do a clean install of LE and try the current scripts again.

they're reset in the middle, without a reboot.

I'm quite certain that none of the LE processes are modifying them.

My custom scripts have been something I've worked on in my spare time over the last 1-2 years and I"m afraid that there may be some old scripts that are messing with these DB files. But I can't seem to find any other scripts that could be doing that. Thus the need for a program like auditctl .

The files are DB files that are used by my custom scripts. They are in a separate folder under my Script folder. No other process should be modifying them, but I see it repeated being reset. I've reviewed my scripts multiple times and I don't see anything that could have reset the DBs.

Hi ,

I have a couple of files that my application manages but some other process seems to be modifying and resetting those files.

I think auditctl would be a good utility to have on this system. Can someone please advice on how to go about installing auditctl or similar program to find out which process modified the files ?

It is impossible to catch the process in the act, so 'lsof' does not work for my needs.

Thanks in advance.

Hi ,

I'm using LE 8.x on an odroid board. Everything works great - I have a USB drive connected that gets auto mounted and becomes available over the network via Samba.

I've updated the samba.conf file under the .conf folder. And the configuration seems to be working as my other shared folders are visible on the network.

How do I keep the USB auto mount configuration of Libreelec intact but disable sharing of that and any other USB drives disabled. i.e. I don't want the drive to be visible on the network.

Thanks in advance.

Thanks chewitt . Once your response ruled out issue with LE. I was able to resolve it.

SecureCRT has a setting under Terminal->Emulation : "Synchronize view to size" which was selected. The gotcha was that It picks up the settings from first tab of SecureCRT. Since I was trying different settings on non first tab, they didn't do anything.

Quitting SecureCRT and starting again resolved the issue for me.

HI ,

I'm running LibreElec on Odroid C2. For SSH sessions, I increased the font size of text on SecureCRT for better visibility and now the longer commands run out of screen space because the terminal column size is 130 but secureCRT can only show around 110 characters.

I tried the command 'stty cols 110' but the command fails with message '-sh: stty: not found'

Please advice on how to install stty or any alternative method I can use to change # of columns.

Thanks,

It looks like it worked with lower value of 20m and then I did a umount and tried it again with 50m and that worked too. (the only thing different is I emptied the destination folder a few minutes ago)

No idea why it didn't work the first time. But now it seems to have survived a reboot as well.

Thanks for confirming that the script was correct and suggesting to try lower value.

Yes, top reports over 1GB free memory:

top - 13:02:46 up 47 min, 1 user, load average: 2.51, 2.44, 2.35

Tasks: 125 total, 2 running, 123 sleeping, 0 stopped, 0 zombie

%Cpu(s): 2.2 us, 1.6 sy, 0.5 ni, 95.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st

KiB Mem : 1856264 total, 1067008 free, 218696 used, 570560 buff/cache

KiB Swap: 0 total, 0 free, 0 used. 1439412 avail Mem

Hi ,

I'm running LibreElec on Odroid hardware and want to create a 50MB Ramdisk. I have other mount scripts for Samba mounts that work. But this one for RAMDISK fails - Here is a copy of the script I've tried. Please advice on how to resolve this:

The mount script is named per LE requirements - script is named 'storage-.tmp-RAMDISK.mount' and located under /storage/.config/system.d

Here is what I did and the error I get:

systemctl enable storage-.tmp-RAMDISK.mount

systemctl start storage-.tmp-RAMDISK.mount

systemctl status storage-.tmp-RAMDISK.mount. results in:

storage-.tmp-RAMDISK.mount - RAMDISK mount script

Loaded: loaded (/storage/.config/system.d/storage-.tmp-RAMDISK.mount; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Tue 2018-11-27 12:25:48 EST; 24s ago

Where: /storage/.tmp/RAMDISK

What: tmpfs

CPU: 4ms

Nov 27 12:25:48 librelec systemd[1]: Mounting RAMDISK mount script...

Nov 27 12:25:48 librelec systemd[1]: storage-.tmp-RAMDISK.mount: Mount process exited, code=exited status=255

Nov 27 12:25:48 librelec systemd[1]: Failed to mount RAMDISK mount script.

Nov 27 12:25:48 librelec systemd[1]: storage-.tmp-RAMDISK.mount: Unit entered failed state.

[Unit]
# Here we will mount a RAMDISK  
Description=RAMDISK mount script

# if we do network mounts like here we *require* 'network-online.service'
# which checks if the network is online
Requires=network-online.service

# our scripts must start *after* 'network-online.service', on timeout and if
# 'network-online.service' fails we can not mount and this scripts fails too
After=network-online.service

# usually we mount networks shares because we want they avaible *before* XBMC starts.
# so XBMC has access to this mounts from beginning. Note: this slows down the boot!
Before=kodi.service


[Mount]
# The share we want mount
What=tmpfs

# Where we want mount this share
Where=/storage/.tmp/RAMDISK

# Any options you usually use with the "-o" parameter in the mount command
Options=size=50m

# I've tried with "size=50m" and that didn't help either

# filesystem type
Type=tmpfs


[Install]
WantedBy=multi-user.target

Thanks aptalca .

I'll try that out sometime.

output of dmesg and journalctl as requested: (The device was rebooted just a few minutes ago to unmount sda1 and run fsck on it)

libreElec:~ # dmesg|paste
http://ix.io/1p0N

libreElec:~ # journalctl|paste
http://ix.io/1p0O

I had tested the power capability of PSU but running script that would max out CPU and still read and write on both hard drives continuously for a couple of hours.

The PSU became hot but I don't think it missed any read/write operation. This was a while ago and I didn't write down all my observations so I'm not a 100% sure. I'll prolly do it again before I add second HDD.

As for what is happening these days - one HDD. almost no activity on CPU. I try to play video on Kodi and hit play, but it hangs with message "working". Journalctl had the errors I posted in first message.

fsck came back clean:

fsck from util-linux 2.29
e2fsck 1.43.4 (31-Jan-2017)
/dev/sda1: clean, 10816/244187136 files, 218674802/976745728 blocks

I noticed that the USB micro cable was 5% not inserted. I pushed it in the HDD and after that I was able to access the directories on HDD. So that may have been the problem. I'll know for sure if this doesn't happen again in the next 3-4 days.

One more question - is there a way for me to install SMART on LE installation ?

I had one USB HDD connected to this LE device permanently and I might add another one soon. I'll make sure it has enough power for device under full load and for the two HDDs.

I'd like to put some sort of monitoring in place to keep an eye on the HDDs and any errors that may come up for the HDDs from time to time.

Please advice on what the right approach to accomplish this would be. Thanks in advance.