Blocks over?

It appears to be working for me now. Please report any remaining outtages in the comments.

Back?

I'm currently unable to verify it, but there are some reports from people that they can access the site. Stand by for more information.

Downtime

So, apparently, the following ISPs have decided to censor http://partyvan.info/:

Verizon
ATT
Bell
Comcast
RoadRunner
Qwest

The server admin is logged in via ssh just fine, but we have numerous reports from the above isps that we are down, even though the box is up. Currently investigating. Below is a traceroute from a romanian server, to the wiki box:

1  gw-mediasat-mpint (85.204.229.1)  0.321 ms  0.241 ms  0.199 ms
2  br1-ge-1-3-0-edge.b.mediasat.ro (81.180.226.153)  8.800 ms  5.877 ms *
3  g1-6.osr0-bukarest.ro.net.telekom.hu (84.1.102.45)  1.337 ms  5.129 ms  15.645 ms
4  * * 84.1.94.87 (84.1.94.87)  69.166 ms
5  bpt-b1-link.telia.net (213.248.81.45)  14.734 ms  14.610 ms  15.338 ms
6  bpt-b2-link.telia.net (213.248.96.98)  19.061 ms  14.697 ms  14.836 ms
7  * hbg-bb2-link.telia.net (80.91.250.134)  55.295 ms  36.726 ms
8  adm-bb2-link.telia.net (80.91.252.42)  45.928 ms  53.415 ms adm-bb2-pos7-0-0.telia.net (213.248.65.161)  46.892 ms
9  adm-b3-link.telia.net (80.91.254.129)  44.864 ms adm-b3-link.telia.net (80.91.253.94)  42.775 ms  44.091 ms
10  xe-2-3-0.cr1.ams2.nl.nlayer.net (213.248.67.158)  48.537 ms  56.639 ms  47.237 ms
11  xe-1-1-0.cr1.lhr1.uk.nlayer.net (69.22.142.33)  50.536 ms  52.094 ms  49.446 ms
12  xe-2-2-0.cr1.nyc3.us.nlayer.net (69.22.142.9)  118.461 ms  124.900 ms  122.476 ms
13  xe-2-1-0.cr2.ord1.us.nlayer.net (69.22.142.6)  137.813 ms  137.989 ms  147.812 ms
14  po2.ar1.ord1.us.nlayer.net (69.31.111.138)  142.537 ms  141.483 ms  141.218 ms
15  as32748.tge8-4-116.ar1.ord1.us.nlayer.net (69.31.111.34)  148.552 ms  144.225 ms  142.935 ms
16  ip17.208-100-32.static.steadfast.net (208.100.32.17)  142.959 ms  143.794 ms  149.534 ms
17  ip250.208-100-10.static.steadfast.net (208.100.10.250)  150.278 ms  145.366 ms  159.134 ms
18  89.46.34.4 (89.46.34.4)  144.302 ms  142.585 ms  145.223 ms

While below here is what happens when a traceroute is run from the USA:

1  Vlan5.css-nts-r1.net.umd.edu (128.8.5.60)  0.534 ms
2  Gi5-1.css-core-r1.net.umd.edu (128.8.0.9)  0.421 ms
3  Gi3-2.css-fw-r1.net.umd.edu (128.8.0.82)  0.407 ms
4  Gi2-1.ptx-cogent-r1.net.umd.edu (128.8.0.238)  0.433 ms
5  ge-0-2-0.cogent-gw.net.ums.edu (131.118.255.213)  0.663 ms
6  gi0-7.na21.b003328-0.dca01.atlas.cogentco.com (38.112.19.133)  1.416 ms
7  te9-2.3688.ccr02.dca01.atlas.cogentco.com (38.20.39.189)  30.526 ms
8  te8-1.mpd02.dca01.atlas.cogentco.com (154.54.2.193)  1.650 ms
9  te7-1.ccr01.dca01.atlas.cogentco.com (154.54.26.38)  1.784 ms
10  *
11  *
12  *

This is another american traceroute:

1 fa0-8.na01.b005944-0.dca01.atlas.cogentco.com (66.250.56.189) 4 msec 4 msec 4 msec
 2 gi1-3.3807.ccr02.dca01.atlas.cogentco.com (66.28.6.189) 4 msec 4 msec 4 msec
 3 te9-1.ccr01.dca01.atlas.cogentco.com (154.54.26.54) 0 msec 4 msec
   te8-1.mpd02.dca01.atlas.cogentco.com (154.54.2.193) 4 msec
 4  *  *  *
 5  *  *  *

Routing seems to stop at .atlas.cogentco.com

wtf

BACK!

Now that all the raidchan drama seems to have passed, the Insurgency Wiki is back up. Back to ra/i/ding.

DDoS

Apparently there is some irc drama e-peenery going on, and so we are down due to ddos. Try using the backup:

http://partyvan.eu/static/

EDIT: disregard,

http://netcollect.org/partyvan-pwnt.txt

**In the same way that taking candy from strangers leads to rape, running strage programs from unknown people also leads to rape.

Backup List

In case of the wiki going down again, I really suggest that you all bookmark this post. Here are some mirrors of the wiki:

Daily Mirror (browse): partyvan.eu
2008-05-03 snapshot (download): massmirror

Here is a quick overview of what has been going on with the wiki.

Basically, everything was swell, then malaphus decided to die. As a result, his hosting account crashed, and we lost the wiki. Luckily we have a relatively recent backup, and google cache caught everything, so it should just be a matter to copy+pasting stuff into the wiki.

We did find a new host, and are currently setting stuff up. After some dns issues, we're now onto fixing php. Here is the checklist of things that need to happen for the wiki:

[ ] = to do, [/] or [xx%] = in progress, [x] = done

1. Set up server [x]
2. Set up mediawiki [x]
   
3. Upload sql dump [x]
4. Import sql dump [x]
5. Upload images [x]
6. Copy content from Google cache [ /]
7. Customize (skins, etc) [x] *need to fix logo
   

GET OFF YOUR ASS AND COPY STUFF FROM GOOGLE CACHE INTO THE WIKI! I will fix the logo and front page tomorrow.

DDoS war

Long story short, fucking shitstorm ddos. Details still emerging, but it seems that 420chan, not 420chan, partyvan.info, and 315chan.org were all taken out, and #xenu was fucked as well as /xenu/ on 711chan.

Nameserver problems

K, so apparently partyvan.info isn't working, due to the nameservers being being broken, but http://xyndros.ath.cx/ and http://67.228.193.162/ should both work.

EDIT: http://partyvan.info/ works again

New Feature

Just a small announcement--you can now embed youtube videos into wiki pages. It works like this:

<Youtube>

title=My test YouTube dealee
movie_url=http://www.youtube.com/v/yWQhBnpFEpg
embed_source_url=http://www.youtube.com/v/yWQhBnpFEpg
wrap = yes
width=500
height=400
</Youtube>

Downtime

Sorry, we had to take the server offline for maintenance. Here is an overview of what happened (copypasted from irc):

[18:31]  the ddos used up all available connections
[18:31]  so I used a config tool to up the connection limit
[18:31]  but the config tool added a newline in a comment in the config file
[18:31]  and part of the comment was parsed as a directive
[18:32]  this filled the error log with errors
[18:32]  and /var was completely full
[18:32]  because /var was full
[18:32]  mysql crashed
[18:32]  and the system wouldn't start except in single user mode
[18:32]  so I had to log in with vmware-server-console to get single user mode and delete the logs
[18:32]  In the process of restarting mysql, it broke the database
[18:33]  the auto-incrementing column in one of the tables broke
[18:33]  so I had to dump and reload the whole database
[18:33]  :D
[18:33]  A nice days work

DNS Censorship

So, we've gotten scattered reports of people being unable to access partyvan.info, even after giving isps 5 days for the dns stuff to propagate. These reports seem to mostly be coming from people with the Rogers ISP, though some people with RoadRunner have also had problems. I've also seen problems accessing partyvan.info from Qwest DSL.

Recently I just tried to recreate the old dns for the wiki (xyndros.ath.cx), but it seems that dyndns blacklisted it. If you don't want to remember the ip, try using http://partyvan.ath.cx/.

In the past, we've had complaints from comcast users that 420chan/711chan/the wiki are down, when they're not.

Clearing some shit up

The server that hosts the wiki has never been hacked. We've put up warnings to everyone to change their passwords before, but these were simply a precaution. The closest to being hacked that the server has ever been, was when Grawp was moving pages around to Hagger?? and the question marks fucked with our ability to delete/fix stuff normally. There have been times when it appeared that we were hacked, but these have all turned out to be misunderstandings--HD dieing, datacenter disabling stuff during ddos, etc. We've never actually been rooted.

Also, note that defacing an openly editable wiki doesn't count as hacking.

Up again (March 08, 2008)

I've finished enough that the wiki should be operational again. The downside is that the latest backup was from the 5th, since I was still working on the backup system the day it went down. Now we're (mainly wedtm) setting it up so that vmware snapshots of the wiki VPS are being sent to the offsite nas every hour.

Next week we expect a meteor strike followed by a plague of locusts, and the loss of all the firstborn.

Downtime (March 07, 2008)

The most recent downtime has been due to the failure of a 1 TB HD (i no rite). Currently I'm installing and configuring the software on the server. As a result of the downtime, WedTM is saying that he will have the wiki vps backed up to an offsite NAS hourly (win). Here is the progress of the wiki:

Done:
Creating disk for VMWare
Loaded freebsd 7
Compiled/configured mysql 5
Compiled/configured apache22
Compiled/configured php5
Compile/configure eaccelerator
Compile/configure memcached
Restore mediawiki files from backup
Restore mediawiki db from backup
Compile/configure php5-extensions
Configure mediawiki for memcached
Various Configuring (/etc/rc.conf, my.cnf, etc)

Currently:
Extra stuff, e.g. ftp, mailserver

Later:
Fix backup system