Posts by Hunduster

    Hello everyone,

    We use a single profile on one TV in our household. I would like to install two more Kodi instances in the bedroom and hobby room.

    Since my “master system” is all set up, I thought I could make a backup of Libreelec and install it on the other two systems. After the recovery, I would then change the computer name and IP address on each system.

    Is this a good, feasible way or not a good idea?

    Hello everyone,

    I wanted to get back to you once again. Since I switched from NFSv3 to NFSv4, I haven't had a crash since then.

    Kodi now has a 1 second pause when exiting media where the screen goes black before returning to the menu interface but that's OK with me. I think this is due to NFSv4.

    If, contrary to expectations, there are problems again, I will contact you again. Thanks again for your prompt help in this thread!

    Hello everyone,

    Thank you very much for your answers.

    The 4kp60 is another good tip. I don't even remember why I activated it in the first place because, as you said popcornmix, the movies usually end up below 30FPS.

    I've just removed the parameter.

    I've mentioned that earlier:

    Hunduster
    January 10, 2024 at 10:07 PM

    Yes, Argon One cases are known for soldering problems on HDMI contacts, but then it wouldn't try to buffer before it crashes. A network issue is much more likely. If I remember correctly, log level 2 includes more network data.

    Hunduster Can you provide another log file for that error at log level 2? We still haven't found the real cause in the log.

    As I said, I don't think it's the case. I first replaced it during my own troubleshooting because I thought it could be the SD card. I also run all my Ubuntu servers in the case on other Raspis, as I kept burning SD cards. But well, that's not an argument, the servers are all headless, connected to the network and are only operated via SSH :S

    However, I still have a Kodi running in the bedroom with the same config in the original Kodi case and SD card, where the same error occurred with exactly the same behavior. I therefore suspect the error is also in the network and had completely replaced the network equipment at the time. The only thing that is still 1:1 the same is the NAS itself and the connection to the NAS. I will replace the Gbic and Fibre Channel cable prohylactically at the end of the week.

    I will be happy to provide a log as soon as the error occurs again. Since I changed the NFS settings from NFSv3 to NFSv4 the day before yesterday and also made granular adjustments to the NFS settings on my NAS, the error has no longer occurred.

    We'll see if it had anything to do with that. It would be nice, although I've been fine with NFSv3 for the last few years. As I said, I've only had the bug since late summer 2023 and that from now on.

    No Problem, I have also changed some NFS settings on my NAS and will try out a few more things here. As I said, I have this problem with two different Kodi systems. Both systems differ in the case, but access the same DB and source. So the error must lie somewhere in this area.

    I'll replace the Gbic on the NAS anyway, you never know.../shrug

    I'm confused to the max myself because I've been using Kodi for a really long time and nothing has changed in the environment (before the error - apart from updates on the systems). If I find the error, I will of course let you know.

    Hello, here I am again.

    Yesterday I switched my Kodi systems to public NTP servers, tested them and made sure that Kodi can reach them. I thought I was safe :D

    Unfortunately, the error occurred twice again yesterday, once on January 13 at 22:32 and then again on January 14 at 01:32:


    https://paste.libreelec.tv/grand-antelope.log

    What I'm reading now is that it's having a problem accessing the network. According to my NAS and my switch, there was no disconnection. However, I have now ordered a new Gbic as a precaution (I have my NAS connected via 10 GE fiber).

    Apart from that, I'm at my wit's end. I will test the connection via SMB again, but I have been using Kodi via NFS for almost 10 years.

    Hello,

    Thank you very much for your help!

    I did indeed replace my firewall with an OPNsense a few months ago and had massive problems with my Raspis when interacting with NTP on the firewall. However, I would never have thought that a faulty NTP query would lead to problems with playback.

    I will reconfigure the whole thing, test it and report back to you.

    Thank you very much for now, I really appreciate your help!

    Yes you can. Use log level 1 or 2 at advancedsettings.xml. Then disable debug mode at GUI, and reboot.

    Does it matter which log level I use for the current troubleshooting, 1 or 2?

    Argon One cases are known for soldering issues. Especially small connectors like microHDMI or USB-C are critical. So I suggest test sessions without that case.

    I had already read that, but it can't be that.

    I have the same problem with a Raspi 4 in the original Kodi Case with SD card in the bedroom and have exactly the same problem here. It is also completely irrelevant what quality the medium has, SD, HD, 4k, the same problem everywhere.

    When I started troubleshooting months ago, I tried everything. The first thing I did was to put the Raspi in the Argon One in the living room. Then I replaced the switch, installed an SSD cache in my NAS and replaced the database. At first I thought it was a release problem, but unfortunately there was no improvement with the current 20.2 either

    Hello everyone,

    Unfortunately, I have been having sporadic problems playing videos for a few months now.

    During playback, the playback suddenly freezes. Kodi briefly shows buffering, but it stops and does not continue. Picture and sound are frozen and after a short time the playback is stopped and you end up back in the selection menu of the movies/series you were watching.

    It doesn't matter whether the content is SD, HD or 4k.
    Sometimes it runs flawlessly for hours until the error mentioned above occurs.

    As of today, I use an RPi4 4GB in an Argon One housing. The content is retrieved from a NAS via NFS.

    A lot has changed since the error occurred. The RPi4 has moved from the official Kodi case and SD card to an Argon One with SSD. The network switch has also been replaced in the meantime. Only the NAS is still the same. The error persists.

    In the meantime, I activated the debug log once and was able to find the following lines in the log yesterday after the error occurred again at around 00:22.