Exit with code 11 - Xibo 2.1/Ubuntu/Docker

[maimonguy]

Player Version

Don’t Know , It’s Xibo 2.1 Docker/Ubuntu, the player is on the same machine.

Issue

Player not Running - Player exited with code 11

I have Xibo 2.1 docker on Ubuntu with player running on the same machine.

Until yesterday , everything was working perfectly, the player is firing on Ubuntu startup, displaying a single layout presentation.

This morning, It has stopped working. the I run the player it get the below error msg - code 11
I have checked all the aspects of the Docker environment, the containers are running, the web server is working,
In fact , I can log on to the CMS and preview all the Layouts, working.

The display is authorized , and the in the Player options it is showing “Ready”.

I am able to preview all the layouts in the CMS, and even tried to make each as the default layout, to make sure the problem is not in a specific layout - no good.

There’s only one thing I can consider as “Strange”:
In the Layouts page, I do not see the thumbnails of the published layouts.

Any help/direction would be greatly appreciated.
Guy

This is the error msg from the player:

0# signalStacktraceHandler(int) in /snap/xibo-player/50/bin/player
 1# 0x00007F1FE8AE68A0 in /lib/x86_64-linux-gnu/libpthread.so.0
 2# 0x00007F1F8045143B in /snap/xibo-player/50/gnome-platform/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 3# 0x00007F1F80451B6D in /snap/xibo-player/50/gnome-platform/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 4# 0x00007F1F80452123 in /snap/xibo-player/50/gnome-platform/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 5# 0x00007F1F805C2558 in /snap/xibo-player/50/gnome-platform/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 6# 0x00007F1F805C25F5 in /snap/xibo-player/50/gnome-platform/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 7# 0x00007F1FE9F941CC in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 8# 0x00007F1FE9FC4770 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 9# 0x00007F1FE9F94330 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
10# 0x00007F1FE9FAAAE6 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
11# gdk_window_end_draw_frame in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
12# 0x00007F1FEA5DC9A3 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
13# gtk_main_do_event in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
14# 0x00007F1FE9F91765 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
15# 0x00007F1FE9FA17F5 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
16# 0x00007F1FE9FA29F6 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
17# 0x00007F1FE9FA2BF0 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
18# g_closure_invoke in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
19# 0x00007F1FE923305E in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
20# g_signal_emit_valist in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
21# g_signal_emit in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
22# 0x00007F1FE9F9AAC9 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
23# 0x00007F1FE9F86080 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
24# 0x00007F1FE8F45D03 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
25# g_main_context_dispatch in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
26# 0x00007F1FE8F45650 in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
27# g_main_context_iteration in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
28# g_application_run in /snap/xibo-player/50/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
29# MainLoop::run(WindowGtk&) in /snap/xibo-player/50/bin/player
30# XiboApp::run() in /snap/xibo-player/50/bin/player
31# main in /snap/xibo-player/50/bin/player
32# __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
33# _start in /snap/xibo-player/50/bin/player

Player exited with code 11

[maimonguy]

I think I have an answer,

• “Exited with code 11” in Linux actually means - “Resources not available temporary”
• “Code 11” will be fired in Xibo player if one of the widget in a running layout will not be accessible to the system when running.
• In my case, described above it was a single layout schedule, with around 30 regions and about 10 interactive widgets (Tickers, DataSets, webpages) - which I was suspecting.
• It has ended up that the problem was in a locally stored video file (4 seconds/2.1MB) sitting inside a small region that cause the “Code 11” to be fired.
• Deleting it solved the problem in my case.

Hope this helps someone…
Guy