LinuxMCE Forums

General => Users => Topic started by: davegravy on July 06, 2010, 06:15:52 pm

Title: Problem with New Weborbiter
Post by: davegravy on July 06, 2010, 06:15:52 pm
After apt-get updating/upgrading this morning, I followed the instructions in the wiki for the "old" weborbiter, as I understand they should still work for the new one.

The home screen will load, but clicking anywhere results in the angry flying red linux penguin (see attached)

The log seems to show that the device kills the connection immediately after loading the home screen (before any input is received from the user).

Log file below shows a router reload (12:08:34) and then starting a session in IE8 (12:09:13). I can post a detailed log if it will help.

Code: [Select]
05 07/06/10 12:08:34.506 Got a reload command from 0  <0xb3d8bb90>
05 07/06/10 12:08:37.982 Dropping all sockets... <0xb4f286f0>
05 07/06/10 12:08:37.982 Done dropping sockets! <0xb4f286f0>
05 07/06/10 12:08:38.029 void ClientSocket::Disconnect() on this socket: 0x923e4b0 (m_Socket: 6) <0xb4f286f0>
Return code: 2
2 07/06/10 12:08:38 88 (spawning-device) Device requests restart... count=1/50 dev=88
Tue Jul  6 12:08:38 EDT 2010 Restart
========== NEW LOG SECTION ==========
1 07/06/10 12:08:46 88 (spawning-device) Starting... 1
1 07/06/10 12:08:46 88 (spawning-device) Found /usr/pluto/bin/LaunchProxy_Orbiter.sh
05 07/06/10 12:08:48.272 Server's internal ip address: 192.168.80.1 <0xb4e336f0>
05 07/06/10 12:08:50.358 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.369 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.410 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.420 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.696 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.716 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.736 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.746 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.876 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.896 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:51.988 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:09:13.567 Received IMAGE 10736, but device hasn't identified itself yet. <0xb2d26b90>
05 07/06/10 12:09:13.567 Received: IMAGE 10736 <0xb2d26b90>
05 07/06/10 12:09:13.568 Sent: IMAGE 16457\n\n<IMAGE> <0xb2d26b90>
05 07/06/10 12:09:13.569 Socket::ReceiveData 0x8a764f0 failed, bytes left 0 start: 590000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 9 Incoming_Conn Socket 9 192.168.80.1 <0xb2d26b90>
05 07/06/10 12:09:13.569 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 9 192.168.80.1 <0xb2d26b90>
05 07/06/10 12:09:13.570 TCPIP: Closing connection to -1 (Proxy_Orbiter) 0x8a764f0 m_Socket: -1 <0xb2d26b90>

Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 06, 2010, 07:02:12 pm
After apt-get updating/upgrading this morning, I followed the instructions in the wiki for the "old" weborbiter, as I understand they should still work for the new one.

The home screen will load, but clicking anywhere results in the angry flying red linux penguin (see attached)

The log seems to show that the device kills the connection immediately after loading the home screen (before any input is received from the user).

Log file below shows a router reload (12:08:34) and then starting a session in IE8 (12:09:13). I can post a detailed log if it will help.

Code: [Select]
05 07/06/10 12:08:34.506 Got a reload command from 0  <0xb3d8bb90>
05 07/06/10 12:08:37.982 Dropping all sockets... <0xb4f286f0>
05 07/06/10 12:08:37.982 Done dropping sockets! <0xb4f286f0>
05 07/06/10 12:08:38.029 void ClientSocket::Disconnect() on this socket: 0x923e4b0 (m_Socket: 6) <0xb4f286f0>
Return code: 2
2 07/06/10 12:08:38 88 (spawning-device) Device requests restart... count=1/50 dev=88
Tue Jul  6 12:08:38 EDT 2010 Restart
========== NEW LOG SECTION ==========
1 07/06/10 12:08:46 88 (spawning-device) Starting... 1
1 07/06/10 12:08:46 88 (spawning-device) Found /usr/pluto/bin/LaunchProxy_Orbiter.sh
05 07/06/10 12:08:48.272 Server's internal ip address: 192.168.80.1 <0xb4e336f0>
05 07/06/10 12:08:50.358 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.369 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.410 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.420 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.696 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.716 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.736 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.746 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.876 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:50.896 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:08:51.988 Could not find text object: 670 <0xb4e10b90>
05 07/06/10 12:09:13.567 Received IMAGE 10736, but device hasn't identified itself yet. <0xb2d26b90>
05 07/06/10 12:09:13.567 Received: IMAGE 10736 <0xb2d26b90>
05 07/06/10 12:09:13.568 Sent: IMAGE 16457\n\n<IMAGE> <0xb2d26b90>
05 07/06/10 12:09:13.569 Socket::ReceiveData 0x8a764f0 failed, bytes left 0 start: 590000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 9 Incoming_Conn Socket 9 192.168.80.1 <0xb2d26b90>
05 07/06/10 12:09:13.569 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 9 192.168.80.1 <0xb2d26b90>
05 07/06/10 12:09:13.570 TCPIP: Closing connection to -1 (Proxy_Orbiter) 0x8a764f0 m_Socket: -1 <0xb2d26b90>



Hi,

I will be writing up a new Wiki page for the new Web Orbiter asap... the config and setup needed is somewhat different to the original Web Orbiter - I will write that up asap. The 'Flying Tux' cursor is a 'placeholder' for a more appropriate 'beach ball' cursor that indicates when a screen update is being processed. There is a new and updated build of Web Orbiter 2.0 in svn now that includes a number of improvements and a more appropriate 'beach ball' style cursor this should appear in the next build ;-)


Here is the wiki page for the new Web Orbiter...more work needed but it should help anyone to get started; http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0 (http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0)

All the best


Andrew

Title: Re: Problem with New Weborbiter
Post by: uplink on July 06, 2010, 07:25:57 pm
After apt-get updating/upgrading this morning, I followed the instructions in the wiki for the "old" weborbiter, as I understand they should still work for the new one.

The home screen will load, but clicking anywhere results in the angry flying red linux penguin (see attached)

The log seems to show that the device kills the connection immediately after loading the home screen (before any input is received from the user).

Log file below shows a router reload (12:08:34) and then starting a session in IE8 (12:09:13). I can post a detailed log if it will help.

Personally I don't like this message: "Could not find text object: 670". Try a full regen (not a quick one).

The "device kills connection immediately" symptom is actually alright, since the web page connects, does its thing and disconnects. Once a second you should see a "ANYNEWS?" message in the logs, because the web page checks for updates every second, and if you don't, it means the Proxy_Orbiter lacks a change (but this change would only prevent automatic refreshes from working, the rest of the web orbiter should work just fine regardless).
Title: Re: Problem with New Weborbiter
Post by: uplink on July 06, 2010, 07:30:10 pm
I will be writing up a new Wiki page for the new Web Orbiter asap... the config and setup needed is somewhat different to the original Web Orbiter - I will write that up asap. The 'Flying Tux' cursor is a 'placeholder' for a more appropriate 'beach ball' cursor that indicates when a screen update is being processed. There is a new and updated build of Web Orbiter 2.0 in svn now that includes a number of improvements and a more appropriate 'beach ball' style cursor this should appear in the next build ;-)

Actually, I didn't upload the beach ball cursor to LinuxMCE :) You still get SuperTux. I'll put it in LinuxMCE SVN now, but leave it disabled until a switch is made for selecting one or the other (some people like SuperTux :P).
Title: Re: Problem with New Weborbiter
Post by: uplink on July 06, 2010, 07:43:09 pm
Also, try Firefox and Chrome, just to rule out any Javascript issues with Internet Explorer.
Title: Re: Problem with New Weborbiter
Post by: davegravy on July 06, 2010, 08:17:47 pm
Also, try Firefox and Chrome, just to rule out any Javascript issues with Internet Explorer.

Tried Chrome and the behaviour is a bit different (though still broken). Instead of the SuperTux persisting after the first button-push, it disappears after a couple seconds and is replaced by a blank (black) screen. The only exception to this is the "Active Calls" button which yields the attached image.
Title: Re: Problem with New Weborbiter
Post by: uplink on July 06, 2010, 08:47:08 pm
OK, that rules in a Javascript issue with Internet Explorer. I don't have it, so I never tested it. The other screens seem to be botched regens.

SuperTux appears before an AJAX request is sent with a command and to load the resulting image, and then it disappears. Somewhere the AJAX request dies on Internet Explorer.
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 06, 2010, 09:34:04 pm
I will be writing up a new Wiki page for the new Web Orbiter asap... the config and setup needed is somewhat different to the original Web Orbiter - I will write that up asap. The 'Flying Tux' cursor is a 'placeholder' for a more appropriate 'beach ball' cursor that indicates when a screen update is being processed. There is a new and updated build of Web Orbiter 2.0 in svn now that includes a number of improvements and a more appropriate 'beach ball' style cursor this should appear in the next build ;-)

Actually, I didn't upload the beach ball cursor to LinuxMCE :) You still get SuperTux. I'll put it in LinuxMCE SVN now, but leave it disabled until a switch is made for selecting one or the other (some people like SuperTux :P).

Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.

Andrew
Title: Re: Problem with New Weborbiter
Post by: posde on July 06, 2010, 11:57:06 pm
Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.

SSHHHH, don't tell them. They will replace it with a waving Windows flag
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 07, 2010, 12:44:19 am
Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.

SSHHHH, don't tell them. They will replace it with a waving Windows flag

:-)
Title: Re: Problem with New Weborbiter
Post by: uplink on July 07, 2010, 01:07:28 am
Actually you just need to replace the file /var/www/pluto-admin/weborbiter/waiting.gif to change from SuperTux to anything else that you like as a 'refresh' cursor.

SSHHHH, don't tell them. They will replace it with a waving Windows flag

Or an Apple... err... apple :)
Title: Re: Problem with New Weborbiter
Post by: Riggs on July 07, 2010, 03:44:08 am
Will i followed the new Wiki, on the latest snapshot, it loaded perfect, thanks for the documentation

However if i click on any of may cams there is no picture at all
Title: Re: Problem with New Weborbiter
Post by: fastie81 on July 07, 2010, 08:25:55 am
hey
Where did you get the documentation?
I have been looking on the Wiki and nothing..
Please let me know.
Fastie
Title: Re: Problem with New Weborbiter
Post by: Kooma on July 07, 2010, 08:32:15 am
http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0 ?
/Kooma
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 07, 2010, 09:14:21 am
Will i followed the new Wiki, on the latest snapshot, it loaded perfect, thanks for the documentation

However if i click on any of may cams there is no picture at all

Are you using motion cams? ie are you using the motion package to do motion detection on your cams?

Andrew
Title: Re: Problem with New Weborbiter
Post by: Viking on July 07, 2010, 04:48:55 pm
Hi Andrew,

I assume the weborbiter picture you show above is a Dinamo edition ;)

Viking
Title: Re: Problem with New Weborbiter
Post by: Viking on July 07, 2010, 04:54:11 pm
According to the documentation  (http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0)one can have several web orbiters you just have to change the port.
But what then, how can one access them ?

Lets say one for a PC, one for a phone, one for an ipad, ...
I assume thats the idea.

Viking
Title: Re: Problem with New Weborbiter
Post by: davegravy on July 07, 2010, 05:12:56 pm
According to the documentation  (http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0)one can have several web orbiters you just have to change the port.
But what then, how can one access them ?

Lets say one for a PC, one for a phone, one for an ipad, ...
I assume thats the idea.

Viking

When you log in, you select which orbiter you want to access. Indeed, a bit of a pain to do each time, which is why chrisbirkinshaw has offered to make logins 'permanent' in this post: http://forum.linuxmce.org/index.php?topic=8880.msg71469#msg71469 (http://forum.linuxmce.org/index.php?topic=8880.msg71469#msg71469)
Title: Re: Problem with New Weborbiter
Post by: Viking on July 07, 2010, 05:33:08 pm
OK, that explains it, thanks :)
Title: Re: Problem with New Weborbiter
Post by: Riggs on July 07, 2010, 06:05:35 pm
Will i followed the new Wiki, on the latest snapshot, it loaded perfect, thanks for the documentation

However if i click on any of may cams there is no picture at all

Are you using motion cams? ie are you using the motion package to do motion detection on your cams?

Andrew

USB webcams through motion wrapper
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 07, 2010, 09:43:39 pm
Hi Andrew,

I assume the weborbiter picture you show above is a Dinamo edition ;)

Viking

Yep it is :-)

Andrew
Title: Re: Problem with New Weborbiter
Post by: Viking on July 07, 2010, 09:46:56 pm
Hi Andrew,

And I assume you are not releasing that for public use ;)

Viking
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 07, 2010, 09:50:41 pm
According to the documentation  (http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0)one can have several web orbiters you just have to change the port.
But what then, how can one access them ?

Lets say one for a PC, one for a phone, one for an ipad, ...
I assume thats the idea.

Viking

Hi Viking,

Yes thats exactly the idea. When you access your Web orbiters from http://192.168.80.1/lmce-admin/weborbiter.php (http://192.168.80.1/lmce-admin/weborbiter.php) you will be asked to login as a valid User and then you will see displayed a dropdown listing all the Web orbiters you have added to your system... simply choose the one that you want to use and click (or touch) the 'Open' button. Once your using the Web Orbiter you can click the 'Logout' button that is displayed underneath the Orbiters screen area in your browser and this will log you out and display the 'Login' screen again.

All the best


Andrew
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 07, 2010, 09:53:06 pm
Will i followed the new Wiki, on the latest snapshot, it loaded perfect, thanks for the documentation

However if i click on any of may cams there is no picture at all

Are you using motion cams? ie are you using the motion package to do motion detection on your cams?

Andrew

USB webcams through motion wrapper

Hmmm... thats interesting. Ok we dont have any USB motion cams here on our test systems (just IP Cams and they work fine). but one of the team here has a USB Cam on his home system...I'll ask him to see if he can reproduce the problem. Thanks.

Andrew
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 07, 2010, 09:56:11 pm
Hi Andrew,

And I assume you are not releasing that for public use ;)

Viking

Sorry we have no plans to release our Dianemo UI1 skin. If we do a refresh of the design at some point we may make the older design available then ;-)

All the best

Andrew
Title: Re: Problem with New Weborbiter
Post by: RayBe on July 08, 2010, 10:05:15 pm
Andrew,
The Dianemo skin really looks stunning, do u have any pointers (guidance) to how to make such a skin on your own?
or do u simply use HA designer?
All help is much appreciated

Super work u guys did,
Greets,
Raymond
Title: Re: Problem with New Weborbiter
Post by: davegravy on July 08, 2010, 10:36:44 pm
.
Andrew,
The Dianemo skin really looks stunning, do u have any pointers (guidance) to how to make such a skin on your own?
or do u simply use HA designer?
All help is much appreciated

Super work u guys did,
Greets,
Raymond

I agree. Would you sell this UI by any chance? Or would I need to buy a complete system from you to get this?
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 08, 2010, 10:46:30 pm
Andrew,
The Dianemo skin really looks stunning, do u have any pointers (guidance) to how to make such a skin on your own?
or do u simply use HA designer?
All help is much appreciated

Super work u guys did,
Greets,
Raymond

Hi Raymond,

Thanks glad you like the design.

Yes we use a combination of HA Designer and Gimp or Photoshop to create our UI's. If you search the Forum you will find numerous threads and Video tutorials by Thom who is the acknowledged master of creating UI's for LinuxMCE - we learnt what we know from him to a large extent. The rest was just a lot of trial and error... the tools currently are really not very friendly and really do demand that you have a very good understanding of the technical structure of the system. The hope is that we can change this over time - the objective is to make the process much more about design so that designers can directly get involved.

All the best


Andrew
Title: Re: Problem with New Weborbiter
Post by: totallymaxed on July 08, 2010, 10:50:53 pm
.
Andrew,
The Dianemo skin really looks stunning, do u have any pointers (guidance) to how to make such a skin on your own?
or do u simply use HA designer?
All help is much appreciated

Super work u guys did,
Greets,
Raymond

I agree. Would you sell this UI by any chance? Or would I need to buy a complete system from you to get this?

We currently do not have any plans to make our UI's available separately to Cascade or Dianemo systems. In fact separating the UI from either Dianemo or Cascade would not work as the UI's are tighly coupled to features & changes we have in our builds.

So currently you would need to purchase a NerveCentre or a complete system to get access to these UI's.

All the best


Andrew
Title: Re: Problem with New Weborbiter
Post by: RayBe on July 10, 2010, 12:55:03 am
Thanks Andrew for your responce,
when i got my new core/hybrid in place i am going to take a shot at making my own skin,
thanks also for your development of lmce

greets
Raymond