"Not Ready" from Test Module - Initially setting u

[MrMeAtus]

I have religiously followed the instructions posted on www.nwnx.org and used all of the latest software (as of yesterday).

1. Installed MySQL database server
2. Installed NWNX MySQL Add-on
3. Installed APS/NWNX
4. Installed & launched MySQL as a Windows Service
5. Set-up Root & User accounts/passwords
6. Created nwnuser account
7. Created the nwn server & pwdata table
8. Installed APS/NWNX to nwn directory
9. Erf-ed aps2.erf
10. Added aps_onload to the OnModuleLoad event

I then launched everything, and ran the aps_demo.mod.

HERE IS MY PROBLEM:

All of the "signs" within the module seem to work correctly with the exception of the first one ... that should say "APS READY"

Instead it says APS NOT READY.

Browsing through the new APS scripts in my module, I noticed the aps_ready script which should relate to this, but doesn't seem to be used (not called by an event in OnModuleLoad that I can see.

What am I doing wrong?

It seems I have missed a step ... please assist.

Also, what are my next steps?
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[MrMeAtus]

I should add that I commented the SQLite section and uncommented the MySQL section in the nwnx.ini as below:

- - - - - - -

[NWNX]
ServerPort = 5121
ModuleName = "aps_demo"
WatchdogProcess = yes
UpdateIntervalProcess = 5
WatchdogGamespy = no
UpdateIntervalGamespy = 20
GamespyRetries = 5
OldGamespyProtocol = no
RestartDelay = 5

[ODBC2]
; Log file
MaxLogSize = 512 ; in KByte
LogLevel = 2 ; 0=nothing, 1=only errors, 2=everything

; Use these two settings for the SQLite internal database
; MUST COMMENT OUT FOR mySQL full
;source = sqlite
;file = sqlite.db

; Use these two settings for ODBC connections
;source = odbc
;dsn = nwn

; Use these five settings for MySQL connections
;source = mysql
;server = localhost
;user = nwn
;pwd = nwn
;db = nwn

;WOS MySQL connections
source = mysql
server = localhost
user = nwnuser
pwd = nwnuser
db = nwn

; Set hookscorco to false if you want to disable hooking of
; StoreCampaignObject and RetrieveCampaignObject entirely
hookscorco = true

[PROFILER]
MaxLogSize = 512 ; in KByte
LogLevel = 1 ; 1=overall statistics, 2=full script callstack

- - - - - - -

Any comments of changes in this file?
Of course, it is in my nwn root directory.
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[Papillon]

aps_ready ? This script does not exist in the windows distribution, but that is what you seem to be installing NWNX on. Did you by chance grab the linux aps2.erf ? The original aps_demo.mod does not check whether APS is ready or not and thus displays no such warning message.
_________________
Papillon

[MrMeAtus]

I hope that is the solution as it will mean I haven't messed up the configuration, etc.

I will re-DL the ODBC components (with aps_demo.mod) to ensure I did not grab the Linux version.

To confirm, for Windows XP I should download:

nwnx_odbc2_0924.zip

Please let me know if this is wrong.
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[MrMeAtus]

Another question:

How do I know the connection is working from the aps_demo.mod?

The signs give me positive feedback (although the pull data sign pulls the following -------------------------------------). Within the MySQL interface, I see the tables, but no additional data is written (meaning the tables where created).

How do I know it is working?
What would you suggest as next steps?

I am at the point where I can really leverage some of the work done already, so please steer me in the correct direction. What is the most compliant system? (HCR, etc.)
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[Anatida]

In OUR Mod, if there is a connection from the MOD to the DB then everytime you launch the NWNx + NWNServer the PWData table should at least have the current date/month/year/time etc. I can't swear that this is not some function my main scripter added though, as he set up all the APS/NWNx stuff.

[Papillon]

First, you downloaded the correct plugin.

[MrMeAtus]

This may sound really silly, but I don't seem to have a log file even though it says it is logging at the command line. Where would this normally reside?
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[JeroenB]

Probably in the log0 sub-directory.If it isn't there please post the contents of nwnx.txt.

[MrMeAtus]

The NWNX.TXT contents:

NWN Extender V.2.6.1
(c) 2005 by Ingmar Stieger (Papillon) and Jeroen Broekhuizen
visit us at http://www.nwnx.org

* Loading plugins...
* An error occured during OnCreate of odbc
* NWNX2 activated.
* NWNX2 shutting down...
* NWNX2 shutdown successfull.

I spent several hours testing and came up with the following conclusions:

MySQL seems to be working correctly on its own. From the command line, I can add data, rows, tables, etc.

From NWN, it is not as successful. Running the aps_demo does not seem successful although creating a table, adding, and removing data seem to be successful in game. A closer inspection of the scripts within the demo show the statements seem to fire without checking the success of the connection to mySQL. I believe mySQL and nwnx are not connecting at all.

1. After clicking placard 1 in game, a quick check of the mySQL database shows no new table creation
2. Placard 2 in game has the same result - no data is written directly into mySQL (verified at the command line).
3. Placard 3 in game lags momentarily as it tries to resolve the connection only to deliver an error message in game. No data is returned from mySQL.

Note: I did alter the scripts in game by commenting the SQLite section and uncommenting the mySQL section.

A couple of points I do not understand relate to the connection between mySQL and NWN.

1. There do not seem to be in date stamps within the log (see above) so I cannot tell if the server stops upon module open or upon my clicking one of the placards.
2. The Windows service seems to be tempermental. It does not seem to start from the Services Screen, although I can start it at the command line. Additionally, the service seems to have the following path which deviates from the installation guide on your website:

Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 4.1/"

I am only trying to guess at potential errors ... at this point, I have no idea why there seems to be no working connection between NWNX & mySQL.

Please assist.
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[DarkstarsDad]

did you set the drivers in windows for the odbc? and install the drivers?
_________________
Just because you think you can't. Is the best reason to try it anyway.

[MrMeAtus]

Please clarify that. I have ODBC in Windows/Administration.

I have not installed anything beyond:

mySQL Database Server 4.1
MySQL Control Panel

NWNX:
nwnx_261.zip
nwnx_odbc2_0924.zip

Based upon the tutorial and comments within this forum, that should be enough? If not, someone point me to the correct ODBC plug-in (with link if possible )

Regards
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[MrMeAtus]

*BUMP*

Someone please assist me. I am still trying to understand why there is no connection between mySQL & NWNX
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore

[JeroenB]

Could you list your contents of the configuration file. Basically you don't need the ODBC driver if you are using MySQL. So, that shouldn't be the problem.

[MrMeAtus]

Here is MY.CNF:

#
# C:\MY.CNF
# "C:\Program Files\mysql\MySQL Server 4.1\bin\mysqld" --defaults-file="C:\MY.CNF" MySQL
#
# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /usr/local/var) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password=
port= 3306
socket= /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port= 3306
socket= /tmp/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
myisam_sort_buffer_size = 8M

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking

# Replication Master Server (default)
# binary logging is required for replication
log-bin

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1

# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin

# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/var/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/var/
#innodb_log_arch_dir = /usr/local/var/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld]
basedir=C:/Program Files/mysql/MySQL Server 4.1/
datadir=C:/Program Files/mysql/MySQL Server 4.1/data/
#basedir=C:\mysql\
#datadir=C:\mysql\data\

# WOS Logging (added by MrMeAtus)
log-long-format
log=mysql_logfile.txt

[WinMySQLAdmin]
Server=C:/Program Files/mysql/MySQL Server 4.1/bin/mysqld-max-nt.exe
user=root
password=abcd

- - - - - - - - -
And my NWNX.INI:

; NWNX2 configuration file
; These are the default values for NWNX2. Values specified on the command
; line take precedence.

[NWNX]
ServerPort = 5121
ModuleName = "aps_demo"
WatchdogProcess = yes
UpdateIntervalProcess = 5
WatchdogGamespy = no
UpdateIntervalGamespy = 20
GamespyRetries = 5
OldGamespyProtocol = no
RestartDelay = 5

[ODBC2]
; Log file
MaxLogSize = 512 ; in KByte
LogLevel = 2 ; 0=nothing, 1=only errors, 2=everything

; Use these two settings for the SQLite internal database
; MUST COMMENT OUT FOR mySQL full
;source = sqlite
;file = sqlite.db

; Use these two settings for ODBC connections
;source = odbc
;dsn = nwn

; Use these five settings for MySQL connections
;source = mysql
;server = localhost
;user = nwn
;pwd = nwn
;db = nwn

;WOS MySQL connections
source = mysql
server = localhost
user = nwnuser
pwd = nwnuser
db = nwn

; Set hookscorco to false if you want to disable hooking of
; StoreCampaignObject and RetrieveCampaignObject entirely
hookscorco = true

[PROFILER]
MaxLogSize = 512 ; in KByte
LogLevel = 1 ; 1=overall statistics, 2=full script callstack
_________________
"I love the smell of napalm in the morning. It smells like... victory."
Lieutenant Colonel Bill Kilgore