1. Dashboard
  2. Forum
    1. Unerledigte Themen
  3. Downloads
  4. Galerie
    1. Alben
  5. Toolbox
    1. Passwort Generator
    2. Portchecker
  6. Mitglieder
    1. Mitgliedersuche
    2. Benutzer online
    3. Trophäen
    4. Team
Fr: 18 Juli 2025
  • Anmelden oder registrieren
  • Suche
Alles
  • Alles
  • Artikel
  • Forum
  • Dateien
  • Seiten
  • Bilder
  • Erweiterte Suche

Schön, dass du den Weg zu NodeZone.net gefunden hast! Aktuell bist du nicht angemeldet und kannst deshalb nur eingeschränkt auf unsere Community zugreifen. Um alle Funktionen freizuschalten, spannende Inhalte zu entdecken und dich aktiv einzubringen, registriere dich jetzt kostenlos oder melde dich mit deinem Account an.

Anmelden oder registrieren
    1. Nodezone.net Community
    2. Mitglieder
    3. SirTim

    Beiträge von SirTim

    • Datenbank Probleme

      • SirTim
      • 18. Februar 2017 um 11:38

      Hier meine Config

      Spoiler anzeigen

      [Main]
      Version = 5
      Threads = 4
      ; Default Value is the number of CPU Cores Detected (max value is 6, min value is 2)

      Randomize Config File = false
      ;This is a legacy option to randomize config file for Arma2 Servers. Only for Windows Builds


      [Rcon]
      ;; This is functional, should be working fine. Just needs abit of testing on a $
      ;; Allow for changing Address for those running server in a VM environment.
      IP = 127.0.0.1
      Port = 2302

      ;; Rcon Password i.e Battleye/beserver.cfg
      Password = XXXXXXXXXXXXXXXXXXX

      ;; Bad Player Name Checks
      ;;This will only work if your mission / mod has started extDB2 Rcon. i.e 9:START_RCON:RCON
      Bad Playername Enable = true
      Bad Playername Kick Message = Bad Player Name

      ;; By default : is a bad character (used as seperator for extDB2 Calls (this is hardcoded in)
      Bad Playername Strings = (:):{:}
      Bad Playername Regex_1 = [:alnum:]
      Bad Playername Regex_2 = [:alnum:]
      Bad Playername Regex_3 = [:alnum:]


      ;; Whitelisting / Reserve Slots
      ;;This will only work if your mission / mod has started extDB2 Rcon. i.e 9:START_RCON:RCON
      Whitelist Enable = false
      Whitelist Kick Message = Only Reserved Slots Left

      Whitelist Public Slots = 999

      ;; Database settings to use (Optional)
      Whitelist Database = MySQL_Example
      Whitelist SQL Prepared Statement = SELECT CASE WHEN EXISTS(SELECT UID FROM PlayerInfo WHERE BattlEyeGUID=? AND Whitelisted=1) THEN 1 ELSE 0 END
      Whitelist Kick on SQL Query Failed = false

      ;; Hardcoded BEGuids for whitelisted players
      ;Whitelist BEGuids = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx : yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy


      [RemoteAccess]
      ;; Remote TCP Access to extDB2
      Enable = false

      Port = 2300
      MaxThreads = 4
      MaxQueued = 4
      IdleTime = 120

      Password = password


      [Steam]
      ;; This is for VAC Protocol for VAC Bans + Steam Friends.
      ;; https://steamcommunity.com/dev/apikey
      API Key = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


      [VAC]
      ;; This feature requires Steam + Rcon to be enabled.
      ;; Also this feature is called via SQF Code atm, i.e it doesn't auto detect players joining server yet....
      Auto Ban = true

      ;; For Player to get banned ( their total VAC Bans => NumberOfVACBans) AND ( Days Since their Last Ban was <= DaysSinceLastBan)
      ;; This is also used extDB Protocol VAC:VACBanned returned results

      NumberOfVACBans = 1
      DaysSinceLastBan = 999999999
      BanDuration = 0
      ;; 0 = Forever, otherwise its x Minutes
      BanMessage = Steam VAC banned


      [Log]
      ;; Flush Logs after each write, more work on Harddrive
      Flush = true

      [AltisLife]
      ;; Example of MySQL
      ;; AtlisLifeRPG uses Database2 by default
      Type = MySQL
      Name = altislife

      Username = arma3
      Password = XXXXXXXXXXXXXXXXXXXXX
      IP = 127.0.0.1
      Port = 3306

      minSessions = 1
      ;maxSessions = 4
      idleTime = 60

      compress = false
      ; Should only use this if MySQL server is external. Also only for MySQL

      Secure Auth = true
      ; Recommend you turn this on

      [SQLite_Example]
      Type = SQLite
      Name = sqlite.db

      minSessions = 1
      ; minSession Default Value = 1

      ;maxSessions = 4
      ; maxSession Default Value = number of Main->Threads
      ; You really should leave this value alone
      idleTime = 60
      ; idleTime no Default Value yet, needs to be defined.
      ; idleTime is the time before a database session is stopped if not used.
      ; If Database Sessions are greater than minSessions


      [HTTP_Example]
      Type = HTTP

      Host = 127.0.0.1
      Port = 80

      ; Username = user
      ; Password = password


      Und meine DB heißt altislife

    • Datenbank Probleme

      • SirTim
      • 18. Februar 2017 um 00:19

      Hi,

      ich wollte generell auf Taunus Life oder so raus. Halt ne andere Karte. Früher war das so das man nur die Missio.sqm ändern musse und es hatte geklappt. Also hab ich bei Altis alles Kopiert und In Taunus Kopiert.
      ABER jetzt habe ich bei der Datenbank


      extDB2: Found [lexicon]extdb[/lexicon]-conf.ini
      extDB2: Detected 8 Cores, Setting up 4 Worker Threads (config settings)


      [00:07:43:253 +00:-1] [Thread 2436] extDB2: No Config Option Found:


      Danach halt nichts. Bei normal Altis Life hatte es ja funktioniert


      Und in live_server ist dynmarket.


      Gruß

      Tim

    • Datenbank Probleme

      • SirTim
      • 16. Februar 2017 um 16:34

      Hi,
      sorry wegen dem Code hatte die Funktionen nicht gesehen Donator ändere ich gerade. Und Dynmarket hab ich nicht eingefügt das war da schon. Ich hatte an der Datei nichts gemacht. Da ich dynmarket gerne später noch haben wollte, kann ich das doch einfach auskommentieren oder ist das schnell einzufügen ?


      Hab nun die Logs der Datenbank vor mir nachdem ich Donator geändert habe.

      Spoiler anzeigen

      [16:33:10:939 +00:-1] [Thread 2700] extDB2: SQL_CUSTOM_V2: Version 12 Detected, Latest Version 12 Available
      [16:33:11:812 +00:-1] [Thread 1752] extDB2: SQL_CUSTOM_V2: Error StatementException: MySQL: [MySQL]: [Comment]: mysql_stmt_prepare error [mysql_stmt_error]: Table 'altislife.dynmarket' doesn't exist [mysql_stmt_errno]: 1146 [mysql_stmt_sqlstate]: 42S02 [statemnt]: SELECT prices FROM dynmarket WHERE id=1;
      [16:33:11:812 +00:-1] [Thread 1752] extDB2: SQL_CUSTOM_V2: Wiping Statements + Session
      [16:33:11:812 +00:-1] [Thread 1752] extDB2: SQL_CUSTOM_V2: Error: UniqueID: 9818 Input String: DYNMARKET_Price_Get


      Ich kann jetzt auch auf den Server joinen und es funktioniert alles. Dennoch würde ich gerne alle Fehler ausmerzen

    • Datenbank Probleme

      • SirTim
      • 16. Februar 2017 um 15:56

      Die altislife.sql sieht bei mir so aus

      SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
      SET time_zone = "+00:00";
      --
      -- Compatible with newer MySQL versions. (After MySQL-5.5)
      -- This SQL uses utf8mb4 and has CURRENT_TIMESTAMP function.
      --


      /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
      /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
      /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
      /*!40101 SET NAMES utf8mb4 */;

      --
      -- Database: `altislife`
      -- Default Schema
      --
      CREATE DATABASE IF NOT EXISTS `altislife` DEFAULT CHARACTER SET utf8mb4;
      USE `altislife`;

      --
      -- Drop procedures to ensure no conflicts
      --
      DROP PROCEDURE IF EXISTS `resetLifeVehicles`;
      DROP PROCEDURE IF EXISTS `deleteDeadVehicles`;
      DROP PROCEDURE IF EXISTS `deleteOldHouses`;
      DROP PROCEDURE IF EXISTS `deleteOldGangs`;
      DROP PROCEDURE IF EXISTS `deleteOldContainers`;
      DROP PROCEDURE IF EXISTS `deleteOldWanted`;

      DELIMITER $$
      --
      -- Procedures
      -- Edit arma3 to match a user in MySQL
      -- For external databases: Edit localhost to match arma3server IP
      --

      CREATE DEFINER=`arma3`@`localhost` PROCEDURE `resetLifeVehicles`()
      BEGIN
      UPDATE `vehicles` SET `active`= 0;
      END$$

      CREATE DEFINER=`arma3`@`localhost` PROCEDURE `deleteDeadVehicles`()
      BEGIN
      DELETE FROM `vehicles` WHERE `alive` = 0;
      END$$

      CREATE DEFINER=`arma3`@`localhost` PROCEDURE `deleteOldHouses`()
      BEGIN
      DELETE FROM `houses` WHERE `owned` = 0;
      END$$

      CREATE DEFINER=`arma3`@`localhost` PROCEDURE `deleteOldGangs`()
      BEGIN
      DELETE FROM `gangs` WHERE `active` = 0;
      END$$

      CREATE DEFINER=`arma3`@`localhost` PROCEDURE `deleteOldContainers`()
      BEGIN
      DELETE FROM `containers` WHERE `owned` = 0;
      END$$

      CREATE DEFINER=`arma3`@`localhost` PROCEDURE `deleteOldWanted`()
      BEGIN
      DELETE FROM `wanted` WHERE `active` = 0;
      END$$

      DELIMITER ;

      -- --------------------------------------------------------

      --
      -- Table structure for table `players`
      --

      CREATE TABLE IF NOT EXISTS `players` (
      `uid` int(6) NOT NULL AUTO_INCREMENT,
      `name` varchar(32) NOT NULL,
      `aliases` text NOT NULL,
      `pid` varchar(17) NOT NULL,
      `cash` int(100) NOT NULL DEFAULT '0',
      `bankacc` int(100) NOT NULL DEFAULT '0',
      `coplevel` enum('0','1','2','3','4','5','6','7') NOT NULL DEFAULT '0',
      `mediclevel` enum('0','1','2','3','4','5') NOT NULL DEFAULT '0',
      `civ_licenses` text NOT NULL,
      `cop_licenses` text NOT NULL,
      `med_licenses` text NOT NULL,
      `civ_gear` text NOT NULL,
      `cop_gear` text NOT NULL,
      `med_gear` text NOT NULL,
      `civ_stats` varchar(32) NOT NULL DEFAULT '"[100,100,0]"',
      `cop_stats` varchar(32) NOT NULL DEFAULT '"[100,100,0]"',
      `med_stats` varchar(32) NOT NULL DEFAULT '"[100,100,0]"',
      `arrested` tinyint(1) NOT NULL DEFAULT '0',
      `adminlevel` enum('0','1','2','3','4','5') NOT NULL DEFAULT '0',
      `donorlevel` enum('0','1','2','3','4','5') NOT NULL DEFAULT '0',
      `blacklist` tinyint(1) NOT NULL DEFAULT '0',
      `civ_alive` tinyint(1) NOT NULL DEFAULT '0',
      `civ_position` varchar(64) NOT NULL DEFAULT '"[]"',
      `playtime` varchar(32) NOT NULL DEFAULT '"[0,0,0]"',
      `insert_time` timestamp DEFAULT CURRENT_TIMESTAMP,
      `last_seen` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
      PRIMARY KEY (`uid`),
      UNIQUE KEY `pid` (`pid`),
      KEY `name` (`name`),
      KEY `blacklist` (`blacklist`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 AUTO_INCREMENT=12 ;

      -- --------------------------------------------------------

      --
      -- Table structure for table `vehicles`
      --

      CREATE TABLE IF NOT EXISTS `vehicles` (
      `id` int(6) NOT NULL AUTO_INCREMENT,
      `side` varchar(16) NOT NULL,
      `classname` varchar(64) NOT NULL,
      `type` varchar(16) NOT NULL,
      `pid` varchar(17) NOT NULL,
      `alive` tinyint(1) NOT NULL DEFAULT '1',
      `blacklist` tinyint(1) NOT NULL DEFAULT '0',
      `active` tinyint(1) NOT NULL DEFAULT '0',
      `plate` int(20) NOT NULL,
      `color` int(20) NOT NULL,
      `inventory` text NOT NULL,
      `gear` text NOT NULL,
      `fuel` double NOT NULL DEFAULT '1',
      `damage` varchar(256) NOT NULL,
      `insert_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
      PRIMARY KEY (`id`),
      KEY `side` (`side`),
      KEY `pid` (`pid`),
      KEY `type` (`type`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 AUTO_INCREMENT=2 ;

      -- --------------------------------------------------------

      --
      -- Table structure for table `houses`
      -- Needed for [lexicon]extDB[/lexicon] latest update on git
      --

      CREATE TABLE IF NOT EXISTS `houses` (
      `id` int(6) NOT NULL AUTO_INCREMENT,
      `pid` varchar(17) NOT NULL,
      `pos` varchar(64) DEFAULT NULL,
      `owned` tinyint(1) DEFAULT '0',
      `garage` tinyint(1) NOT NULL DEFAULT '0',
      `insert_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
      PRIMARY KEY (`id`,`pid`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 AUTO_INCREMENT=4 ;

      -- --------------------------------------------------------

      --
      -- Table structure for table `gangs`
      -- Needed for [lexicon]extDB[/lexicon] latest update on git
      --

      CREATE TABLE IF NOT EXISTS `gangs` (
      `id` int(6) NOT NULL AUTO_INCREMENT,
      `owner` varchar(32) DEFAULT NULL,
      `name` varchar(32) DEFAULT NULL,
      `members` text,
      `maxmembers` int(3) DEFAULT '8',
      `bank` int(100) DEFAULT '0',
      `active` tinyint(1) DEFAULT '1',
      `insert_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
      PRIMARY KEY (`id`),
      UNIQUE KEY `name_UNIQUE` (`name`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

      -- --------------------------------------------------------

      --
      -- Table structure for table `containers`
      -- Needed for [lexicon]extDB[/lexicon] latest update on git
      --

      CREATE TABLE IF NOT EXISTS `containers` (
      `id` int(6) NOT NULL AUTO_INCREMENT,
      `pid` varchar(17) NOT NULL,
      `classname` varchar(32) NOT NULL,
      `pos` varchar(64) DEFAULT NULL,
      `inventory` text NOT NULL,
      `gear` text NOT NULL,
      `dir` varchar(128) DEFAULT NULL,
      `active` tinyint(1) NOT NULL DEFAULT '0',
      `owned` tinyint(1) DEFAULT '0',
      `insert_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
      PRIMARY KEY (`id`,`pid`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 AUTO_INCREMENT=4;

      -- --------------------------------------------------------

      --
      -- Table structure for table `wanted`
      -- Needed for [lexicon]extDB[/lexicon] latest update on git
      --

      CREATE TABLE IF NOT EXISTS `wanted` (
      `wantedID` varchar(64) NOT NULL,
      `wantedName` varchar(32) NOT NULL,
      `wantedCrimes` text NOT NULL,
      `wantedBounty` int(100) NOT NULL,
      `active` tinyint(1) NOT NULL DEFAULT '0',
      `insert_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
      PRIMARY KEY (`wantedID`)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

      -- --------------------------------------------------------

      /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
      /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
      /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

    • Datenbank Probleme

      • SirTim
      • 15. Februar 2017 um 18:04

      Hallo,
      ich hab ein Problem mit der Datenbank. DB-Logs sind angehängt sowie die RPT-Datei.
      Noch dazu hab ich die fn_asyncCall.sqf dazu getan. Da dort angeblich auch ein Fehler sein soll denn ich aber nicht erkennen kann.

      Ich habe schon mehrmals den Rootserver neu aufgesetzt aber immer ohne erfolg. Altis Life habe ich auch mehre male neu Installiert.

      Ich hoffe ihr könnt mir helfen.

      Dateien

      fn_asyncCall.txt 1,56 kB – 168 Downloads DB-Logs.txt 195,76 kB – 164 Downloads RPT.txt 192,67 kB – 192 Downloads

    Registrieren oder Einloggen

    Du bist noch kein Mitglied von NodeZone.net? Registriere dich kostenlos und werde Teil einer großartigen Community!

    Registrieren

    Wichtige Links & Informationen

    Server & Hosting-Ressourcen

      Server Administration & Hosting Basics

      Windows Server Support & Guides

      Linux Server Configuration & Help

      Setting up TeamSpeak 3 & VoIP Servers

      Domains & Web Hosting for Beginners & Professionals

      Cloud Hosting, Docker & Kubernetes Tutorials

    Gameserver & Modding-Ressourcen

      ArmA 3 Tutorials & Script Collection

      Renting & Operating Gameservers

      DayZ Server Management & Help

      FiveM (GTA V) Server & Script Development

      Rust Server Modding & Administration

      Setting up & Optimizing ARK Survival Servers

    NodeZone.net – Deine Community für Gameserver, Server-Hosting & Modding

      NodeZone.net ist dein Forum für Gameserver-Hosting, Rootserver, vServer, Webhosting und Modding. Seit 2015 bietet unsere Community eine zentrale Anlaufstelle für Server-Admins, Gamer und Technikbegeisterte, die sich über Server-Management, Hosting-Lösungen und Spielemodding austauschen möchten.


      Ob Anleitungen für eigene Gameserver, Hilfe bei Root- und vServer-Konfigurationen oder Tipps zu Modding & Scripting – bei uns findest du fundiertes Wissen und praxisnahe Tutorials. Mit einer stetig wachsenden Community findest du hier Antworten auf deine Fragen, Projektpartner und Gleichgesinnte für deine Gaming- und Serverprojekte. Schließe dich NodeZone.net an und werde Teil einer aktiven Community rund um Server-Hosting, Gameserver-Management und Modding-Ressourcen.

    Wer jetzt nicht teilt ist selber Schuld:
    1. Nutzungsbestimmungen
    2. Datenschutzerklärung
    3. Impressum
    4. Urheberrechts- oder Lizenzverstoß melden
  • Trimax Design coded & layout by Gino Zantarelli 2023-2025©
    Community-Software: WoltLab Suite™