Jump to content

Recommended Posts

 

Why this syserr is giving

 

SYSERR: May 16 15:01:47.538962 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: May 16 15:01:47.631599 :: ChildLoop: AsyncSQL: query failed: Query execution was interrupted (query: UPDATE player SET job = 8, voice = 0, dir = 0, x = 867720, y = 243835, z = 0, map_index = 43, exit_x = 867720, exit_y = 243835, exit_map_index = 43, hp = 6876, mp = 4918, stamina = 1330, random_hp = 5236, random_sp = 2618, playtime = 1887, level = 120, level_step = 0, st = 6, ht = 26, dx = 2, iq = 105, gold = 285428954, exp = 0, stat_point = 234, skill_point = 104, sub_skill_point = 61, stat_reset_count = 0, ip = '192.168.2.87', part_main = 0, part_hair = 0, part_acce = 0, last_play = NOW(), skill_group = 1, alignment = 5485, horse_level = 30, horse_riding = 0, horse_hp = 50, horse_hp_droptime = 1495198894, horse_stamina = 200, horse_skill_point = 0, cheque = 767, skill_level = '\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0(\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
SYSERR: May 16 15:01:47.631765 :: ChildLoop: AsyncSQL: query failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) (query: REPLACE INTO item (id, owner_id, window, pos, count, vnum, bind, evolution, socket0, socket1, socket2, socket3) VALUES(10000001, 10123, 1, 0, 1, 149, 0, 0, 1, 1, 1, 0) errno: 2002)
SYSERR: May 16 15:01:47.631789 :: ChildLoop: AsyncSQL: retrying
SYSERR: May 16 15:01:47.637689 :: pid_deinit: 
End of pid

SYSERR: May 16 15:05:06.399372 :: pid_init: 
Start of pid: 928

SYSERR: May 16 15:05:06.399569 :: Start: TABLE_POSTFIX not configured use default
SYSERR: May 16 15:05:08.201390 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
 

Link to comment
Share on other sites

  • Replies 2
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

21 hours ago, iltizio said:

 

170516 15:01:52 mysqld_safe mysqld from pid file /var/db/mysql/host.home.pid ended
170516 15:02:30 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
170516 15:02:30 InnoDB: The InnoDB memory heap is disabled
170516 15:02:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170516 15:02:30 InnoDB: Compressed tables use zlib 1.2.7
170516 15:02:30 InnoDB: Initializing buffer pool, size = 128.0M
170516 15:02:30 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
170516 15:02:30  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
170516 15:02:30  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
170516 15:02:30  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
170516 15:02:30  InnoDB: Waiting for the background threads to start
170516 15:02:31 InnoDB: 5.5.33 started; log sequence number 0
170516 15:02:31 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
170516 15:02:31 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
170516 15:02:31 [Note] Server socket created on IP: '0.0.0.0'.
170516 15:02:31 [Note] Event Scheduler: Loaded 0 events
170516 15:02:31 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.5.33'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

 

 

MySQL sunucunuzu başlatın.


Başlamazsa, uyarı günlüğünü kontrol edin (/var/db/mysql/<hostname>.err).

 

 

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



×
×
  • 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.