Stall at splash screen after update

potadalia · 3 August 2015 21:28

I updated with a manual update via the My OSMC app and am now stuck at the splash screen after files were seemingly successfully downloaded and installed. Once stalled at the spash screen for 10mins or so, the screen goes to black (wired keyboard inputs don’t produce any response on either splash screen or black screen for what it’s worth). The first time this happened, I ssh-ed in and rebooted, only for it to go through the same cycle again.

Can you upload your kodi.log? (I’m pasting from when I finished watching something and went to do an update, though I can’t see any sign of the update…)

19:57:39 T:1579152416  NOTICE: -->Python Interpreter Initialized<--
19:57:39 T:1957257216  NOTICE: CDVDPlayer::CloseFile()
19:57:39 T:1957257216  NOTICE: DVDPlayer: waiting for threads to exit
19:57:39 T:1957257216  NOTICE: DVDPlayer: finished waiting
19:57:39 T:1957257216  NOTICE: CDVDPlayer::CloseFile()
19:57:39 T:1957257216  NOTICE: DVDPlayer: waiting for threads to exit
19:57:39 T:1957257216  NOTICE: DVDPlayer: finished waiting
19:57:39 T:1957250080  NOTICE: Found 1 Lists of Devices
19:57:39 T:1957250080  NOTICE: Enumerated PI devices:
19:57:39 T:1957250080  NOTICE:     Device 1
19:57:39 T:1957250080  NOTICE:         m_deviceName      : HDMI
19:57:39 T:1957250080  NOTICE:         m_displayName     : HDMI
19:57:39 T:1957250080  NOTICE:         m_displayNameExtra:
19:57:39 T:1957250080  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
19:57:39 T:1957250080  NOTICE:         m_channels        : FL,FR
19:57:39 T:1957250080  NOTICE:         m_sampleRates     : 8000,11025,16000,22050,24000,32000,44100,48000,88200,96000,176400,192000
19:57:39 T:1957250080  NOTICE:         m_dataFormats     : AE_FMT_FLOAT,AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S32LE,AE_FMT_S16LE,AE_FMT_FLOATP,AE_FMT_S32NEP,AE_FMT_S16NEP,AE_FMT_AC3,AE_FMT_DTS,AE_FMT_EAC3
19:57:39 T:1957250080  NOTICE:     Device 2
19:57:39 T:1957250080  NOTICE:         m_deviceName      : Analogue
19:57:39 T:1957250080  NOTICE:         m_displayName     : Analogue
19:57:39 T:1957250080  NOTICE:         m_displayNameExtra:
19:57:39 T:1957250080  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
19:57:39 T:1957250080  NOTICE:         m_channels        : FL,FR
19:57:39 T:1957250080  NOTICE:         m_sampleRates     : 48000
19:57:39 T:1957250080  NOTICE:         m_dataFormats     : AE_FMT_FLOAT,AE_FMT_S32LE,AE_FMT_S16LE,AE_FMT_FLOATP,AE_FMT_S32NEP,AE_FMT_S16NEP
19:57:39 T:1957250080  NOTICE:     Device 3
19:57:39 T:1957250080  NOTICE:         m_deviceName      : Both
19:57:39 T:1957250080  NOTICE:         m_displayName     : HDMI and Analogue
19:57:39 T:1957250080  NOTICE:         m_displayNameExtra:
19:57:39 T:1957250080  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
19:57:39 T:1957250080  NOTICE:         m_channels        : FL,FR
19:57:39 T:1957250080  NOTICE:         m_sampleRates     : 48000
19:57:39 T:1957250080  NOTICE:         m_dataFormats     : AE_FMT_FLOAT,AE_FMT_S32LE,AE_FMT_S16LE,AE_FMT_FLOATP,AE_FMT_S32NEP,AE_FMT_S16NEP
19:57:39 T:1606415392  NOTICE: Thread JobWorker start, auto delete: true
19:58:01 T:1598026784  NOTICE: Previous line repeats 3 times.
19:58:01 T:1598026784  NOTICE: Thread LanguageInvoker start, auto delete: false
19:58:01 T:1598026784  NOTICE: -->Python Interpreter Initialized<--
19:58:02 T:1805218848   ERROR: EXCEPTION: Non-Existent Control 300
19:58:15 T:1498412064  NOTICE: Thread LanguageInvoker start, auto delete: false
19:58:15 T:1498412064  NOTICE: -->Python Interpreter Initialized<--
19:58:15 T:1498412064 WARNING: CPythonInvoker(23): Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.
19:58:15 T:1498412064  NOTICE: OSMC settings sending response, update
19:58:15 T:1498412064  NOTICE: OSMC settings sent response, update
19:59:13 T:1957257216  NOTICE: NFS is idle. Closing the remaining connections.

Can you upload sudo journalctl | paste-log
http://paste.osmc.io/nusavilabu

Do you use Kodi’s library mode?
It accesses video files off an NFS network share

Is it a large library?
100-200 files max (including support files)

If there’s anything else I can provide to help, let me know. In the meantime, I’m going to do a full power down and restart to see if that helps.

Thanks for all the hard work!

ActionA · 3 August 2015 21:30

We need the COMPLETE Kodi log, preferably at paste.osmc.io or some similar pastebin site please.

sam_nazarko · 3 August 2015 21:33

You haven’t answered this: do you use the library mode (Set Content option)?

potadalia · 3 August 2015 21:34

I do

DBMandrake · 3 August 2015 21:38

From ssh, what happens if you run the following:

sudo systemctl start mediacenter

If that seems to launch Kodi properly, try re-enabling the service using:

sudo systemctl enable mediacenter

However if it does not start Kodi properly run this command instead and post the output:

sudo systemctl status mediacenter

Please check that you have not run out of disk space, using:

df -h

Also it would be very helpful to see your apt log files that will show what happened during the update process:

paste-log /var/log/apt/term.log

paste-log /var/log/apt/history.log

potadalia · 3 August 2015 21:45

here’s the full log with some minor redactions to hide IPs:
http://paste.osmc.io/isuzapudih.vhdl

sam_nazarko · 3 August 2015 21:46

21:07:09 T:1957257216 NOTICE: Kodi compiled Apr 9 2015 by GCC 4.9.2 for Linux ARM (Thumb) 32-bit version 3.16.7 (200711)
21:07:09 T:1957257216 NOTICE: Running on Open Source Media Center 0.9.9, kernel: Linux ARM 32-bit version 3.18.10-1-osmc

Does not look like you’re even on the final release of OSMC. You’ve only uploaded kodi.log, so there’s not much we can discern from that.

Sam

potadalia · 3 August 2015 21:51

From ssh, what happens if you run the following:

sudo systemctl start mediacenter

If that seems to launch Kodi properly, try re-enabling the service using:

sudo systemctl enable mediacenter

Success! I’ve followed both steps and it’s now booting as expected.

Thank you so much for all the help (at what I’d imagine is a stressful post-launch point). If there’s anything I can provide to help pin down what went wrong then do let me know, otherwise I shall see myself over to the donation page

potadalia · 3 August 2015 21:56

I guess you’ll have to chalk it up to OSMC’s relentless stability(!) I’ve had it up and running at least since the RC that required a clean install (and a few manual updates beyond that), though I assumed it was updating automatically.

Dilligaf · 3 August 2015 22:34

You should ssh into OSMC and runsudo apt-get update && sudo apt-get dist-upgrade
as there was a problem with auto updates on an earlier version, this has since been fixed. If you get disconnected from your ssh session then just wait 20 minutes or so. There was a networking update that will disconnect your session when it applies, the actual updates will continue to run. You can check that all updates were installed by rerunning the above commands after a reboot

potadalia · 4 August 2015 19:31

That all worked as promised, so please consider this solved.

Thank you for all the help!