Simple IPTV Client hangs

Help and Support Raspberry Pi
1

Hi,

Suddenly, a couple of weeks ago, my Simple IPTV Client started acting up . I have not made any changes or installed any addons so can’t really point to a specific event causing the issue. I did get the latest update of OSMC but that was some time before the issue appeared.

So … to the problem. Whenever I go in to the “PVR & Live TV” option in the menu I get an animated OSMC logo for a couple of seconds and then the whole system freezez. Only thing to do is to reboot hard (pulling the power).

Logs … hmm … log uploader only says “URL: https://paste.osmc.tv/”??

2

That would indicate a issue with the log size (or the SD card). Reboot twice and then to directly upload the log.

3

Rebooted twice, still same URL.

Any way to do it manually or do you think it is the SD card?

4

Well you can login via ssh and run grab-logs -A if that doesn’t give a full URL you can try grab-logs -X

5

Both grab-logs commands give the same output … no valid URL I’m afraid.

6

Hi,

Does the issue occur, if you disable the EPG/guide?

Sounds like the PI may be running out of memory.

Thanks Tom.

7

Really odd, some additional tests before calling the SD Card broken

grab-logs -J
grab-logs -K
paste-log .kodi/temp/kodi.log
ls -lah .kodi/temp/kodi.log

8

Also the output of

df -h

may help.

1 Like
9

How do I disable EPG. Was looking for it earlier but couldn’t find anything except removing the EPG URL?

10

grab-logs -J gave https://paste.osmc.tv/ecacepejox

Should I run the other commands aswell?

11

yes will need temporarily remove the epg url to test.

12

Yes maybe that gives us a better picture. The previous command just proves that memory based logs are working

13

grab-logs -K: https://paste.osmc.tv/raqepetuso

paste-log .kodi/temp/kodi.log
Unable to upload log. Log file is too large. (32MB)

By the way, EPG is disabled.

14

Do you have component specific logging enabled? We only want debug logging enabled at this time.

15

Are you sure that you rebooted twice?
What is the output of the ls command?

17

No, only debug logging active

18

The ls -lah command output: -rw-r–r-- 1 osmc osmc 31M Mar 4 19:52 .kodi/temp/kodi.log

19

Filesystem Size Used Avail Use% Mounted on
devtmpfs 368M 0 368M 0% /dev
tmpfs 374M 9.8M 364M 3% /run
/dev/mmcblk0p2 59G 2.7G 53G 5% /
tmpfs 374M 0 374M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 374M 0 374M 0% /sys/fs/cgroup
/dev/mmcblk0p1 316M 29M 287M 10% /boot
tmpfs 75M 0 75M 0% /run/user/1000

20

Ok, more than enough space free

Not sure how long after the reboot this was done but maybe a addon is flushing the log files. I suggest to:
Run tail -n 50000 .kodi/temp/kodi.log | paste-log and tail -n 50000 .kodi/temp/kodi.old.log | paste-log

That should give you a proper URL.

21

Restarted twice (from console) and straight after boot ran the commands.

Believe it or not:
osmc@osmc-Grumbole:~$ tail -n 50000 .kodi/temp/kodi.log | paste-log
Unable to upload log. Log file is too large. (11MB)
osmc@osmc-Grumbole:~$ tail -n 50000 .kodi/temp/kodi.old.log | paste-log
Unable to upload log. Log file is too large. (11MB)

This system just does not want to be debugged! :exploding_head: