Skip to main content

Setting MySQL General Log

  1. Add parameters to my.cnf file (For Windows, my.ini).
    1. Go to %MYSQL_HOME directory.
    2. Open my.cnf (for UNIX) or my.ini (for Windows) with your text editor.
    3. Add the following parameters in [mysqld] section.
      general_log=1
      log_output=TABLE
      
    4. Restart MySQL databases.
  2. Change the definition of "mysql.general_log" table.
    1. Switch the engine from CSV to MyISAM. To switch the engine from CSV to MyISAM, execute the following commands (the default is ENGINE=CSV).
      mysql> SET GLOBAL general_log = 'OFF';
      mysql> ALTER TABLE mysql.general_log ENGINE = MyISAM;
      mysql> SET GLOBAL general_log = 'ON';
      
  3. Check the definition of "mysql.general_log" table. Execute the following SQL command:
    mysql> show create table mysql.general_log;
    
    +-------------+-----------------------------------------------------------------
    -----------------------------------------+
    | Table       | Create Table
    -----------------------------------------+
    | general_log | CREATE TABLE `general_log` (
      `event_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TI
    MESTAMP,
      `user_host` mediumtext NOT NULL,
      `thread_id` int(11) NOT NULL,
      `server_id` int(11) NOT NULL,
      `command_type` varchar(64) NOT NULL,
      `argument` mediumtext NOT NULL
    ) ENGINE=MyISAM DEFAULT CHARSET=utf8 COMMENT='General log' |
    +-------------+--------------------------------------------
    
  4. Check if logging started. Execute the following command:
    mysql> select * from mysql.general_log;
    
    +---------------------+------------------------------------+-----------+--------
    ---+--------------+----------------------------------+
    | event_time          | user_host                          | thread_id | server_
    id | command_type | argument                         |
    +---------------------+------------------------------------+-----------+--------
    ---+--------------+----------------------------------+
    | 2009-07-29 16:44:23 | root[root] @ localhost [127.0.0.1] |         1 |
     0 | Connect      | root@localhost on mysql          |
    | 2009-07-29 16:44:23 | root[root] @ localhost [127.0.0.1] |         1 |
     0 | Query        | select @@version_comment limit 1 |
    | 2009-07-29 16:44:37 | root[root] @ localhost [127.0.0.1] |         1 |
     0 | Query        | show create table general_log    |
    | 2009-07-29 16:45:19 | root[root] @ localhost [127.0.0.1] |         1 |
     0 | Query        | set global general_log='OFF'     |
    | 2009-07-29 16:46:18 | root[root] @ localhost [127.0.0.1] |         1 |
     0 | Query        | select * from mysql.general_log  |
    +---------------------+------------------------------------+-----------+--------
    ---+--------------+----------------------------------+
    5 rows in set (0.00 sec)

Comments

Popular posts from this blog

Offline AI Coding in VSCode: Continue + Ollama Complete Setup Guide

Want GitHub Copilot-level code assistance — but fully offline, air-gapped, and private? This guide walks you through setting up Continue (a VSCode extension) with Ollama (a local model runner) so you get chat, autocomplete, and inline editing powered entirely by models running on your own machine. No internet required at runtime. Table of Contents What Are Continue and Ollama? Prerequisites & Hardware Requirements Choosing the Right Models Step 1 — Installing Ollama & Pulling Models Step 2 — Installing Continue in VSCode (Offline) Step 3 — Configuring config.yaml Step 4 — Disabling Telemetry Step 5 — Usage & Shortcuts Troubleshooting What Are Continue and Ollama? Continue is an open-source VSCode (and JetBrains) extension that adds AI-powered coding features directly into your editor — think chat, inline edits, and tab autocomplete. By default it can connect to Claude, GPT-4, or any API. But it also supports local providers , which is exactly what we want here. Ollama i...

Local LLM on Ubuntu (CPU-Only): Ollama + Qwen Coder + Open WebUI + RAG Setup

Local LLM on Ubuntu (CPU-Only): Ollama + Qwen Coder + Open WebUI + RAG Run a private, high-performance internal AI coding assistant on your own hardware—no GPU required. Feb 13, 2026 Qwen 2.5 Coder RAG Enabled Enterprise Ready Keeping your code and documents on your own infrastructure is the gold standard for enterprise security. By combining Ollama , Qwen Coder , and Open WebUI , we can build a production-grade AI assistant that respects your privacy. Environment: CPU-only Ubuntu server (e.g., i9/Threadripper) with 64GB+ RAM for smooth 14B model inference. 1. System Preparation First, update your local environment and install necessary dependencies: sudo apt update && sudo apt upgrade -y sudo apt install -y curl git ca-certificates lscpu 2. Ollama & Model Tuning Install Ollama and optimize the configuration for CPU-only inference by setting the thread count: ...

Defining tomcat and mysql server Amazon EC2 instance

-- Create new amazon ec2 instance http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html -- Give permisson to pem file chmod 400 mycertificate.pem -- Connect to EC2 instance ssh -i mycertificate.pem ubuntu@ec2-51-51-51-51.eu-west-1.compute.amazonaws.com -- Installation Oracle Java 1.8 $ wget --no-check-certificate --no-cookies --header "Cookie: oraclelicense=accept-securebackup-cookie" http://download.oracle.com/otn-pub/java/jdk/8u92-b14/jdk-8u92-linux-x64.tar.gz $ tar -xzvf jdk-8u92-linux-x64.tar.gz $ sudo mkdir -p /usr/java/ $ sudo mv jdk1.8.0_92/ /usr/java/ $ sudo vim  /etc/profile         JAVA_HOME=/usr/java/jdk1.8.0_92         PATH=$PATH:$HOME/bin:$JAVA_HOME/bin         JRE_HOME=/usr/java/jdk1.8.0_92/jre         PATH=$PATH:$HOME/bin:$JRE_HOME/bin         export JAVA_HOME...