Problem ispconfig: 'TRUNCATE sys_datalog'

Discussion in 'General' started by, Jun 19, 2014.

  1. As an object, I wanted to point out that, after transferring an entire server on another machine, I noticed an exponential growth of data in the table sys_datalog.
    I also moved the old ispconfig database to the new machine.
    If it is true that ispconfig deletes the data of the previous 30 days, how did I find myself still data in the table sys_datalog three months ago?
    Unfortunately I can not truncate this table, the panel would be unusable.
    Solution that can be taken to remove the old data?
    Thank you so much in advance.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig is deleting all data that is not required anymore after 30 days. Some data is required even after 30 days and thats why ispconfig keeps this data.

    Thats right and for that reason, ispconfig is not truncating it. By truncating the table, ispconfig willloose its data histoy and will stop to prcess changes.

    You said the database is huge, how many gigabytes of data do you have in the datalog?
  3. Thank you so much for your reply till.
    With approximately 400 sites hosted ispconfig database is about 900 MB.
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, thats quite big indeed. Is this a multiserver system? If yes, did you move a slave or the master server?
  5. No is a single server! I synchronized the webserver data, vmail and transferred the database to the new server! I had not noticed previously a value so high dbispconfig! I noticed only by transferring the data to the new server!
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    There is a method to truncate the data as its a single server. In multiservers etups, this would cause problems.

    1) Truncate the sys_datalog table, e.g. with phpmyadmin
    2) Edit the server record in the server database table, set the updated column to 0. This will reset the history counter.

    In case that you plan to add a slave server to this system anytime in future, then you will have to run a resync on clients and databases with the resync tool or the slave will not work as it cant pick up the history for these tables.
  7. Ok Till, I'll do this test in a few hours on a local machine and not on a production server. I have to first install it!
    As soon as I did this test I'll tell you the outcome!
    Again many thanks Till...
  8. Perfect Till, it works.
    See you soon and thanks again...

Share This Page