Very Long restart and lag. [L2j]

[Kzah]

Hello,

 

I do not know where the problem is, so I just ask for help. My server runs on Ubuntu, it's a L2j server and it seems very slow to restart. And we have some lag in the game,  for example. when a monster gives an object.

 

Someone help me please?

 

Thanks !

 

Restart.

GM shutdown countdown is over. restarting NOW!

OfflineTradersTable: Offline traders stored.

Offline Traders Table: Offline shops stored(1227ms).

All players disconnected and saved(16010ms).

Stopping GameTimeController

Game Time Controller: Timer stopped(0ms).

All ThreadPools are now stopped

Thread Pool Manager: Manager has been shut down(5002ms).

Community Server Thread: Thread interruped(0ms).

Login Server Thread: Thread interruped(1ms).

GM restart received. Restarting NOW!

SevenSigns: Seven Signs data saved(42040ms).

SevenSigns: Seven Signs status saved(150ms).

RaidBossSpawnManager: All raidboss info saved(49845ms).

GrandBossManager: All Grand Boss info saved(2243ms).

Hellbound Manager: Data saved(0ms).

Item Auction Manager: All tasks stopped(0ms).

Olympiad System: Data saved(2ms).

Hero System: Data saved(0ms).

Clan System: Data saved(1264ms).

Cursed Weapons Manager: Data saved(3ms).

Castle Manor Manager: Data saved(1500ms).

FortressOfResistance: Sucessfully saved attackers down to database!

DevastatedCastle: Sucessfully saved attackers down to database!

BanditStronghold: Sucessfully saved attackers down to database!

WildBeastReserve: Sucessfully saved attackers down to database!

FortressOfTheDead: Sucessfully saved attackers down to database!

CHSiegeManager: Siegable hall attacker lists saved!

Quest Manager: Data saved(1190ms).

Global Variables Manager: Variables saved(3ms).

Items On Ground Manager: Data saved(621117ms).

Items On Ground Manager: Cleaned up(1ms).

Game Server: Selector thread has been shut down(1ms).

L2Database Factory: Database connection has been shut down(4ms).

 

My configuration :

i3 2130 3.4+ GHz

8 Go RAM

Connection 100 Mbps

 

My my.cnf

[client]

port    = 3306

socket  = /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.sock

nice    = 0

 

[mysqld]

#

# * Basic Settings

#

user    = mysql

pid-file    = /var/run/mysqld/mysqld.pid

socket  = /var/run/mysqld/mysqld.sock

port    = 3306

basedir  = /usr

datadir  = /var/lib/mysql

tmpdir  = /tmp

lc-messages-dir = /usr/share/mysql

skip-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  = 32M

max_allowed_packet  = 32M

thread_stack    = 192K

thread_cache_size = 8

# This replaces the startup script and checks MyISAM tables if needed

# the first time they are touched

myisam-recover = BACKUP

max_connections = 3000

#table_cache = 64

#thread_concurrency = 10

#

# * Query Cache Configuration

#

query_cache_limit = 2M

query_cache_size = 32M

#

# * 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 log - should be very few entries.

#

log_error = /var/log/mysql/error.log

#

# 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.log

expire_logs_days    = 10

max_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]

quick

quote-names

max_allowed_packet  = 32M

 

[mysql]

#no-auto-rehash # faster start of mysql but no tab completition

 

[isamchk]

key_buffer  = 32M

 

#

# * 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/

 

innodb_flush_log_at_trx_commit=2

 

innodb_buffer_pool_size=1024M

 

innodb_thread_concurrency=80

 

CPU and Ram:

CPU : ~6%

RAM : ~25%

[Intrepid]

Items On Ground Manager: Data saved(621117ms).

 

there lies your problem :D

[Devlin]

Items On Ground Manager: Data saved(621117ms).

 

there lies your problem :D

True.

 

Many items are dropped on the ground. It's better to disable dropping items on the ground.

[Intrepid]

True.

 

Many items are dropped on the ground. It's better to disable dropping items on the ground.

 

just disable the itemsongroundmanager, its pointless anyway.

[Kzah]

Too many objects on the ground cause a general latency ?

Even the raidboss save ? Or Seven sign ? Or Other ?

 

RaidBossSpawnManager: All raidboss info saved(49845ms).

SevenSigns: Seven Signs data saved(42040ms).

 

On my old machine (Windows), I did not have as big of time, even with a lot of objects on the ground. :/

 

[Intrepid]

Too many objects on the ground cause a general latency ?

Even the raidboss save ? Or Seven sign ? Or Other ?

 

On my old machine (Windows), I did not have as big of time, even with a lot of objects on the ground. :/

 

 

what pack are you using?

[Kzah]

L2J Revision Number: 6098

L2JDP Revision Number: 9859

 

I also had the pack on my old dedicated server.

[Intrepid]

L2J Revision Number: 6098

L2JDP Revision Number: 9859

 

I also had the pack on my old dedicated server.

 

Do you have any modification in it or its a clean pack?

[Kzah]

There have been changes. I try to make a clean and stable version to see if anything changes?

[Intrepid]

There have been changes. I try to make a clean and stable version to see if anything changes?

 

Run a clean one and test it. If the issue doesnt exist in a clean pack than its your modifications probably.

[Kzah]

This is better, but this is normal because the database contains only the initial data, except one player. But by making the difference with an image of a developer of L2j .. it's still important. I will try again when my database will be filled.

The pack is the last stable version de L2j.

 

 

All players disconnected and saved(834ms).

Stopping GameTimeController

Game Time Controller: Timer stopped(1ms).

All ThreadPools are now stopped

Thread Pool Manager: Manager has been shut down(5003ms).

Community Server Thread: Thread interruped(0ms).

Login Server Thread: Thread interruped(0ms).

GM shutdown received. Shutting down NOW!

SevenSignsFestival: Festival data saved(2129ms).

SevenSigns: Seven Signs data saved(1ms).

SevenSigns: Seven Signs status saved(157ms).

RaidBossSpawnManager: All raidboss info saved(48047ms).

GrandBossManager: All Grand Boss info saved(4643ms).

Hellbound Manager: Data saved(0ms).

TradeController saving data.. This action may take some minutes! Please wait until completed!

TradeController: All count Item saved(760ms).

Item Auction Manager: All tasks stopped(0ms).

Olympiad System: Data saved(312ms).

Hero System: Data saved(0ms).

Clan System: Data saved(0ms).

Cursed Weapons Manager: Data saved(2ms).

Castle Manor Manager: Data saved(7ms).

FortressOfResistance: Sucessfully saved attackers down to database!

DevastatedCastle: Sucessfully saved attackers down to database!

BanditStronghold: Sucessfully saved attackers down to database!

WildBeastReserve: Sucessfully saved attackers down to database!

FortressOfTheDead: Sucessfully saved attackers down to database!

CHSiegeManager: Siegable hall attacker lists saved!

Quest Manager: Data saved(494ms).

Global Variables Manager: Variables saved(1325ms).

Game Server: Selector thread has been shut down(0ms).

L2Database Factory: Database connection has been shut down(3ms).

[Kzah]

I have update Mysql and i have no problem. Thanks.

[FighterBoss]

I have update Mysql and i have no problem. Thanks.

Then locked.