主页 / computer / 问题

问题[mariadb](computer)

Martin Hope
Timo Treichel
Asked: 2024-02-23 21:08:03 +0800 CST
  • 7

我有下表：

CREATE TABLE t1 (
    a INT, 
    b INT, 
    CONSTRAINT a_greater CHECK (a>b)
);

所以，a一定大于b。执行此插入时，它不应该起作用：

insert into t1(a,b) values (4,5);

不过，我可以运行该声明。

1

数据库版本：10.1.48-MariaDB-0+deb9u2

我知道，我可以通过触发器来实现这一点，但这需要太多的努力，只是为了完成检查约束实际应该完成的事情。

是否存在错误或者可能是由于任何错误的配置造成的？什么可能导致此行为以及如何修复它？

mariadb
Martin Hope
theber
Asked: 2020-05-01 05:38:51 +0800 CST
  • 6

在新安装的 Kubuntu 20.04 上全新安装 MariaDB。使用“stock”数据库成功设置 MariaDB 后，它运行良好。然后我移动并重命名了 /var/lib/mysql 的原始内容，并使用绑定挂载将我的真实数据库引入新的 /var/lib/mysql 文件夹。重新启动后，真实数据库位于正确的文件夹中，具有正确的权限，但 MariaDB 服务器将不再启动。我已经在 Kubuntu 19.04、Kubuntu 19.10、Manjaro 等上成功使用了这个过程。我无法让它在 Fedora 31、OpenSUSE、Mageia 等上工作。
以下是 systemctl status mariadb 和 journalctl -xe 的输出：

Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2020-04-30 14:55:16 CEST; 12min ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 3343 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 3348 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 3362 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
    Process: 3411 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 3411 (code=exited, status=1/FAILURE)

Apr 30 14:55:16 murphy systemd[1]: Starting MariaDB 10.3.22 database server...
Apr 30 14:55:16 murphy mysqld[3411]: 2020-04-30 14:55:16 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 3411 ...
Apr 30 14:55:16 murphy systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Apr 30 14:55:16 murphy systemd[1]: mariadb.service: Failed with result 'exit-code'.
Apr 30 14:55:16 murphy systemd[1]: Failed to start MariaDB 10.3.22 database server.  


Starting MariaDB 10.3.22 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit mariadb.service has begun execution.
-- 
-- The job identifier is 2434.
Apr 30 15:20:18 murphy mysqld[3849]: 2020-04-30 15:20:18 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 3849 ...
Apr 30 15:20:18 murphy systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- An ExecStart= process belonging to unit mariadb.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Apr 30 15:20:18 murphy systemd[1]: mariadb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
Apr 30 15:20:18 murphy systemd[1]: Failed to start MariaDB 10.3.22 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit mariadb.service has finished with a failure.
-- 
-- The job identifier is 2434 and the job result is failed.
Apr 30 15:21:13 murphy su[2897]: pam_unix(su:session): session closed for user root
Apr 30 15:21:13 murphy sudo[2896]: pam_unix(sudo:session): session closed for user root

有人可以帮我澄清一下吗？我需要提供更多信息吗？谢谢，
瑟伯

Attie：这是 journalctl -u mariadb.service 的输出

-- Logs begin at Sat 2020-04-25 15:11:36 CEST, end at Thu 2020-04-30 20:46:28 CEST. --
 Apr 30 13:25:09 murphy systemd[1]: Starting MariaDB 10.3.22 database server...
Apr 30 13:25:09 murphy mysqld[4197]: 2020-04-30 13:25:09 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 4197 ...
Apr 30 13:25:09 murphy systemd[1]: Started MariaDB 10.3.22 database server.
Apr 30 13:25:09 murphy /etc/mysql/debian-start[4233]: Upgrading MySQL tables if necessary.
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Looking for 'mysql' as: /usr/bin/mysql
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Phase 1/7: Checking and upgrading mysql database
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Processing databases
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.column_stats                                 OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.columns_priv                                 OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.db                                           OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.event                                        OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.func                                         OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.gtid_slave_pos                               OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.help_category                                OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.help_keyword                                 OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.help_relation                                OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.help_topic                                   OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.host                                         OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.index_stats                                  OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.innodb_index_stats                           OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.innodb_table_stats                           OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.plugin                                       OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.proc                                         OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.procs_priv                                   OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.proxies_priv                                 OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.roles_mapping                                OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.servers                                      OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.table_stats                                  OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.tables_priv                                  OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.time_zone                                    OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.time_zone_leap_second                        OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.time_zone_name                               OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.time_zone_transition                         OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.time_zone_transition_type                    OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.transaction_registry                         OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql.user                                         OK
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Phase 2/7: Installing used storage engines... Skipped
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Phase 3/7: Fixing views
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Processing databases
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: information_schema
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: performance_schema
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Phase 4/7: Running 'mysql_fix_privilege_tables'
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Phase 5/7: Fixing table and database names
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Processing databases
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: information_schema
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: mysql
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: performance_schema
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Phase 6/7: Checking and upgrading tables
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Processing databases
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: information_schema
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: performance_schema
Apr 30 13:25:10 murphy /etc/mysql/debian-start[4236]: Phase 7/7: Running 'FLUSH PRIVILEGES'

/var/log/mysql/error.log 的输出：

2020-05-01  8:50:24 0 [Note] InnoDB: Using Linux native AIO
2020-05-01  8:50:24 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-05-01  8:50:24 0 [Note] InnoDB: Uses event mutexes
2020-05-01  8:50:24 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-05-01  8:50:24 0 [Note] InnoDB: Number of pools: 1
2020-05-01  8:50:24 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-05-01  8:50:24 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-05-01  8:50:24 0 [Note] InnoDB: Completed initialization of buffer pool
2020-05-01  8:50:24 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriorit>
2020-05-01  8:50:24 0 [Note] InnoDB: Downgrading redo log: 2*50331648 bytes; LSN=22077728
2020-05-01  8:50:24 0 [Note] InnoDB: Starting to delete and rewrite log files.
2020-05-01  8:50:24 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
2020-05-01  8:50:24 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes
2020-05-01  8:50:24 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2020-05-01  8:50:24 0 [Note] InnoDB: New log files created, LSN=22077728
2020-05-01  8:50:25 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-05-01  8:50:25 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-05-01  8:50:25 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-05-01  8:50:25 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-05-01  8:50:25 0 [Note] InnoDB: Waiting for purge to start
2020-05-01  8:50:25 0 [Note] InnoDB: 10.3.22 started; log sequence number 22077728; transaction id 31153
2020-05-01  8:50:25 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2020-05-01  8:50:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-05-01  8:50:25 0 [Note] Recovering after a crash using tc.log
2020-05-01  8:50:25 0 [Note] Starting crash recovery...
2020-05-01  8:50:25 0 [Note] Crash recovery finished.
2020-05-01  8:50:25 0 [Note] Server socket created on IP: '127.0.0.1'.
2020-05-01  8:50:25 0 [ERROR] Fatal error: Can't open and lock privilege tables: 'mysql.user' is not of type 'TABLE'
kubuntu mariadb
Martin Hope
sanjihan
Asked: 2019-12-15 00:05:22 +0800 CST
  • 5

我在 Centos 7 上安装 MariaDB 10.4 时遇到了一些麻烦。官方的mariaDB 指南说MariaDB.repo应该创建一个新的 repo 文件，/etc/yum.repos.d/其中包含以下内容：

# MariaDB 10.4 CentOS repository list - created 2019-12-13 22:03 UTC
# http://downloads.mariadb.org/mariadb/repositories/
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.4/centos7-ppc64le
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

我已经运行yum-config-manager --enable MariaDB.repo并yum update检查了启用的存储库：

$ enabled | grep maria
mariadb          MariaDB              86

这确认新的 repo 已启用。向导后来说跑步sudo yum install MariaDB-server MariaDB-client。不幸的是，没有什么要安装的，因为我收到了一条消息：

Failed to set locale, defaulting to C
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: centos.anexia.at
 * epel: ftp.uni-kl.de
 * extras: mirror.easyname.at
 * remi-php74: remi.mirror.karneval.cz
 * remi-safe: remi.mirror.karneval.cz
 * updates: centos.anexia.at
No package MariaDB-server available.
  * Maybe you meant: mariadb-server
No package MariaDB-client available.

请注意，没有提到MariaDB.repo我刚刚启用。此外，建议的软件包mariadb-server是 5.5 版。在 Centos 7 上安装 MariaDB 10.4 版的正确方法是什么？

centos mariadb
Martin Hope
WestCoastProjects
Asked: 2019-05-14 09:44:18 +0800 CST
  • 5

我在一个基于centos的amazon linux实例上：例如我用过

 sudo yum install -y mysql

和

 sudo yum install -y postgresql

虽然这些确实安装没有错误，但我不太了解如何在这个非/etc/init.d环境中使用它们。跑步时

  systemctl | grep sql

什么都没有出现。当我什至找不到它们时，如何启用/操作这些..

postgresql mariadb
Martin Hope
C yp
Asked: 2019-04-04 19:11:48 +0800 CST
  • 0

作为我大学项目的一部分，我的目标是为书籍创建第二个分类程序。

想知道项目设备申请是要申请【AWS】，还是可以用【NAS】覆盖。

当我简化我想做的工作时，如下图

  1. 保存图书数据库信息。

  2. 将保存的DB信息上传到服务器端后，会与Android app（客户端）进行链接（貌似需要处理一个DB查询，处理一下）。

如果继续这个过程[aws]，它会顺利进行

但是可以用 [NAS] 来实现吗？

Synology [NAS] 支持 mariaDB

但

但是，我不知道使用 Synology NAS 通过 SQL 查询是查询还是答案

谢谢！

nas amazon-web-services mariadb
Martin Hope
jost21
Asked: 2019-04-03 20:24:26 +0800 CST
  • 7

我在 Arch Linux (Manjaro) 上运行 MariaDB (v 10.3.13)。它在过去几个月中正常工作，但现在出现了一些问题。当我尝试重新启动计算机时，它卡在

A stop job is running for MariaDB 10.3.13 database server

它应该花费的时间每分钟增加一次，直到它最终超时（大约 20 分钟后）。

当我尝试重新启动/停止它时，手动停止 MariaDB 也会卡住

sudo systemctl stop/restart mariadb

然后跑sudo systemctl status mariadb节目

/usr/bin/mysqld (initiated by: unknown): Normal shutdown
Event Scheduler: Purging the queue. 0 events
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
InnoDB: Buffer pool(s) dump completed at 190402 20:31:01
InnoDB: Waiting for page_cleaner to finish flushing of buffer pool

每分钟都会添加另一行InnoDB: Waiting for page_cleaner to finish flushing of buffer pool。

有没有办法重置 MariaDB？或者获取更多信息的方法是什么问题？

PS：我最近通过包管理器安装了一些更新，之后我第一次注意到这个问题。

更新：

当我卸载、重新启动并重新安装 MariaDB 时，我可以毫无问题地停止/重新启动 MariaDB，并且关机也没有问题。但是再次启动后，我又回到了上述问题。

linux arch-linux mariadb