Difference between revisions of "VRkour"

From CSLabsWiki
Line 1: Line 1:
|ip_addr =
|ip_addr =
|contact_person = [[User:Jared|Jared Dunbar]]
|contact_person = [[User:Jared|Jared Dunbar]]
Line 8: Line 9:
|category = Service
|category = Service
|handoff = yes
|handoff = yes
VRkour is a service which runs a VR site.
VRkour is a service which runs a VR site.

Latest revision as of 23:30, 28 November 2017

|ip_addr = |contact_person = Jared Dunbar |last_update = May 2017 |host_vm = VRkour |vm_host = hydra |services = vrkour |category = Service |handoff = yes

VRkour is a service which runs a VR site.

Handed off to Jared Dunbar in late October 2016

Basic Diagnosis

Basically, I rooted the VM and determined what was on it.

In bruskajp's home folder there's a file called start.sh and a folder called VRArena

To start the software, cd to that folder and then run 'npm start'. That will then start the stuff


I did a few things to make it operational again.


First, I set up a systemd service



ExecStart=/bin/bash /home/bruskajp/start.sh


Enable and start that service:

systemctl enable vrkour.service && systemctl start vrkour.service

Iptables Rules

Next, I added some iptables rules so that we can view port 3001 from 80 without privilege escalation.

So I added /etc/iptables.rules:

# Generated by iptables-save v1.4.21 on Wed Nov  2 17:27:10 2016
-A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 3001
# Completed on Wed Nov  2 17:27:10 2016

and as well, we have a script in /etc/systemd/system/iptables.service, which loads that file.

The systemd service file reloads whenever it crashes. Apparently, according to James, crashing is a common problem.