All client connections lost - no reconnect possible

Asked by Stephan Benik

Situation:
Server:
Ubuntu 10.04
Xibo Server 1.3.2

Clients:
3 x Ubuntu 10.04 Xibo Clients Python clients 1.2.0
2 x Windows (Win7 + XP) Clients 1.2.2

All clients worked fine for a long time. Since yesterday all connections are broken between clients and server. The only change on the server the last days I made, was to install postgres database support, but I don't see a time context between the install and the broken connections. The last shown connection on the "Displays"-page was definitely AFTER the installation-time.

All network connections are unchanged and still working. I tried to reregister both Windows-machines, but I got the message: "Your client is not of the correct version for communication with this server." By the way it worked with exactly this client-versions a long time.

Where can I start to debug?

Thanks a lot in advance for your help!

Regards. Benki

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Stephan Benik
Solved:
Last query:
Last reply:
Revision history for this message
Alex Harrington (alexharrington) said :
#1

Xibo server 1.3.2 is NOT compatible with any 1.2 series client.

The clients will never have talked to this version server.

You either need to revert the server to 1.2.2 (restoring the 1.2.2 database backup you took before you upgraded) or upgrade your clients to 1.3.2 (Windows) and 1.3.0 (Ubuntu) - having read the information about 1.3 series being a development preview and unsuitable for production use - you'll find a copy in the release notes.

Alex

Revision history for this message
Stephan Benik (stephan-benik) said :
#2

Thank you for your very soon response.

Thats really strange. I definitely never updated the server/clients manually. I did changes on layouts last week, which were direct taken by the clients.

Are there automatic xibo update functions within the Ubuntu updates? I'm not able to explain how long and why the server is on this version. But they talked last week and a long time before.

Since I never knowingly upgraded the server and havent backed up the 1.2.2 database is there a way back to 1.2.2 at all? It seens easier to downgrade one server than upgrade all clients.

Thanks

Benki

Revision history for this message
Alex Harrington (alexharrington) said :
#3

There's no automatic updates in Xibo or in Ubuntu for Xibo. Somebody upgraded that server at some point.

It's not possible to roll back server versions without a database backup as the database schema is changed as part of the upgrade.

As I explained before, it's not possible for your 1.2.x clients to talk to a 1.3 series server - although they would have continued to show cached content since the server was upgraded. They use a different XMDS schema version which is incompatible.

Alex

Revision history for this message
Stephan Benik (stephan-benik) said :
#4

Sorry, I gave you wrong informations. The 3 Ubuntu clients running version 1.3.0. This explains the taken change of the layout last week. I upgraded one Windows-1.2.-client and it connects! :-)

So the problems are only those 3 Ubuntu clients.

Where can I start to debug?

Thanks

Revision history for this message
Alex Harrington (alexharrington) said :
#5

If you restart the clients to they connect then?

If not, what colour are the status lights on the infoscreen?

Alex

Revision history for this message
Stephan Benik (stephan-benik) said :
#6

I've restartet all clients and the server. No connection. Status-lights are all red.

Revision history for this message
Alex Harrington (alexharrington) said :
#7

So red status lights mean that there's an error condition.

If they're all red, then it's very likely that either they're not licensed or the server key has been changed.

Check the configuration on them carefully.

If that doesn't work, switch them to logging to screen and then see if there's any output on the console to show why they won't connect.

In the site.cfg, add/amend as follows:

[Logging]
logWriter=XiboLogScreen
logLevel=10

Alex

Revision history for this message
Stephan Benik (stephan-benik) said :
#8

Thanks a lot. I'll try it on monday and give feedback. :-)

Revision history for this message
Stephan Benik (stephan-benik) said :
#9

The logging told me I run a wrong client version, but it is 1.3.0 on Server 1.3.2

I unregister the display and run the automated client update and - voilà - its working fine again :-)

Thanks for all the help!