Terminal/infobeamer logs

Help
1

How can I see the logs in the terminal or somewhere else of my rpi3b+? We’re having some issues and we’d like to check out the logs.

2

Enable [X] Show remote terminal on device page on your account page, the go to your device, click on Connect and you can read the log. See also https://info-beamer.com/doc/debugging

3

The proble; is that we have a video with a lenth around 2 minutes, it plays the video and after that the screen goes black for a couple minutes and after a couple minutes its starts playing the video again. Our question is, what could be the problem? The video should play continuously on repeat without a break or blackscreen.

4

Can you provide a setup id and device id, otherwise I have no idea where to start investigating.

6

setup 19279

2026986321

7

I cannot offer extensive free support in that case, as you’re running your own custom package. But looking in the log output shows:

# logread |grep rss
Nov 12 14:04:01 ... uptime 7630s, cpu 127s+89s, rss 31724kb, 2800 objs, 60'C
Nov 12 14:04:11 ... uptime 7640s, cpu 128s+89s, rss 31724kb, 165 objs, 59'C
Nov 12 14:04:21 ... uptime 7650s, cpu 128s+89s, rss 31724kb, 146 objs, 59'C
Nov 12 14:04:31 ... uptime 7660s, cpu 128s+89s, rss 31724kb, 124 objs, 59'C
Nov 12 14:04:41 ... uptime 7670s, cpu 129s+89s, rss 31724kb, 102 objs, 59'C
Nov 12 14:04:51 ... uptime 7680s, cpu 129s+89s, rss 31724kb, 82 objs, 58'C

Notice the high objs value. This value counts the number of resource created by resource.load_image, resource.load_video and so on. This hints at a resource leak. So you allocate resource but then don’t explicitly free them. Normally this isn’t a problem as Lua is garbage collected. But image and especially video resources use up lots of GPU memory and if not enough is available, loading additional videos or images will fail. Be sure to understand https://info-beamer.com/blog/understanding-garbage-collection

To see where this resource leak is coming from, run pkill -usr1 info-beamer, which instructs info-beamer to dump a traceback of each resource allocation into the log. You can then run logread|less to see those:

[....]
stack traceback:
        scroller/tile.lua:273: in function <scroller/tile.lua:271>
image (0x144b0e0 #408005 0s ago) dynamically created (1x1)
stack traceback:
        scroller/tile.lua:273: in function <scroller/tile.lua:271>
image (0x144b340 #408006 0s ago) dynamically created (1x1)
stack traceback:
        scroller/tile.lua:273: in function <scroller/tile.lua:271>
image (0x143ad90 #408007 0s ago) dynamically created

So look at scroller/tile.lua line 273 and make sure you either don’t use resource.create_colored_texture repeatedly or use :dispose on those object if you no longer need them.

8

Where can I find the source? of scroller/tile.lua

9

You’ll have to ask your programmer or the person that created your package.