[PROBLEM]User creates new char

hknippon · 08/28/2020, 05:16

Heya!

I'm having this issue when the server is online for a few hours (not more than 12) it requires the user to create a new character although they already have it on the account. (Issue doesn't occur locally, its on vps)

Someone has point me out the solution from Soul's post but it doesn't seems to work.

The post:

Spoiler

Added to my.ini but its still the same.

Spoiler

Hope someone would correct me or provide me any solution for this.

Thank you so much!!!!

SoulNecturn · 08/28/2020, 06:46

Hey

Well ensure that:
- You placed this code in proper place (e.g. after [mysqld] part? Proper palce matters

- restarted machine after this? (or all mysql services etc)?

here is my test serv setup:

works this way all fine for me

You must work this out - as this should be the solution you need there

hknippon · 08/28/2020, 10:38

Quote:

set-variable = max_connections=1500
skip-locking
set-variable = key_buffer=384M
set-variable = max_allowed_packet=10M
set-variable = table_cache=512
set-variable = record_buffer=2M
set-variable = thread_cache=8

set-variable = thread_concurrency=8
set-variable = myisam_sort_buffer_size=64M

set-variable = wait_timeout=600000
set-variable = interactive_timeout=600000

Thank you so much!! I'll test this now. will update here after 24hrs

*UPDATE*

I tried login (11hours after last maintenance) and the problem continue to exists (idk when it occurs).

My.ini files:

Quote:

#This File was made using the WinMySQLAdmin 1.4 Tool
#8/10/2020 5:29:36 AM

#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]

basedir=C:/Program Files (x86)/MySQL/MySQL Server 5.0
#bind-address=~~xxxxx~~
datadir=C:/Program Files (x86)/MySQL/MySQL Server 5.0/data
#language=C:/Program Files (x86)/MySQL/MySQL Server 5.0/share/your language directory
#slow query log#=
#tmpdir#=
#port=3306
#set-variable=key_buffer=16M

set-variable = max_connections=1500
skip-locking
set-variable = key_buffer=384M
set-variable = max_allowed_packet=10M
set-variable = table_cache=512
set-variable = sort_buffer=2M
set-variable = record_buffer=2M
set-variable = thread_cache=8

set-variable = thread_concurrency=8
set-variable = myisam_sort_buffer_size=64M

set-variable = wait_timeout=600000
set-variable = interactive_timeout=600000

[WinMySQLadmin]
Server=C:/Program Files (x86)/MySQL/MySQL Server 5.0/bin/mysqld-nt.exe
user=test
password=test

magewarior2 · 09/01/2020, 19:56

is it possible your msg server stacks to much ram space?

SoulNecturn · 09/01/2020, 20:28

Quote:

Originally Posted by magewarior2

is it possible your msg server stacks to much ram space?

Such thing would hang the msg server.
Here issue lies on losing connection to DB... and I am still Sure the my.ini parts are the way and reasons...
Whats wrong and why not catching setting - not sure... but anyway I would just stick and look for solutions on this part

Will ask again:
- restarted server after changes?
- ensured my.ini that is edited is the one in effect?
- you using default mysql provided with serv files or anything own?
- try run mysqladmin as admin privilages..?

hknippon · 09/02/2020, 05:32

Quote:

is it possible your msg server stacks to much ram space?

idk, will try to clear up some maps to ensure low usage of ram. thanks!

Quote:

restarted server after changes?
yes, everytime this problem occurs

ensured my.ini that is edited is the one in effect?
100%, there is only 1 mysql in the desktop.

you using default mysql provided with serv files or anything own?
no, im using mysql installed from mysql installer. maybe this is the reason?

try run mysqladmin as admin privilages..?
already run as admin

Thank you for the replies guys, I will try clearing some maps to reduce the ram usage and use the default mysql provided by server files.

///////Update

So I tried setting up divine fire files I received before, along with acc/msg/npc. the msg is closing and wont connect.

Original:

Spoiler

Translated:

Spoiler

apoxdeath · 09/02/2020, 08:43

Ive had this problem before and i had to use an old backup of accounts only way i could fix it, something with the account and cq_user an pretty much anything that stores character data, but after i restored it with working files it was fine(characters saved like normal) an then i just deleted each thing individually from the backup but thats just in my experience.

SoulNecturn · 09/02/2020, 08:54

Well mysql from installer (can but doesnt mean is) could be sourcing my.ini details/setup from other path/source... so yeah try on default one just to ensure - as well you can change path inside your my.ini and see if can start mysql (if wrong paths will have then you shouldnt be able

).

-----------

About the Dfire files you having problem now

Depends what are the files/how configured (as you said received before - from someone??).

I would check:
- database structure -> till 1.6.3.9 versions having different DB structure then on 1.6.4.3. Check on this part
- on 1643 ver I remember some map files had problem on running properly - required to use proper dmaps? So can check on this one

In problems like this Always try to look directly into servrer sys logs!

magewarior2 · 09/02/2020, 09:03

You've messed with cq_map right?

Quote:

>Create(pDb))★ in e:\Magic Technical Information\3.0Magic Engine\source\Arrow Breaking Sky\server\jehadserver\mapgroupkernel\mapgroup.cpp , 182
12:49:32 Message: SHELL: Kernel closing...

Closes after trying to load the maps. You have syslogs. Normally in some you can see on what map id it stops m. Add that map into cq_map again so it will load again. (The logs like soul said)

also if you deleted a map, make sure cq_generator does not has monsters spawning there, or your server wont load either.

hknippon · 09/02/2020, 10:26

Quote:

Originally Posted by apoxdeath

Ive had this problem before and i had to use an old backup of accounts only way i could fix it, something with the account and cq_user an pretty much anything that stores character data, but after i restored it with working files it was fine(characters saved like normal) an then i just deleted each thing individually from the backup but thats just in my experience.

I would do this too except this is the new database, it uses cq_user_new. but i'll give it a try, thanks for helping out!

This is actually from syslog itself, the error appears as soon as msg ran.

Spoiler

I already reconfigured my.ini to my new directory so it should'nt be a problem (mysql already detect the new path).

Quote:

I would check:
- database structure -> till 1.6.3.9 versions having different DB structure then on 1.6.4.3. Check on this part
- on 1643 ver I remember some map files had problem on running properly - required to use proper dmaps? So can check on this one

I received the files which is already on 1.6.4.3 and it works fine (a few months back when I set up my test server, so it should be fine right?)

Anyway, ill try checking out dmaps and cq_maps if there is any unsync data.

Thank you everyone!!

-----------------------------UPDATE---------------------------

My server is up and running thank god. Thanks for everyone for helping.
Will update again here in 24hrs if the problem persists.

Cheers!

|>SomeGuy<| · 09/11/2020, 08:17

Quote:

Originally Posted by hknippon

-----------------------------UPDATE---------------------------

My server is up and running thank ***. Thanks for everyone for helping.
Will update again here in 24hrs if the problem persists.

Cheers!

How did you fix the issue in the end? Im having the same issue at the moment.

hknippon · 09/11/2020, 13:44

Quote:

Originally Posted by |>SomeGuy<|

How did you fix the issue in the end? Im having the same issue at the moment.

1. Used MySQL files provided with the serverfiles (gameserver,accserver).

2. Added this into my.ini (located in C:\Windows).

Spoiler

*makesure u put under [mysqld] not [WinMySQLadmin]

3. Removed several *unused* maps in cq_maps.

Sometimes the problem do occurs but not as frequent as before. The first time I tried, my server got online for 4 days before the problem occured again. Goodluck!

Cheers!