Thursday 4 July 2013

How to run xibo on Wheezy, in a n00b way


I will share my impressions on ,
Running xibo python player on Debian machine.


The beginning was terrible mission... Mission impossible for my beginner knowledge in python and linux.

The machine I use for this exercise is an Ulra small form factor unit with Intel Atom n270 fan less with 1GB. of DDR2 and 160GB Sata HDD. I will not mention manufacturers or brands in my post !

    Installing basic Wheezy system in this kind of machine is not difficult, everything went smooth. First thing I did is installing xorg and fluxbox, then started investigating which used by Xibo libraries I should try to install.
   Installed:
 - Libadv
 - GCC
 - PIL - python image library
 - python-dev

Started Xibo and got plenty of errors:
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib/libstdc++.so.6' from LD_PRELOAD cannot be preloaded: ignored.
Xibo Client v1.5.2
Reading default configuration
Reading user configuration
Log Level is: 0
Logging will be handled by: XiboLogXmds
Switching to new logger

*********************************************************
The version of Berkelium installed on this system is not compatible with this version of Xibo.
Please check you have the correct version of Berkelium installed for this version of the client.
*********************************************************
I commented out the code at line 4228. exit on error exception and started run.sh again.
 - It works :) well: it displays media files and images, but not flash and websites.
Tried to find a way to install "Berkelium", but it seems everyone have problems to run it on Debian.

Seems like libstdc++.so.6 used by Xibo is older version than the one we have in Wheezy.
This player could become operational ! We just need to read the code and understand it better so we can eliminate the bugs.

I am starting to deploy Xibo also in Windows environment (written in dot.NET). Starting a new post for it.

The player plays clips since 48 hours now, no issues with this, but getting weird kernel error messages:
    Message from syslogd@debian at Jul  5 11:48:00 ...
    kernel:[ 2561.100799] Code: eb 0d 8d b6 00 00 00 00 8d bc 27 00 00 00 00 eb 0e 8d b4 26 00 00 00 00 8d bc 27 0 0 00 00 00 48 75 fd 48 c3 ff 15 e4 bb 3f c1 c3 <64> 8b 15 1c fa 47 c1 6b d2 3e c1 e0 02 f7 e2 8d 42 01 e9 e2 ff                                    
Found a huge weakness on this "Industrial" machine as the manufacturer call's it. The HDD overheats.
Ran the smartctl -Hc /dev/sda and voila, the result :)

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0022   048   039   045    Old_age   Always   In_the_past 52 (0 4 52 41)

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (    0) seconds.
Offline data collection
capabilities:                    (0x73) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        No Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (  55) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103b) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

root@debian:~# smartctl -A /dev/hda
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-4-686-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Smartctl open device: /dev/hda failed: No such device
root@debian:~# smartctl -A /dev/sda
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-4-686-pae] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   111   100   006    Pre-fail  Always       -       35896195
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       34
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       69957
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       72
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       34
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   095   089   000    Old_age   Always       -       4295032953
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   048   039   045    Old_age   Always   In_the_past 52 (0 4 52 41)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       12
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1748
194 Temperature_Celsius     0x0022   052   061   000    Old_age   Always       -       52 (0 21 0 0)
195 Hardware_ECC_Recovered  0x001a   072   067   000    Old_age   Always       -       35896195
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

Used hddtemp to see the current temp. 54°C. according to my Velleman multitester around the HDD it keeps around 60°C. I don't know how normal this could be!

Conclusions:
    Xibo is a good platform to start developing a digital signage player however, the problems I met could be solved with more research. Tried Xibo on Ubuntu, but it takes 100% of the CPU and this is not good as we risk to overheat the system we use as it is with passive cooling. As long as I understood, Xibo on debian uses the CPU for video encoding and this is what makes it overheating the system. with the same system Navori 5.2 player on Windows XP Embedded the HDD keeps under 54°C and overall system temperature it's about 50°C.

If anyone wants to help, please feel free to post your reply.


Xibo is a community open source Digital signage player, written for Ubuntu 10.04 - 32 bit and Microsoft Windows


3 comments:

  1. couold you possibly be more specific as to the reason you installed those various packages?

    ReplyDelete
  2. Hi Jessica, I had to install those packages as they are required by xibo python player!
    and seems broken

    ReplyDelete
  3. This comment has been removed by the author.

    ReplyDelete

Contact Form

Name

Email *

Message *