[00:12] *** JesseW has joined #urlteam [00:13] *** svchfoo1 sets mode: +o JesseW [00:26] *** dashcloud has quit IRC (Read error: Operation timed out) [00:39] *** dashcloud has joined #urlteam [00:39] *** svchfoo1 sets mode: +o dashcloud [00:52] *** VADemon has quit IRC (Read error: Connection reset by peer) [00:56] *** Fletcher has quit IRC (Read error: Operation timed out) [00:59] *** Fletcher has joined #urlteam [02:21] *** zhongfu has quit IRC (Read error: Operation timed out) [02:22] *** zhongfu has joined #urlteam [02:55] I think I may have borked the tracker... :-/ [02:57] arkiver, chfoo- -- could you look into the tracker and see why it's returning 500 error codes...? [02:57] 504, to be specific. [03:21] *** chfoo has joined #urlteam [03:21] *** svchfoo3 sets mode: +o chfoo [03:33] seems to be working again now [03:45] could have been exporting or something. In case you didn't know, both trackers are on the same machine. [03:45] ah, I didn't know. [03:46] I presumed they were on different machines because of the separate software [03:46] nope, same one. so that can help narrow things down, if one works and the other isn't. [03:46] welp, it's down again [03:46] they both are [03:47] but now the main one is back up [03:47] and so is the other one [03:47] I hope it isn't my changes. But it probably is. :-) [03:48] I don't know, but it would have to be something to take out both [03:49] well, if my changes make something take too long, that could take out both, is what I'm thinking [03:49] they are separate stacks, I believe [03:49] hm [03:50] but the only info I have is here: http://zeppelin.xrtc.net/corp.xrtc.net/zloty.corp.xrtc.net/index.html [04:16] I think when I ask it for the results for a project that has no results, that's when it freaks out (because it has to look through the whole, very large, result table) [04:16] and that is locking up the tracker [04:17] I wish there was a shorter timestamp chart than per day [04:28] *** aaaaaaaaa has quit IRC (Read error: Operation timed out) [04:43] i just restarted redis [04:44] Thank you. [04:44] Did you see any further evidence that the breakage is caused by requesting project-specific results for a project with no results? [04:45] no, redis was running out of memory [04:46] also i'm not sure why the tracker is running as root now [04:48] hm. both of those are odd things. [04:49] what does the tracker store in redis? [04:50] and it's down again [04:52] yes, i'm fixing it [04:52] ah, ok -- I'll stop bothering you then. :-) [04:54] the tracker stores the statisitics that is shown on the front page [04:55] stores in redis * [07:24] *** JesseW has quit IRC (Leaving.) [07:48] *** WinterFox has quit IRC (Read error: Operation timed out) [07:54] *** WinterFox has joined #urlteam [11:54] *** WinterFox has quit IRC (Remote host closed the connection) [13:10] *** toad1 has quit IRC (Read error: Operation timed out) [14:04] *** toad1 has joined #urlteam [15:21] *** ersi has joined #urlteam [15:21] *** swebb sets mode: +o ersi [16:06] *** Fletcher has quit IRC (Ping timeout: 252 seconds) [16:20] *** JesseW has joined #urlteam [16:20] *** svchfoo3 sets mode: +o JesseW [16:55] *** JesseW has quit IRC (Leaving.) [19:42] *** Start has quit IRC (Read error: Connection reset by peer) [19:43] *** Start has joined #urlteam [19:53] *** SimpBrai1 has quit IRC (Leaving) [19:54] *** SimpBrain has joined #urlteam [20:11] *** Fletcher has joined #urlteam [22:23] *** SilSte has quit IRC (Read error: Connection reset by peer) [23:08] *** bwn has joined #urlteam [23:47] *** aaaaaaaaa has joined #urlteam [23:47] *** swebb sets mode: +o aaaaaaaaa