Jump to content
×
×
  • Create New...
  • 0

Bug Stack


btiaguim

Question

hi all, i have a problem with my server.
When i have 1 stack i can negociate, but when have more then 1 in stack and trade, server go down!

 

Quote

SYSERR - CHANNEL 1

 

SYSERR: Dec  2 12:09:42 :: pid_init: 
Start of pid: 3235

SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:21:52 :: pid_deinit: 
End of pid

SYSERR: Dec  2 12:23:20 :: pid_init: 
Start of pid: 1029

SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:42 :: pid_deinit: 
End of pid

SYSERR: Dec  2 12:35:40 :: pid_init: 
Start of pid: 1051

SYSERR: Dec  2 12:36:41 :: pid_init: 
Start of pid: 1068

Quote

SYSLOG - CHANNEL 1

 

SYSERR: Dec  2 12:09:42 :: pid_init: 
Start of pid: 3235

SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:21:52 :: pid_deinit: 
End of pid

SYSERR: Dec  2 12:23:20 :: pid_init: 
Start of pid: 1029

SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:42 :: pid_deinit: 
End of pid

 

 

 

BD:

Quote

DB_SYSLOG

SYSERR: Dec  2 12:09:37 :: Process: FDWATCH: peer null in event: ident 18
SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
End of pid

SYSERR: Dec  2 12:23:16 :: pid_init: 
Start of pid: 1019

SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:41 :: pid_deinit: 
End of pid

SYSERR: Dec  2 12:35:36 :: pid_init: 
Start of pid: 1041

SYSERR: Dec  2 12:36:36 :: Process: FDWATCH: peer null in event: ident 18
SYSERR: Dec  2 12:36:36 :: Process: FDWATCH: peer null in event: ident 18
SYSERR: Dec  2 12:36:36 :: Process: FDWATCH: peer null in event: ident 18

Quote

DB_SYSERR

 

SYSERR: Dec  2 12:09:37 :: Process: FDWATCH: peer null in event: ident 18
SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:21:50 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
End of pid

SYSERR: Dec  2 12:23:16 :: pid_init: 
Start of pid: 1019

SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:41 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Dec  2 12:26:41 :: pid_deinit: 
End of pid

SYSERR: Dec  2 12:35:36 :: pid_init: 
Start of pid: 1041

SYSERR: Dec  2 12:36:36 :: Process: FDWATCH: peer null in event: ident 18
SYSERR: Dec  2 12:36:36 :: Process: FDWATCH: peer null in event: ident 18
SYSERR: Dec  2 12:36:36 :: Process: FDWATCH: peer null in event: ident 18

 

 

 

Edited by btiaguim
add syserr
Link to comment
Share on other sites

  • Answers 7
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

7 answers to this question

Recommended Posts

  • 0
Quote

CHANNEL 1 : Core1

 

SYSERR: Dec  2 12:05:14 :: ChildLoop: MySQL connection was reconnected. querying locale set
SYSERR: Dec  2 12:05:14 :: ChildLoop: AsyncSQL: query failed: Incorrect information in file: './log/loginlog2.frm' (query: INSERT INTO loginlog2(type, is_gm, login_time, channel, account_id, pid, ip, client_version) VALUES('INVALID', 'Y', NOW(), 1, 1, 26, inet_aton('xx.xx.xx.xx'), '') errno: 1033)
SYSERR: Dec  2 12:05:52 :: ChildLoop: MySQL connection was reconnected. querying locale set
SYSERR: Dec  2 12:05:52 :: ChildLoop: AsyncSQL: query failed: Incorrect information in file: './log/loginlog2.frm' (query: INSERT INTO loginlog2(type, is_gm, login_time, channel, account_id, pid, ip, client_version) VALUES('INVALID', 'N', NOW(), 1, 3, 25, inet_aton('xx.xx.xx.xx'), '') errno: 1033)
SYSERR: Dec  2 12:05:54 :: ChildLoop: AsyncSQL: query failed: Incorrect information in file: './log/loginlog2.frm' (query: INSERT INTO loginlog2(type, is_gm, login_time, channel, account_id, pid, ip, client_version) VALUES('INVALID', 'N', NOW(), 1, 2, 27, inet_aton('xx.xx.xx.xx'), '') errno: 1033)
SYSERR: Dec  2 12:07:22 :: pid_init: 
Start of pid: 3069

  Quote

DB: Syserr

 

SYSERR: Dec  2 12:09:37 :: Process: FDWATCH: peer null in event: ident 18

 

This is not true syserr

Link to comment
Share on other sites

  • 0
Quote

#0  0x289d8f3c in strlen () from /lib/libc.so.7
No symbol table info available.
#1  0x289d0a3a in gettimeofday () from /lib/libc.so.7
No symbol table info available.
#2  0x28933a08 in vsnprintf_l () from /lib/libc.so.7
No symbol table info available.
#3  0x28933ae4 in vsnprintf () from /lib/libc.so.7
No symbol table info available.
#4  0x081666e6 in ?? ()
No symbol table info available.
#5  0xbfbfa2eb in ?? ()
No symbol table info available.
#6  0x00000401 in ?? ()
No symbol table info available.
#7  0x297fb2cc in ?? ()
No symbol table info available.
#8  0xbfbfa71c in ?? ()
No symbol table info available.
#9  0x0000a31b in ?? ()
No symbol table info available.
#10 0x00000401 in ?? ()
No symbol table info available.
#11 0xbfbfa2e8 in ?? ()
 

 

Edited by btiaguim
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


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.