15 réponses à ce sujet

[Jenna WSI]

Again, trying to work out issues with returning to box that collected dust for three years. All our dms, and I think every player, on login... has the 'this ip is banned' server message... but everyone is still logging in just fine. Any ideas?

[Jenna WSI]

Okay, think I figured what this is... but not how to solve it. I think it isn't calling the database. Not sure how to fix that, because this isn't my sort of work... but there's no one else to do it.

[Failed.Bard]

What sort of database is it running off of? If it's an SQL/SQLite, is it properly configured on this system?

Databases are one of my weaker areas script wise, but that information might let others give some specific advice/help on it.

[Jenna WSI]

I think so. Someone else had set it up on the box. I looked in the documentation and checked the files that specify login/location but not sure if I did it right. In any case, that didn't work.

[Failed.Bard]

This is a scripted check inside the server itself, not related to the automatic one that uses the ini file?
That it says they're banned, but doesn't boot them is odd. Maybe the check to send that message just got inverted, checking for false for the message instead of true.

[Jenna WSI]

Oh, I think I forgot to mention that half our scripts aren't working now because nothing is connecting to the database at all? Also I don't want it to work if it's trying to boot every dm and player... I suspect it's all because of the database issue.

Modifié par Jenna WSI, 25 août 2011 - 04:06 .

[Failed.Bard]

Is the new NWN install on this machine to the same drive and directory path as the old install? It may be looking for the database in the wrong location.

[Jenna WSI]

We set up this box originally as our first host, then moved the module later to a different host... now, three years later, back to the original box. Which is why I don't understand why it doesn't connect. Working in the admin account of Ubuntu on the same nwn installation that was there when we started the server up for the first time.

[Alex Warren]

You can check db type in nwnx.ini ([ODBC2] section; source)

Could you post odbc plugin log here? (nwnx_odbc.txt) It may contain some useful info

[Jenna WSI]

nwnx_odbc.txt

Error while connecting to the database: Can't connect to the local mySQL server through socket '/var/run/mysql.sock' (2)

Edit: Heh, great minds think alike Alex!
ODB Source is mysql

Modifié par Jenna WSI, 25 août 2011 - 04:39 .

[Alex Warren]

OK, so it's mySQL configuration issue :/
Sorry, never configured mySQL server on Linux

[Jenna WSI]

Okay... I'll try and find someone to access the box and fix it. I have no idea either.

Modifié par Jenna WSI, 25 août 2011 - 04:45 .

[Alex Warren]

There can be two reasons why ODBC can't connect to database:
1. Connection information is wrong (nwnx.ini - wrong server, user, pwd?)
2. Database is not setup correctly
How did you migrate the db form one server to another?

[Jenna WSI]

Well, I have no idea how to fix either one...

[Skildron]

Check if the sock file in question is there at all - on my system, it is named mysqld.sock - on letter 'd' more than in your error message. If you quoted the message correctly, then perhaps the sock file has another name and you have to change the configuration of nwnx. Otherwise, if the sock file is not present, check if mysql is running at all: at a command line type:

ps -Af|grep -i [m]ysql

and check the output.

Bear in mind, though, that I know nwn and Linux very well but don't know much about nwnx and persistent world setups.

HTH
Greetings
Skildron

Modifié par Skildron, 28 août 2011 - 10:17 .

[Calvinthesneak]

It's the same deal for PW setup Skil. Also check the location of your mySQL installation, sometimes they move about a bit on different ubuntu versions. The mysqld sounds familiar to me, but it's been a few months since I had a linux box running.