Jump to content

Package Disable


Go to solution Solved by Sanchez,

Recommended Posts

  • Management

Thanks, I'm compiling the game to see if results...

 

I have another question:

 

My syserr from channels:

SYSERR: Jan  3 19:22:39 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:22:42 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:22:45 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:22:48 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:22:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:22:54 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:22:57 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:23:00 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:23:03 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Jan  3 19:23:06 :: socket_connect: HOST localhost:15000, could not connect.

What this mean?

 

Thanks

raw

raw

Link to comment
Share on other sites

  • Management

I'm not a expert, just started today on source, but I had many times this error, but always worked everything...
 
My db conf.txt:
 

WELCOME_MSG = "DB Server has been started"

SQL_ACCOUNT = "localhost account mt2 mt2!@# 0"
SQL_PLAYER = "localhost player mt2 mt2!@# 0"
SQL_COMMON = "localhost common mt2 mt2!@# 0"
SQL_HOTBACKUP = "localhost hotbackup mt2 mt2!@# 0"

TABLE_POSTFIX = ""

BIND_PORT = 15000
DB_SLEEP_MSEC = 10
CLIENT_HEART_FPS = 10
HASH_PLAYER_LIFE_SEC = 600
BACKUP_LIMIT_SEC = 3600
PLAYER_ID_START = 100
PLAYER_DELETE_LEVEL_LIMIT = 120

ITEM_ID_RANGE = 2000000000 2100000000

MIN_LENGTH_OF_SOCIAL_ID = 6

#NAME_COLUMN = "gb2312name"
#LOCALE = "germany"
SIMPLE_SOCIALID = 1
Block "Y/QSB7omi36awq4ctpUxuiwRARM="

 


My db syserr:

SYSERR: Jan  3 19:49:32 :: pid_init: 
Start of pid: 3367

SYSERR: Jan  3 19:49:32 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Jan  3 19:49:35 :: Load:  DirectQuery failed(SELECT login FROM block_exception)
SYSERR: Jan  3 19:49:42 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 19:49:44 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Jan  3 19:49:44 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Jan  3 19:49:45 :: pid_deinit: 
End of pid

raw

raw

Link to comment
Share on other sites

  • Management

Now I have those errors:

 

SYSERR: Jan  3 22:32:50 :: pid_init: 
Start of pid: 3894

SYSERR: Jan  3 22:33:09 :: Process: FDWATCH: peer null in event: ident 25
SYSERR: Jan  3 22:33:23 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:24 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:24 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:24 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:33:34 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:33:37 :: Process: FDWATCH: peer null in event: ident 20
SYSERR: Jan  3 22:33:37 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:33:41 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jan  3 22:33:41 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Jan  3 22:33:45 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Jan  3 22:33:52 :: Process: FDWATCH: peer null in event: ident 30
SYSERR: Jan  3 22:33:53 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:54 :: Process: FDWATCH: peer null in event: ident 25
SYSERR: Jan  3 22:33:54 :: Process: FDWATCH: peer null in event: ident 27
SYSERR: Jan  3 22:33:58 :: Process: FDWATCH: peer null in event: ident 26
SYSERR: Jan  3 22:33:59 :: Process: FDWATCH: peer null in event: ident 28
SYSERR: Jan  3 22:34:04 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:34:14 :: Process: FDWATCH: peer null in event: ident 30
SYSERR: Jan  3 22:34:25 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:34:38 :: Process: FDWATCH: peer null in event: ident 30
SYSERR: Jan  3 22:34:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:34:50 :: Process: FDWATCH: peer null in event: ident 20
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 29
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 29
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 29
SYSERR: Jan  3 22:34:55 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Jan  3 22:34:55 :: Process: FDWATCH: peer null in event: ident 21 

raw

raw

Link to comment
Share on other sites

  • Former Staff

Now I have those errors:

 

SYSERR: Jan  3 22:32:50 :: pid_init: 
Start of pid: 3894

SYSERR: Jan  3 22:33:09 :: Process: FDWATCH: peer null in event: ident 25
SYSERR: Jan  3 22:33:23 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:24 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:24 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:24 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:33:34 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:33:37 :: Process: FDWATCH: peer null in event: ident 20
SYSERR: Jan  3 22:33:37 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:33:41 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Jan  3 22:33:41 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Jan  3 22:33:45 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Jan  3 22:33:52 :: Process: FDWATCH: peer null in event: ident 30
SYSERR: Jan  3 22:33:53 :: Process: FDWATCH: peer null in event: ident 23
SYSERR: Jan  3 22:33:54 :: Process: FDWATCH: peer null in event: ident 25
SYSERR: Jan  3 22:33:54 :: Process: FDWATCH: peer null in event: ident 27
SYSERR: Jan  3 22:33:58 :: Process: FDWATCH: peer null in event: ident 26
SYSERR: Jan  3 22:33:59 :: Process: FDWATCH: peer null in event: ident 28
SYSERR: Jan  3 22:34:04 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:34:14 :: Process: FDWATCH: peer null in event: ident 30
SYSERR: Jan  3 22:34:25 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:34:38 :: Process: FDWATCH: peer null in event: ident 30
SYSERR: Jan  3 22:34:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Jan  3 22:34:50 :: Process: FDWATCH: peer null in event: ident 20
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 29
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 29
SYSERR: Jan  3 22:34:54 :: Process: FDWATCH: peer null in event: ident 29
SYSERR: Jan  3 22:34:55 :: Process: FDWATCH: peer null in event: ident 24
SYSERR: Jan  3 22:34:55 :: Process: FDWATCH: peer null in event: ident 21 

i'm so sorry i don't know these errors :/

 

mmm give us more information what are you triennial to do ??

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



  • Similar Content

  • Activity

    1. 5

      OLDGODSMT2 [ MEGA SF RELEASE ]

    2. 24

      Experimental Renderer

    3. 11

      Multi Language System

    4. 0

      [FREE DESIGN] Interface + Logo + Discord Banner and Avatar

    5. 4

      Feeding game source to LLM

    6. 0

      Quest 6/7 Problem

    7. 5

      Effect weapons

    8. 0

      [C++] Fix Core Downer Using Negative Number in GM Codes

  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.