Page 684 of 744 FirstFirst ... 184584634674682683684685686694734 ... LastLast
Results 6,831 to 6,840 of 7437
  1. #6831
    Hi.I very often receive such messages in the console:
    [09:53:02 17] [AdKats] ALTER TABLE ******.`tbl_chatlog` ADD INDEX (logDate)
    [09:53:02 17] [AdKats] SUCCESS: SQL Update 'addChatlogDateIndex' completed execution (tbl_chatlog.logDate index successfully created).
    [09:53:02 56] [AdKats] ALTER TABLE ******.`adkats_records_main` ADD INDEX `adkats_records_main_fk_record_time` (`record_time` ASC)
    [09:53:02 57] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

    this is normal?

  2. #6832
    Quote Originally Posted by klait68 View Post
    Nice :-) Another question: Our database is real big - is there a way to delete entries - for example i want to kick out all entries from players which arent permabanned and who didnt played on our servers the last half year. If there was a solution or script for it i would be happy.
    Player records themselves don't take up much space. The biggest table is usually your chat log table.

    run this, but replace schema_name with your AdKats schema name:

    SELECT TABLE_NAME, table_rows, data_length, index_length,
    round(((data_length + index_length) / 1024 / 1024),2) "Size in MB"
    FROM information_schema.TABLES WHERE table_schema = "schema_name"
    ORDER BY (data_length + index_length) DESC;

    That will tell you which table(s) take up the most data. Once we know that we can do more.
    ____

  3. #6833
    Quote Originally Posted by keb2 View Post
    Hi.I very often receive such messages in the console:
    [09:53:02 17] [AdKats] ALTER TABLE ******.`tbl_chatlog` ADD INDEX (logDate)
    [09:53:02 17] [AdKats] SUCCESS: SQL Update 'addChatlogDateIndex' completed execution (tbl_chatlog.logDate index successfully created).
    [09:53:02 56] [AdKats] ALTER TABLE ******.`adkats_records_main` ADD INDEX `adkats_records_main_fk_record_time` (`record_time` ASC)
    [09:53:02 57] [AdKats] SUCCESS: SQL Update 'addRecordTimeIndex' completed execution (adkats_records_main.record_time index successfully created).

    this is normal?
    no it's not. perhaps it's showing a success message when it's actually failing? Does the account you have given to AdKats have permissions to create indexes on tables?
    ____

  4. #6834
    Quote Originally Posted by ColColonCleaner View Post
    no it's not. perhaps it's showing a success message when it's actually failing? Does the account you have given to AdKats have permissions to create indexes on tables?
    2018-01-24_221142.png 2018-01-24_224147.png
    Last edited by keb2; 24-01-2018 at 19:42.

  5. #6835
    Quote Originally Posted by keb2 View Post
    Run the following on your database manually:

    ALTER TABLE `tbl_chatlog` ADD INDEX (logDate);
    ALTER TABLE `adkats_records_main` ADD INDEX `adkats_records_main_fk_record_time` (`record_time` ASC);

    After this you shouldn't see those messages anymore.
    ____

  6. #6836
    Quote Originally Posted by ColColonCleaner View Post
    Run the following on your database manually:

    ALTER TABLE `tbl_chatlog` ADD INDEX (logDate);
    ALTER TABLE `adkats_records_main` ADD INDEX `adkats_records_main_fk_record_time` (`record_time` ASC);

    After this you shouldn't see those messages anymore.
    I get this error

    SQL :

    ALTER TABLE `adkats_records_main` ADD INDEX `adkats_records_main_fk_record_time` (`record_time` ASC)

    MySQL:
    #1061 — Duplicate key name 'adkats_records_main_fk_record_time'

  7. #6837
    Quote Originally Posted by keb2 View Post
    I get this error

    SQL :

    ALTER TABLE `adkats_records_main` ADD INDEX `adkats_records_main_fk_record_time` (`record_time` ASC)

    MySQL:
    #1061 — Duplicate key name 'adkats_records_main_fk_record_time'
    So it's unable to see that the index is already there, i wonder why. This doesn't happen on my layer.
    I'll remove it from the sql updater.
    Tomorrow you should stop seeing the messages without any further action on your part.
    ____

  8. #6838
    I added an automatic purge of AdKats statistic data older than 90 days into the plugin last night. The existing systems don't look at data older than this anyway so updating to the latest version should help reduce the size of your databases, at least a little bit.

    Extended round stats already purges data older than 60 days, so this is just building on that.

    tbl_extendedroundstats - 60 days
    adkats_statistics - 90 days

    /pupdate to get the latest version.
    ____

  9. #6839
    [23:34:14 14] [AdKats] ERROR-7018: [Server Crashed (35 Players Lost)]

    First time I have noticed the above ever displaying. Blaze disconnect or some other reason ?

  10. #6840
    Quote Originally Posted by sixpax12 View Post
    [23:34:14 14] [AdKats] ERROR-7018: [Server Crashed (35 Players Lost)]

    First time I have noticed the above ever displaying. Blaze disconnect or some other reason ?
    select * from adkats_records_debug where record_message like "%Server Crashed%";

    You likely just haven't noticed this before. AdKats logs whenever your server crashes or there is a blaze disconnect.
    ____

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •