[MCOL-38] console command "getLogConfigure" return data log setting Created: 2016-05-04  Updated: 2023-10-26  Resolved: 2016-06-02

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: None
Fix Version/s: 1.0.0

Type: Bug Priority: Minor
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

Data transaction is not longer used and transaction replay is no longer available. We should remove the data log in the system, as well as console commands to configures and displays it.
getLogConfig
getlogconfig Wed May 4 10:30:37 2016

Calpont System Log Configuration Data

System Logging Configuration File being used: /etc/rsyslog.d/calpont.conf

Module Configured Log Levels
------ ---------------------------------------
um1 Critical Error Warning Info Debug Data
pm1 Data
pm2 Critical Error Warning Info Debug Data

 Comments   
Comment by David Hill (Inactive) [ 2016-06-02 ]

fixed

mscadmin> getlogconfig
getlogconfig Thu Jun 2 08:23:09 2016

MariaDB Columnstore System Log Configuration Data

System Logging Configuration File being used: /etc/rsyslog.d/columnstore.conf

Module Configured Log Levels
------ ---------------------------------------
pm1 Critical Error Warning Info Debug
mscadmin>

Comment by David Hill (Inactive) [ 2016-06-02 ]

please retest

Comment by Daniel Lee (Inactive) [ 2016-06-02 ]

Build verified:

mscadmin> getsoft
getsoftwareinfo Thu Jun 2 15:19:20 2016

Name : mariadb-columnstore-platform Relocations: (not relocatable)
Version : 1.0 Vendor: MariaDB Corporation Ab
Release : 0 Build Date: Thu 02 Jun 2016 12:12:01 PM EDT
Install Date: Thu 02 Jun 2016 03:09:33 PM EDT Build Host: srvbuilder
Group : Applications Source RPM: mariadb-columnstore-1.0-0.src.rpm

mscadmin> getlogconfig
getlogconfig Thu Jun 2 15:23:28 2016

MariaDB Columnstore System Log Configuration Data

System Logging Configuration File being used: /etc/rsyslog.d/columnstore.conf

Module Configured Log Levels
------ ---------------------------------------
pm1 Critical Error Warning Info Debug
pm2 Critical Error Warning Info Debug

Generated at Thu Feb 08 02:18:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.