Log Upload gets Stuck at 'Retrieving System'

Help and Support
1

Was trying to upload logs for a different issue and found that I couldn’t use the OSMC tool to upload my logs. Seems to get stuck at ‘Retrieving System’ see screenshot below. I left it there for a few minutes with no progress. Command line tool seemed to stall out too, had to CTRL-C to cancel it, here’s where it was when I did that:

Traceback (most recent call last):
  File "/usr/bin/grab-logs", line 893, in <module>
m.launch_process()
  File "/usr/bin/grab-logs", line 705, in launch_process
result = self.write_to_temp_file()
  File "/usr/bin/grab-logs", line 775, in write_to_temp_file
self.log_blotter = [x.replace('\0', '') for x in self.log_blotter]
KeyboardInterrupt

Any tips on what should do to fix?
PS: FWIW this is running on a Vero 4K (not +)

Log%20Stuck
Log%20Stuck3871×2167 319 KB

2

Do you have free space?
Check df -h

3

Seems I should have plenty:

osmc@vero:~$ df -h
Filesystem           Size  Used Avail Use% Mounted on
devtmpfs             774M     0  774M   0% /dev
tmpfs                895M  472K  895M   1% /run
/dev/vero-nand/root   14G  6.2G  7.0G  47% /
tmpfs                895M     0  895M   0% /dev/shm
tmpfs                5.0M     0  5.0M   0% /run/lock
tmpfs                895M     0  895M   0% /sys/fs/cgroup
tmpfs                179M     0  179M   0% /run/user/1000
4

Reboot twice and try logs again. If the logs are to large, they may fail (but not normally this way)

Try from ssh as you get get more feedback.

5

I rebooted a few times and tried to crash it again. Crashed as expected. Grabbing the logs took a while but eventually it finished:

$ date;grab-logs -A -C;date
Mon Jun 17 18:45:40 PDT 2019
Logs copied to /boot/uploadlog.txt on the SD card FAT partition
Mon Jun 17 18:52:17 PDT 2019

Can’t upload though because they’re too large:

$ paste-log /boot/uploadlog.txt
Unable to upload log. Log file is too large. (113MB)

Anything I should do to clear old logs now that I’ve grabbed the file?

6

Rebooting twice will clear the kodi logs so they will not be the problem.

I’m not sure what to try from here, hopefully @sam_nazarko will have an idea.

7

Thanks @bmillham

I uploaded the logs on my own and referenced them in this issue: