New Server Setup issues

[nannite]

Hello all
I started playing on a private eqemu server and I'm enjoying it so much I thought I'd try setting up my own server.

I'm using a Ubuntu 12.04 machine and followed the outdated linux installation guide and thought I got most of it working but I don't think it's completely starting up.

The world, queryserv, and eqlaunch processes all startup and stay running, but most of the logs just say:

[01.29. - 19:32:26] Starting Log: logs/eqemu_zone_30186.log
[01.29. - 19:32:26] Using database 'eq' at 127.0.0.1:3306

and that's it and the server never shows up on the public login server.

I've been searching through the forums, and trying different setup steps as I find them, but I haven't found anything to give me more debugging information and more steps to try. There aren't any build errors that I see and no errors in the logs.

Anyone know any more steps I could try?

I'm using this start script: http://www.eqemulator.org/forums/sho...r+start+script

and my eqemu_config.xml just have my server short and long name, and the database information defined.

Not sure what to try next...

[joligario]

It wouldn't hurt to post your config (password omitted of course). Also, you can turn on logging in cmake interactive mode to get a better picture of what is happening.

[nannite]

Thanks for the reply, here is my config:

<?xml version="1.0"?>
<server>
<world>
<shortname>Shadow Keep</shortname>
<longname>The Shadow Keep Server</longname>

<loginserver>
<host>eqemulator.net</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver>
</world>

<!-- Database configuration, replaces db.ini. Defaults shown -->
<database>
<host>127.0.0.1</host>
<port>3306</port>
<username>eqemu_user</username>
<password>xxxx</password>
<db>eq</db>
</database>

<qsdatabase>
<host>127.0.0.1</host>
<port>3306</port>
<username>eqemu_user</username>
<password>xxxx</password>
<db>eq</db>
</qsdatabase>

</server>

I'll take a look at the CMake options.

Thanks!

[Kingly_Krab]

Someone else had a similar issue, the new server compiles have less logging, meaning it doesn't show the entire process of the server turning on, could you turn it on and give it 5 minutes to see if it ever shows up on the list?

[nannite]

Just for grins I deleted my source directory and pulled the latest version from git to start fresh. But now I'm getting a build error...

/home/eqemu/source/EQEmuServer/zone/spawngroup.cpp: In member function ‘uint32 SpawnGroup::GetNPCType()’:
/home/eqemu/source/EQEmuServer/zone/spawngroup.cpp:54:77: error: cast from ‘SpawnGroup*’ to ‘uint32 {aka unsigned int}’ loses precision [-fpermissive]
make[2]: *** [zone/CMakeFiles/zone.dir/spawngroup.cpp.o] Error 1
make[1]: *** [zone/CMakeFiles/zone.dir/all] Error 2
make: *** [all] Error 2

[nannite]

Hmm looks like the issue goes away if I don't turn on lua support. Got it compiled it again.

[demonstar55]

Turn your debug down to 5 (higher kind of gets messy) if you want them. And make sure you turn on logging

That would be in interactive mode

Variable Name: EQEMU_DISABLE_LOGSYS
Description: Disable Logging INI System
Current Value: ON
New Value (Enter to keep current value):

You would want to set that to OFF then it will enable logging stuff.

If you're using the PEQ quest system I would highly recommend turning Lua and Perl on since they use both.

[nannite]

I let the server run over night but still didn't show up in the list this morning.

I'm rebuilding the server with the option EQEMU_DISABLE_LOGSYS turned off now.

Once I get it the server working I'll try compiling with Lua turned on, but I believe that's what was giving me the compile error last night.

[nannite]

Ok user error as usual. I had originally attempted to get the server up and running with minilogin so I still had the record in the variables table. That's why it wasn't showing up on the server list. Deleted that record and now the server shows up in the list...

Now I'll try and get Lua turned on and search around to try and figure out how I can connect to the server on my network when I'm trying to connect from inside my network.