Posts by booster

Quote from Da Flex

So you use the same static IP on your router menu, and on RPi, right? In that case it could be a router problem, and your other network devices have the same problem.

No the static IP is reserved manually on the router DHCP Server but even if I don't do this and manually set the IP on the RPI4 using an IP outside the DHCP Server range the same thing happens i.e. rpi4 requires a reboot

If I was to reboot the router or just for a test remove the ethernet cable the RPI4 running LE12, and previous versions, the RPI4 does not refresh the network connection, whereas given the same scenario all other devices on the network do refresh their connections and are fine, I can see the other devices refresh happening within the router logs - nothing comes from RPI4 until a reboot; the RPI4 using manjaro for instance does refresh the connection

Quote from Da Flex

Do you use a static IP for LE?

Yes it uses static IP from DHCP and even if I manually set the static IP address on the RPI4, so not using DHCP, it's the same; as I say this happened in 10 and 11 and I think 9 also but it's been a while since I used 9; if the router restarted or network cable is disconnected it needs a reboot - wifi is disabled I don't use it, obviously I rarely, if ever take out the network cable, it's more rebooting the router; you can't reconnect from the gui as only the connect option is available along with refresh and edit; using connect and refresh causes the error and you can do anything from the cli as the rpi4 is not reachable via the network bu I'd imagine it'd fail as well

Bit the bullet and did a clean install of 12; everything definitely working as expected now - haven't gone backwards; it actually fixed and error notification I used to get after startup whereby the PVR-HTS addon would report an invalid response from the TVHeadend server hosted on this same device - this now connects straight away without error

The behaviour of having to reboot if you restart your router or take the Ethernet cable out is still there, you get the Input/output error I reported earlier if you try to refresh or connect - this was there in 10 and 11 so not new

Spoke too soon, couldn't connect via dns again this morning, so will enable debugging and post the logs in a few days

So I had updated to https://test.libreelec.tv/12.0/RPi/RPi4/…-4513878.img.gz 12 pre-release

Before and after this update I noticed, nothing to do with previous or this version, the addon search was causing a crash and reboot, so after this update I deleted /storage/.kodi/userdata/Database/Addons33.db as it appeared to be corrupt, this is ok as it gets recreated after a reboot, all addon data isn't lost, they just need re-enabling again; after the reboot I then re-enabled and updated all my addons; I'd also noticed that the cli argoone40 v1 script no longer worked, it didn't seem to close down rpi4 properly, I've removed this cli script and have installed the addon version 0.0.13 mentioned in RE: [RPi4B] Argon One Case Shutdown - must say the addon is a lot better to manage than the cli IMHO, thanks HarryH

After a few days of testing my Libreelec 12 is functioning as expected; thank you Libereelec team

Quote from Da Flex

booster

We currently do internal tests on LE 12. No issues so far. Maybe official release next week.

You can configure LE as NAS, or you can autostart Kodi on Raspberry Pi OS.

Yeah LE NAS is a bit limited in the Samba users department when I was looking at it, unfortunately I'd like more control with that, hence the thought of a full OS....saying that I'm still more than happy with LE it does it's job very well, so no great hurry as the Synology is still alive and kicking

As regards this issue; if it fails overnight I'll be tempted to do a fresh install, if for nothing else but to rule out any spurious settings; doesn't harm to have a bit of a spring clean now and again

Da Flex You must be reading my mind yeah was waiting for LE12.0 to come out then I'm going to back that up and give a full Linux OS a go as I want a little more functionality than just Kodi; I'm looking at Manjaro as I already use that elsewhere, but I was also thinking of giving Raspberry Pi OS another blast, I tried it a few years ago but Libreelec peaked my interest more. My synology NAS is 10 years old now, it still works fine, gets no updates though and I'm pretty sure RPI4B consumes less juice, but ultimately an OS allows me more control and flexibility especially needed if I eventually retire my Synology NAS or it dies, whichever comes first

VLouis Yeah, rebooting it every day you will not see the issue, it seems to happen sometime after 24 hours or so. I've installed the LE 12 Pre release from the nightly of the 26/04 now and I'm running the test again with debugging, so will post the log as I'm pretty sure the problem is still there

But in anticipation of it still failing I've got the cron reboot waiting in the wings, about 3-4am should be about right for me on this I think

Quote from MatteN

Not sure when this started for me but its been there a while, i have four Pi4 but only one thats on 24/7 and shows this behaviour, maybe i should leave the others on for now and see what happens.

MatteN pretty sure 11.0.6 was fine, can't remember this scenario occurring; looking at the change logs from 12 beta 2 to the pre release I'd be amazed if the behaviour wasn't still there, I'll confirm after testing once it's been built

If push comes to shove I was thinking I could add a cron to restart in the quiet hours of the morning, I'm running a central mariadb for kodi on this so turning it off would be inconvenient, unless I move the database to my nas

Once the problem triggers you can't do anything with the network connection, the gui thinks it's disconnected as the connect option is available but using that gives the input/output error, and it just hangs when you try to take it down and up via ssh; nothing in the router logs seem to indicate anything's up; as we've both said it is still accessible via the IP Address of course

Just a quick update, contrary to my initial thoughts , the LE 12 Beta 1 also exhibited this behaviour, so for me, 11.0.6 was fine

As there is a pre release LE 12 incoming, githash 4513878, I shall wait for that nightly to be built; I'll install and test this one and I'll link to the log if it fails

Quote from chewitt

booster share a full debug log please.

Thanks for the reply, will get the logs done in the next couple of days, I'm just retesting beta 1, but can confirm the problem exists in the nightly of 21/04.

I should also add for completeness that I rebooted my router which had no affect, but this wasn't a surprise as I noticed since I started using libreelec from version 9 onwards that the reboot of a router also requires the reboot of the libreelec rpi4....

MatteN thanks for confirmingyeah the ip address is accessible but not as nice to use and if you change ip address for whatever reason you have to change it everywhere and there is obviously some issue somewhere, which, who knows, may be causing other issues

I'm using a RPI4 8GB which is on 24/7, connected only via an ethernet cable, with 12 Beta 2, after running for 24 hours I'm unable to connect using the host name from any linux or android devices; if I go into the Libreelec Configuration Addon the top option on the connection is connect rather than disconnect, implying it's not connected at all, but when you choose the connect option it results in a Input/output error - see attachment log file snippet; the RPI4 is however still accessible using the static IP Address it has been assigned, so it is connected but somehow has lost the ability to be access via the hostname , the only way I've found to resolve the issue is to reboot the RPI4 and all then works until a day passes and then it is again unreachable via the hostname until a further restart; using 12 Beta 1 or 11.0.6 this didn't happen

Just confirming the LiberELEC 11 RPI4 nightly build of the 20240117 fixes the CIFS regression issue

sky42 thanks for the swift turnaround, much appreciated

I've an RPI4 and upgraded to 11.0.5, I have a CIFS mount to a NAS and I use the TVHeadend service with the pvr-hts Addon

Upon upgrade no previously recorded programmes from TVHeadend are listed in the TV section and any attempt to record fails; on looking at the logs the error message reports insufficient disk space on the mount, this isn't correct as there is 880+GB free; I can browse the files, copy files and play the recorded programmes from the mount, however when I df the mount it returns with resource temporarily unavailable. On further investigation / googling there seems to be a suggestion that kernels 6.1.70 and 6.1.71 have a regression which breaks getting available disk space on CIFS

I've reverted back to 11.0.4 and all is working as expected again; in that the df now returns the 880+GB free space, I am able to record and I can see previous recordings again