» Find Revision
L2J Revision 4668:
L2JDP Revision 8058M:
i have a strange error on my GS console what that means and what can i do?
tnx for understanding
ERROR1
Code: Select all
Exception in thread "GeneralSTPool-1" java.lang.NullPointerExceptionException in thread "GeneralSTPool-1" java.lang.NullPointerExceptionException in thread "GeneralSTPool-9" java.lang.NullPointerExceptionException in thread "GeneralSTPool-5" java.lang.NullPointerExceptionException in thread "GeneralSTPool-7" java.lang.NullPointerExceptionException in thread "GeneralSTPool-9" java.lang.NullPointerExceptionException in thread "GeneralSTPool-7" java.lang.NullPointerExceptionException in thread "GeneralSTPool-8" java.lang.NullPointerExceptionException in thread "GeneralSTPool-11" java.lang.NullPointerExceptionException in thread "GeneralSTPool-12" java.lang.NullPointerExceptionException in thread "GeneralSTPool-12" java.lang.NullPointerExceptionException in thread "GeneralSTPool-8" java.lang.NullPointerExceptionException in thread "GeneralSTPool-8" java.lang.NullPointerExceptionException in thread "GeneralSTPool-4" java.lang.NullPointerExceptionException in thread "GeneralSTPool-3" java.lang.NullPointerExceptionERROR2
Code: Select all
Client: [Character: DavyJones[268470833] - Account: baffo3 - IP: 87.12.247.242] - Failed running: [C] 04 Action - L2J Server Version: 4668 - DP Revision: 8058M ; nulljava.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerException java.lang.NullPointerExceptionserver configuration:
Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz, 8 cores
8g RAM DDR3
OS: debian 6.0 x64
Startup config:
Code: Select all
#!/bin/bash # exit codes of GameServer:# 0 normal shutdown# 2 reboot attempt while :; do [ -f log/java0.log.0 ] && mv log/java0.log.0 "log/`date +%Y-%m-%d_%H-%M-%S`_java.log" [ -f log/stdout.log ] && mv log/stdout.log "log/`date +%Y-%m-%d_%H-%M-%S`_stdout.log" java -server -Djava.util.logging.manager=com.l2jserver.util.L2LogManager -Xms3g -Xmx3g -cp ./../libs/*:l2jserver.jar com.l2jserver.gameserver.GameServer > log/stdout.log 2>&1 [ $? -ne 2 ] && break# /etc/init.d/mysql restart sleep 10done Thread config:
Code: Select all
# ---------------------------------------------------------------------------# Thread Configuration# ---------------------------------------------------------------------------# Extreme caution should be here, set to defaults if you do not know what you are doing.# These could possibly hurt your servers performance or improve it depending on your server's configuration, size, and other factors.# Default: 10ThreadPoolSizeEffects = 10 # Default: 13ThreadPoolSizeGeneral = 13 # Default: 2UrgentPacketThreadCoreSize = 2 # Default: 4GeneralPacketThreadCoreSize = 4 # Default: 4GeneralThreadCoreSize = 4 # Default: 6AiMaxThread = 6Code: Select all
## The MySQL database server configuration file.## You can copy this to one of:# - "/etc/mysql/my.cnf" to set global options,# - "~/.my.cnf" to set user-specific options.# # One can use all long options that the program supports.# Run program with --help to get a list of available options and with# --print-defaults to see which it would actually understand and use.## For explanations see# http://dev.mysql.com/doc/mysql/en/server-system-variables.html # This will be passed to all mysql clients# It has been reported that passwords should be enclosed with ticks/quotes# escpecially if they contain "#" chars...# Remember to edit /etc/mysql/debian.cnf when changing the socket location.[client]port = 3306socket = /var/run/mysqld/mysqld.sock # Here is entries for some specific programs# The following values assume you have at least 32M ram # This was formally known as [safe_mysqld]. Both versions are currently parsed.[mysqld_safe]socket = /var/run/mysqld/mysqld.socknice = 0 [mysqld]## * Basic Settings#user = mysqlpid-file = /var/run/mysqld/mysqld.pidsocket = /var/run/mysqld/mysqld.sockport = 3306basedir = /usrdatadir = /database/mysqltmpdir = /tmplanguage = /usr/share/mysql/englishskip-external-locking## Instead of skip-networking the default is now to listen only on# localhost which is more compatible and is not less secure.#bind-address = 127.0.0.1## * Fine Tuning#key_buffer = 16Mmax_allowed_packet = 16Mthread_stack = 192Kthread_cache_size = 8# This replaces the startup script and checks MyISAM tables if needed# the first time they are touchedmyisam-recover = BACKUP#max_connections = 100#table_cache = 64#thread_concurrency = 10## * Query Cache Configuration#query_cache_limit = 1Mquery_cache_size = 1M## * Logging and Replication## Both location gets rotated by the cronjob.# Be aware that this log type is a performance killer.# As of 5.1 you can enable the log at runtime!#general_log_file = /var/log/mysql/mysql.log#general_log = 1## Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.## Here you can see queries with especially long duration#log_slow_queries = /var/log/mysql/mysql-slow.log#long_query_time = 2#log-queries-not-using-indexes## The following can be used as easy to replay backup logs or for replication.# note: if you are setting up a replication slave, see README.Debian about# other settings you may need to change.#server-id = 1#log_bin = /var/log/mysql/mysql-bin.logexpire_logs_days = 10max_binlog_size = 100M#binlog_do_db = include_database_name#binlog_ignore_db = include_database_name## * InnoDB## InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.# Read the manual for more InnoDB related options. There are many!## * Security Features## Read the manual, too, if you want chroot!# chroot = /var/lib/mysql/## For generating SSL certificates I recommend the OpenSSL GUI "tinyca".## ssl-ca=/etc/mysql/cacert.pem# ssl-cert=/etc/mysql/server-cert.pem# ssl-key=/etc/mysql/server-key.pem [mysqldump]quickquote-namesmax_allowed_packet = 16M [mysql]#no-auto-rehash # faster start of mysql but no tab completition [isamchk]key_buffer = 16M # The default storage engine that will be used when create new tables whendefault-storage-engine=INNODB # The maximum amount of concurrent sessions the MySQL server will# allow. One of these connections will be reserved for a user with# SUPER privileges to allow the administrator to login even if the# connection limit has been reached.max_connections=600 # Maximum size for internal (in-memory) temporary tables. If a table# grows larger than this value, it is automatically converted to disk# based table This limitation is for a single table. There can be many# of them.tmp_table_size=256M # Additional memory pool that is used by InnoDB to store metadata# information. If InnoDB requires more memory for this purpose it will# start to allocate it from the OS. As this is fast enough on most# recent operating systems, you normally do not need to change this# value. SHOW INNODB STATUS will display the current amount used.innodb_additional_mem_pool_size=8M # If set to 1, InnoDB will flush (fsync) the transaction logs to the# disk at each commit, which offers full ACID behavior. If you are# willing to compromise this safety, and you are running small# transactions, you may set this to 0 or 2 to reduce disk I/O to the# logs. Value 0 means that the log is only written to the log file and# the log file flushed to disk approximately once per second. Value 2# means the log is written to the log file at each commit, but the log# file is only flushed to disk approximately once per second.innodb_flush_log_at_trx_commit=2 The size of the buffer InnoDB uses for buffering log data. As soon as# it is full, InnoDB will have to flush it to disk. As it is flushed# once per second anyway, it does not make sense to have it very large# (even with long transactions).innodb_log_buffer_size=16M # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and# row data. The bigger you set this the less disk I/O is needed to# access data in tables. On a dedicated database server you may set this# parameter up to 80% of the machine physical memory size. Do not set it# too large, though, because competition of the physical memory may# cause paging in the operating system. Note that on 32bit systems you# might be limited to 2-3.5G of user level memory per process, so do not# set it too high.innodb_buffer_pool_size=1024M # Size of each log file in a log group. You should set the combined size# of log files to about 25%-100% of your buffer pool size to avoid# unneeded buffer pool flush activity on log file overwrite. However,# note that a larger logfile size will increase the time needed for the# recovery process.innodb_log_file_size=512M # Number of threads allowed inside the InnoDB kernel. The optimal value# depends highly on the application, hardware as well as the OS# scheduler properties. A too high value may lead to thread thrashing.innodb_thread_concurrency=60 memlock innodb_file_per_table ## * IMPORTANT: Additional settings that can override those from this file!# The files must end with '.cnf', otherwise they'll be ignored.#!includedir /etc/mysql/conf.d/