Some raw notes
--BlueMax 06:41, 3 August 2012 (EDT)
Here's my plaintext unformatted dump of what I've written so far:
Setting up the Warrior:
- Your machine needs to be relatively powerful with an internet connection to run the Warrior. You'll need at least:
- a 2.0ghz dual core processor - 2 gigabytes of RAM - 100GB of hard drive space - a fast internet connection (at the very least 1mbps down/up)
- Although we do recommend something more powerful (or if you plan to do more with your machine while you also use the Warrior):
- a quad core processor - 4 gigabytes of RAM - as fast of an internet connection as possible (we love universities!) - most or all of your background downloading/uploading programs turned off (such as torrent clients)
- To use the Warrior, we recommend using VirtualBox. VirtualBox is a program available for all major operating systems that emulates a desktop computer. The Warrior is a preconfigured Linux system (or "virtual appliancce") designed to automate the process of downloading and uploading data for an ArchiveTeam project.
- Visit https://www.virtualbox.org/wiki/Downloads and download the latest version for your platform, and:
-Open and follow the setup as prompted. Default settings will be fine for the most part. Do not unselect the VirtualBox Networking selection where it appears, as it is required to run the Warrior.
For Mac OS X:
For Linux systems:
- Once you have VirtualBox installed, open it via your preferred method (command line, shortcut or what have you).
- Now download the Warrior using the below link. The current version of the Warrior is a 167MB .ova (virtual appliance) file. You'll download this file and import it into VirtualBox. Save it to somewhere you will be able to access it.
- When the main menu has opened, click File > Import Appliance. You'll be given a pop-up window. Click the Choose box and navigate to the .ova file you just downloaded, and select it, then click Next.
- Do not uncheck either of the tick boxes in the next window, simply click Import. It may take a few minutes for the next part of the process to take place.
Now to boot the ArchiveTeam Warrior and get it working on a project.
- Double-click the new option that has just appeared in the main VirtualBox window. It should have the name "archiveteam-warrior-2" or similar. A new popup window will appear if you have done it right.
- While the system boots in the background, a few VirtualBox pop-up messages may appear. Feel free to just click "OK" on them. There should be no need to touch any of the options or press any keys on your keyboard until the warrior has booted up.
- You'll eventually be presented with a screen that says "Configure your warrior via the web interface." Minimize the VirtualBox window on your desktop (if you are unable to move your mouse, press the Right Control button on your keyboard).
- Open your choice of web browser. We require a modern web browser (the latest versions of Firefox and Chrome will work, we do not support IE on account of not willing to be suicidal) and enter "http://localhost:8001" without quotes into the address bar, and press Enter.
- If you've done this correctly you should see the ArchiveTeam Warrior page. On the left side of the screen you'll see several options, including "All projects" and "Your settings". We want to set up your settings first, so click "Your settings".
- Enter your nickname in the first box so that we can identify who you are on our tracker. Only use letters and numbers (Ph1shF00d would work, but Ph*shF**d wouldn't, for example).
- The second box is how many items will download at a time. You may put this up as high as 6 if you have a very speedy internet connection, but slower connections may want to stick to the default selection.
- You can leave the rest of the settings as they are. Click "Save settings" once you're done and then click "All projects" on the left pane.
- You'll be presented with a list of projects on the right pane of the browser window. If you just want the Warrior to do what the ArchiveTeam wants it to, simply click the "Work on this project" button to the right of the "ArchiveTeam's Choice" project. Your browser will be redirected to the "Current Project" tab and the Warrior will start work on what the main project for ArchiveTeam currently is. If you see a bunch of black windows scrolling down your screen, your Warrior is working as intended and you're free to leave your computer, or do other things. (You may close the web browser window as well, it won't affect the Warrior).
- If you want to select a different project, simply go to the "All projects" page again and select which one you'd like. Stopping your Warrior is just as simple, go to the All projects page and click "Stop this project" at the top of the page (under "Your current project").
- To shut down the ArchiveTeam Warrior, click the "Shut down" button on the page, and close the webpage. Eventually the VirtualBox window will close (in the background if you minimised it) and you can close the main VirtualBox window.
Some additional notes
Here's some of the things I noticed when using the warrior:
- use the archiveteam-warrior-v2 .ovf from archive.org, not the v1 linked from the article!
- if you use vmware, ignore the warning about the .ovf file not passing validation
- however, before starting the VM, you have to do these steps
- remove the VM from the list of favorites on the left side (simply select it and hit DEL -- don't worry, you won't delete it and will add it again later)
- edit the *.vmx file (virtual machine config file)
- If on OS X, this can be found by right-clicking on the .vmwarevm file that VMWare generates and selecting "Show package contents" - Machawk1 15:54, 5 August 2014 (EDT)
- change all lines that start with "ide1:1" to "ide1:0" (i.e. replace the second 1 with a 0). This is because the .ovf file specifies the second harddisk as secondary slave, which won't work in VMware if you don't configure a secondary master first.
- re-add the vmx file to VMware. Either double-click it, or drag&drop it to the are where you deleted it earlier.
- however, before starting the VM, you have to do these steps
- The start screen will tell you to open "http://localhost:8001". At least on VMware (and I guess also on VirtualBox, but I don't know) this will not work. Instead, do the following:
- Press Alt-F3 to get to the 3rd console
- login as "root" with password "archiveteam"
- type "ifconfig" and note the IP address given under "eth0"
- enter "http://x.x.x.x:8001" in your browser (where x.x.x.x is the IP address you noted)
- (I really hope the login screen will, at some point in time, display the external IP Address instead of "localhost")
--Darkstar 18:55, 9 August 2012 (EDT)
Autorun for lazy people
I've given up running the warrior on fedora because I have to fix the VirtualBox packages manually every time I update the kernel, but I'm now trying on an Ubuntu machine I don't use personally. Something that the instructions should cover, at some point, is how to set it up so that it's started automatically at system boot. I found only slightly complicated instructions around the web, but also some indication that it may be much easier with VirtualBox 4.2 (Ubuntu repos currently have 4.1, AFAICS). --Nemo 07:55, 12 June 2013 (EDT)
Lifetime stats page for the warrior?
It'd be nice if the warrior had a lifetime bandwidth stats page.
To get some additional visibility and make the life of the occasional users of the Warrior on AWS, it would be nice to get an ArchiveTeam Warrior image in the AWS marketplace (for free, of course). Also in other directories and for other hosting providers, of course, if someone prefers contributing to those. --Nemo 11:18, 23 December 2013 (EST)
Viewing the Control Panel on a external computer
If you run the Warrior VM on an external computer, it might be useful to view the control panel from your main computer.
To do this, on the remote computer, go to VirtualBox, select the Warrior VM, Settings, and then Network.
If not already down, click the Advanced tab and you should then see a button that says Port Forwarding. Click it.
In the Web Interface Row, find the Host IP Column, and change it to 0.0.0.0 and press OK.
On your main computer, you can now type in the remote computer's local IP address into the web browser with the port number to view its stats.
--Crypto 16:48, 10 August 2014 (EDT)
Running more than one warrior on a computer (VirtualBox)
Sometimes the situation might arise that you want to run two or even more warriors on one machine. For this example, we are going to assume you are already running one warrior, and you want to add another one.
Please note, make sure you have enough resources to run multiple warrior VMs. Each Warrior will use 400MB of ram, and at Max 60GB of Disk Space.
First off, you are going to need to import the warrior instance. If you still have the .ova file you used to import the original warrior, you may use import it again.
While importing, make sure to change the name.
Once imported, go to the second warrior and go to settings.
In the settings menu, go to Network, then click the Advanced Tab, and click on Port Forwarding.
Once in the Port Forwarding menu, change the host port to 8002, but leave the guest one alone.
Done! You can boot up the second warrior, and administrate it through port 8002. You may change the host port to whatever you want, just leave the guest port to 8001.
--Crypto 02:55, 11 August 2014 (EDT)
That's very useful but instead of importing a new warrior I just right clicked on my original one and chosen clone. I created as many warriors as my laptop could afford -taking into consideration its specs- and then followed you steps about Port Forwarding. It's a very easy and straightforward process.
--PanoIgano 16:17, 08 May 2015 (EDT)
Split the FAQ into "Problems" and "I'm curious" sections
I'd like to do that for one reason: there're too many entries even for the list of contents & it would make the troubleshooting much easier for newcomers.
Another proposal is to rewrite the questions, because as of now some of them start with fillers like "4.2 Why am I seeing a message that no item was received?" although they can be reduced to the core content as "4.13 I can't connect to localhost."