8.10 Weborbiter strange behavior + connect to proxy orbiter failed

[sq8ijk]

Hello,
I have reinstalled my LinuxMCE with beta 8.10, before I was using some alpha version on top of 8.10.

I have added web-orbiter (generic-orbiter) and it finished regenerating after which I did the quick reload.

The orbiter was listed but when I was trying to login, I was always getting the:
"Connect to proxy orbiter failed, please try again"

After this I have removed the web-orbiter from my device tree and re-added. While accessing the weborbiter.php site nothing was listed this time in the Device dropdown, so I have added yet another generic orbiter and now it was listed (In the device tree I had two generic orbiters, but only one was listed through the weborbiter.php). Anyhow the symptoms while I was trying accessing were the same:
"Connect to proxy orbiter failed, please try again"

Basically I was following the instructions from:
http://wiki.linuxmce.org/index.php/Add_Web_Orbiter

Could someone point me to the information how I could fix/debug the problem? What log level should I enable to find what might go wrong?

[jimbodude]

Did you reload the DCE Router?  If you don't the device won't start...

[sq8ijk]

Did you reload the DCE Router?  If you don't the device won't start...

I did Quick Reload Router and this didn't worked, also later I have rebooted the whole system without success.

[pga57]

Did you reload the DCE Router?  If you don't the device won't start...

I did Quick Reload Router and this didn't worked, also later I have rebooted the whole system without success.

I have the same problem this week-end (network install) and after read you post and made a core reboot this morning it worked now !

Philippe

[sq8ijk]

I have the same problem this week-end (network install) and after read you post and made a core reboot this morning it worked now !

I was trying this several times, but it didn't help. I would like to know how to find what is wrong and possibly fix it, otherwise I am left with quite unusable system

[pga57]

I have the same problem this week-end (network install) and after read you post and made a core reboot this morning it worked now !

I was trying this several times, but it didn't help. I would like to know how to find what is wrong and possibly fix it, otherwise I am left with quite unusable system

Do you have try a Quick Regen of the Generic Proxy Orbiter ?

Philippe

[theteju]

Did you reload the DCE Router?  If you don't the device won't start...

I did Quick Reload Router and this didn't worked, also later I have rebooted the whole system without success.

Once following the wiki and after quick Reload.....
You need to be extremely patient and let the system generate the orbiter. For the first time, system take more than usual time depending on your processor speed. I just generated mine after reading your post. everything went just fine.

The progress status is best seen under Advance ----> pending task. rather than under webadmin (my experience)

Hope this helps. Thanks

[jimbodude]

This has always "just worked" for me...  There are 3 things that need to happen - 1) device created, 2) router reloaded, 3) orbiter (re)generated

Once you get the device created in the web admin per instructions, reload the router.  If nothing comes up, go to Web Admin --> Devices --> Orbiters.  If the proxy orbiter isn't regenerating, you can tell it to do a full regen, and wait for the progress bar to go all the way full two times.  Once it's done, you should be able to look at the web orbiter.  Reload the router if there are still issues - but I'm usually running by this point.

[sq8ijk]

This has always "just worked" for me...  There are 3 things that need to happen - 1) device created, 2) router reloaded, 3) orbiter (re)generated

Once you get the device created in the web admin per instructions, reload the router.  If nothing comes up, go to Web Admin --> Devices --> Orbiters.  If the proxy orbiter isn't regenerating, you can tell it to do a full regen, and wait for the progress bar to go all the way full two times.  Once it's done, you should be able to look at the web orbiter.  Reload the router if there are still issues - but I'm usually running by this point.

Ok after a while I gave it a second try and it worked. So the problem was with my nvidia drivers which I have installed manually and from then nothing could be installed as apt-get was failing due to some unresolved dependency. I suspect that some packages needed to be installed to make weborbiter working properly.