no communication with the server
I installed the xibo pyclient and the server on the my Linux Ubuntu 14.04.1 server.
I have configured the site.cfg:
[Main]
xmdsUrl=http://
xmdsClientID=test
xmdsKey=test
xmdsUpdateInt
requireXmds=false
width=960
height=540
bpp=24
fullscreen=true
But if I start the client and press "i" all flags are grey and no new monitor was showen at the server CMS.
I have allready checkt the problem with the same Client at another Xibo Server.
Xibo pyclient version is 1.6.2 timestamp: Fri 2014-07-18 23:43:48 +0100
message:
[hotfix][cms] Missing statemaents from structure.sql
Another problem is the the screen is flare independently from the update interval at the side.cfg
I hope you can help me
Thanks a lot
Moritz Kirchner
Max-Planck-Society Munich
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Xibo Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Moritz Kirchner
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Pls check your xmdsURL it should be like xmdsUrl=http://
Revision history for this message
|
#2 |
Thanks for the fast answer but the problem is still persists.
Revision history for this message
|
#3 |
14.04 isn't supported for the client so I'd be surprised if it works at
all. However, try setting requireXmds to true initially to get the client
Registered
Revision history for this message
|
#4 |
Now i built it again on a Ubuntu 12.04.5 LTS and still have the same Problem.
When i activate requireXmds the Register Display flag would be red.
Thanks for the great support.
Revision history for this message
|
#5 |
That's normal. You need to go to your CMS and licence the display before
anything else will happen
Revision history for this message
|
#6 |
But there is no display showen in the CMS
Revision history for this message
|
#7 |
Then the server key in the client config is wrong. If you look at the
client logs it will tell you why it's unable to register
Revision history for this message
|
#8 |
The logfile says that the client can not connect to XMDS:
LOG: 2014-08-25 10:17:12 (.check:3434) 0 error Could not connect to XMDS.
LOG: 2014-08-25 10:17:12 (.check:3420) 2 info Connecting to XMDS at URL: http://
LOG: 2014-08-25 10:17:12 (.frameHandle:4604) 5 debug Added new node to info
LOG: 2014-08-25 10:17:12 (.enqueue:4584) 3 info Enqueue: setBitmap ('M1-2-3', <libavg.avg.Bitmap object at 0x951fd24>)
LOG: 2014-08-25 10:17:12 (.frameHandle:4604) 5 debug Added new node to info
LOG: 2014-08-25 10:17:12 (.enqueue:4590) 3 info Queue length is now 66
LOG: 2014-08-25 10:17:12 (.enqueue:4584) 3 info Enqueue: resize ('M1-2-3', 1280.0, 720.0, 'centre', 'centre')
LOG: 2014-08-25 10:17:12 (.enqueue:4590) 3 info Queue length is now 67
LOG: 2014-08-25 10:17:12 (.check:3434) 0 error Could not connect to XMDS.
LOG: 2014-08-25 10:17:12 (.check:3420) 2 info Connecting to XMDS at URL: http://
LOG: 2014-08-25 10:17:12 (.__init__:30) 2 info FadeInTransition plugin loaded!
LOG: 2014-08-25 10:17:12 (.frameHandle:4604) 5 debug Added new node to info
LOG: 2014-08-25 10:17:12 (.check:3434) 0 error Could not connect to XMDS.
LOG: 2014-08-25 10:17:12 (.RequiredFiles
LOG: 2014-08-25 10:17:12 (.enqueue:4584) 3 info Enqueue: setOpacity ('infoRFGreen', 0)
LOG: 2014-08-25 10:17:12 (.check:3420) 2 info Connecting to XMDS at URL: http://
Revision history for this message
|
#9 |
Then you need to investigate why that is.
If you open a browser on the client and visit
http://
Revision history for this message
|
#10 |
A XML File:
-<definitions targetNamespace
Revision history for this message
|
#11 |
So your webserver is returning a different address for itself
http://
That url isn't correct so the client can't then connect to the service.
You need to configure your webserver correctly to return either a fully
qualified DNS name for itself or something like 'localhost'
Revision history for this message
|
#12 |
I have check this with localhost and 127.0.0.1 on the server to. It was just to copy it from my workstation to this window because the xibo server isn't connect to the internet.
Revision history for this message
|
#13 |
Yes, but in the xml returned you'll see that the server is redirecting the
client to that other address.
Revision history for this message
|
#14 |
But if I add a windows client to the server there wouldn't any problems.
Revision history for this message
|
#15 |
The Windows client doesn't correctly honour the redirect in the WSDL.
You need to get that correct, then it will work. I can't help you any
further until you fix that
Revision history for this message
|
#16 |
Thanks Alex Harrington, that solved my question.
Revision history for this message
|
#17 |
But if i type http://
sorry for the trouble caused to you
Revision history for this message
|
#18 |
From the client machine, can you access the CMS at http://
If so, then use localhost in the configuration file rather than 127.0.0.1
Revision history for this message
|
#19 |
Yes, I can reach it. But after the configuration change the problem is still the same.
Revision history for this message
|
#20 |
That's very strange. Can you connect the client to a cloud account? You can
sign up for a free demo at http://
Revision history for this message
|
#21 |
No sorry
We have very hard safety instructions for our network. But thanks for your help. I will test it at a ubuntu 10.04 to check xibo with older client versions .
Revision history for this message
|
#22 |
Try hardcoding the correct address in the WSDL at the CMS end - it is in lib/service/
Revision history for this message
|
#24 |
What does it say now in the logs?
LOG: 2014-08-25 10:17:12 (.check:3434) 0 error Could not connect to XMDS.
LOG: 2014-08-25 10:17:12 (.check:3420) 2 info Connecting to XMDS at URL: http://
Revision history for this message
|
#25 |
Sorry but there are no changes in the logfile
Just the same:
LOG: 2014-08-25 10:17:12 (.check:3434) 0 error Could not connect to XMDS.
LOG: 2014-08-25 10:17:12 (.check:3420) 2 info Connecting to XMDS at URL: http://
Revision history for this message
|
#26 |
Sorry, that has progressed beyond my knowledge - you may have to try on 12.02
Revision history for this message
|
#27 |
Without being able to test against a known good CMS I don't see how we can
progress this I'm afraid
Revision history for this message
|
#28 |
Thanks for your help all problems are solved i have set of a new ubuntu 10.04 server and installed it manualy.