Again, the latest update ("… Kodi needs to exit. Do you want to do that?" or similar) surprised me with the incapability to access the network via Wifi.
First incident was when I tried to watch a movie and Kodi said “not available any more. Delete from library?” or similar. I restarted Kodi, tried again, the same. Noticed Kodi didn’t obtain an IP address. Rebooted again. Kodi got an IP address. Tried to watch movie, this time: absolutely unresponsive. Rebooted. Tried to SSH into it. Took a couple attempts. After finally logged in, sluggish and slow and laggy. Keypresses delayed. CPU according to Kodi’s UI ~2%.
Activated logging. Rebooted. Tried to reproduce. No reaction, CPU/FPS counter not changing. After 5min, hit the “Back” key on the remote. Re-SSH’d into it. Wanted to ‘grab-logs -A’, came back with
osmc@osmc:~$ grab-logs -A
Logs successfully uploaded.
Logs available at https://paste.osmc.tv/<html>
Tried to use MyOSMC’s log uploader. After a while it came back with
URL: https://paste.osmc.tv/<html>
At least, after a ~5 min waiting time, Kodi reacted, and I could watch the video.
So. How can I get rid of the delay, and what is happening to the log uploader?
Can you attach an Ethernet cable and check for updates again?
There was an update a while ago that caused problems with WiFi but this has since been fixed. If your device cached the old update, it’s possible you updated to this version.
Please reboot and upload new logs after trying the above.
There’s a limit of 10MB post size.
Can you stop Kodi (systemctl disable mediacenter) and reboot? The issue with networking won’t be caused by Kodi. You should then be able to upload logs.
You can try to send the log to a file on the SD card: /boot/uploadlog.txt
grab-logs -A -C
If the file is less than 10 MB, you can upload it using paste-log /boot/uploadlog.txt, since we know that paste-log is working. If it’s greater than 10 MB, use a file sharing site, such as dropbox.com or volafile.org
Ok this one worked, so we at least have a first starting point.
But what is really strange is that this file only starts 8 seconds into the boot process [ 8.026754] hdmitx: fs = 2, cd = 4, tmds_clk = 148500
So just first to recap a bit, you are generally connected via Wifi which broke with the latest upgrade and now for uploading the logs you are connected via Ethernet?
Can you run this command and share the URL. dmesg | grep dhd | paste-log
I’m watching this, but the logs aren’t complete, so hard to advise yet.
If journalctl doesn’t work, I’d suggest backing things up (copy ~/.kodi) and reinstalling OSMC
@Toast, is there any guideline by which I could proceed?
@sam_nazarko, @fzinken, thank you very much. Wifi is enabled. I am connected via Wifi. I have not used cabled Ethernet to upload logs. I also did not try another update, because I have already the latest update.
The current status is: the situation eased up a bit. For the last couple restarts, vero got an IP address via wifi, and immediately (without waiting ~5min) was able to access the network. I am not aware of a change I made in vero. I first thought that maybe my NFS server was hicking up, but the message “could not reach network” from the weather plugin and the inability to SSH into vero speaks against that.
It feels like OSMC needed a certain time or a certain amount of reboots to come back to normal operation again. Is that possible? I rebooted at least 10 times in the course of like 24 hours before I posted this thread.
Remainder of the situation: After leaving vero idle for ~16 hours, I tried to start a movie. OSMC froze up for a couple moments and came back with “not available in library any more. Delete?”. I am using autofs. So I had to reboot. Why is osmc unable to revisit the video library?
I left OSMC unattended for ~8 hours, same behaviour: selected a movie, but couldn’t be played because “missing in library”. Luckily I had the log option turned on. I had to save the logfile to SD card, because the log uploader wouldn’t upload it. SSH access also was not possible.
Tried to upload the file after a reboot, but the log is 42M big. I’ll copy it to a safe place until you tell me what to do with it
Wifi needs to be a separate issue from everything else, since issues with OSMC cannot really be worked until the network problem is solved.
I’m always surprised when people use NFS over wifi. I suppose it would be ok with read-only mounts. I’ve always been too afraid of data corruption to use NFS with wifi. But it is your data.
