Stuck at logo screen and can't exit to check the client! Help!

Asked by Nicholas

So here's my situation: the guy who used to manage all of my company's IT work, including xibo, has taken an extended leave of absence. He's also unable to be contacted so I can't ask him directly. So I, as the youngest person here, am the default IT guy for the time being. I have been working with xibo since he left and got a pretty good feel for updating layouts etc. The way it is set up is for the xibo client to automatically open and play as soon as the computer starts with a brief flash of the desktop and one icon that says "run.sh". The client has been functional for the past several months and plays all videos, tickers, etc that I have assigned to the layout. However, several days ago when I booted up the LAMP the xibo client just flashes the xibo logo. Multiple days and restarts later, here I am. I know the tower is connected to the network through ifconfig. Once the client has started, I have found no way to back out of it to the desktop and check the program itself. I can switch between terminals and log in to the text terminals but I'm not sure what, if anything, to do from there. I am EXTREMELY new to linux and networking in general. Any help would be greatly appreciated.

More info: To edit layouts, schedules, etc. I have been using the LAMP server's IP and going in that way. Since the above problem started, the IP comes up as "unavailable" when I type it into a URL bar. Also, since I've been messing with it, I've noticed that the LAMP IP is apparently 192.168.1.108 but the tower that supposedly runs the LAMP's IP is 192.168.1.188. Is that possible? Am I just not looking in the right place? Our server room is a mess of towers and cords, so that is a very real possibility. Thanks.

Question information

Language:
English Edit question
Status:
Answered
For:
Xibo Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Dan Garner (dangarner) said :
#1

Blimey - sounds like you fell into a mess! :-)

If the server is no longer listening on the IP address that the client is configured to connect to - then that is most likely the issue. You can get some more error information up by pressing "i" on the keyboard, which will show you a little overlay window containing the general status of the player.

I would suggest that you open the cfg file and try the other IP address.

Can you help with this problem?

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

To post a message you must log in.