| Time |
Nickname |
Message |
|
18:37
🔗
|
shaqfu |
Today's goal: hack+build seesaw on RPi |
|
18:43
🔗
|
shaqfu |
(Would that be the part governing job handling?) |
|
19:07
🔗
|
shaqfu |
Actually, hm. Looking through these scripts - it might be best to just roll a fresh OS, set up dependencies, adjust make-data-disk, and let rip |
|
19:51
🔗
|
shaqfu |
Scratch that - simply running the scripts falls apart :( |
|
19:51
🔗
|
Smiley |
~D: |
|
20:10
🔗
|
alard |
I'm wondering: would it be useful to have statically linked Wget+Lua binaries? |
|
20:11
🔗
|
alard |
Because that would let it run on any system, without installing or compiling anything, correct? |
|
20:11
🔗
|
Smiley |
as long as you ship the libs |
|
20:11
🔗
|
shaqfu |
alard: Might be, esp. since it'll run alongside vanilla wget |
|
20:11
🔗
|
alard |
I thought that the idea was that the libs are in the binary? |
|
20:11
🔗
|
Smiley |
hmmm not sure |
|
20:11
🔗
|
Smiley |
:D |
|
20:12
🔗
|
Smiley |
then yes, go ahead. |
|
20:12
🔗
|
alard |
But I have little experience with that, so it may be a naive idea. |
|
20:13
🔗
|
shaqfu |
Hm, so I have Warrior theoretically running, but nothing's showing up when I try and connect |
|
20:13
🔗
|
Smiley |
ok i've asked some clever people :D |
|
20:13
🔗
|
shaqfu |
Er, connect to the device locally* |
|
20:13
🔗
|
Smiley |
connect to the device? how so? |
|
20:13
🔗
|
Smiley |
Oh, you can't connect to the pi? |
|
20:14
🔗
|
shaqfu |
Smiley: not via HTTP, no |
|
20:14
🔗
|
Smiley |
It doesn't start sshd by default. |
|
20:14
🔗
|
Smiley |
or tornado. |
|
20:14
🔗
|
Smiley |
seesaw =! the web front end. |
|
20:14
🔗
|
Smiley |
afaik. |
|
20:14
🔗
|
shaqfu |
Wait, really? |
|
20:14
🔗
|
alard |
seesaw == the web front end. |
|
20:14
🔗
|
shaqfu |
Kind of odd - I got the "point your browser to xxxx:8001" |
|
20:14
🔗
|
Smiley |
you need to start tornado? |
|
20:14
🔗
|
Smiley |
Or does it pull it in? |
|
20:14
🔗
|
alard |
run-pipeline and run-warrior both start a web server. |
|
20:14
🔗
|
Smiley |
alard: ah ok :/ |
|
20:14
🔗
|
Smiley |
then weird. |
|
20:15
🔗
|
alard |
shaqfu: Are you connecting to localhost? |
|
20:16
🔗
|
shaqfu |
alard: No, device on my LAN |
|
20:16
🔗
|
shaqfu |
Here we go - needed to start warrior-runner and not boot |
|
20:16
🔗
|
alard |
Ah, you're talking about the warrior scripts. |
|
20:16
🔗
|
shaqfu |
Yeah |
|
20:16
🔗
|
Smiley |
go ahead alard with statical linking, it makes sense |
|
20:16
🔗
|
Smiley |
just see what size teh binary comes out at. |
|
20:17
🔗
|
alard |
2.5 MB or so. |
|
20:17
🔗
|
shaqfu |
Oh, hey, it runs now |
|
20:17
🔗
|
Smiley |
shaqfu: nice |
|
20:18
🔗
|
alard |
shaqfu: Ah, yes, I remember. The boot script is for tty1, it updates the code, shows the splash screen. It tells 'you can start now' to the warrior-runner on tty2. |
|
20:19
🔗
|
shaqfu |
Gotcha |
|
20:19
🔗
|
Smiley |
wooo |
|
20:19
🔗
|
shaqfu |
(aw - I didn't expect "stop the warrior" to send a halt :( |
|
20:19
🔗
|
alard |
https://github.com/ArchiveTeam/warrior-preseed/blob/master/warrior-preseed.cfg#L757-L758 |
|
20:20
🔗
|
alard |
Always check the scripts you're running. :) There's a --real-shutdown option that does that. |
|
20:20
🔗
|
Smiley |
urgh |
|
20:20
🔗
|
Smiley |
i really really wanna figure out AMI at some point |
|
20:20
🔗
|
Smiley |
just so dang lazy and so much going on xD |
|
20:20
🔗
|
Smiley |
can someone else jhust do it for me :D |
|
20:21
🔗
|
shaqfu |
alard: thankfully the other job I was running was trivial :) |
|
20:21
🔗
|
shaqfu |
Seems to be running fine now - just need to make install wget-lua |
|
20:21
🔗
|
shaqfu |
But it looks like it shouldn't be too painful to roll a disk image with everything nice and set up |
|
20:22
🔗
|
Smiley |
shaqfu: interested if it's any good ;D |
|
20:22
🔗
|
shaqfu |
Mostly just setting up dependencies and clearing out some funkiness with the Pi |
|
20:22
🔗
|
Smiley |
ram could be a big issue depending. |
|
20:22
🔗
|
shaqfu |
e.g., lspci breaking |
|
20:22
🔗
|
Smiley |
but if you run the small projects, should be nice |
|
20:22
🔗
|
Smiley |
shaqfu: btw what distro you used as a base? |
|
20:23
🔗
|
shaqfu |
Smiley: Raspbian |
|
20:23
🔗
|
shaqfu |
alard: what happens if /data runs out of room? does it purge+return the job to queue+take a new one? |
|
20:23
🔗
|
Smiley |
I'm still waiting to hear gentoo runs nicely, and then I'll likely get one |
|
20:23
🔗
|
Smiley |
I'd expect it to blow up in spectacular fashion. |
|
20:24
🔗
|
alard |
shaqfu: If Wget fails it should remove the files from that item and start again, I think. |
|
20:24
🔗
|
shaqfu |
alard: start the job again, or get a new one? |
|
20:24
🔗
|
alard |
No, job fails, remove job, get a new one. |
|
20:24
🔗
|
Smiley |
alard: will his pi rebot every 7 days now? |
|
20:25
🔗
|
shaqfu |
Gotcha; awesome. Was just concerned if I hit a runaway job |
|
20:25
🔗
|
Smiley |
I'd think wget would OOM before that. |
|
20:26
🔗
|
Smiley |
doesn't it cache all the links it hasn't yet followed? |
|
20:26
🔗
|
alard |
With --real-shutdown it reboots after 7 days, otherwise: no. |
|
20:26
🔗
|
Smiley |
ah ok |
|
20:32
🔗
|
shaqfu |
Seems like most of the issues are rising from the scripts expecting the warrior user |
|
20:33
🔗
|
shaqfu |
Which are a huge pain now, but not later :) |
|
20:36
🔗
|
shaqfu |
alard: do you have any estimates on RAM use for small-medium jobs? |
|
20:37
🔗
|
shaqfu |
e.g. anything under 16GB or so, since I doubt many Pis can hold more than that |
|
21:20
🔗
|
alard |
Static Wget+Lua: 4.8M. |
|
21:20
🔗
|
alard |
warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking |
|
21:20
🔗
|
alard |
warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking |
|
21:20
🔗
|
alard |
warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking |
|
21:37
🔗
|
shaqfu |
Hm, wget-lua isnt building... |
|
21:41
🔗
|
shaqfu |
Oh, it expects lua5.1 |
|
22:03
🔗
|
shaqfu |
Strange; still isn't building... |
|
23:01
🔗
|
omf_ |
Can the warrior do video jobs? I got a list of 1700 videos |
|
23:01
🔗
|
omf_ |
We would use a python script to grab the video |
|
23:02
🔗
|
omf_ |
1 video per request |
|
23:02
🔗
|
omf_ |
I am just thinking aloud because getting video is going to be more common |
|
23:42
🔗
|
shaqfu |
Weird. I put wget-lua in warrior-code2/wget-lua/, but it won't see it |
|
23:49
🔗
|
Smiley |
omf_: it'd be a nice framework to have. |