Install Percona Monitoring Tools for Nagios – MySQL Plugins
Kedar
Recently a friend asked about Installing Percona Monitoring Tools for Nagios as he was facing a few issues. I managed to set-it-up on my ubuntu VM. Sharing the the work-log…
Browsing Category
MySQL
128 posts
Articles related to MySQL, Percona Server, MariaDB
UMASK & UMASK_DIR – changing default MySQL file dir permissions
UMASK and UMASK_DIR are amongst few MySQL Environment variables which defines directory and file creation modes (file permissions). In this post we will understand using UMASK & UMASK_DIR for changing the database directory and file permissions from it’s default to what we need.
Setup and configure MySQL backup using Holland and Xtrabackup
Setting up a database backup is a primary task for database administrators and we see perl and shell scripts wrapped around few of the backup-tools in practice. With right tools…
Cannot connect to MySQL server on ‘localhost’: Cacti Error
FATAL: Cannot connect to MySQL server on ‘localhost’: Cacti Error – Solution to the issue while setting-up.
How-to extract from mysqldump | mysql-dump-splitter recipes
This post will answer how to extract database, tables etc from mysqldumpsplitter utility.
How to fix definer does not exist error 1449 MySQL
Explaining and providing solutions of MySQL error 1449: The user specified as a definer does not exist using SQL SECURITY INVOKER and DEFINER.
5 responses to “How to fix definer does not exist error 1449 MySQL”
Great post.
I am have just installed mariadb 10.4 and I want to list users with root priviledge. But when I run `SELECT User FROM mysql.user;`, I get this message.
MariaDB [(none)]> SELECT User FROM mysql.user;
ERROR 1449 (HY000): The user specified as a definer (‘mariadb.sys’@’localhost’) does not exist
Anyone can help me?
Hi,
Seems the “definer” user isn’t there on the database which is required for the mysql.user view to execute.
Ref: https://jira.mariadb.org/browse/MDEV-22909
The solution to the error is very simple, we just have to make an upgrade to our database.
mysql_upgrade -u root -p
With this command, a large part of the problems will be solved.
This user must exist and is always better to use ‘localhost’ as hostname. So I think that if you check that the user exists and change it to ‘localhost’ on create view you won’t have this error.