A lot of empty kodi_crashlog_yyyymmdd.log files
Killi138
Junior Member
Posts: 24
#1
2016-08-14, 10:13
Hi,

I'm searching a problem with my live tv and wanted to have a look at the logs. But the kodi.log is empty and there are many kodi_crashlog files - please have a look:

PHP Code:
MediaMaster:~ # ls -lah /storage/.kodi/temp/
total 38
drwxr-xr-x    5 root     root        1.0K Aug 14 10:06 .
drwxr-xr-x    8 root     root        1.0K Jan  1  1970 ..
-rw-r--r--    1 root     root        3.4K Aug 26  2015 changelog.txt
-rw-r--r--    1 root     root           0 Jul 28  2015 commoncache.db
srwxr-xr-x    1 root     root           0 Jan  1  1970 commoncache.socket
-rw-r--r--    1 root     root           0 Jul 23 19:31 cookies.dat
-rw-r--r--    1 root     root           9 Aug 14 10:06 kodi.log
-rw-r--r--    1 root     root       17.9K Jan  1  1970 kodi.old.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100601.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100603.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100605.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100608.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100610.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100612.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100614.log
-rw-r--r--    1 root     root         608 Aug 14 10:06 kodi_crashlog_20160814100617.log
-rw-r--r--    1 root     root         617 Aug 14 10:06 kodi_crashlog_20160814100619.log
-rw-r--r--    1 root     root         617 Aug 14 10:06 kodi_crashlog_20160814100621.log
drwxr-xr-x    6 root     root        1.0K Jul 27  2015 scrapers
drwxr-xr-x    2 root     root        1.0K Jan  1  1970 temp
drwxr-xr-x    2 root     root        1.0K Jul 14 15:28 weather 


The crashlogs renew every few seconds (deleting old ones, creating new ones). Now I want to know why it's creatings these files - but how can I check that witzout any log outputs?

It's an openelec system on a raspberry pi 2 without monitor, only console.

I hope you can help me
Find
Reply
nickr
Retired Team-Kodi Member
Posts: 19,982
#2
2016-08-14, 10:59
Read the crashlog.

Sounds like kodi is crashing and restarting. That creates a new kodi.log, but the old one is there.

How about ssh in and run
Code:
systemctl stop kodi

That should stop the run crash cycle and enable you to look at a log. The crashlogs may be helpful too.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Find
Reply
Killi138
Junior Member
Posts: 24
#3
2016-08-14, 11:30
Ah, thank you for that stop command. Now I can read the crashlogs - but it isn't really helpfull:

PHP Code:
############## kodi CRASH LOG ###############

################ SYSTEM INFO ################
 Date: Sun Aug 14 11:26:48 CEST 2016
 kodi Options: --standalone -fs --lircdev /run/lirc/lircd
 Arch: armv7l
 Kernel: Linux 4.1.18 #1 SMP Mon Feb 29 20:48:22 CET 2016
 Release: OpenELEC 6.0.3
############## END SYSTEM INFO ##############

############### STACK TRACE #################
gdb not installed, can't get stack trace.
############# END STACK TRACE ###############

################# LOG FILE ##################



############### END LOG FILE ################

############ END kodi CRASH LOG ############# 

kodi.log is empty and the last entry in kodi.old.log is from Feb 19 2016
Find
Reply
nickr
Retired Team-Kodi Member
Posts: 19,982
#4
2016-08-14, 11:36
As a quick test you could move your .kodi folder and start kodi again.

Code:
mv .kodi .kodi.backup
systemctl start kodi
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Find
Reply
Killi138
Junior Member
Posts: 24
#5
2016-08-14, 11:56
It only creates the crashfiles again - same value in all of the files

Would it help to have a monitor connected? I use this raspberry to stream the tv signals from tvheadend into my network of kodi raspberries
Find
Reply
Milhouse
Retired Team-Kodi Member
Posts: 17,855
#6
2016-08-14, 17:27
A monitor won't help, Kodi is crashing on startup - most likely a missing a library but resetting .kodi should have resolved that.

Run this and paste the results:
Code:
journalctl | pastebinit
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Find
Reply
Killi138
Junior Member
Posts: 24
#7
2016-08-14, 18:02
PHP Code:
Aug 14 17:55:09 MediaMaster systemd[1]: kodi.service holdoff time over, scheduling restart.
Aug 14 17:55:09 MediaMaster systemd[1]: Starting Kodi Media Center...
Aug 14 17:55:09 MediaMaster systemd[1]: Started Kodi Media Center.
Aug 14 17:55:10 MediaMaster kodi.sh[12909]: Bus error
Aug 14 17:55:10 MediaMaster kernel: [[1;31mSQUASHFS error: lzo decompression failed, data probably corrupt[[0m
Aug 14 17:55:10 MediaMaster kernel: [[1;31mSQUASHFS error: squashfs_read_data failed to read block 0x31f0e90[[0m
Aug 14 17:55:10 MediaMaster kodi.sh[12909]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20160814175510.log
Aug 14 17:55:10 MediaMaster systemd[1]: [[1;39mkodi.service: main process exited, code=exited, status=135/n/a[[0m
Aug 14 17:55:10 MediaMaster kill[12928]: kill: you need to specify whom to kill
Aug 14 17:55:10 MediaMaster systemd[1]: [[1;39mkodi.service: control process exited, code=exited status=1[[0m
Aug 14 17:55:10 MediaMaster systemd[1]: [[1;39mUnit kodi.service entered failed state.[[0m 

So my question is.....which data is corrupt? Everything is readable on my sd card (as I know)

Can I repair the corrupt data or do I have to use a fresh image?
Find
Reply
Milhouse
Retired Team-Kodi Member
Posts: 17,855
#8
2016-08-14, 18:10
The SYSTEM file on your /flash partition is corrupt. This might mean your FAT fileystem is having problems, or you just need to replace the SYSTEM file with a non-corrupted version in which case drop the OE 6.0.3 tar file in your update folder and reboot your system to refresh it. Other files may also be corrupted which could prevent the upgrade from completing but as you only posted a snippet rather than what you were asked for I can't tell, so best of luck.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Find
Reply
Killi138
Junior Member
Posts: 24
#9
2016-08-14, 20:03
this is the complete output, there is no need for pastebin, the output is repeating

PHP Code:
MediaMaster:~ # journalctl
-- Logs begin at Sun 2016-08-14 17:55:03 CEST, end at Sun 2016-08-14 18:00:57 CEST. --
Aug 14 17:55:03 MediaMaster kodi.sh[12837]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20160814175503.log
Aug 14 17:55:03 MediaMaster systemd[1]: [[1;39mkodi.service: main process exited, code=exited, status=135/n/a[[0m
Aug 14 17:55:03 MediaMaster kill[12854]: kill: you need to specify whom to kill
Aug 14 17:55:03 MediaMaster systemd[1]: [[1;39mkodi.service: control process exited, code=exited status=1[[0m
Aug 14 17:55:03 MediaMaster systemd[1]: [[1;39mUnit kodi.service entered failed state.[[0m
Aug 14 17:55:03 MediaMaster systemd[1]: [[1;39mkodi.service failed.[[0m
Aug 14 17:55:05 MediaMaster systemd[1]: kodi.service holdoff time over, scheduling restart.
Aug 14 17:55:05 MediaMaster systemd[1]: Starting Kodi Media Center...
Aug 14 17:55:05 MediaMaster systemd[1]: Started Kodi Media Center.
Aug 14 17:55:05 MediaMaster kodi.sh[12861]: Bus error
Aug 14 17:55:05 MediaMaster kernel: [[1;31mSQUASHFS error: lzo decompression failed, data probably corrupt[[0m
Aug 14 17:55:05 MediaMaster kernel: [[1;31mSQUASHFS error: squashfs_read_data failed to read block 0x31f0e90[[0m
Aug 14 17:55:05 MediaMaster kodi.sh[12861]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20160814175505.log
Aug 14 17:55:05 MediaMaster systemd[1]: [[1;39mkodi.service: main process exited, code=exited, status=135/n/a[[0m
Aug 14 17:55:05 MediaMaster kill[12878]: kill: you need to specify whom to kill
Aug 14 17:55:05 MediaMaster systemd[1]: [[1;39mkodi.service: control process exited, code=exited status=1[[0m
Aug 14 17:55:05 MediaMaster systemd[1]: [[1;39mUnit kodi.service entered failed state.[[0m
Aug 14 17:55:05 MediaMaster systemd[1]: [[1;39mkodi.service failed.[[0m
Aug 14 17:55:07 MediaMaster systemd[1]: kodi.service holdoff time over, scheduling restart.
Aug 14 17:55:07 MediaMaster systemd[1]: Starting Kodi Media Center...
Aug 14 17:55:07 MediaMaster systemd[1]: Started Kodi Media Center.
Aug 14 17:55:07 MediaMaster kodi.sh[12885]: Bus error
Aug 14 17:55:07 MediaMaster kernel: [[1;31mSQUASHFS error: lzo decompression failed, data probably corrupt[[0m
Aug 14 17:55:07 MediaMaster kernel: [[1;31mSQUASHFS error: squashfs_read_data failed to read block 0x31f0e90[[0m
Aug 14 17:55:07 MediaMaster kodi.sh[12885]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20160814175507.log
Aug 14 17:55:07 MediaMaster systemd[1]: [[1;39mkodi.service: main process exited, code=exited, status=135/n/a[[0m
Aug 14 17:55:07 MediaMaster kill[12902]: kill: you need to specify whom to kill
Aug 14 17:55:07 MediaMaster systemd[1]: [[1;39mkodi.service: control process exited, code=exited status=1[[0m
Aug 14 17:55:07 MediaMaster systemd[1]: [[1;39mUnit kodi.service entered failed state.[[0m
Aug 14 17:55:07 MediaMaster systemd[1]: [[1;39mkodi.service failed.[[0m
Aug 14 17:55:09 MediaMaster systemd[1]: kodi.service holdoff time over, scheduling restart.
Aug 14 17:55:09 MediaMaster systemd[1]: Starting Kodi Media Center...
Aug 14 17:55:09 MediaMaster systemd[1]: Started Kodi Media Center.
Aug 14 17:55:10 MediaMaster kodi.sh[12909]: Bus error
Aug 14 17:55:10 MediaMaster kernel: [[1;31mSQUASHFS error: lzo decompression failed, data probably corrupt[[0m
Aug 14 17:55:10 MediaMaster kernel: [[1;31mSQUASHFS error: squashfs_read_data failed to read block 0x31f0e90[[0m
Aug 14 17:55:10 MediaMaster kodi.sh[12909]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20160814175510.log
Aug 14 17:55:10 MediaMaster systemd[1]: [[1;39mkodi.service: main process exited, code=exited, status=135/n/a[[0m
Aug 14 17:55:10 MediaMaster kill[12928]: kill: you need to specify whom to kill
Aug 14 17:55:10 MediaMaster systemd[1]: [[1;39mkodi.service: control process exited, code=exited status=1[[0m
Aug 14 17:55:10 MediaMaster systemd[1]: [[1;39mUnit kodi.service entered failed state.[[0m 
Find
Reply
willieaames
Junior Member
Posts: 25
#10
2016-08-15, 15:27
FactoryCodec - Audio: passthrough - Failed. May be you need to look into audio Codecs now.
Find
Reply
nickr
Retired Team-Kodi Member
Posts: 19,982
#11
2016-08-16, 01:04
Milhouse has given the answer - did it work?
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Find
Reply
Killi138
Junior Member
Posts: 24
#12
2016-08-21, 12:42
No, the yellow "busy" led glowed for an hour - I will reinstall everything with a fresh image
Find
Reply

Home
Search
Help
Logout Mark Read Team Forum Stats Members Help
A lot of empty kodi_crashlog_yyyymmdd.log files0