[00:01] I'm still getting the same error from passenger. [00:01] This has to be my coding curse showing up again. [00:03] what is the error message? [00:03] copy it into a paste website if needed [00:05] http://pastebin.com/kiRS8EZC [00:11] I suspect it has something to do with the above domain name because it makes some request there, and the response is too small to be useful or is really compressed. [00:12] but the error message says HOME isn't set [00:14] oh [00:14] why would mine be set and yours not? [00:14] its the same machine, isn't it? [00:15] i have no idea other than my virtual machines start up quickly on my desktop [00:15] can you log in as "dev", password "dev" and run "sudo restart nginx-tracker"? [00:16] good thinking [00:18] same result, and is the same if I reboot completely. I'll try digging some more through their docs. [00:24] if that doesn't work,edit /etc/init/nginx-tracker by editing the "exec" line by inserting "HOME=/home/tracker" after "exec" so it reads like "exec HOME=/home/tracker /home/tracker/nginx/sb[...rest of the line goes here]" [00:34] could you do a fresh import and paste /home/tracker/nginx/logs/error.log somewhere so I can compare? [00:35] sure, give me a min [00:36] do I need a semicolon after what you wanted be to insert before the rest of what was there? [00:39] no semicolon, i wanted something like "exec VARIABLE=abcd /bin/program args" [00:40] ok, just checking. I've got in trouble for missing semicolons before. [00:40] for the least used punctuation, they sure are important in most computer-related things. [00:41] here's my error.log: http://pastebin.com/hLxwVg6m [00:44] Thanks [00:44] shorter than mine [00:45] should I try rebooting with your new init script? [00:47] exec HOME=/home/tracker not found [00:47] then nginx-tracker terminates with status 127 [00:49] hmm.. [00:49] wait [00:50] was that the entirety of the error log? [00:50] yes, that's the entire log [00:50] oh, undo what i said to the init file. but add "env HOME=/home/tracker" on a new line above the exec line [00:53] and also add "export HOME" [00:54] between the two on its own line? [00:56] yes, you should have the 'env', 'export', and then the 'exec' line [00:56] * chfoo hopes it works this time [00:57] ok [00:57] i still don't know the underlying reason why it's not set though [01:00] * aaaaaaaaa never understands why people like graphical boot screens [01:00] you're not going to believe this [01:01] I deleted those lines from the init script on accident and it started just fine. [01:01] I'm going to have to look at these logs and figure out what happened [01:02] got it [01:02] I think my computer was too slow and the multiple reboots fixed it [01:02] it tried to download a binary and when that failed, to compile support natively [01:03] that had to be timing out and screwing everything else up. [01:03] but it shouldn't be needing to compile anything though [01:04] The logs say it did [01:04] maybe your machine is way faster than mine [01:04] can you post the logs where it says that? [01:06] i was wondering why you were concerned about the logs [01:06] They are long [01:07] plus, when I don't know what is wrong, I've found reading the logs tend to tell you, if you can read the language they used. [01:09] is there a way to copy it off of here without writing the whole thing? Or do you not know vb on windows that well? [01:10] on ubuntu i used ssh, after fixing the port mapping, and just copy and pasted it from the terminal [01:10] oh duh [01:12] but for serious work, i would just use sftp and filezilla for transfering files [01:12] gotta love filezilla [01:23] couldn't get the port mapping to work right [01:23] but it is here [01:24] http://pastebin.com/1X9zyEXx [01:24] near the bottem [01:24] bottom [01:30] i don't think i'll be able to figure it out. did you want to file an issue about this or should i? [01:30] on the archiveteam-dev-env issue tracker i mean [01:31] Could you do it for me, please. My frustration level is too high. Or maybe add a suggesting to use a screaming fast PC. [01:33] I'll be back when I'm ready to mess with it some more. [17:11] * aaaaaaaaa belatedly thanks chfoo for his Herculean effort in helping him. [17:14] no problem. at least we know continuously rebooting makes the problem go away. [17:15] I found a better solution [17:15] I was updating the bug tracker with it. [17:16] apparently it is a widespread problem [17:19] Basically, you can force it to compile without a time limit. [17:21] Rather than hope it gets further each time. [17:33] Good to know it wasn't just me. [21:25] any recommended minimum memory for setting up a tracker? [21:33] a rough guess is 1 GB for every 5 million items [21:37] ok. trying to set up a dev env for tracker. long on my todo list [21:40] If you want to use the prebuilt image instead of installing it all manually, be sure to do the stuff in the bug tracker. [21:41] starting from scratch, but had a look at preseeds for dev env and so on [23:28] got to the step of rvm requirements..getting " tracker password required for 'apt-get --quiet --yes update': " [23:30] does it maybe think 'tracker' is the sudo account or? .. since it's not [23:56] figured it out? you can either give it sudo access temporarily or install the things it wants manually