My latest hurdle with getting the Multiverse world server running from trunk on my Ubuntu box was that the instance server couldn't find the world files that were specified in config/sampleworld/startup_instance.py:
instance.out:ERROR [2012-06-08 19:36:44,035] Instance-2 CreateInstanceHook: world file not found fileName=../config//.mvw
instance.out:ERROR [2012-06-08 19:36:44,043] Instance-4 CreateInstanceHook: world file not found fileName=../config//bigbrother.mvw
instance.out:ERROR [2012-06-08 19:36:44,049] Instance-6 CreateInstanceHook: world file not found fileName=../config//frontier.mvw
instance.out:ERROR [2012-06-08 19:36:44,061] Instance-8 CreateInstanceHook: world file not found fileName=../config//video.mvw
Checking that startup_instance.py file, here's what it's trying to load:
In server/plugins/InstanceClient.java, WORLD_DIR is set to $MV_HOME/config/$WORLD_NAME. OK, so it looks like WORLD_NAME is missing from the path. It's also missing from the first filename, so not getting set.
There's a problem with the multiverse.sh script where it isn't picking up the multiverse.worldname setting from the multiverse.properties file. It's supposed to use that to set the MV_WORLDNAME variable, which is used to set WORLD_NAME.
If you specify the world name as a commandline argument for multiverse.sh like this, WORLD_NAME gets set and the instance server finds the .mvw files and runs successfully:
./multiverse.sh -w sampleworld -v start
I am now able to log into the sampleworld running on my own server using the source files from svn trunk. It has a working master and you can create a character and walk around. Victory!