Author Topic: Dedicated Server - Mission won't run/ Server won't auth.  (Read 2738 times)

Server is running on linux via wine (May be the cause, but was working before the latest revision)
Have tried reloading the missions/ forcing auth to no avail

Code: [Select]
Starting server authentication...

*** CREATING MISSION
*** Stage 1 create
136 environmental resource files found
Regenerating file manifest
Got 1429 items in manifest, 0 files hashed

ERROR: WebCom_PostServer() - mission is not running
BackTrace: ->[TeledoorPackage]onStart->[TeledoorPackage]serverPart2->[TeledoorPackage]dedicatedKeyCheck->[TeledoorPackage]initDedicated->[TeledoorPackage]createServer->createMission->onMissionLoaded->WebCom_PostServer

Engine initialized...
Dedicated server is now running.

>Auth
Starting server authentication...
>Webcom
Can't post to master yet, must auth...
Can't post to master yet, must auth...
Syntax error in input.
eval error >> auth_Init_Server()
BackTrace:
>Reload mission
Starting server authentication...
*** ENDING MISSION

*** CREATING MISSION
*** Stage 1 create
registerOutputEvent() - Output event "setBotType" already registered on class fxDTSBrick - overwriting.
registerOutputEvent() - Output event "PlayGesture" already registered on class Bot - overwriting.
registerOutputEvent() - Output event "SetWanderDistance" already registered on class Bot - overwriting.
registerOutputEvent() - Output event "SetSearchRadius" already registered on class Bot - overwriting.
registerOutputEvent() - Output event "SetIdleBehavior" already registered on class Bot - overwriting.
Regenerating file manifest
Got 1429 items in manifest, 0 files hashed

ERROR: WebCom_PostServer() - mission is not running
BackTrace: ->createMission->onMissionLoaded->WebCom_PostServer

Dedicated server is now running.

if anyone has any suggestions/fixes please let me know.

Thanks.

Is it on a headless server or do you have a desktop environment/X server?

Was running headless, appears to auth on a desktop environment. But i would ideally like to run it headless. any solutions towards this approach?

Lugnut and I have spent hours trying to figure this out. We still didn't get it.

Well thats a pain, any idea whats causing it to be unable to auth when headless?

Well thats a pain, any idea whats causing it to be unable to auth when headless?

Read this: http://forum.blockland.us/index.php?topic=252569.msg7335259#msg7335259

Let us know if you figure anything out.

Was running headless, appears to auth on a desktop environment. But i would ideally like to run it headless. any solutions towards this approach?
loving hell are you srs
yeah, let us know.

Well the strange thing is that when running on the desktop environment; using the screen command to load the blockland server, it still opens a new console, rendering the screen shell useless.

This would explain the drivel about display not been set at the beginning, and many this inability to open it is the cause?

Lugnut has it working on one user while the rest of his users do not work. Mine does not work. This led us to think that it has to do with some user-specific config.

My results suggest otherwise. As under the same user it doesn't work under a headless but does on a desktop environment. Both on the same user.

Right, when there's a desktop environment it always works.

However, when it's headless it only works on certain users. We've compared the users' home directories and can't find anything different that would be significant.

Well how odd, is there any difference in wine/screen config?

Nope. Screen doesn't matter though because the same problem occurs if you run it without screen.

Are you using the script I posted?

thats the current method i am doing. I can get it to run 'headless' via a python script but it renders input unavailable. And i can't get it to work properly in a screen environment.

i actually have it working under my personal user and under root now


i have no loving idea what i did - was loving around with the debugging settings (greek knows the specifics, the WINEDEBUG thing) and i decided to try running as root and it just worked
now both root and my personal user work on any copy of blockland on my computer, so it's definitely user specific, not blockland-copy-specific.