One Hour One Life Forums

You might have the old version of the server still running.  Try rebooting the VM then start the game server again to see if you can connect after that.

I am not sure why you're seeing that error looking for a stack.cpp file - I don't see a file with that name in the current build.  If you haven't already, you might try running the refreshBuildScript.sh and pullAndBuildTestSystem.sh scripts to make sure you have the latest code.

It does look like the update script is now "convertDBs.sh", so you can try that instead:

./convertDBs.sh

I'm sorry about the disk allocation on the image - that was a dumb mistake on my part.  I'll get new images up soon, it's been a busy couple of weeks.

And great post, Roolstar, thanks for putting those instructions together.

You might also make sure the old version of the server isn't still running.  Easiest way to do that is to reboot the VM.  The latest version of the server (when I post this) is 78 - check inside the file Ilap mentions above (serverCodeVersionNumber.txt), and if it's 78 or higher, then it's almost certainly that an old version of the server is still running on the system.

Weird, but glad it worked.  If the last image you downloaded didn't have the refresh script, let me know and I'll re-upload the newer image.

Did you try making a test map with the editor, per the instructions?  I have no idea if that makes a difference, but if you haven't, it could be worth trying.

Glad it finally worked!

Hm, bummer.  I added a "refreshBuildScript.sh" script that redownloads the pull script to the images - they're uploading now.  That's the only major change made to the image, no need for a redownload.

The script just runs this command (which you can run in the ohol-build directory to get the latest pull script):

wget -N https://raw.githubusercontent.com/jasonrohrer/OneLife/master/scripts/pullAndBuildTestSystem.sh

When I ran it on a VM where I'd already updated with the old script I got the messages that said it was already up-to-date, but the script still made some changes (like setting the contents of the version file to 72).  I hadn't been able to connect with the client before, but when I stopped the server and started it up after running the newer build script, I was able to connect.

Not normal.  Are you sure you got the right architecture (64-bit for a 64-bit OS, or 32-bit for a 32-bit OS)?

The "ip a" command should show you the network adapters configured on the VM, so it won't show your computer's IP address there - just the addresses being used by the VM.  The adapter in "bridged" mode should be asking your router for its own IP address on the LAN, which is why that's different.

If you have more than one network adapter on your computer (a wired connection and a wireless adapter, for example), you might make sure the bridged adapter is using the right adapter (click the name to see a drop-down menu).

If you haven't already, I'd try pinging one computer from the other, or seeing if you can mount a share from the other, just to make sure that the computers can actually connect to each other on the LAN.

Otherwise...yeah, I'm not sure what else could be going on.  You can try searching for "virtualbox LAN connection" to see what you can find in the way of tutorials or explanations on StackExchange.  You might find answers from people with more experience troubleshooting it than I do.

The port forwarding I set up in the instructions only accepts connections to localhost (127.0.0.1).  You could try adding another port forwarding rule similar to that, but using the main IP address of your computer for the "Host IP" (with everything else the same).

Another approach would be to shut down the VM, then go to its Network Settings, then enable a second network adapter and set it to "Bridged" mode.  That should let the VM get its own IP address on the local network.  You can check it by starting the VM back up again and running "ip a" to see if there's a new IP address that matches your LAN.

Note that you might need to open port 8005 in your computer's firewall to let the connection through as well.

I'll update the instructions, but basically I'd imagine the problems come from the update.  If you use the latest client with the server on the image there are probably Issues.

I'd suggest stopping the server with control-Z (in the terminal you're running it in), then cd your way to the ohol-build directory, then run the pullAndBuildTestSystem.sh.  Basically, that looks like:

cd ~/ohol-build
sh pullAndBuildTestSystem.sh

That will download the latest server code and compile it.  When it's done, try running the server and see if it works any better.

If you need to update the client to the latest version, change the value in useCustomServer.ini in the client's Settings directory to "0", then launch the client and log in to the game to auto-update, then quit and set that back to "1" to connect to your local server again.

Note that if you see a socket error or the like trying to launch the server, then the old server might still be running (that can happen if you double-click the server in a file browser window).  To fix that, go into the terminal and type:

ps -ef | grep OneLife

If you see a line with "./OneLifeServer" in it, then it's running.  Make a note of the first number in the line so you can kill it.  If that number were 12345, for example, run:

kill -1 12345

That should tell the server to shut down, then you can start the newly-updated server in its place.