Problem with New Weborbiter

[davegravy]

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>



[totallymaxed]

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

All the best


Andrew

[uplink]

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).

[uplink]

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 ).

[uplink]

Also, try Firefox and Chrome, just to rule out any Javascript issues with Internet Explorer.

[davegravy]

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.

[uplink]

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.

[totallymaxed]

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 ).

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

[Marie.O]

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

[totallymaxed]

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

:-)

[uplink]

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

[Riggs]

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

[fastie81]

hey
Where did you get the documentation?
I have been looking on the Wiki and nothing..
Please let me know.
Fastie

[Kooma]

http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0 ?
/Kooma

[totallymaxed]

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