Posts by nvdias

    # INTRO


    I've made a small openvpn server that can be installed on LibreELEC running raspberry pi devices (and eventually other arm devices).


    The server runs in a small docker image (around 20MB) that is automatically loaded on first start


    After first run, you should configure your server address givinh its ddns name or wan ip address


    Then go to your ssh console and run:

    "openvpn-add-server" to create the server config and keys, and define your router address (so your openvpn clients ca get access to your lan).

    Note that the keys will take up to 15 minutes to create in a Raspberry Pi 4 (be patient).


    Then call:

    "openvpn-add-user" to create users and get the ovpn file of each one.

    Theses are the files you must give to the client to acess your openvpn server using an openvpn client software.


    Restart the add-on and it's done !


    ### DOWNLOAD HERE

    Sendspace.com Mobile File


    w w w . sendspace . com / file / t5ezm2





    # TECH STUFF


    ### The docker is hosted in:

    Docker Hub


    ### The git source is:

    GitHub - nvdias0/rpi-docker-openvpn: Docker OpenVPN image for Raspberry Pi


    it is a fork from olivierguerriat/rpi-docker-openvpn, which in turn is a fork from kylemanna/docker-openvpn with an armhf base image


    Loom at those links above if you want to know more.

    So, your RasPi connects directly to the TV, without AV-Receiver?
    Could you do me a favor: While judder and frame-dropping...can you switch off the TV (let the RasPi run!) and switch it on after 20 seconds again.
    Does this make any difference and the judder is gone for a few minutes? Thanx, Greetings!

    That's what happens to me at the moment: First I had the same problems you described in the first post, than I could get rid of it for a few weeks ( algorithmdirtyregions) and now all is back much worse.

    I've also tried algorithmdirtyregions. But after some time, all the isswues were back.

    The set of setting above is giving the best results.


    Note: I've tried your test ith the TV, But I notice no diference - I'm using a Sony Android TV (2016 model) with a Raspberry Pi 4.

    I've watched somme movies which had judder with MMAL other without-it.

    After some more testing, I've had the most stable video viewing experience using the following set of settings:


    Settings


    Player

    Adjust display refresh rate ALWAYS

    Sync playback to display YES

    Enable HQ Scalers above 50%

    Allow hardware accel. MMAL YES


    System / Display

    White list - only All 1920x1080 resolutions (this will force upscaling in kodi when needed)

    Preferred mode Same as Movies


    System / Audio

    Allow passthrough NO



    (The bold settings seems to be the more influent)

    I need to revive the thread:

    I've been noticing that my simple web server running over docker's container "linuxserver/letsencrypt" is stopping.


    After several days looking into the logs, I've found that it only happens after a docker update as the one following:

    Code
    1. Apr 20 04:05:00 LibreELEC crond[2632]: USER root pid 4212 cmd /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.sh > /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.log && /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/prune.sh > /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/prune.log


    At this time docker container stops and do not start again unless I reboot the system.


    I'm using LibreELEC 9.2.1 runnng in a RPi 4

    I was able to replicate the problem with a fresh install:


    I've Installed LibreELEC 9.1.502 in another new 8GB SD-CARD in my Pi 4 4GB.


    After 1st boot configured ssh, wired ethernet, fixed ip (into which my router forwards ports 80 and 443).

    Activated debug logging.

    Installed docker, linux.io repo and the add-on with letsencrypt and nginx

    Configured ddns in the add-on as requested per install.

    All seem to be ok.


    After another reboot, docker crashed as in my initial SD-CARD.

    (as before, this happens roughly 1 in each 3 reboots).


    This happens only in beta 2. In beta 1, All is ok.



    This url is for full untouched logs of this fresh install:


    http://ix.io/20xr

    (search for "segmentation fault")


    Hope this help in finding the issue.



    Thanks Guys.

    LibreELEC has been awesome !

    LibreELEC 9.2 Beta 2 and Docker

    I'm creating this thread to easily read and get support :), as the previous post was placed in the news section.



    Updated the system to Beta 2

    I have docker installed with only the official container for letsencrypt and nginx.


    a) At each 3 reboots, docker fails, at least 1 time - sometimes work, sometimes don't - always working fine in beta 1;

    b) Doing a "docker restart docker.linuxserver.letsencrypt" in ssh shell, takes a lot of time (compared to Libreelec Beta 1) and fails to start again a lot of times.

    c) System shutdown / reboot taking a lot of time (a stop job is running for docker container .... 3 minutes) - almost immediate with beta 1


    Logs from a failed docker start after system boot:




    Note docker crashes in this lines:

    Code
    1. Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760117072+01:00" level=info msg="libcontainerd: started new containerd process" pid=430
    2. Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760551072+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc
    3. Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760600776+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
    4. Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797000224+01:00" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0 <nil>}]" module=grpc
    5. Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797126520+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
    6. Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797396094+01:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x4d6ab50, CONNECTING" module=grpc
    7. Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.819133578+01:00" level=error msg="containerd did not exit successfully" error="signal: segmentation fault (core dumped)" module=libcontainerd




    Back to LibreELEC 9.1 Beta 1 .. All is fine with docker .. no more core dumps.


    I 've also tried a Beta 2 fresh install in a clean sd-card and got the same symptoms - testing several restarts, and docker fails to start 30% to 40% of the time

    I've just installed Docker and Letsencypt on a RPi4 4G without issues. Not too sure what the issue might be with your setup, but I would uninstall Docker and letsencrypt and then reinstall.


    If you still have issues:

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem.

    Note: Full logs only. No partial or modified logs.

    Do not post your logs directly into the forum, use pastebin.com and post the link.

    LibreELEC 9.2 Beta 2 and Docker

    (replicated the issue)


    Updated (again) the system to Beta 2



    a) At each 3 reboots, docker fails, at least 1 time - sometimes work, sometimes don't - always working fine in beta 1;

    b) Doing a "docker restart docker.linuxserver.letsencrypt" in ssh shell, takes a lot of time (compared to Libreelec Beta 1) and failing to start again.

    c) System shutdown / reboot taking a lot ff time (a stop job is running for docker container .... 3 minutes) - almost immediate with beta 1


    Logs from a failed docker start after system boot:


    Back to LibreELEC 9.1 Beta 1 .. All is fine with docker .. no more core dumps.


    (All I've made was upgrading from beta1 to beta 2 and then back to beta 1.
    (Also tried a Beta 2 fresh install in a clean sd-card)



    Should I create a new thread for this issue ?

    As I've said, I've re installed everything in a new sd card, and the same issues - very slow docker loading docker container (in this case, letsencrypt with nginx) and failing with core dump 50% of the time.
    I will repeat the process and provide the logs.

    I've upgraded my Pi4 to LibreELEC-RPi4.arm-9.1.502.tar and found some issues with Docker.

    (using docker, linuxserver.io to support docker.linuxserver.letsencrypt).

    After the upgrade the letsecenrypt add-on (which includes nginx) takes a long time to boot and docker service itself fails around 50% of the boots with a core dumped error.


    Docker restarts also taking a long time and exiting many times with core dumps.


    Just to be sure I've re installed everything in a new sd card, and the same issues.

    I've downgraded to 9.1.501 and everything is good again with docker.


    I just cannot say if it is something with docker or with libreelec 9.1.502, nor what it is.




    Thanks

    I can think in three possible issues:

    A - in settings, input devices, hdmi - configure-it NOT to switch tv input, turn on or turn off the tv.

    B - try checking if your cables are ok

    C - you may have a defective pi4 (mine had a non working micro hdmi 1 (had to replace it at the shop) - validate by installing a different distribution , as the official raspbian.

    i guess i have the exact same issue, but there is a solution that i found.


    if you run the pi in any 60hz resolution, everything will be fine. 1080p @ 60z or 2160p @ 60hz.


    the 60hz removes absolutely ALL judder for all video types and audio profiles, and with and without subtitles. just my two cents.

    that is odd. You can not have judder free when watching 23.976fps or 25 / 50 fps movies at 60hz.

    There is no direct conversion. These formats should be played at native refresh rates configured in the white list.

    To add my voice to the mix I'm also noticing stuttering and juddering on Pi4, with newest LibreElec on videos with 5.1 audio in all formats (AC3, EAC3, and DTS). I'm using an external USB sound card and I do set the audio to 'Fixed' at 48KHz. This setup, and these videos, have been playing fine on a 3B+ for months.


    I've also noticed that, sometimes when the juddering starts the audio channels suddenly get randomly mixed up - eg center becomes left, left becomes subwoofer, etc etc - this happens during playback and then it gets stuck like that. Sometimes even a reboot doesn't cure it. There's nothing whatsoever in the kodi log.


    that is basically the same behaviour I've got.

    Try forcing 4.0 audio output (or less) and confirm that Judder disappears.

    (Stutter will continue on some subtitles - if you use them)



    Yes. Ir works fine with Pi 3.

    Waiting for new betas for pi4 :)