RE: [beagleboard] Cloud9 Blank White Screen

[William Pretty Security]

I just tried with my version of Firefox and it worked fine.

 

My version is: 18.0.2

 

Hope this helps

 

 

From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com] On Behalf Of ahunt...@gmail.com
Sent: Friday, February 15, 2013 10:34 PM
To: beagl...@googlegroups.com
Subject: [beagleboard] Cloud9 Blank White Screen

 

Hi all,

First of all, go easy on me; I am about as green to the world of electronics as one can get. I am a Mechanical engineer looking to expand my horizons with an imbedded robot control project. I figured I would start by going through some of the BeagleBone tutorials. I've gotten the bone up and running. It talks to my laptop over USB and ethernet via Putty. When I navigate to 192.168.7.2, the BeagleBone 101 page loads, but when I navigate to 192.168.7.2:3000, a blank white screen loads. It does, however, label the tab as cloud9.

I'm pretty sure it is a problem on my PC, since I do not get the same blank screen on my CAD station at work; Cloud9 loads just fine. On my laptop, I get the same white screen on both FireFox and Chrome. Anybody have any ideas what is causing this?

Thanks,

Aaron

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2899 / Virus Database: 2639/6101 - Release Date: 02/13/13

---

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2899 / Virus Database: 2639/6101 - Release Date: 02/13/13

[Aaron Hunter]

I tried updating both FireFox and Chrome, with no changes. Anybody else have any ideas?

[Jason Kridner]

On Sat, Feb 16, 2013 at 10:10 PM, Aaron Hunter <ahunt...@gmail.com> wrote:
> I tried updating both FireFox and Chrome, with no changes. Anybody else have
> any ideas?

Have you tried deleting all cookies?

[Aaron Hunter]

[Aaron Hunter]

Thanks, but I tried that, and still no love. I tried to pull it up on my wife's laptop, and got the white screen. So far, the only real difference I can come up with is that my work machine is 64 bit, while the home computers are 32 bit.

[Aaron Hunter]

An update: I tried again on my work computer, and now it is also getting the white screen, so it looks like it is something on the bone causing the problem. That said, I am about to move on, since I never planned on using BoneScript for my project anyways.

[bissch...@gmail.com]

Sorry to reboor this thread, but the same problem occured on my Bone. I have been working on it locally last week and since then I can't access it from my laptop anymore. I'm kind of at a loss here, because I do need the rmote connection every once in a while. It seems that it is indeed a problem on the Bone itself.

I'm using a BeagleBone Black rev C, with stock Debian and cloud9. Before last week I had no problem what so ever... 

For the record... I do see the Cloud9 logo popping up in my (remote) browser for a few secs and afterwards the screen goed blank. The tab does show Cloud9 with the logo. Owh... and I can still access it via PuTTY, so it's not the connection itself.

Any idea's???

Op zaterdag 16 februari 2013 16:56:59 UTC+1 schreef William Pretty Security:

[brettma...@gmail.com]

I'm also seeing the exact problem you mention. This seems to have happened to us both within the last 24 hours. I think it must involve some 3rd party server that is called from a client-side script. Please see my comment below that I posted on another support site.

-----------------

I've been doing development on the Beaglebone Black using the Cloud9 IDE for over a year now. It always worked for me until today when suddenly it started showing a blank white screen after the "Loading Your Workspace" screen. The Cloud9 IDE works fine when working directly in the BBB but not when I remotely access it from 192.168.7.2:3000.

I've tried the following to troubleshoot: - Cleared all browser data, cookies, etc. - Tried on two separate BBB with clean re-installation of Debian. This image always worked fine for me in the past. Both BBB show the same result. - Tried the BBB on two separate computers, one Win7 and the other Win8. - Tried on both Chrome and IE.

Everything I tried showed the same result. It really has me baffled! Can anyone offer some words of wisdom?

My only guess is that some client side script in the Cloud9 IDE is making a call to a server which is down at the moment. But, my understanding is that the Cloud9 IDE is completely contained in the BBB and makes no external calls from the client.

[William Hermans]

The two of you, may have to seek help from the maintainer of cloud9.

 

--

For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[brettma...@gmail.com]

I'm trying to address this to the Cloud9 community HERE.

[bissch...@gmail.com]

Thanks for the effort and keeping us up to date. I just saw in your link that the solution is to simply install the latest Debian image... sometimes the most brilliant solutions are the best. ;-)

Knowing this... can I install the latest image without losing data? Or will it wipe my entire system? (I'm preparing it for a demonstration... whould be a shame if I need to reinstall everything ;-) )

Thanks again... :)

Op zondag 24 mei 2015 21:38:04 UTC+2 schreef brettma...@gmail.com:

[Rick Bisschop]

Thanks for the effort and keeping us up to date. I just saw that the solution is to simply install the latest Debian image... sometimes to most brilliant solutions are the best. ;-)

Knowing this... can I install the latest image without losing data? Or will it wipe my entire system?

On 24 May 2015 at 04:49, <brettma...@gmail.com> wrote:

I'm trying to address this to the Cloud9 community HERE.

--

For more options, visit http://beagleboard.org/discuss
---

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/pRhUPjAdVHo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brett Maurer]

You will need to reinstall everything after updating the image. Knowing it's a version issue though, you may be able to update the Cloud9 package on your machine and it might solve the problem. I'm not sure how this is done though. Check the Cloud9 docs.

[Robert Nelson]

On Mon, May 25, 2015 at 5:21 PM, Brett Maurer <brettma...@gmail.com> wrote:
> You will need to reinstall everything after updating the image. Knowing it's
> a version issue though, you may be able to update the Cloud9 package on your
> machine and it might solve the problem. I'm not sure how this is done
> though. Check the Cloud9 docs.

sudo apt-get update
sudo apt-get install cloud9-installer

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Walker Archer]

I'll add myself as a third person who experienced the same white screen with Cloud9 via Chrome over the weekend.  However, I switched to Firefox and was able to work without any issue.  So I thought it may have been an update to Chrome that caused the issue.  I haven't updated the BBB recently.

I'll try updating cloud 9 this evening.

[Jason Kridner]

I've been able to reproduce this error. It showed up first on the
early builds of Chrome, but it now seems to have leaked into their
production releases. It seems they've added some code that generates
an exception that older versions of Chrome didn't produce. The issue
only seems to show up for me when I don't have an Internet connection.
Hopefully the cloud9 update fixes it, but seeing the issue is
wide-spread, I'll try a bit harder to track down a reliable resolution
to it.

> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard...@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

[Robert Nelson]

On Tue, May 26, 2015 at 11:59 AM, Jason Kridner
<jkri...@beagleboard.org> wrote:
> I've been able to reproduce this error. It showed up first on the
> early builds of Chrome, but it now seems to have leaked into their
> production releases. It seems they've added some code that generates
> an exception that older versions of Chrome didn't produce. The issue
> only seems to show up for me when I don't have an Internet connection.
> Hopefully the cloud9 update fixes it, but seeing the issue is
> wide-spread, I'll try a bit harder to track down a reliable resolution
> to it.

cloud9 master seems a little more broken on chrome then firefox:

chrome: random white text:
firefox: gui shows up, but un-usable...

cd /opt/cloud9/build/

wget http://rcn-ee.homeip.net:81/farm/testing/c9-core_3.0.1+git20150522-build.tar.xz

rm -rf standalonebuild

tar xf c9-core_3.0.1+git20150522-build.tar.xz

(reboot)

May 26 17:06:53 beaglebone cloud9ide[4680]: Authentication is required
when not running on localhost.
May 26 17:06:53 beaglebone cloud9ide[4680]: Please use -a user:pass or
--listen localhost to listen locally.
May 26 17:06:53 beaglebone cloud9ide[4680]: switching to localhost
May 26 17:06:55 beaglebone cloud9ide[4680]: LISTEN_FDS = 1
May 26 17:06:55 beaglebone cloud9ide[4680]: Connect server listening
at http://127.0.0.1:3000
May 26 17:06:55 beaglebone cloud9ide[4680]: CDN: version standalone
initialized /opt/cloud9/build/standalonebuild/build
May 26 17:06:56 beaglebone cloud9ide[4680]: Started
'/opt/cloud9/build/standalonebuild/configs/standalone' with config
'standalone'!
May 26 17:06:57 beaglebone cloud9ide[4680]: Error: write EPIPE
May 26 17:06:57 beaglebone cloud9ide[4680]: at errnoException (net.js:905:11)
May 26 17:06:57 beaglebone cloud9ide[4680]: at Object.afterWrite (net.js:721:19)
May 26 17:06:58 beaglebone cloud9ide[4680]: events.js:72
May 26 17:06:58 beaglebone cloud9ide[4680]: throw er; // Unhandled 'error' event
May 26 17:06:58 beaglebone cloud9ide[4680]: ^
May 26 17:06:58 beaglebone cloud9ide[4680]: Error: spawn ENOENT
May 26 17:06:58 beaglebone cloud9ide[4680]: at errnoException
(child_process.js:1011:11)
May 26 17:06:58 beaglebone cloud9ide[4680]: at
Process.ChildProcess._handle.onexit (child_process.js:802:34)

To recover:

sudo apt-get install c9-core-installer --reinstall

Which will reinstall "c9-core_3.0.1+git20150306-build.tar.xz"

git20150306 was one of the last node 0.10, before git master went 0.12
only. they have since allowed 0.10 again, so i've been trying to get
an update pushed.

[bissch...@gmail.com]

So far the cloud9 update is not working for me. I get an "unable to locate package cloud9-installer"-error. I've been searching for other ways, but nothing of real use and/or not willing to take the risk at the moment. I'll be sure to try FireFix again though, maybe that'll be a good temp fix for me. Hope to see it working with Chrome again though. Glad to hear it is being adressed. :) I'll be sure to keep monitoring this thread in case another solution arises.

Op dinsdag 26 mei 2015 18:59:37 UTC+2 schreef Jason Kridner:

[bissch...@gmail.com]

Before I forget... I do have the issue with an internet connection present. In my case it doesn't seem to matter for both my laptop and the BBB.

Op dinsdag 26 mei 2015 18:59:37 UTC+2 schreef Jason Kridner:

I've been able to reproduce this error. It showed up first on the

[Robert Nelson]

On Tue, May 26, 2015 at 12:08 PM, <bissch...@gmail.com> wrote:
> So far the cloud9 update is not working for me. I get an "unable to locate
> package cloud9-installer"-error. I've been searching for other ways, but
> nothing of real use and/or not willing to take the risk at the moment. I'll
> be sure to try FireFix again though, maybe that'll be a good temp fix for
> me. Hope to see it working with Chrome again though. Glad to hear it is
> being adressed. :) I'll be sure to keep monitoring this thread in case
> another solution arises.

Then you have a "really" old version, probably May 2014.

cat /etc/dogtag

and sorry, the actual package is now "c9-core-installer" as it's now
open source and no longer in a private repo..

[Robert Nelson]

On Tue, May 26, 2015 at 1:18 PM, Robert Nelson <robert...@gmail.com> wrote:
> On Tue, May 26, 2015 at 12:08 PM, <bissch...@gmail.com> wrote:
>> So far the cloud9 update is not working for me. I get an "unable to locate
>> package cloud9-installer"-error. I've been searching for other ways, but
>> nothing of real use and/or not willing to take the risk at the moment. I'll
>> be sure to try FireFix again though, maybe that'll be a good temp fix for
>> me. Hope to see it working with Chrome again though. Glad to hear it is
>> being adressed. :) I'll be sure to keep monitoring this thread in case
>> another solution arises.
>
> Then you have a "really" old version, probably May 2014.
>
> cat /etc/dogtag

ps: updated images can be found here:

http://beagleboard.org/latest-images

[bissch...@gmail.com]

Yup, apperantly I'm still running the version it got shipped with. I'll update as soon as my project is finished. I don't have enough time left to afford the risk of a complete reinstall atm. I am glad we got to adress the issue though... and yes... I probably should have chekd for an update right away and prevented all of this in the first place... ah well. Thanks for all the information though... and that goes out to all of you ;-)

Op dinsdag 26 mei 2015 20:21:58 UTC+2 schreef RobertCNelson:

[Robert Nelson]

On Tue, May 26, 2015 at 2:00 PM, <bissch...@gmail.com> wrote:
> Yup, apperantly I'm still running the version it got shipped with. I'll
> update as soon as my project is finished. I don't have enough time left to
> afford the risk of a complete reinstall atm. I am glad we got to adress the
> issue though... and yes... I probably should have chekd for an update right
> away and prevented all of this in the first place... ah well. Thanks for all
> the information though... and that goes out to all of you ;-)

Well, we can get your cloud9 updated....

cd /opt/cloud9/build/

sudo mv standalonebuild backup

wget http://repos.rcn-ee.com/pkgs/c9v3/c9-core_3.0.1+git20150306-build.tar.xz

tar xf c9-core_3.0.1+git20150306-build.tar.xz

sudo reboot

If you need to go back to the old one:

sudo rm standalonebuild
sudo mv backup standalonebuild
sudo reboot

[bissch...@gmail.com]

Above fix works like a charm. It does however gets you the errormessage that there is an old node.js version present. You can ignore this, but this gives you weird "Reconnect" errors and weird cloud9 behaviour.

You can fix this by following this link. (Warning... on the BBB this takes a VERY long time when you start to "make". 2 hours+!)

After a quick reboot everything is functional again. (And yes... I'm still going to update in the future, but first things first ;-) )

Thanks again.

Op dinsdag 26 mei 2015 21:53:35 UTC+2 schreef RobertCNelson:

[William Hermans]

Odd . . . as it only takes around an hour to compile Nodejs from source ( natively ). . . I think the bigger problem would be space wasted, using the current image as a "dev image" assuming the link you posted does recompile from source as well.

--