Xibo Client 1.2.2 loose connection to server, but display stays ok

Asked by Greebo on 2012-02-11

Hi there Guys!

Xibo is an awesome project, congrats for such a good piece of work!

Anyway I am using a few Xibo 1.2.2 Windows Clients with an Ubuntu 10.10 server and Ubuntu 10.04LTS server. Everything goes pretty well beside that one problem...

I have been noticing, from time to time, some connection problems, the client "logged in" flag is going down (red), and I sure cannot tell why, ande because of what. Even sometimes it goes down for like one or two days, and then it comes up again. The Clients are located around a few small cities around mine, so i've been checking it the displays are ok, and they were. Everything from last flawless download was being displayed, and the client itself was ok (no error and crash), just the connection to servers.

I am using XiboClients 1.2.2 with XiboServer 1.2.2 (1.2.2.1 tar gz). Windows xp sp3 and Windows 7 HP on ubuntu 10.10. and 10.04 as i mentioned. Generally everything is ok, but i am concerned what is wrong with the connection. The funny thing is, that it happens only on some of the clients, and generally every client is almost the same configuration (no additional software, just xibo nad ultravnc, sometimes thightvnc). Besides, even if the flag goes down, and the client doesn't have connection to the server, i can ping it and even use vnc in local network, it does not say it is connected to the web, but it has its static ip like it should)...

If anyone can help where to start finding the solution, I would be glad and Thank You!

To be honest, I would love to donate Xibo project, i am Just a student, but If I earned some good money, I would! You guys rock!

Stay cool :)!

Question information

Language:
English Edit question
Status:
Answered
For:
Xibo Edit question
Assignee:
No assignee Edit question
Last query:
2012-02-21
Last reply:
2012-02-21
Greebo (greeboss) said : #1

I was wondering if there could be some point in the IP adress, here is what i am concerned about:

- above problem happens on client where there is an external static IP adress of the network (two clients are in local area network, but in the IP adress is the same, and the server is not in this area network, it is outside)

- there are some clients I use which are in other local area (server outside) but the external IP of the network is dynamic (it changes every few days)

Is there any possibility that is the issue? and why ?

Cheers

Piotr

Dan Garner (dangarner) said : #2

I don't think the ip address changing on the client will cause any problems... as long as the server ip address remains the same.

The client does all the communication - so if the login light goes red it means that client hasn't been able to reach the server recently.

Does your server IP address change?

Greebo (greeboss) said : #3

Thanks for such a fast answer!

Of course, the server's IP is static and it's online 24h.

I quess the problem is in either client internet connection or IP adress (maybe firewall or something?) or some software bug on the client side (Windows configuration? Client configuration?).

To bo honest i've been using Xibo for quite a long time (1,5 y), I have been using diffirent configs and operating systems. And I just can't figure out what can be wrong. I hope it is just the connection bug. Where can I seek for some errors? any log beside apache?

Can any firewall (windows?switch?main router?) disable the connection of xibo client after some period of time? like after 24 or 48 hours?

Just to be clear, connection interval is set to 180 sec and 60 sec on these "error" clients, so the red light should remain green all the time.

Cheers

Piotr

Greebo (greeboss) said : #4

hmm... I was just wondering if the connection can be interuppted by local Windows server or some main router?

I mean, I used to configure and register displays at home office, and then just plug them into the web in mentioned places in local networsk. Maybe there is some proxy server? but would the displays worked fine for like a week or two and then crush if there were a proxy server or something like that (local dynamic ip or smthing)?

Sorry for so many questions, but I cannot stop thinking about the problem, and I am a person who has to find the answers ;).

Thanks again, looking forward to hear from You,

Cheers
Piotr

Greebo (greeboss) said : #5

And one more thing ;)

reloading the xiboclient (restarting the computer) helps in most cases. i am starting to worry :)

Cheers

Dan Garner (dangarner) said : #6

There really isn't anything that complex about the clients communication with XMDS (the server) - it is a simple SOAP web service. Because its a simple SOAP service, we could treat it as a simple webpage for the purposes of debugging the problem... so perhaps there is something occasionally causing a problem with that clients internet connection?

I would say that if it connected fine while you were registering the display, and also connected fine for the first few collection intervals... then the client is probably fine.

It is quite odd that a restart would fix the problem (this does go against what I mentioned above as it points to a client problem).

For debugging in the short term, perhaps you could consider installing the DEBUG client on one of the problem PC's, we will then get a much more detailed FILE output of the internals of the client. Perhaps this would help us shed some light on the problem.

The good news (in the long term) is that we are currently rewriting and unifying the communication with XMDS across both clients into an app that we are currently calling "Media Collection Agent"

Greebo (greeboss) said : #7

Thanks for YOur interest very much!

Today I have visisted those players I mentioned, and checked simple operation while the client was on. I tried to reach some websites and it went fine, without any problem. But Client was still offline at server (red icon). I restarted the app XiboClient, and then it has connected to the server instantly. I am worried, cause that means it is the client, right? IS there anything that can make disturb client connection after a few hours? like some firewall or something?

So should i download the debug client? and then where shall i look for some logs?

Thanks a lot, hope i will find the problem.

Piotr

Dan Garner (dangarner) said : #8

Yes, please try the debug client... it it doesn't automatically create a log file in the install directory, then you can follow these instructions (http://wiki.xibo.org.uk/wiki/Turn_on_Debugging_in_the_Debug_Client_Build)

Feel free to either upload the resulting log file somewhere and post the link here... or send the file to <email address hidden> quoting the question number.

Greebo (greeboss) said : #9

Hello Dan!

Again, I have noticed that one of my players went down (status not logged in), but it was at my office. I checked the display, but unfortunately there was a windows which said something like that:XiboClient.exe stopped working, and the program is closed" and there was a windows which said that there could be more info in some files. The text from those files is listed below:

WER.3BB.tmp.appcompat.txt

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="XiboClient.exe" FILTER="CMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="AxInterop.ShockwaveFlashObjects.dll" SIZE="28672" CHECKSUM="0xF8966FB9" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION=" " FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="AxInterop.ShockwaveFlashObjects.dll" INTERNAL_NAME="AxInterop.ShockwaveFlashObjects.dll" LEGAL_COPYRIGHT=" " VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="02/03/2012 13:41:21" UPTO_LINK_DATE="02/03/2012 13:41:21" VER_LANGUAGE="Język neutralny [0x0]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="AxInterop.WMPLib.dll" SIZE="61440" CHECKSUM="0xD0C7B299" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION=" " FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="AxInterop.WMPLib.dll" INTERNAL_NAME="AxInterop.WMPLib.dll" LEGAL_COPYRIGHT=" " VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="02/03/2012 13:41:21" UPTO_LINK_DATE="02/03/2012 13:41:21" VER_LANGUAGE="Język neutralny [0x0]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="Interop.ShockwaveFlashObjects.dll" SIZE="32768" CHECKSUM="0x36912007" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION=" " COMPANY_NAME=" " PRODUCT_NAME="Assembly imported from type library 'ShockwaveFlashObjects'." FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="Interop.ShockwaveFlashObjects.dll" INTERNAL_NAME="Interop.ShockwaveFlashObjects" LEGAL_COPYRIGHT=" " VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="02/03/2012 13:41:19" UPTO_LINK_DATE="02/03/2012 13:41:19" VER_LANGUAGE="Język niezmienny (kraj niezmienny) [0x7f]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="Interop.WMPLib.dll" SIZE="339968" CHECKSUM="0x76C2B368" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION=" " COMPANY_NAME=" " PRODUCT_NAME="Assembly imported from type library 'WMPLib'." FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="Interop.WMPLib.dll" INTERNAL_NAME="Interop.WMPLib" LEGAL_COPYRIGHT=" " VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="02/03/2012 13:41:20" UPTO_LINK_DATE="02/03/2012 13:41:20" VER_LANGUAGE="Język niezmienny (kraj niezmienny) [0x7f]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="XiboClient.exe" SIZE="397312" CHECKSUM="0x9F98AB6B" BIN_FILE_VERSION="2.0.0.0" BIN_PRODUCT_VERSION="2.0.0.0" PRODUCT_VERSION="2.0.0.0" FILE_DESCRIPTION="XiboClient" COMPANY_NAME="Xibo" PRODUCT_NAME="Xibo Digital Signage" FILE_VERSION="2.0.0.0" ORIGINAL_FILENAME="XiboClient.exe" INTERNAL_NAME="XiboClient.exe" LEGAL_COPYRIGHT="Copyright Dan Garner © 2008, 2009" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="2.0.0.0" UPTO_BIN_PRODUCT_VERSION="2.0.0.0" LINK_DATE="02/03/2012 13:41:30" UPTO_LINK_DATE="02/03/2012 13:41:30" VER_LANGUAGE="Język neutralny [0x0]" EXE_WRAPPER="0x0" FILE_ID="0000ff300afa847e396eb24f8a3b8a10a63c4f0ee004" PROGRAM_ID="0003d18ce9336856088bafc99756bf7f866200000000" />
    <MATCHING_FILE NAME="XiboClient.vshost.exe" SIZE="5632" CHECKSUM="0xB0D5BDDE" BIN_FILE_VERSION="8.0.50727.42" BIN_PRODUCT_VERSION="8.0.50727.42" PRODUCT_VERSION="8.0.50727.42" FILE_DESCRIPTION="vshost.exe" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft (R) Visual Studio (R) 2005" FILE_VERSION="8.0.50727.42" ORIGINAL_FILENAME="vshost.exe" INTERNAL_NAME="vshost.exe" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x2EDC" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.0.50727.42" UPTO_BIN_PRODUCT_VERSION="8.0.50727.42" LINK_DATE="09/23/2005 10:27:36" UPTO_LINK_DATE="09/23/2005 10:27:36" VER_LANGUAGE="Język neutralny [0x0]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="XiboClient.XmlSerializers.dll" SIZE="49152" CHECKSUM="0x2798C1C6" BIN_FILE_VERSION="2.0.0.0" BIN_PRODUCT_VERSION="2.0.0.0" PRODUCT_VERSION="2.0.0.0" FILE_DESCRIPTION=" " FILE_VERSION="2.0.0.0" ORIGINAL_FILENAME="XiboClient.XmlSerializers.dll" INTERNAL_NAME="XiboClient.XmlSerializers.dll" LEGAL_COPYRIGHT=" " VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="2.0.0.0" UPTO_BIN_PRODUCT_VERSION="2.0.0.0" LINK_DATE="02/03/2012 13:41:31" UPTO_LINK_DATE="02/03/2012 13:41:31" VER_LANGUAGE="Język neutralny [0x0]" EXE_WRAPPER="0x0" />
</EXE>
<EXE NAME="nvd3dumx.dll" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="nvd3dumx.dll" SIZE="11778664" CHECKSUM="0x307D9A92" BIN_FILE_VERSION="8.17.11.9666" BIN_PRODUCT_VERSION="8.17.11.9666" PRODUCT_VERSION="8.17.11.9666" FILE_DESCRIPTION="NVIDIA Compatible Vista WDDM D3D Driver, Version 196.66 " COMPANY_NAME="NVIDIA Corporation" PRODUCT_NAME="NVIDIA Windows Vista WDDM driver" FILE_VERSION="8.17.11.9666" ORIGINAL_FILENAME="NVD3DUM.DLL" INTERNAL_NAME="NVD3DUM" LEGAL_COPYRIGHT="(C) NVIDIA Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x3" MODULE_TYPE="WIN32" PE_CHECKSUM="0xB46B81" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.17.11.9666" UPTO_BIN_PRODUCT_VERSION="8.17.11.9666" LINK_DATE="02/17/2010 16:48:29" UPTO_LINK_DATE="02/17/2010 16:48:29" EXPORT_NAME="NVD3DUMX.dll" VER_LANGUAGE="Angielski (Stany Zjednoczone) [0x409]" EXE_WRAPPER="0x0" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="1162240" CHECKSUM="0x52ABA30C" BIN_FILE_VERSION="6.1.7600.16385" BIN_PRODUCT_VERSION="6.1.7600.16385" PRODUCT_VERSION="6.1.7600.16385" FILE_DESCRIPTION="Biblioteka DLL klienta Windows NT BASE API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="System operacyjny Microsoft® Windows®" FILE_VERSION="6.1.7600.16385 (win7_rtm.090713-1255)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. Wszelkie prawa zastrzeżone." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x128DD7" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7600.16385" UPTO_BIN_PRODUCT_VERSION="6.1.7600.16385" LINK_DATE="07/14/2009 01:31:11" UPTO_LINK_DATE="07/14/2009 01:31:11" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="Polski (Polska) [0x415]" EXE_WRAPPER="0x0" />
</EXE>
</DATABASE>

WERE986.tmp.WERInternalMetadata.xml

<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
 <OSVersionInformation>
  <WindowsNTVersion>6.1</WindowsNTVersion>
  <Build>7600 </Build>
  <Product>(0x3): Windows 7 Home Premium</Product>
  <Edition>HomePremium</Edition>
  <BuildString>7600.16617.amd64fre.win7_gdr.100618-1621</BuildString>
  <Revision>1</Revision>
  <Flavor>Multiprocessor Free</Flavor>
  <Architecture>X64</Architecture>
  <LCID>1045</LCID>
 </OSVersionInformation>
 <ProblemSignatures>
  <EventType>APPCRASH</EventType>
  <Parameter0>XiboClient.exe</Parameter0>
  <Parameter1>2.0.0.0</Parameter1>
  <Parameter2>4f2be40a</Parameter2>
  <Parameter3>nvd3dumx.dll</Parameter3>
  <Parameter4>8.17.11.9666</Parameter4>
  <Parameter5>4b7c1ddd</Parameter5>
  <Parameter6>c000041d</Parameter6>
  <Parameter7>00000000005987b6</Parameter7>
 </ProblemSignatures>
 <DynamicSignatures>
  <Parameter1>6.1.7600.2.0.0.768.3</Parameter1>
  <Parameter2>1045</Parameter2>
  <Parameter22>917f</Parameter22>
  <Parameter23>917f5fee584d46d9dccd514186da928c</Parameter23>
  <Parameter24>3f18</Parameter24>
  <Parameter25>3f1830c2c2d908444d69b778933f2ef4</Parameter25>
 </DynamicSignatures>
 <SystemInformation>
  <MID>116E994B-8072-496A-8616-46469B9B621E</MID>
  <SystemManufacturer>Acer</SystemManufacturer>
  <SystemProductName>Aspire R3700</SystemProductName>
  <BIOSVersion>P01-A2</BIOSVersion>
 </SystemInformation>
</WERReportMetadata>

To be honest, I have got no idea what is this all about... but maybe we can run a script which is monitoring XiboClient.exe and when such error occurs, it just restarts XiboClient.exe?

Cheers Piotr

Greebo (greeboss) said : #10

and there is one more thing, I use XiboClient.exe as shell, instead of explorer.exe. Does it have to do something with crashes?

It's not a configuration we've ever tested. It would certainly be worth setting one machine up using Explorer as the shell and running the client as we intend and see if that changes anything.

Can you help with this problem?

Provide an answer of your own, or ask Greebo for more information if necessary.

To post a message you must log in.