Posts by vpeter

Can you post both outputs of iptables -L and ip6tables -L to compare?

edit file /storage/.cache/services/sshd.conf and change/add -E log_file

SSH_ARGS="-E /var/log/sshd.log"

restart sshd service

systemctl restart sshd

check log file /var/log/sshd.log

cat /var/log/sshd.log

Check if you can add StandardOutput to file in sshd.service file.

I don't know if there is any such log file. BUt i see with command above

Jun 02 11:25:22 LibreELEC sshd[1340]: Failed password for root from 192.168.2.3 port 47442 ssh2
Jun 02 11:25:22 LibreELEC sshd[1340]: Connection closed by authenticating user root 192.168.2.3 port 47442 [preauth]

Maybe some cron job could create log file with grepping systemctl status.

Quote from Borygo77

Anyone can point me where accepted and failed logins to ssh are stored ?

Maybe

systemctl status sshd -l --no-pager

Would not be easier to restart Kodi at 3AM every night? It is not a fix but still

Try

robocopy "D:\Media\Fotoramen" "Z:\Fotoramen" /MIR /COPY:DT /DCOPY:T

Compare the content of both archives to see what is the difference

I updated build Milhouse #0528and removed kodi profile folder. After new start I could install whatever addon version was in the repository.

Are you sure you look enough?

Quote from chelobaka

No. Intel is still working on kernel HDR support ....

Intel is also working on S9xxx SoC?

Quote from soyxan

Do you have any explanation for that?

No actually. I just look around how other docker services are started and saw this small change. Maybe

--attach , -a Attach STDOUT/STDERR and forward signals
-t, --time int Seconds to wait for stop before killing it (default 10)

Try with this Start and Stop:

ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start -a domoticz
ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop -t 2 domoticz

Then I can't help you anymore. I only create container and for me it runs fine after reboot too.

After you create domoticz container do you run it from console to initialize it? Because I can run it just fine.

docker start domoticz

# look if completely started with
docker logs domoticz

When creating docker try without --restart unless-stopped.

You need to set variables STRIP and PKG_MAKE_OPTS_TARGET in function pre_configure_target() to evaluate them correctly because you are using environment variables STRIP and CC which are known little later. Correct reason can tell someone else

pre_configure_target() {
  STRIP="--strip --strip-program=$STRIP"
  PKG_MAKE_OPTS_TARGET="SYSCONFDIR=/storage/.config CC=$CC CWFLAGS="
  PKG_MAKEINSTALL_OPTS_TARGET="SYSTEMD_DIR=/usr/lib/systemd/system BINDIR=/usr/sbin install-systemd"
}

Also your build was compiled with ggdb

It starts for me fine. What was the command to create domoticz container?