debian problem with eqlaunch

[trevius]

You are using an AX database it seems. AX sets it's launcher to "zones", not "zone" for some strange reason (why doesn't AX change it?)

You will either need to change the one in your database Launcher table, or the one in the ./start file you are running.

11097 [10.23. - 02:42:24] [WORLD__LAUNCH] Adding pending launcher 1
11097 [10.23. - 02:42:24] [WORLD__LAUNCH] Unknown launcher 'zone' connected. Disconnecting.

[Romell]

Thank you!
Is it the one i bold and underlined?

#!/bin/sh

#ulimit -c 99999999

rm -f .zone_shutdown
rm -f .world_shutdown

set -x

LNAME="zones" #launcher name
if [ "$1" = "test" ]; then
LNAME="test"
fi

P=`pwd`
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$P"

#make sure we have a place to log
mkdir -p logs 2>&1 > /dev/null

#clear out old logs, if both are stopped
if [ ! -e .lock-zones -a ! -e .lock-world ] ; then
for f in logs/eqemu_*.log
do
if [ "$f" = "logs/eqemu_commands_zone.log" ]; then
continue;
fi

rm -f $f
done
fi

#boot up world
if [ ! -e .lock-world ] ; then
touch .lock-world
# ./world 2>&1 > logs/world &
./persist_world 2>&1 > logs/world &
# wait for shared memory to load
sleep 15
fi

#start up the official launcher
if [ ! -e .lock-launcher ]; then
touch .lock-launcher
./eqlaunch $LNAME 2>&1 > logs/launcher &
fi

[Romell]

Ok i made the change above and It appears to be running and creating many more logs. however on my server select it shows 0 instead of locked, but keeps kicking me back to the login screen when i try to connect to the server.

[trevius]

You need to be sure that your server is running the same EQEmu code version that will match up with the database you are running. Or, if the DB you are running is older, you can run all of the required SQL in the change logs and in the SQL directory of the server code. If the DB and server code don't match, you will almost certainly have issues like getting kicked out, crashing, or even just weird stuff happening in game.

[Romell]

I'm running the 11-28 release of Angelox's databse and the source, I didn't run a core update because it was the same release as the full database. I can try and reboot my machine but im a little scared with linux, do i just ./stop and then reboot or is there a process that I need to know about? I've heard about the databse being corrupted in linux if its done improperly.

Thanks again

[Romell]

and rebooting the box did nothing=/

[Romell]

sourced in the core updates...nothing =/