integral Posted February 7, 2012 Group: Members Topic Count: 51 Topics Per Day: 0.01 Content Count: 167 Reputation: 4 Joined: 02/01/12 Last Seen: August 20, 2017 Share Posted February 7, 2012 I have here a picture of errors that occurred after I enabled the log feature. Quote Link to comment Share on other sites More sharing options...
KeiKun Posted February 7, 2012 Group: Members Topic Count: 31 Topics Per Day: 0.01 Content Count: 967 Reputation: 53 Joined: 11/13/11 Last Seen: June 11, 2023 Share Posted February 7, 2012 try to update your svn and re-execute the sql files~ Quote Link to comment Share on other sites More sharing options...
integral Posted February 7, 2012 Group: Members Topic Count: 51 Topics Per Day: 0.01 Content Count: 167 Reputation: 4 Joined: 02/01/12 Last Seen: August 20, 2017 Author Share Posted February 7, 2012 (edited) try to update your svn and re-execute the sql files~ How do you update the SVN? EDIT: If by updating, you mean that I should open mySQL Query Browser, click log 2 times, open script, choose upgrade_svn15519_log, and then execute. I just finished it, but the error is still there. Edited February 7, 2012 by integral Quote Link to comment Share on other sites More sharing options...
Brian Posted February 7, 2012 Group: Members Topic Count: 75 Topics Per Day: 0.02 Content Count: 2223 Reputation: 593 Joined: 10/26/11 Last Seen: June 2, 2018 Share Posted February 7, 2012 ../trunk/conf/log_athena.conf // Logging tables/files // Following settings specify where to log to. If 'sql_logs' is // enabled, SQL tables are assumed, otherwise flat files. // Dead Branch Log log_branch_db: log/branchlog.log //log_branch_db: branchlog // Drops & Pickups log_pick_db: log/picklog.log //log_pick_db: picklog // Zeny log_zeny_db: log/zenylog.log //log_zeny_db: zenylog // MVP Drops log_mvpdrop_db: log/mvplog.log //log_mvpdrop_db: mvplog // GM Log log_gm_db: log/atcommandlog.log //log_gm_db: atcommandlog // NPC Log log_npc_db: log/npclog.log //log_npc_db: npclog // CHAT Log log_chat_db: log/chatlog.log //log_chat_db: chatlog The default settings are for TXT logs (saved in the /log/ folder). To use SQL, you have to switch them to SQL configs, or add this to /conf/import/log_conf.txt log_branch_db: branchlog log_pick_db: picklog log_zeny_db: zenylog log_mvpdrop_db: mvplog log_gm_db: atcommandlog log_npc_db: npclog log_chat_db: chatlog Quote Link to comment Share on other sites More sharing options...
integral Posted February 8, 2012 Group: Members Topic Count: 51 Topics Per Day: 0.01 Content Count: 167 Reputation: 4 Joined: 02/01/12 Last Seen: August 20, 2017 Author Share Posted February 8, 2012 ../trunk/conf/log_athena.conf // Logging tables/files // Following settings specify where to log to. If 'sql_logs' is // enabled, SQL tables are assumed, otherwise flat files. // Dead Branch Log log_branch_db: log/branchlog.log //log_branch_db: branchlog // Drops & Pickups log_pick_db: log/picklog.log //log_pick_db: picklog // Zeny log_zeny_db: log/zenylog.log //log_zeny_db: zenylog // MVP Drops log_mvpdrop_db: log/mvplog.log //log_mvpdrop_db: mvplog // GM Log log_gm_db: log/atcommandlog.log //log_gm_db: atcommandlog // NPC Log log_npc_db: log/npclog.log //log_npc_db: npclog // CHAT Log log_chat_db: log/chatlog.log //log_chat_db: chatlog The default settings are for TXT logs (saved in the /log/ folder). To use SQL, you have to switch them to SQL configs, or add this to /conf/import/log_conf.txt log_branch_db: branchlog log_pick_db: picklog log_zeny_db: zenylog log_mvpdrop_db: mvplog log_gm_db: atcommandlog log_npc_db: npclog log_chat_db: chatlog and this did the trick. Thank you very much. Problem Solved. Quote Link to comment Share on other sites More sharing options...
Question
integral
I have here a picture of errors that occurred after I enabled the log feature.
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.