Official Community Forums
 
HomeHome  FAQFAQ  SearchSearch  MemberlistMemberlist  UsergroupsUsergroups  RegisterRegister  Log in  The Wiki  Website  github Project  

Share | 
 

 Server startup errors: startup_instance.py ?

View previous topic View next topic Go down 
AuthorMessage
theryn
Newbie
Newbie
avatar

Posts : 8
Join date : 2012-05-22
Location : Sydney, Australia

PostSubject: Server startup errors: startup_instance.py ?   Tue 22 May - 14:44

Hi all,

I'm on Vista Home Basic service pack 2. I've installed everything according to the Platform Tutorial, but have trouble starting the server.

I have a command prompt open, I'm in mv_home/bin, I type: start-multiverse.bat

I see the startup lines I'm expecting, but each "Starting insert_here server" line doesn't have SUCCESS. Then I see:

Wait for finished initializing msg...

C:\multiverse\bin>Multiverse server version 1.5 0 (- -)

<after some time passes:>
STARTUP FAILED -- didnt complete after 120 seconds.
Please stop server.

Here's the only ERROR lines in mv_home/logs/sampleworld/*.out (and all lines before it up to "Executing script file::

Quote :

DEBUG [2012-05-22 12:49:18,532] main Engine, Executing script file: ..\config\sampleworld\startup_instance.py
DEBUG [2012-05-22 12:49:18,532] main runPYFile: file=..\config\sampleworld\startup_instance.py
DEBUG [2012-05-22 12:49:18,548] main sendRPC type=mv.REGISTER_INSTANCE_TEMPLATE id=23 class=multiverse.server.plugins.InstanceClient$RegisterInstanceTemplateMessage
DEBUG [2012-05-22 12:49:18,548] main Sending mv.REGISTER_INSTANCE_TEMPLATE id=23 to instance
DEBUG [2012-05-22 12:49:18,548] SelfMessage SelfMessageHandler.handle pos=169
DEBUG [2012-05-22 12:49:18,563] SelfMessage handleSelfMessage id=23 type=mv.REGISTER_INSTANCE_TEMPLATE class=multiverse.server.plugins.InstanceClient$RegisterInstanceTemplateMessage
DEBUG [2012-05-22 12:49:18,563] SelfMessage deliverMessage rpc to multiverse.server.plugins.InstancePlugin@740a59
DEBUG [2012-05-22 12:49:18,563] Instance-1 EnginePlugin.handleMessage: got msg id 23, matching 1 hooks for msgtype MessageType['mv.REGISTER_INSTANCE_TEMPLATE', 118]
DEBUG [2012-05-22 12:49:18,563] Instance-1 RegisterInstanceTemplateHook: template=[Template: name=sampleworld template (ns=NS.instance, key=worldFileName, val=$WORLD_DIR/$WORLD_NAME.mvw)(ns=NS.instance, key=initScriptFileName, val=$WORLD_DIR/instance_load.py)
DEBUG [2012-05-22 12:49:18,563] Instance-1 RegisterInstanceTemplateHook: added template name=sampleworld template
DEBUG [2012-05-22 12:49:18,563] Instance-1 sendResponse to instance,23 type=msgsys.RESPONSE id=24 class=multiverse.msgsys.BooleanResponseMessage
DEBUG [2012-05-22 12:49:18,563] SelfMessage SelfMessageHandler.handle pos=30
DEBUG [2012-05-22 12:49:18,563] SelfMessage handleSelfMessage id=24 responseTo=23 type=msgsys.RESPONSE class=multiverse.msgsys.BooleanResponseMessage
DEBUG [2012-05-22 12:49:18,563] Instance-1 EnginePlugin.handleMessage: processed msg 23, type=MessageType['mv.REGISTER_INSTANCE_TEMPLATE', 118], time in ms=0
DEBUG [2012-05-22 12:49:18,563] main sendRPC type=mv.CREATE_INSTANCE id=25 class=multiverse.server.plugins.InstanceClient$CreateInstanceMessage
DEBUG [2012-05-22 12:49:18,563] main Sending mv.CREATE_INSTANCE id=25 to instance
DEBUG [2012-05-22 12:49:18,563] SelfMessage SelfMessageHandler.handle pos=86
DEBUG [2012-05-22 12:49:18,563] SelfMessage handleSelfMessage id=25 type=mv.CREATE_INSTANCE class=multiverse.server.plugins.InstanceClient$CreateInstanceMessage
DEBUG [2012-05-22 12:49:18,563] SelfMessage deliverMessage rpc to multiverse.server.plugins.InstancePlugin@740a59
DEBUG [2012-05-22 12:49:18,563] Instance-2 EnginePlugin.handleMessage: got msg id 25, matching 1 hooks for msgtype MessageType['mv.CREATE_INSTANCE', 119]
DEBUG [2012-05-22 12:49:18,563] Instance-2 CreateInstanceHook: templateName=sampleworld template override=[Template: name=null (ns=NS.instance, key=name, val=default)
DEBUG [2012-05-22 12:49:18,563] Instance-2 CreateInstanceHook: assigned world manager WorldManager1 host=OfficePC
ERROR [2012-05-22 12:49:18,563] Instance-2 handleMessageImpl java.lang.NullPointerException
at java.lang.String.replace(Unknown Source)
at multiverse.server.util.FileUtil.expandFileName(FileUtil.java:10)
at multiverse.server.plugins.InstancePlugin$CreateInstanceHook.createInstance(InstancePlugin.java:307)
at multiverse.server.plugins.InstancePlugin$CreateInstanceHook.handleMessage(InstancePlugin.java:222)
at multiverse.server.plugins.InstancePlugin$CreateInstanceHook.processMessage(InstancePlugin.java:216)
at multiverse.server.engine.EnginePlugin.handleMessageImpl(EnginePlugin.java:424)
at multiverse.server.engine.EnginePlugin$QueuedMessage.run(EnginePlugin.java:458)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
DEBUG [2012-05-22 12:49:18,563] Instance-2 sendResponse to instance,25 type=msgsys.RESPONSE id=26 class=multiverse.msgsys.ExceptionResponseMessage
DEBUG [2012-05-22 12:49:18,563] SelfMessage SelfMessageHandler.handle pos=864
DEBUG [2012-05-22 12:49:18,563] SelfMessage handleSelfMessage id=26 responseTo=25 type=msgsys.RESPONSE class=multiverse.msgsys.ExceptionResponseMessage
ERROR [2012-05-22 12:49:18,563] main ScriptManager.runPYFile: file=..\config\sampleworld\startup_instance.py Traceback (innermost last):
File "..\config\sampleworld\startup_instance.py", line 15, in ?
multiverse.msgsys.RPCException(java.lang.NullPointerException in instance)
at java.lang.String.replace(Unknown Source)
at multiverse.server.util.FileUtil.expandFileName(FileUtil.java:10)
at multiverse.server.plugins.InstancePlugin$CreateInstanceHook.createInstance(InstancePlugin.java:307)
at multiverse.server.plugins.InstancePlugin$CreateInstanceHook.handleMessage(InstancePlugin.java:222)
at multiverse.server.plugins.InstancePlugin$CreateInstanceHook.processMessage(InstancePlugin.java:216)
at multiverse.server.engine.EnginePlugin.handleMessageImpl(EnginePlugin.java:424)
at multiverse.server.engine.EnginePlugin$QueuedMessage.run(EnginePlugin.java:458)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

multiverse.msgsys.RPCException: multiverse.msgsys.RPCException(java.lang.NullPointerException in instance)
at org.python.core.Py.JavaError(Unknown Source)
at org.python.core.Py.JavaError(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx5.f$0(..\config\sampleworld\startup_instance.py:15)
at org.python.pycode._pyx5.call_function(..\config\sampleworld\startup_instance.py)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at multiverse.server.engine.ScriptManager.runPYFile(ScriptManager.java:181)
at multiverse.server.engine.ScriptManager.runFile(ScriptManager.java:94)
at multiverse.server.engine.Engine.processPostScripts(Engine.java:527)
at multiverse.server.engine.Engine.main(Engine.java:382)
DEBUG [2012-05-22 12:49:18,563] main Engine, script completed
DEBUG [2012-05-22 12:50:15,613] DBKeepalive Database: ping
DEBUG [2012-05-22 12:51:15,626] DBKeepalive Database: ping
DEBUG [2012-05-22 12:52:15,639] DBKeepalive Database: ping
DEBUG [2012-05-22 12:53:15,652] DBKeepalive Database: ping
DEBUG [2012-05-22 12:54:15,665] DBKeepalive Database: ping
DEBUG [2012-05-22 12:55:15,679] DBKeepalive Database: ping
DEBUG [2012-05-22 12:56:15,692] DBKeepalive Database: ping
DEBUG [2012-05-22 12:57:15,705] DBKeepalive Database: ping
DEBUG [2012-05-22 12:58:15,706] DBKeepalive Database: ping
DEBUG [2012-05-22 12:59:15,714] DBKeepalive Database: ping
DEBUG [2012-05-22 13:00:15,727] DBKeepalive Database: ping
DEBUG [2012-05-22 13:01:15,740] DBKeepalive Database: ping
DEBUG [2012-05-22 13:02:15,753] DBKeepalive Database: ping
DEBUG [2012-05-22 13:03:15,766] DBKeepalive Database: ping
DEBUG [2012-05-22 13:04:15,780] DBKeepalive Database: ping
DEBUG [2012-05-22 13:05:15,794] DBKeepalive Database: ping
DEBUG [2012-05-22 13:06:15,808] DBKeepalive Database: ping
DEBUG [2012-05-22 13:07:15,816] DBKeepalive Database: ping
DEBUG [2012-05-22 13:08:15,829] DBKeepalive Database: ping
DEBUG [2012-05-22 13:09:15,843] DBKeepalive Database: ping
DEBUG [2012-05-22 13:10:15,856] DBKeepalive Database: ping
DEBUG [2012-05-22 13:11:15,870] DBKeepalive Database: ping
DEBUG [2012-05-22 13:12:15,883] DBKeepalive Database: ping

Help?
Back to top Go down
Xangis
Foundation Developer
avatar

Posts : 124
Join date : 2011-12-30
Location : Beaverton, OR

PostSubject: Re: Server startup errors: startup_instance.py ?   Tue 22 May - 17:21

Did you also get a bunch of messages about "processing new jar" when you started up?

Was the mysql connector in that list of jars? When you run start-multiverse.bat, what does it say for "JDBC is" near the beginning (around line 4)? And your Java version?

I've seen an error that looked something like that when I didn't have my MySQL JDBC connector path set right.
Back to top Go down
http://zetacentauri.com
theryn
Newbie
Newbie
avatar

Posts : 8
Join date : 2012-05-22
Location : Sydney, Australia

PostSubject: Re: Server startup errors: startup_instance.py ?   Tue 22 May - 17:32

Thanks for the quick response, Xangis! Smile

I got the "processing new jar" lines when I started, but I didn't memorize any of them. Wink

start-multiverse.bat says:
JDBC is c:\mysql-connector-java-5.0.8\mysql-connector-java-5.0.8\mysql-connector-java-5.0.8-bin.jar

(I created the folder, then unzipped in that folder, hence why it's in there twice!)

The error in the log is somewhere in mv_home/config/sampleworld/startup_instance.pl (line 15), but I know nothing about Python otherwise I'd investigate. I tried upgrading python from 2.6.x to the latest 2.7.3, but no change.

I also found the startup_instance.pl on the wiki (and some example code on the Instancing wiki page) and tried to tweak a couple of things, in case it was a simple syntax error. It was a long shot; if other people had the problem, they would have reported it by now.
Back to top Go down
Xangis
Foundation Developer
avatar

Posts : 124
Join date : 2011-12-30
Location : Beaverton, OR

PostSubject: Re: Server startup errors: startup_instance.py ?   Wed 23 May - 18:21

If the JDBC path in the properties file exactly matches what you have on disk I don't have any other ideas. Maybe someone with more MV experience will know...
Back to top Go down
http://zetacentauri.com
Delurin
Head of Platform Development


Posts : 424
Join date : 2011-08-03

PostSubject: Re: Server startup errors: startup_instance.py ?   Thu 24 May - 2:04

It looks like your error is related to the file name of your default instance defined in startup_instance.py
you need to open startup_instance.py and check that the path to the file name is correct
Back to top Go down
theryn
Newbie
Newbie
avatar

Posts : 8
Join date : 2012-05-22
Location : Sydney, Australia

PostSubject: Re: Server startup errors: startup_instance.py ?   Thu 24 May - 19:46

Thanks for your post, Delurin.

I used the startup_instance.py that came with the server files I downloaded the day of my first post (or the night before that).

Here is startup_instance.py (line 15 is the second line that begins with: rc = ):
Code:
from multiverse.server.plugins import *
from multiverse.server.objects import *
from multiverse.server.engine import *


template = Template("sampleworld template")
template.put(Namespace.INSTANCE, InstanceClient.TEMPL_WORLD_FILE_NAME, "$WORLD_DIR/$WORLD_NAME.mvw")
template.put(Namespace.INSTANCE, InstanceClient.TEMPL_INIT_SCRIPT_FILE_NAME, "$WORLD_DIR/instance_load.py")

rc = InstanceClient.registerInstanceTemplate(template)

overrideTemplate = Template()
overrideTemplate.put(Namespace.INSTANCE, InstanceClient.TEMPL_INSTANCE_NAME, "default")

rc = InstanceClient.createInstance("sampleworld template", overrideTemplate)
Log.debug("startup_instance.py: createInstance result=" + str(rc))



template = Template("bigbrother template")
template.put(Namespace.INSTANCE, InstanceClient.TEMPL_WORLD_FILE_NAME, "$WORLD_DIR/bigbrother.mvw")

rc = InstanceClient.registerInstanceTemplate(template)

overrideTemplate = Template("bigbrother")
overrideTemplate.put(Namespace.INSTANCE, InstanceClient.TEMPL_INSTANCE_NAME, "bigbrother")

rc = InstanceClient.createInstance("bigbrother template", overrideTemplate)
Log.debug("startup_instance.py: createInstance result=" + str(rc))



template = Template("frontier template")
template.put(Namespace.INSTANCE, InstanceClient.TEMPL_WORLD_FILE_NAME, "$WORLD_DIR/frontier.mvw")

rc = InstanceClient.registerInstanceTemplate(template)

overrideTemplate = Template("frontier")
overrideTemplate.put(Namespace.INSTANCE, InstanceClient.TEMPL_INSTANCE_NAME, "frontier")

rc = InstanceClient.createInstance("frontier template", overrideTemplate)
Log.debug("startup_instance.py: createInstance result=" + str(rc))


template = Template("video template")
template.put(Namespace.INSTANCE, InstanceClient.TEMPL_WORLD_FILE_NAME, "$WORLD_DIR/video.mvw")

rc = InstanceClient.registerInstanceTemplate(template)

overrideTemplate = Template("video")
overrideTemplate.put(Namespace.INSTANCE, InstanceClient.TEMPL_INSTANCE_NAME, "video")

rc = InstanceClient.createInstance("video template", overrideTemplate)
Log.debug("startup_instance.py: createInstance result=" + str(rc))

Engine.getPlugin("Instance").setPluginAvailable(True)

I tried replacing $WORLD_NAME with sampleworld, but that led to the same errors. A null pointer error suggests that either the "sampleworld template" or the overrideTemplate are the problem. Or perhaps the problem is WorldManager1 (see the error lines in the debug log in my previous post).

Or perhaps the problem is the step that normally follows the assigning of the world manager. Can someone post a copy of their mv_home/logs/sampleworld/instance.out from the point where it begins to execute startup_instance.pl? Make sure to remove any passwords or ip addresses from the log!

Thanks for the continued help. Smile
Back to top Go down
Delurin
Head of Platform Development


Posts : 424
Join date : 2011-08-03

PostSubject: Re: Server startup errors: startup_instance.py ?   Wed 30 May - 3:28

Most likely you need to make sure that this "$WORLD_DIR/$WORLD_NAME.mvw" is set to a valid path if you having a lot of trouble with it you can set it to an absolute path just make sure that there is a mvw file with a spawn marker in it and that there is a path to that file. You can get rid of the other templates. You also need to have markers in the mvw file that correspond to all of the markers in the instance_load.py or you can comment it that out to remove all of the npcs.

I was going to post my instance.out but it would probably confuse you more than anything since we have made significant modifications to the server.
Back to top Go down
theryn
Newbie
Newbie
avatar

Posts : 8
Join date : 2012-05-22
Location : Sydney, Australia

PostSubject: Re: Server startup errors: startup_instance.py ?   Wed 30 May - 20:58

Thanks for the continued help, Delurin!

Alas, none of those suggestions work. I've tried to look through as much of the code as I can read, but don't have experience in the right languages to contribute anything.

Unfortunately, Multiverse has just gone past my effort barrier, given that the server install files and the wiki instructions are obviously insufficient for me and my hardware setup. I will keep checking into the forum, and I might retry Multiverse again in another year or so, as I still believe it could be what I'm looking for.

Thanks to all for trying to help. Smile

For now, I'm uninstalling all Multiverse/MySQL/Java stuff and I'm off to try Realm Crafter and others. Wish me luck!
Back to top Go down
Xangis
Foundation Developer
avatar

Posts : 124
Join date : 2011-12-30
Location : Beaverton, OR

PostSubject: Re: Server startup errors: startup_instance.py ?   Thu 31 May - 4:12

I understand. It's a bit rough to get started with at the moment. Check back again in the future, it'll steadily be getting easier over time.
Back to top Go down
http://zetacentauri.com
Sponsored content




PostSubject: Re: Server startup errors: startup_instance.py ?   

Back to top Go down
 
Server startup errors: startup_instance.py ?
View previous topic View next topic Back to top 
Page 1 of 1
 Similar topics
-
» Server connection errors
» .^f2F-.Swemmei Recruting in server 1
» Lag playing in Taiwan server from Shanghai
» Proxy Server Taiwan: How To.
» WoW "Development" Server

Permissions in this forum:You cannot reply to topics in this forum
 :: Development :: Getting Started-
Jump to: