Search the Community

Showing results for tags 'exile.ini'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Exile
    • Changelogs
    • Feedback
  • Exile Community
    • General Discussion
    • New Feature Voting
    • Problems & Bugs
    • Cat Walk
    • Recruitment
    • Small Talk
  • Exile Mod XM8 App
    • XM8 Server Administration
    • XM8 Android App
    • XM8 Discord Bot
  • Exile Mod Server Administration
    • Ask a Game Server Provider
    • Hosting
    • Operating Systems
    • Installation
    • Database
    • Security
    • Maintenance
  • Exile Mod Customization
    • Downloads & Releases
    • Content
    • Environment
    • Gameplay
    • Look & Feel
    • Tech Talk
  • Exile Life Mod
    • Visit forum on exilelifemod.com

Categories

  • Knowledge Base
  • Items
  • Constructions
  • Traders
  • Vehicles

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Homepage

Found 3 results

  1. TheFarFlash

    Territory not saved in DB

    Hi, I try to get a new 1.0.4 running on a root with a new DB with extDB3. Territories will not be safed in the DB and the RTP Log give me following error: Here the whole RTP https://pastebin.com/G3sAiDdx The extDB Log https://pastebin.com/EbDW51C0 After that I corrected in the exile.ini the number of SQL1_INPUTS @ the line 558 of [createTerritory] from 11 to 12 Here the old exile.ini https://pastebin.com/isDDkJYS The result is the same error in the RTP but the error in the extDB Log changes to this The whole LOG here: https://pastebin.com/Pm0p7u5H Could anyone help me out of this misery, pls. The Testserver with 1.0.3 I was working on, was always fine. :-( THX
  2. LangeBlonds

    SQL CUSTOM V2

    Hello !! someone there you had this problem ?? [01:03:52 +00:00] [Thread 7845] extDB2: Database Type: MySQL [01:03:52 +00:00] [Thread 7845] extDB2: Database Session Pool Started [01:03:52 +00:00] [Thread 7845] extDB2: SQL_CUSTOM_V2: Loading Template Filename: /home/dd192148-ovh/12972/arma3/@exileserver/extDB/sql_custom_v2/exile.ini [01:03:52 +00:00] [Thread 7845] extDB2: SQL_CUSTOM_V2: Version 8 Detected, Latest Version 12 Available [01:04:27 +00:00] [Thread 7845] extDB2: SQL_CUSTOM_V2: Error StatementException: MySQL: [MySQL]: [Comment]: mysql_stmt_execute error [mysql_stmt_error]: Field 'assigned_items' doesn't have a default value [mysql_stmt_errno]: 1364 [mysql_stmt_sqlstate]: HY000 [statemnt]: INSERT INTO player SET account_uid = ?, name = ? [01:04:27 +00:00] [Thread 7845] extDB2: SQL_CUSTOM_V2: Wiping Statements + Session [01:04:27 +00:00] [Thread 7845] extDB2: SQL_CUSTOM_V2: Error: UniqueID: 1 Input String: createPlayer:76561197972519305:Major Lynx.D
  3. I think I may have found an issue with the following exile.ini cleanup commands: deleteOldContainers deleteOldConstructions deleteOldVehicles deleteUnpaidTerritories I have tested this on the territory table using the deleteUnpaidTerritories command. (I have a territory last_paid_at set to 2015-01-01 for testing purposes) Adapted to be a select instead of a delete (I removed the DELETE keyword and added SELECT * so i could see what was being returned/wht would have been deleted): SELECT * FROM territory WHERE last_paid_at < UNIX_TIMESTAMP(DATE_SUB(NOW(), INTERVAL 14 DAY)) Produces the following warning and returns no results: "Incorrect datetime value: '1448678464' for column 'last_paid_at' at row 1" Modifying the query to remove the UNIX_TIMESTAMP() block fixes this and I get the 1 result I was expecting: SELECT * FROM territory WHERE last_paid_at < DATE_SUB(NOW(), INTERVAL 14 DAY) With the original query, territories are not being deleted. Original: DELETE FROM territory WHERE last_paid_at < UNIX_TIMESTAMP(DATE_SUB(NOW(), INTERVAL ? DAY)) Modified to work: DELETE FROM territory WHERE last_paid_at < DATE_SUB(NOW(), INTERVAL ? DAY) This testing was performed on a MySQL server with version 5.6.17