It's probably stuck in single user mode. At any rate, I am very well equipped to deal with stuck linux boxen. If it turns out to be truly dead - what do I re-image it with?-bOn Wed, Dec 21, 2011 at 6:53 PM, Michael Tyka <mike...@gmail.com> wrote:Hi all,so yeah it looks like the central linux box is not booting up. We've had such a problem before but i went there, literally just rebooted and it sprang to life again so I have no idea what happened there.Brian, there should be a keyboard and a screen already in the cube sitting on the central platform.Try plugging those in and seeing if you can boot up the box.If it turns out the box has truly died (which i doubt, frankly) we'll need to order or find another box.Lee gave me a black MacBook that is sitting on my dresser in my room that we could use although it will take a little software fiddling to get it to work since the /usb/ttyUSB devices are called something else.I think just making symlinks to /usb/ttyUDBx where x = 1..13 will work. I can do all that remotely though, i just need a running box. The IP needs to be set statically to 10.0.40.85 if i remember correctly.As for power to the LEDs i believe that is all in goo shape. However if it does turns out there are dead powersupplies then the temporary fix is easy:Currently each dimduino is only connected to a single computer powersupply (ATX style). THe reason is that the other, aluminum cased water-proof supplies were giving a dirty signal and were causing USB disconnections. However they do work in principle so if you neded to replace one of the ATXes just plug in a nearby aluminum supply - they are all still in there, just disconnected.I'll try and check my mail as frequently as I can to help with any issues. Once the central machine comes back online i can prolly do most of the software work from here.Thanks!MikeOn Thu, Dec 22, 2011 at 2:34 AM, Barry Brumitt <bar...@gmail.com> wrote:
There's a fair chance it's something other rather than dead computer, but someone has to get in there to figure it out further.B>On Wed, Dec 21, 2011 at 5:22 PM, Brian Retford <bret...@gmail.com> wrote:
I can certainly try,though I'm quite unfamiliar
On Dec 21, 2011 4:52 PM, "Barry Brumitt" <bar...@gmail.com> wrote:Can either of you (Chris, Brian) do anything about this? We really should jump on it; I would but I'm leaving on a jet plane, as it were.
B>
--
You received this message because you are subscribed to the Google Groups "Groovik's Hackers" group.
To post to this group, send email to grooviks...@googlegroups.com.
To unsubscribe from this group, send email to grooviks-hacke...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/grooviks-hackers?hl=en.
Chris set up the machine originally - sadly don't think there's an image
or a duplicated box.
I think we need is a clean Ubuntu install and then we can just
re-checkout the code. I can deal with the scripting part etc once it's
back at PacSci and accessible from the intrewebs.
So I guess the course of action is:
a) reinstall Ubuntu
b) set it to static IP 10.0.40.85
c) install a user "cube" and make him be sudoable. Password was
"PowerOfLove" for both accounts
d) in user cube's home dir do
hg clone https://mike...@code.google.com/p/grooviks-cube/
Follow instructions in grooviks-cube/webserver/README to test-
run the server
YOu may hae to install some missing packages here (e.g. hg and probably
django and whatnot, more info in the README )
e) make a script in /etc/rc.2/ to autostart
./manage.py runserver 0.0.0.0:8080"
hookbox -d -r bakonv8 -p 2974 --cbhost=127.0.0.1 --cbport=8080"
./groovikhookbox.py"
in their respective directories (see README)
z) make an image so next time we dont have to do all this again. Sorry
for dropping the ball on this - that was dumb of me.
(actually wait b4 making the image until we know everything is back to
working order)
Thanks for you guys' help!
Mike
Okay the cubes fixed. two notable errata it runs on port 80 not port 8080 and the netmask seems to be whack 16 not whack 24
--
You received this message because you are subscribed to the Google Groups "Groovik's Hackers" group.
To post to this group, send email to grooviks-hackers@googlegroups.com.
To unsubscribe from this group, send email to grooviks-hackers+unsubscribe@googlegroups.com.
YOu mean its reinstalled and installed physically back at PacSci ?
I still can't log into it remotely .. maybe there's a firewall issue ?
I'll email Michael (the sysadmin at pacsci) to see if he changed something.
Mike
On 12/24/11 12:26 AM, Brian Retford wrote:
> Okay the cubes fixed. two notable errata it runs on port 80 not port
> 8080 and the netmask seems to be whack 16 not whack 24
>
> On Dec 22, 2011 7:01 PM, "Michael Tyka" <mike...@gmail.com
> <mailto:mike...@gmail.com>> wrote:
>
> Thanks for the diagnosis!
>
> Chris set up the machine originally - sadly don't think there's an
> image or a duplicated box.
>
> I think we need is a clean Ubuntu install and then we can just
> re-checkout the code. I can deal with the scripting part etc once
> it's back at PacSci and accessible from the intrewebs.
> So I guess the course of action is:
> a) reinstall Ubuntu
> b) set it to static IP 10.0.40.85
> c) install a user "cube" and make him be sudoable. Password was
> "PowerOfLove" for both accounts
> d) in user cube's home dir do
> hg clone https://mike...@code.google.__com/p/grooviks-cube/
> <https://mike...@code.google.com/p/grooviks-cube/>
>
> Follow instructions in grooviks-cube/webserver/README to test-
> run the server
>
> YOu may hae to install some missing packages here (e.g. hg and
> probably django and whatnot, more info in the README )
>
> e) make a script in /etc/rc.2/ to autostart
>
> ./manage.py runserver 0.0.0.0:8080 <http://0.0.0.0:8080>"
> hookbox -d -r bakonv8 -p 2974 --cbhost=127.0.0.1 --cbport=8080"
> ./groovikhookbox.py"
>
> in their respective directories (see README)
>
> z) make an image so next time we dont have to do all this again.
> Sorry for dropping the ball on this - that was dumb of me.
> (actually wait b4 making the image until we know everything is back
> to working order)
>
> Thanks for you guys' help!
>
> Mike
>
>
> On 12/22/11 4:01 PM, Brian Retford wrote:
>
> Oh, and the main computer is sitting at AND, I have a date, but if
> someone is feeling really ambitious and wants to come over and
> magically
> fix it all, I won't complain. But, I at least need to know how
> to make a
> new cube image.
>
> -b
>
> On Thu, Dec 22, 2011 at 3:56 PM, Brian Retford
> <bret...@gmail.com <mailto:bret...@gmail.com>
> <mailto:bret...@gmail.com <mailto:bret...@gmail.com>>> wrote:
>
> Okay! The root disk image is fux0r3d it has a kernel, but
> nothing
> else, and it kernel panics on boot. So, we'll need to
> re-image it. I
> suggest we also make a duplicate backup machine running the
> same image.
>
> Is there an image? Hopefully?
>
> -b
>
>
> On Thu, Dec 22, 2011 at 6:34 AM, Brian Retford
> <bret...@gmail.com <mailto:bret...@gmail.com>
> <mailto:bret...@gmail.com <mailto:bret...@gmail.com>>> wrote:
>
> It's probably stuck in single user mode. At any rate, I
> am very
> well equipped to deal with stuck linux boxen. If it
> turns out to
> be truly dead - what do I re-image it with?
>
> -b
>
>
> On Wed, Dec 21, 2011 at 6:53 PM, Michael Tyka
> <mike...@gmail.com <mailto:mike...@gmail.com>
> <mailto:bar...@gmail.com <mailto:bar...@gmail.com>>> wrote:
>
> There's a fair chance it's something other
> rather than
> dead computer, but someone has to get in there
> to figure
> it out further.
>
> B>
>
>
>
> On Wed, Dec 21, 2011 at 5:22 PM, Brian Retford
> <bret...@gmail.com <mailto:bret...@gmail.com>
> <mailto:bret...@gmail.com <mailto:bret...@gmail.com>>> wrote:
>
> I can certainly try,though I'm quite unfamiliar
>
> On Dec 21, 2011 4:52 PM, "Barry Brumitt"
> <bar...@gmail.com <mailto:bar...@gmail.com>
> <mailto:bar...@gmail.com <mailto:bar...@gmail.com>>> wrote:
>
> Can either of you (Chris, Brian) do anything
> about this? We really should jump on it;
> I would
> but I'm leaving on a jet plane, as it were.
> B>
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Groovik's Hackers" group.
> To post to this group, send email to
> grooviks-hackers@googlegroups.__com
> <mailto:grooviks...@googlegroups.com>.
> To unsubscribe from this group, send email to
> grooviks-hackers+unsubscribe@__googlegroups.com
> <mailto:grooviks-hackers%2Bunsu...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/__group/grooviks-hackers?hl=en
> <http://groups.google.com/group/grooviks-hackers?hl=en>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Groovik's Hackers" group.
> To post to this group, send email to grooviks...@googlegroups.com.
> To unsubscribe from this group, send email to
> grooviks-hacke...@googlegroups.com.
rock on yo!
Thank you Brian - you're our hero!!
YOu mean its reinstalled and installed physically back at PacSci ?
I still can't log into it remotely .. maybe there's a firewall issue ?
I'll email Michael (the sysadmin at pacsci) to see if he changed something.
Mike
On 12/24/11 12:26 AM, Brian Retford wrote:
Okay the cubes fixed. two notable errata it runs on port 80 not port
8080 and the netmask seems to be whack 16 not whack 24
On Dec 22, 2011 7:01 PM, "Michael Tyka" <mike...@gmail.com
<mailto:mike...@gmail.com>> wrote:
Thanks for the diagnosis!
Chris set up the machine originally - sadly don't think there's an
image or a duplicated box.
I think we need is a clean Ubuntu install and then we can just
re-checkout the code. I can deal with the scripting part etc once
it's back at PacSci and accessible from the intrewebs.
So I guess the course of action is:
a) reinstall Ubuntu
b) set it to static IP 10.0.40.85
c) install a user "cube" and make him be sudoable. Password was
"PowerOfLove" for both accounts
d) in user cube's home dir do
hg clone https://mike...@code.google.__com/p/grooviks-cube/
<mailto:grooviks-hackers@googlegroups.com>.
To unsubscribe from this group, send email to
grooviks-hackers+unsubscribe@__googlegroups.com
<mailto:grooviks-hackers%2Bunsu...@googlegroups.com>.
For more options, visit this group at
http://groups.google.com/__group/grooviks-hackers?hl=en
<http://groups.google.com/group/grooviks-hackers?hl=en>.
--
You received this message because you are subscribed to the Google
Groups "Groovik's Hackers" group.
To post to this group, send email to grooviks-hackers@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/grooviks-hackers?hl=en.
--
You received this message because you are subscribed to the Google Groups "Groovik's Hackers" group.
To post to this group, send email to grooviks-hackers@googlegroups.com.
To unsubscribe from this group, send email to grooviks-hackers+unsubscribe@googlegroups.com.