Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error trying to start login server #16

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 10 comments
Open

Error trying to start login server #16

GoogleCodeExporter opened this issue Mar 16, 2015 · 10 comments
Labels
auto-migrated Priority-Low Type-Other

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Compile server from latest SVN
2. attempt to start server using "login_server --nodaemon"

What is the expected output? What do you see instead?

Expected:
[2010:04:18: 16:46:42.515]: Reading quests...
[2010:04:18: 16:46:42.515]: Connecting to the database...
[2010:04:18: 16:46:42.515]: Opening Dreamcast ports for connections.
[2010:04:18: 16:46:42.515]: Opening PSO for PC ports for connections.
[2010:04:18: 16:46:42.515]: Opening PSO for Gamecube ports for connections.

What I see:
[2012:08:28: 00:31:50.864]: Reading quests...
[2012:08:28: 00:31:50.864]: Couldn't open param/param_files.txt

What version of the product are you using? On what operating system?

Latest SVN. Cygwin (latest ver.) on Windows XP

Please provide any additional information below.

To the best of my knowledge, all XML files and databases are setup correctly. 
I'm able to start shipgate and ship_server successfully (it would seem). Is the 
login server even required to run sylverant?

Original issue reported on code.google.com by gumbyand...@gmail.com on 28 Aug 2012 at 12:41
@GoogleCodeExporter
Copy link
Author 

This isn't really a bug, but rather a documentation issue.  The file it is 
referring to is needed to support Blue Burst, and is just one of many different 
files that are needed for it. I've been pretty lax in documentation stuff, 
mainly because I'm usually the only one that actually tries to run the whole 
suite of programs.

As for whether or not login_server is needed, if you're trying to set up a 
whole server infrastructure, then yes it is. login_server is so named because 
it is the first piece that the users playing the game will come in contact 
with. It is the piece that actually gives the initial ship list and offers up 
downloadable quests.

Original comment by bluecrab on 28 Aug 2012 at 1:58

  • Changed state: Accepted
  • Added labels: Type-Other, Priority-Low
  • Removed labels: Type-Defect, Priority-Medium

@GoogleCodeExporter
Copy link
Author 

Is there a quick and dirty way to disable BB support on the login server, 
avoiding the check for BB related files?

Original comment by gumbyand...@gmail.com on 28 Aug 2012 at 5:52

@GoogleCodeExporter
Copy link
Author 

There is not, at least not without changing the code itself. I don't know what 
lines would need to be changed at the moment either.

Original comment by bluecrab on 28 Aug 2012 at 6:35

@GoogleCodeExporter
Copy link
Author 

Howdy BlueCrab,

I was wondering if you could touch base with me regarding which files I would 
need outside of the initial sylverant install to get the server up and running. 
I am too getting this error:


/usr/local/bin/login_server --nodaemon
[2012:09:19: 22:18:41.481]: Reading quests...
[2012:09:19: 22:18:41.482]: Couldn't open param/param_files.txt

Original comment by kotor...@gmail.com on 19 Sep 2012 at 10:21

@GoogleCodeExporter
Copy link
Author 

Lets see... Here's the list of Blue Burst-related files that need to be loaded:

In /usr/local/share/sylverant/blueburst:
ItemPT.gsl
default_HUcaseal.nsc
default_RAcast.nsc
default_FOmar.nsc
default_HUcast.nsc
default_RAmar.nsc
default_FOmarl.nsc
default_HUmar.nsc
default_RAmarl.nsc
default_FOnewearl.nsc
default_HUnewearl.nsc
default_FOnewm.nsc  
default_RAcaseal.nsc

And, in /usr/local/share/sylverant/blueburst/param:
BattleParamEntry.dat    
BattleParamEntry_on.dat
BattleParamEntry_ep4.dat
ItemMagEdit.prs
BattleParamEntry_ep4_on.dat
ItemPMT.prs
BattleParamEntry_lab.dat
PlyLevelTbl.prs
BattleParamEntry_lab_on.dat

The .nsc files are the default starting character data for Blue Burst and are 
the same as those provided by Fuzziqer's newserv. The rest of the files are all 
the item/battle parameter data for Blue Burst. Note that as of r659, the 
param_files.txt file is gone (all it was was a list of the files in the 
blueburst/param directory).

Original comment by bluecrab on 21 Sep 2012 at 6:27

@GoogleCodeExporter
Copy link
Author 

Wow thanks for that info BlueCrab, I seem to have everything in order now 
except one thing. Fuzzy's server, newserv, seems to have a different naming 
convention for the default_*.nsc files. Sylverant is looking for 
default_<CLASS>.nsc while fuzzy's uses 'player_class_<NUM>.nsc'

Is it safe to simply rename those files to your format? Do you have a 
recommended translation scheme?
Example:
player_class_0.nsc -> default_HUcaseal.nsc
player_class_1.nsc -> default_RAcast.nsc

Those are probably wrong, I'm just looking for some advice on howto get the 
correct files that Sylverant is looking for.

Thanks Again for your previous remark!

Original comment by kotor...@gmail.com on 26 Sep 2012 at 1:46

@GoogleCodeExporter
Copy link
Author 

Think I just figured it out, I simply renamed the files in the order that 
Sylverant was accessing them:

[2012:09:26: 01:57:33.786]: Loading default character file: default_HUmar.nsc       0
[2012:09:26: 01:57:33.786]: Loading default character file: 
default_HUnewearl.nsc   1
[2012:09:26: 01:57:33.786]: Loading default character file: 
default_HUcast.nsc      2
[2012:09:26: 01:57:33.786]: Loading default character file: default_RAmar.nsc       3
[2012:09:26: 01:57:33.786]: Loading default character file: 
default_RAcast.nsc      4
[2012:09:26: 01:57:33.786]: Loading default character file: 
default_RAcaseal.nsc    5
[2012:09:26: 01:57:33.786]: Loading default character file: 
default_FOmarl.nsc      6
[2012:09:26: 01:57:33.786]: Loading default character file: 
default_FOnewm.nsc      7
[2012:09:26: 01:57:33.787]: Loading default character file: 
default_FOnewearl.nsc   8
[2012:09:26: 01:57:33.787]: Loading default character file: 
default_HUcaseal.nsc    9
[2012:09:26: 01:57:33.787]: Loading default character file: 
default_FOmar.nsc       10
[2012:09:26: 01:57:33.787]: Loading default character file: 
default_RAmarl.nsc      11




Now the only issue that remains is the shipgate. As you can see below it does 
attempt to start, however it errors out upon clearing existing online_ships. 
Should my database already contain entries in pso.ship_data ?

$ ./shipgate_start.sh 
[2012:09:26: 02:01:37.362]: Generating Diffie-Hellman parameters...
This may take a little while.
[2012:09:26: 02:01:37.928]: Done!
[2012:09:26: 02:01:37.929]: Connecting to the database...
[2012:09:26: 02:01:37.933]: Clearing online_ships...
[2012:09:26: 02:01:37.934]: Error clearing online_ships

Original comment by kotor...@gmail.com on 26 Sep 2012 at 2:04

@GoogleCodeExporter
Copy link
Author 

Well, it shouldn't run into problems clearing online_ships regardless of 
whether or not anything's in ship_data. You do need to have all the tables in 
the database created before running the shipgate, however.

Original comment by bluecrab on 26 Sep 2012 at 3:02

@GoogleCodeExporter
Copy link
Author 

Thats what I thought as well. The table certainly exists.

$ mysql pso -e "SELECT * from ship_data"
+-----+-----------+-------------+------+----------------------+
| idx | main_menu | ship_number | memo | sha1_fingerprint     |
+-----+-----------+-------------+------+----------------------+
|   0 |         1 |           0 |      | �-�l�YB��K�.>uȸ        |
+-----+-----------+-------------+------+----------------------+

## Function that is causing the fail ##

debug(DBG_LOG, "Clearing online ships...\n");
if(sylverant_db_query(&conn, "DELETE FROM online_ships"))
{
    debug(DBG_ERROR, "Error clearing online ships\n");
    exit(1);
}


Should the query be 'DELETE FROM online_ships' or 'DELETE * FROM online_ships', 
its quite odd that this fails, if I startup the ship server, it definitely 
connects to the database.

Here is my working copy of ship_config.xml, I don't see where the point of 
failure is here.

## ship_config.xml ##
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE ships PUBLIC "-//Sylverant//DTD Ship Configuration 1.11//EN"
  "http://sylverant.net/dtd/ship_config1.11/ship_config.dtd">

<ships>
    <shipgate ip="127.0.0.1" port="3455" ca="" />
    <ship name="KShip" blocks="2" key="sylverant-key.pem" gms="kserv_gms.xml" gmonly="false" cert="sylverant-cert.pem" >
        <net port="3480" ip="56.56.65.65" />
    <itempt v2="config/ItemPT.afs" v3="config/ItemPT.gsl" />
    <bbparam dir="blueburst/param" />
    <bbmaps dir="blueburst/map" />
        <motd file="motd.txt" />
    <versions v1="true" v2="true" ep3="true" bb="true" />
    </ship>
</ships>

Original comment by kotor...@gmail.com on 26 Sep 2012 at 4:02

@GoogleCodeExporter
Copy link
Author 

'DELETE * from online_ships'  is not valid SQL syntax. The query is correct as 
it stands in the code.

I also know it all works just fine in my case regardless of what is in the 
online_ships table. I'm not sure why it wouldn't work on your end. Perhaps try 
sticking something in the online_ships table (even if its just a fake entry) 
and see if it still fails then?

Anyway, I think it would probably be a good idea to take this discussion 
elsewhere, as it really isn't related to this particular bug report at this 
point anymore. If you have a chance, stop by my IRC channel sometime, and I can 
try to help you figure out what's going on there... The channel is #ljsdcdev on 
chat.freenode.net .

Original comment by bluecrab on 26 Sep 2012 at 4:09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Low Type-Other
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter