[00:21] *** eprillios has joined #warrior [00:25] Heya all. I am running a Warrior instance, currently on the Tumblr project. A few successive power outages occured, which have resulted in jobs being lost. Those outstanding claims would need to be freed. My name on the tracker is the same. [00:26] you can mention it in #tumbledown if you haven't gotten a response yet, the admins are active there [00:50] Thanks! Will post it there. [01:15] *** nertzy has joined #warrior [01:38] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [02:10] oh no... [02:11] I set the number of tasks to 6 (maximum), but ended up with 5 blogs with 15000+ items that go on for 8 hours or longer... there's either a memleak in wget-lua or it's trying to keep the entire structure in memory [02:12] the VM comes preset with only 400MB ram, and it seems now it's in the process of committing suicide from all the memory pressure [02:15] Yeah, wget-lua keeps the URL table in memory. [02:15] I've had some processes that ate 2 GB RAM or more. [02:19] ugh... so why give the vm only 400 megs, or, why allow so many threads [02:20] I didn't know, it seemed to be working fine at the beginning... but now it's swapping nonstop, not sure if it'll eventually fail completely [02:21] Well, most previous projects had items much smaller than Tumblr, so it was never a problem. [02:22] The issue is simply that some Tumblr blogs are *massive*, and it's not easily possible to split them up. [02:22] Anyway, it might be best to just kill the VM. This will not end well. [02:54] how many items tend to be on these bigger blogs? [03:00] will pressing the 'shut down' button abort all the jobs? no saved progress or anything? [03:15] *** tsr has quit IRC (Read error: Operation timed out) [03:24] *** tsr has joined #warrior [03:31] ultramage: Shutting down the VM will abort the job and all progress will be lost. If your VM was started more than 4 hours ago, don't worry and just restart the VM. [03:32] There were some code optimizations made. The decision was made to ditch downloading notes. The jobs should finish faster now. [03:33] You can also ask questions in #tumbledown because that channel is currently very active. [03:38] alright [03:39] my workaround was to kill -TSTP four of the six jobs and wait for one or both of them to finish while the others get swapped out entirely [03:48] ultramage: Oh. Nice. [03:49] Just make sure you're using the latest code. [04:20] *** ultramage has left [04:55] *** nertzy has joined #warrior [05:00] *** zyphlar_ has joined #warrior [05:34] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [05:37] *** nertzy has joined #warrior [07:10] *** zyphlar_ has quit IRC (Quit: Connection closed for inactivity) [07:38] *** nertzy has quit IRC (Read error: Connection reset by peer) [07:55] *** JL421 has joined #warrior [08:00] *** Atom-- has quit IRC (Read error: Connection reset by peer) [08:09] *** tuluu has quit IRC (Read error: Connection refused) [08:11] *** tuluu has joined #warrior [09:39] *** teej_ has quit IRC (Ping timeout: 252 seconds) [09:44] *** pnJay has quit IRC (Ping timeout: 260 seconds) [09:44] *** bitspill has quit IRC (Ping timeout: 260 seconds) [09:44] *** davidar has quit IRC (Ping timeout: 260 seconds) [09:45] *** Dj-Wawa has quit IRC (Ping timeout: 260 seconds) [09:46] *** HCross has quit IRC (Ping timeout: 260 seconds) [09:47] *** pnJay has joined #warrior [09:47] *** davidar has joined #warrior [09:48] *** bitspill has joined #warrior [09:48] *** Dj-Wawa has joined #warrior [09:48] *** BuildTheR has quit IRC (Ping timeout: 260 seconds) [09:48] *** BuildTheR has joined #warrior [09:49] *** HCross has joined #warrior [09:49] *** chr1sm has quit IRC (Ping timeout: 260 seconds) [09:49] *** svchfoo3 sets mode: +o HCross [09:50] *** svchfoo1 sets mode: +o HCross [09:50] *** octarine has quit IRC (Ping timeout: 260 seconds) [09:51] *** chr1sm has joined #warrior [09:53] *** octarine has joined #warrior [09:55] *** teej_ has joined #warrior [11:08] *** Knuckx has joined #warrior [11:08] *** Knuckx has left [12:34] *** kiska1 has joined #warrior [13:30] *** MrRadar2 has quit IRC (Read error: Operation timed out) [13:31] *** jesso_ has joined #warrior [13:32] *** jesso has quit IRC (Ping timeout: 268 seconds) [13:33] *** yuitimoth has quit IRC (Read error: Operation timed out) [13:33] *** yuitimoth has joined #warrior [13:33] *** zerkalo has quit IRC (Read error: Operation timed out) [13:34] *** zerkalo has joined #warrior [13:34] *** fennec has quit IRC (Ping timeout: 268 seconds) [13:34] *** BnAboyZ has quit IRC (Ping timeout: 268 seconds) [13:35] *** bsmith093 has quit IRC (Ping timeout: 268 seconds) [13:35] *** BnAboyZ has joined #warrior [13:35] *** fennec has joined #warrior [13:36] *** bsmith093 has joined #warrior [13:37] *** MrRadar2 has joined #warrior [13:40] *** Jusque has quit IRC (Read error: Operation timed out) [13:42] *** Jusque has joined #warrior [13:44] *** sep332 has quit IRC (Read error: Operation timed out) [13:48] *** kiska1 has quit IRC (Read error: Connection reset by peer) [13:51] *** sep332 has joined #warrior [13:52] *** kiska1 has joined #warrior [14:13] *** SilSte has quit IRC (Read error: Operation timed out) [14:30] *** Atom has joined #warrior [15:29] *** guest4792 has joined #warrior [15:29] one of my warrior items is giving an rsync error [15:29] rsync error: error starting client-server protocol (code 5) at main.c(1653) [sender=3.1.1] [15:30] Yes we know this error, come join #tumbledown [15:30] I'm banned [15:31] guest4792: Please choose a proper nickname. [15:32] Oh wait, nevermind. [15:34] uhh... [15:39] so, what's going on? [15:40] The server is overloaded. Just let it do its thing, it should keep retrying until it succeeds. [15:40] ok [15:52] it's going now [16:08] is the item count on the tracker page referring to claimed or completed items? [16:15] guest4792: done = completed, out = claimed, todo = not yet claimed [16:16] thanks, I actually meant the counts for individual users [16:18] so if a user shows 100 items, is that done or out? [16:28] guest4792: That's completed items. [16:28] thanks [18:10] *** mtntmnky has joined #warrior [18:18] *** teiserse has joined #warrior [18:22] Hey, the FAQ says to notify if I see messages about rsync errors, and I am seeing them? [18:22] Hi there! If it's with the tumblr-grab we're having a little bit of an overload with our rsync target. We're working to load balance it very soon! [18:23] if you leave teh warrior running, it will eventually get a chance to upload [18:23] Oh, okay then. [18:28] Here it comes actually [18:39] *** jut has quit IRC (Ping timeout: 252 seconds) [19:26] *** teiserse has quit IRC (Quit: http://www.mibbit.com ajax IRC Client) [19:30] *** nertzy has joined #warrior [20:44] *** sec^nd has quit IRC (Ping timeout: 260 seconds) [20:46] *** second has joined #warrior [21:06] have you guys ever tried virtualbox guest additions for monitoring your warrior from the host machine? [21:07] it would be nice to be able to monitor disk and ram usage [21:08] I don't really know if it's worth it since I can login directly [23:18] does the elapsed time counter on the web interface start over at 24 hrs? [23:23] It does [23:23] ive never gotten the additions installed, but having that packaged would be pretty nice [23:24] thanks, good to know this thing didn't start over :) [23:25] reading the guest additions documentation I discovered something interesting called "memory ballooning" where VMs can share memory, kind of interesting [23:28] I guess it's more about re-allocating than having a common pool [23:34] Don't the guest additions depend on the host OS and VirtualBox version? If so, it's not really possible to ship a generic .ova which works on every platform. [23:37] afaik, the guest additions virtual cd has individual executables in it for each guest os it works with [23:39] oh, not the relevant answer [23:39] not sure about that [23:40] I almost installed it but since I don't know how much memory it uses I decided not to [23:42] hmm, looks like tumblr is under heavy load