Vero 4K+ crashed

Hello all,

I received and installed the new Vero I received, happy to discover.

After have spent some hours to know why I can’t show 3D MVC (even after downgrade of the OSMC version to 18.6.0-13, it didn’t run until it was ok… I don’t know why), everything’s fine, I’m happy.

But in one week, two times I found the OSMC not available, with the front “Cross” lighted on red. No SSH access, no video output, nothing. I need to remove power on and plug it again. It doesn’t happen when I’m showing a movie, only during idle time, and to always.

Do you have any idea about what I should do ? Is there logs I can share ?

Thank you

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

Thank you for your quick answer, but I probably wasn’t clear in my previous message : “reproduce the issue” will be difficult, as I don’t know when and why it happens. I can switch on logs, but I’m afraid about the fact it will be verrrrryyyyy long if the bug doesn’t happen again before some days.

Thank you.

Than maybe not activate debug logs and just upload logs after it happened. The logs will include the previous log also.

Thank you for your help : here you are, the log I just export. The crash came about 20m minutes before, I think : http://paste.osmc.io/oxawitibon.xml

Thank you again :slight_smile:

@Sinisan If you add this to advancedsettings.xml, debug logging will be enabled but you won’t get the annoying text on-screen.

<advancedsettings>
        <loglevel>1</loglevel>
        <debug>
                <showloginfo>false</showloginfo>
        </debug>
</advancedsettings>

From what we see without debug logging, the only thing happening just before the crash is some failed hits on thetvdb.com which seems unlikely to be the cause but may be related.

Could you please try to get debug logs using the trick above?

Quitting due to POSIX signal is a kind of “clean shutdown”.
Could be overheating. Suggest you may try the OSMC skin for a couple of days to see if the crash goes away with that.

1 Like

If the device is overheating, it won’t shutdown cleanly.
Something (perhaps an add-on or system timer) is triggering a shut down on the device. If the device was overheating, it wouldn’t be possible to power it back up again immediately.