debian problem with eqlaunch
 

I have my debian server up and sourced (first time with linux so I'm still learning). When I try to log in from my windows machine the server shows as locked from the server select screen. Ive added the <unlocked></unlocked> to my eqemu_config.xml file and still nothing. Went into the HTTP manager and it shows unlocked. When I lock and unlock it from there it just gives me "boot_quest does not take any arguments.boot_quest does not take any arguments.boot_quest does not take any arguments." error in my terminal. I scanned around some posts here and compated my logs and I think I the problem may be with eqlaunch, but if it is I'm not sure how to fix it.

It appears to be in an endless loop and wont launch any dynamic zones.

when I ./start ther server i get this, which l think is normal.

if I need to provied anything else please lt me know.

Thank you.

Zone logs would be best, since it seems like they're infinitely crashing (never booting up far enough to be usable).

Here are all the logs in my logs folder. if what you asked for is somewhere else please let me know. Thanks for the quick response, I appreciate it.

---------------------------------------------

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.

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

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.

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.

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

and rebooting the box did nothing=/

sourced in the core updates...nothing =/

I have only ever used PEQ, and I know PEQ works fine. I am not sure what the state of AX is currently. Is there a particular reason you went with AX over PEQ?

It was the database I started with, Its worked fine on the 2 windows servers I've done. Angelox keeps it really up to date and Is able to run his database on Linux fine from what hes said. I think I may have just missed something with this linux install. This is my 3rd install attempt with linux and its the closest to working yet just cant log in lol. Im running MiniLogin with wine, maybe i forgot to bring in a file besides MiniLogin.exe and Opcodes.conf.