Physical attack stop!

[Spyrox92]

hey guys,

at the moment im running a l2j epilogue lowrate server,

but following problem appeard.

all physical attacks stops for 1-10 hits.

after it stops you arent able to attack again without moving a bit and attack again.

then same starts again.

it doesnt care wich revision ive used, same problem.

some infos about server machine:

AMD Athlon 64 x2 3400+

centos

4GB ram

500gb HDD

100mbits line

 

maybe one of you know an answer..

 

[CriticalError]

hey guys,

at the moment im running a l2j epilogue lowrate server,

but following problem appeard.

all physical attacks stops for 1-10 hits.

after it stops you arent able to attack again without moving a bit and attack again.

then same starts again.

it doesnt care wich revision ive used, same problem.

some infos about server machine:

AMD Athlon 64 x2 3400+

centos

4GB ram

500gb HDD

100mbits line

 

maybe one of you know an answer..

 

you try with another system? maybe is something there but not sure about that, forme is something in DP.

[Spyrox92]

yeah ive tried it also at my home pc..

everything works fine there.

the problem happens only at this machine.

thats why i dont know whats the problem there.

also updated java and mysql to the latest version but didnt helped.

still same problem.

probably there´s something wrong with the mysql config?

could you take a look there?

[mysqld]
port = 3306
skip-locking
set-variable = key_buffer=600M
set-variable = max_allowed_packet=32M
set-variable = table_cache=1024
set-variable = sort_buffer=256K
set-variable = net_buffer_length=4K
set-variable = myisam_sort_buffer_size=2M
set-variable = query_cache_size=512
set-variable = max_connections=3000
set-variable = local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1

# Disabling symbolic-links is recommended to prevent assorted security risks;
# to do so, uncomment this line:
# symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

 

thats the current my.cnf im using.

 

[CriticalError]

yeah ive tried it also at my home pc..

everything works fine there.

the problem happens only at this machine.

thats why i dont know whats the problem there.

also updated java and mysql to the latest version but didnt helped.

still same problem.

probably there´s something wrong with the mysql config?

could you take a look there?

[mysqld]
port = 3306
skip-locking
set-variable = key_buffer=600M
set-variable = max_allowed_packet=32M
set-variable = table_cache=1024
set-variable = sort_buffer=256K
set-variable = net_buffer_length=4K
set-variable = myisam_sort_buffer_size=2M
set-variable = query_cache_size=512
set-variable = max_connections=3000
set-variable = local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1

# Disabling symbolic-links is recommended to prevent assorted security risks;
# to do so, uncomment this line:
# symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

 

thats the current my.cnf im using.

 

and  you try copy your config of mysql o check all figure there is same?

[Tryskell]

What release are you using, on what revision ?

When exactly it happens ?

Any critical error in GS ?

 

Except a badass lag, it has nothing to do with mySQL nor hardware.

 

If you use a release which isn't L2J Free / L2J, you increase by 191,21% your luck to be on a crappy pack.

[SkyNet]

has not really to do with a bad pack i guess ;)

i had the same as player on TNS which u can't say they use a bad pack or are bad dev xD

 

well this uhm lets call it "bug" is nice against bots :D but really boring u can't really enjoy the farming with a fighter :S

[Spyrox92]

well it doesnt care wich revision it was cuz the problem happened at every revision of every version (gracia final,epilogue etc.)

ive made a clean compile of latest epilogue revision.

no errors at GS.

problem happened from the first start of gs and didnt stopped.

but problem is fixed now. :)

for some reasons l2j server got some trouble with CentOS.

installed ubuntu now and everything works fine there.

but thx anyway for you help!

[B1ggBoss]

well it doesnt care wich revision it was cuz the problem happened at every revision of every version (gracia final,epilogue etc.)

ive made a clean compile of latest epilogue revision.

no errors at GS.

problem happened from the first start of gs and didnt stopped.

but problem is fixed now. :)

for some reasons l2j server got some trouble with CentOS.

installed ubuntu now and everything works fine there.

but thx anyway for you help!