Hi all, i need help to finish my new server.

john smith · #1 05-11-2010, 12:30 PM

I compiled emu few days ago, now i can to see it (world of warland) in server list with the locked status and i can create a character but after this step when i try to enter in the world a message appear who say: "That zone is unavailable".

My account is configured with the 250 status but nothing to do, i can't pass the character select.

Plz, someone can help me?

Tabasco · #2 05-11-2010, 01:50 PM

What's your startup process?

What do you see when you run 'ps aux |grep eqlaunch' ?

john smith · #3 05-11-2010, 02:20 PM

To start the server i launch command ./world in my server directorie.

And the command result:

root@ks364142:/home/eqemu/server# ps aux |grep eqlaunch
root 27563 0.0 0.0 3016 764 pts/4 R+ 20:25 0:00 grep eqlaunch

Tabasco · #4 05-11-2010, 02:42 PM

In order to get a completely operable server running you need world as well as zones.

Try running './eqlaunch zone' after your world server is running.

Optionally, you can start ucs after that if you want to support SoF+ client friend lists and channels.

john smith · #5 05-11-2010, 02:52 PM

ok, result on ./eqlaunch zone:

root@ks364142:/home/eqemu/server# ./eqlaunch zone
[Debug] Starting Log: logs/eqemu_debug_28953.log
[Debug] [LAUNCHER__INIT] Loading server configuration..
[Debug] [COMMON__THREADS] Starting TCPConnectionLoop with thread ID -1213248624
[Debug] [LAUNCHER__INIT] Starting main loop...
[Debug] [NET__WORLD] Connected to World: localhost:9000
[Debug] [LAUNCHER__WORLD] World told us to start zone akanon.
[Debug] [LAUNCHER__STATUS] Starting zone akanon
[Debug] [LAUNCHER__STATUS] Zone akanon has been started.
[Debug] [LAUNCHER__STATUS] Waiting 20000 milliseconds before booting the second zone.
[Debug] [LAUNCHER__STATUS] Zone akanon has gone down. Restart timer started.
[Debug] [LAUNCHER__STATUS] Starting zone akanon
[Debug] [LAUNCHER__STATUS] Zone akanon has been started.
[Debug] [LAUNCHER__STATUS] Waiting 20000 milliseconds before booting the second zone.
[Debug] [LAUNCHER__STATUS] Zone akanon has gone down. Restart timer started.
[Debug] [LAUNCHER__STATUS] Starting zone akanon
[Debug] [LAUNCHER__STATUS] Zone akanon has been started.
[Debug] [LAUNCHER__STATUS] Waiting 20000 milliseconds before booting the second zone.
[Debug] [LAUNCHER__STATUS] Zone akanon has gone down. Re........

And on the server logs:

[Debug] [WORLD__CLIENT] Validating char creation info...
[Debug] [WORLD__CLIENT] Found 0 errors in character creation request
[Status] Start zone query: SELECT x,y,z,zone_id,bind_id FROM start_zones WHERE player_choice=1 AND player_class=11 AND player_deity=201 AND player_race=1

[Status] Found starting location in start_zones
[Debug] [WORLD__CLIENT] warland: Current location: qcat -427.00, 302.00, -38.22
[Debug] [WORLD__CLIENT] warland: Bind location: qcat -427.00, 302.00, -38.22
[Debug] [WORLD__CLIENT] warland: Character creation successful: Ondapixiso
[Debug] [WORLD__CLIENT] warland: Attempting autobootup of tutorialb (189:0)
[Debug] [WORLD__CLIENT_ERR] warland: No zoneserver available to boot up.
[Debug] [WORLD__LAUNCH] zone: akanon reported state STARTED (8 starts)
[Debug] [WORLD__LAUNCH] zone: akanon reported state STOPPED (8 starts)
[Debug] [WORLD__LAUNCH] zone: akanon reported state STARTED (9 starts)
[Debug] [WORLD__LAUNCH] zone: akanon reported state STOPPED (9 starts)
[Debug] [WORLD__LAUNCH] zone: akanon reported state STARTED (10 starts)
.............

But always message: that zone is una... :'(

Tabasco · #6 05-11-2010, 02:56 PM

What does your eqemu_config.xml look like?

Also, what's your launcher table in the database have in it?

john smith · #7 05-11-2010, 02:58 PM

<?xml version="1.0">
<server>
<world>
<shortname>warland</shortname>
<longname>World of Warland</longname>






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


<!!-- <locked/>-->
<unlocked/>


<tcp ip="localhost" port="9000" telnet="disable"/>


<key>some long random string</key>


<http port="9080" enabled="false" mimefile="mime.types" />
</world>


<chatserver>
<host>channels.eqemulator.net</host>
<port>7778</port>
</chatserver>


<mailserver>
<host>channels.eqemulator.net</host>
<port>7779</port>
</mailserver>

<zones>
<defaultstatus>20</defaultstatus>


<ports low="7000" high="7100"/>
</zones>


<database>
<host>localhost</host>
<port>3306</port>
<username>root</username>
<password>*******</password>
<db>eqemu</db>
</database>


<launcher>




</launcher>


<files>




</files>

<directories>



</directories>
</server>

Tabasco · #8 05-11-2010, 03:05 PM

Try fixing the <exe> section in your <launcher> config.
I use '<exe>./zone</exe>'

In my launcher table I have a single row, name=zone dynamics=5
When I launch it boots 5 dynamic zones.

I'm not honestly sure how the dynamic zones work though. It either means I can keep any 5 zones up at a time or that the zone server maintains 5 listeners for the purpose of booting new zones as they are needed.

john smith · #9 05-11-2010, 03:16 PM

Can you show me this part of your eqemu_config.xml plz?

Tabasco · #10 05-11-2010, 03:18 PM

<launcher>


<exe>./zone</exe> -->

</launcher>

john smith · #11 05-11-2010, 03:30 PM

Same logs and same problem after this modification.. :(

**Derision** · #12 05-11-2010, 03:31 PM

Quote:

Originally Posted by john smith

[Debug] [LAUNCHER__STATUS] Starting zone akanon
[Debug] [LAUNCHER__STATUS] Zone akanon has been started.
[Debug] [LAUNCHER__STATUS] Waiting 20000 milliseconds before booting the second zone.
[Debug] [LAUNCHER__STATUS] Zone akanon has gone down. Restart timer

Your zones are crashing. The most likely cause of this is because your database is not up to date with the version of the source you are using.

E.g. if you are using the latest PEQ database, which is compatible with Revision 1410 of the source, but you compile Rev 1478 (say) of the source, you should source in any non-optional .sql in utils/sql/svn with a number between 1411 and 1478.

The only two I see there that are mandatory are 1446_allowrest_required.sql and 1451_guilds.sql (assuming you are using the PEQ 1410 database),

john smith · #13 05-11-2010, 03:34 PM

i have this in my server log:

[Debug] [WORLD__CLIENT] New connection from 90.29.127.214:58965
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: First opcode 0x4dd0 did not match expected 0x2792
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: Tried patch 6.2_world, and it did not match.
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: First opcode 0x4dd0 did not match expected 0x2ec9
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: Tried patch 6.2_zone, and it did not match.
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: First opcode matched 0x4dd0 and length matched 464
[Debug] [NET__IDENTIFY] Identified stream 90.29.127.214:58965 with signature Titanium_world
[Debug] [WORLD__CLIENT] Checking inbound connection 90.29.127.214 against BannedIPs table
[Debug] [WORLD__CLIENT] Connection 90.29.127.214 PASSED banned IPs check. Processing connection.

Looks like problem with patch 6.2, can explain my problem?

**Derision** · #14 05-11-2010, 03:36 PM

Quote:

Originally Posted by john smith

i have this in my server log:

[Debug] [WORLD__CLIENT] New connection from 90.29.127.214:58965
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: First opcode 0x4dd0 did not match expected 0x2792
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: Tried patch 6.2_world, and it did not match.
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: First opcode 0x4dd0 did not match expected 0x2ec9
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: Tried patch 6.2_zone, and it did not match.
[Debug] [NET__IDENT_TRACE] 90.29.127.214:58965: First opcode matched 0x4dd0 and length matched 464
[Debug] [NET__IDENTIFY] Identified stream 90.29.127.214:58965 with signature Titanium_world
[Debug] [WORLD__CLIENT] Checking inbound connection 90.29.127.214 against BannedIPs table
[Debug] [WORLD__CLIENT] Connection 90.29.127.214 PASSED banned IPs check. Processing connection.

Looks like problem with patch 6.2, can explain my problem?

That is normal. The server is trying to identify which version of the EQ client you are using (6.2, Titanium, SoF, SoD, etc.). It checked for the 6.2 version first and didn't get a match, then it checked for Titanium and got a match and carried on as normal.

john smith · #15 05-11-2010, 05:13 PM

ok for the patch 6.2 thx for details.

I update my db with latest svn/sql and i redownload MAPS but i have exactly the same logs...