Since the update, I come back to TV and its att he home page but its totally unresponsive
no SMB, SSH, Web Interface
looking at the logs i see this
2024-08-29 20:02:37.827 T:5546 info : CActiveAESink::OpenSink - initialize sink
2024-08-29 20:02:42.545 T:5546 info : CAESinkALSA::Initialize - Requested layout FL, FR
2024-08-29 20:02:43.390 T:5546 info : CAESinkALSA::Initialize - set digital codec 0
2024-08-29 20:02:45.337 T:5546 info : CAESinkALSA::Initialize - Attempting to open device “default”
2024-08-29 20:03:35.744 T:5546 info : CAESinkALSA::Initialize - Opened device “default”
2024-08-29 20:03:37.400 T:5546 info : CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2024-08-29 20:03:38.344 T:5546 info : CAESinkALSA::InitializeHW - Using data format AE_FMT_S24NE4
2024-08-29 20:03:40.592 T:5546 info : CAESinkALSA::Initialize - speaker layout 0
2024-08-29 20:03:50.457 T:5546 error : CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
2024-08-29 20:04:10.750 T:5546 error : Skipped 3 duplicate messages…
2024-08-29 20:04:03.842 T:5546 error : CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
2024-08-29 20:04:16.106 T:5546 error : CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
2024-08-29 20:04:27.709 T:5546 error : Skipped 2 duplicate messages…
2024-08-29 20:04:27.184 T:5546 error : CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
2024-08-29 20:04:58.093 T:8626 info : Skipped 1 duplicate messages…
2024-08-29 20:04:57.745 T:8626 info : weather.metoffice: Fetching Daily Forecast for ‘Wakefield (324229)’ from the Met Office…
2024-08-29 20:05:13.080 T:5546 error : CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
2024-08-29 20:05:28.222 T:5546 error : Skipped 2 duplicate messages…
this repeats on till
2024-08-29 20:17:47.692 T:5546 error : Skipped 2 duplicate messages…
2024-08-29 20:17:47.016 T:5546 error : CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover
then end of file
Hi
It’s hard to tell the issue with partial logs. Please try checking for updates again and make sure your device is fully up to date.
If the issue persists please provide some full logs via My OSMC.
Sam
Cheers Sam
Do I need to turn logs on? And can it not show all data on screen
There’s been no further updates to system just checked
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:
1 Like
cheers I know how to do that, but when I enable this, top left shows
Log output file
Mem usage
CPU usage
this is fine when the issue can be replicated straight away, this could be 24hrs later and dont want to watch tv with them in corner all time
Then put <loglevel>1</loglevel> into .kodi/userdata/advancedsettings.xml
Changed this in log went to reboot and system locked up
login as: osmc
osmc@192.168.0.222’s password:
Linux osmcCAH1982 4.9.269-60-osmc #1 SMP PREEMPT Wed Aug 28 00:45:28 UTC 2024 a arch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Aug 31 14:05:02 2024 from 192.168.0.108
osmc@osmcCAH1982:~$ grab-logs -A
Grabbing log UNAME …
Grabbing log cmdline …
Grabbing log Debian version …
Grabbing log OSMC Build Information …
An error occurred while grabbing OSMC Build Information:
FileNotFoundError: [Errno 2] No such file or directory: ‘/etc/osmc_build_info’
Grabbing log GUI Settings (abridged) …
Grabbing log guisettings.xml …
Masking private information …
Grabbing log advancedsettings.xml …
Masking private information …
Grabbing log sources.xml …
Masking private information …
Grabbing log fstab …
Masking private information …
Grabbing log mounts …
Grabbing log OSMC Packages …
Grabbing log All Other Packages …
Grabbing log APT term.log …
Grabbing log APT history.log …
Grabbing log APT sources.list …
Grabbing log APT apt.conf.d …
Grabbing log APT preferences.d …
Grabbing log APT sources.list.d …
Grabbing log System Journal …
Grabbing log lircd.conf …
Grabbing log init.d …
Grabbing log systemd …
Grabbing log Kernel Message Log …
Grabbing log Memory …
Grabbing log Diskspace …
Grabbing log /boot Contents …
Grabbing log Display Cap CTA …
Grabbing log Display Cap VESA …
Grabbing log Display Cap 3D …
Grabbing log User Display Overrides …
Grabbing log Display Mode …
Grabbing log EDID …
Grabbing log Audio Cap …
Grabbing log edid-decode …
Grabbing log ifconfig …
Grabbing log Kodi Log …
Masking private information …
Grabbing log Kodi Old Log …
Masking private information …
Writing logs to temp file …
Dispatching logs …
Exception Details:
Traceback (most recent call last):
File “/usr/bin/grab-logs”, line 1051, in dispatch_logs
raise Exception(‘Log file too large for upload’)
Exception: Log file too large for upload
Failed to upload log files, copying to /boot instead. (Unable to verify)
think ive got the file is 10.7mb, but on here says I cant upload txt
