Zabbix Server is not running on Ubuntu 14.04

[mudit.gupta]

Hello All

My Zabbix server is not running. In logs it shows

1540:20170202:164440.869 database is down: reconnecting in 10 seconds
1540:20170202:164450.879 [Z3001] connection to database 'zabbixdb' failed: [0] FATAL: password authentication failed for user "zabbix"
FATAL: password authentication failed for user "zabbix"

I have checked DBpassword and Zabbix PHP file and Zabbix Server file. At front end password is also correct.

Output of :: netstat -anlp | grep 10051 , is noting .

Zabbix server , service is running.

Please help me.

Thanks
Mudit Gupta

[batchenr]

Hello All

My Zabbix server is not running. In logs it shows

1540:20170202:164440.869 database is down: reconnecting in 10 seconds
1540:20170202:164450.879 [Z3001] connection to database 'zabbixdb' failed: [0] FATAL: password authentication failed for user "zabbix"
FATAL: password authentication failed for user "zabbix"

I have checked DBpassword and Zabbix PHP file and Zabbix Server file. At front end password is also correct.

Output of :: netstat -anlp | grep 10051 , is noting .

Zabbix server , service is running.

Please help me.

Thanks
Mudit Gupta

did you made some changes for this to happen?

look at this file :
/etc/zabbix/zabbix_server.conf
DBName=zabbixdb
DBUser=zabbix
DBPassword=PASS

make sure in the database when you run this commaend :

select host,user from mysql.user where user like '%zab%';

return a response with a user zabbix localhost

make sure zabbix user have this grants :
GRANT USAGE ON *.* TO 'zabbix'@'localhost' IDENTIFIED BY PASSWORD
GRANT ALL PRIVILEGES ON `zabbixdb`.* TO 'zabbix'@'localhost'

check it via
show grants for 'zabbix'@'localhost';


check zabbix user mysql connection via :
mysql -u zabbix -p

see if it connecting.

[mudit.gupta]

Hello batchenr

Thanks for your response. I tried, what you have suggested but I am in same condition. Still Error: Zabbix server is not running , the information displayed may not be current.

Before this error Zabbix Server was running fine and suddenly , it stopped running.

Here is the output of your steps.

mysql> select host,user from mysql.user where user like '%zab%';
+-----------+--------+
| host | user |
+-----------+--------+
| localhost | zabbix |
+-----------+--------+

|
+----------------------------------------------------+
mysql> show grants for 'zabbix'@'localhost';
+---------------------------------------------------------------------------------------------------------------+
| Grants for zabbix@localhost |
+---------------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'zabbix'@'localhost' IDENTIFIED BY PASSWORD '*FBA7C2D27C9D05F3FD4C469A1BBAF557114E5594' |
| GRANT ALL PRIVILEGES ON `zabbixdb`.* TO 'zabbix'@'localhost' |
+-------------------------------------------------------------------------------------

I am also able to login by ::

root@mudit-VirtualBox:~# mysql -u zabbix -p
Enter password:
Welcome to the MySQL monitor.

There is no change in Zabbix_Server.conf file.

Please help me.

Thanks
Mudit

[kloczek]

I am also able to login by ::

root@mudit-VirtualBox:~# mysql -u zabbix -p
Enter password:
Welcome to the MySQL monitor.

There is no change in Zabbix_Server.conf file.

Here you are trying establish connectivity to DB engine from root user. Zabbix server is trying to do the same from non-root account (probably zabbix).
Please disable SELinux or add SELinux rule to allow zabbix user connect to port 3306.

[mudit.gupta]

Hello

I have changed selinux status to disabled but no help.

root@mudit-VirtualBox:~# sestatus
SELinux status: disabled

Please help me !!!

Thanks
Mudit

[Pada]

I'd suggest that you also disable DNS resolving on your MySQL server, by adding "skip-name-resolve" to the "[mysqld]" section and then restarting MySQL server.

Then also take note that there is a difference between letting your Zabbix server connect to localhost:3306 and 127.0.0.1:3306.
So please make sure that your MySQL username is in the format of <DBUser>@<DBHost>, as specified in your /etc/zabbix/zabbix_server.conf

Also make sure that your "DBName" setting in zabbix_server.conf is set to "zabbixdb", because that is the database that you granted permission to for your zabbix@localhost MySQL user.

[mudit.gupta]

Hello Pada

It is confirmed that "DBName" setting in zabbix_server.conf is set to "zabbixdb",

Can you please guide me that how can I do this, which is suggested by you { disable DNS resolving on your MySQL server, by adding "skip-name-resolve" to the "[mysqld]" section } and { please make sure that your MySQL username is in the format of <DBUser>@<DBHost> } , please tell me in which location, I need to make such changes.


Thanks
Mudit

[Pada]

The MySQL server config location is typically at /etc/my.cnf

For instance my /etc/my.cnf contains like the following (and more which I left out to keep this post small):

[mysqld]
port            = 3306
socket          = /var/lib/mysql/mysql.sock
datadir         = /home/mysql
skip-name-resolve
skip-external-locking
key_buffer_size = 384M

As for the MySQL user, if you've created a MySQL user called: 'zabbix'@'localhost'
Then your Zabbix server configuration (typically in /etc/zabbix/zabbix_server.conf) should have like:

DBUser=zabbix
DBHost=localhost

and not like

DBUser=zabbix
DBHost=127.0.0.1

I hope this makes more sense now...

[mudit.gupta]

Hello Pada

First of all Thanks for your reply, I made the changes suggested by you but no help.

File :: /etc/mysql/my.cnf at my end.

[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
skip-name-resolve
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking

after this I restarted Zabbix server and mysql service also.

In /etc/zabbix/zabbix_server.conf

DBUser=zabbix
DBHost=localhost

it is already there .

But still no luck .


PLease any one can help me!!

Thanks
Mudit

[batchenr]

Hello Pada

First of all Thanks for your reply, I made the changes suggested by you but no help.

File :: /etc/mysql/my.cnf at my end.

[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
skip-name-resolve
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking

after this I restarted Zabbix server and mysql service also.

In /etc/zabbix/zabbix_server.conf

DBUser=zabbix
DBHost=localhost

it is already there .

But still no luck .


PLease any one can help me!!

Thanks
Mudit

what is you mysql version ?
do you have a mysql error log ? can you check if there some info there ?
if you dont have please set .

can you post you full my.cnf ?

do you have an external zabbix ip or just internal ?

[mudit.gupta]

Hello batchenr

Cat /var/log/mysql/error.log

170206 12:30:58 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170206 12:30:58 [Note] Plugin 'FEDERATED' is disabled.
170206 12:30:58 InnoDB: The InnoDB memory heap is disabled
170206 12:30:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170206 12:30:58 InnoDB: Compressed tables use zlib 1.2.8
170206 12:30:58 InnoDB: Using Linux native AIO
170206 12:30:58 InnoDB: Initializing buffer pool, size = 128.0M
170206 12:30:58 InnoDB: Completed initialization of buffer pool
170206 12:30:58 InnoDB: highest supported file format is Barracuda.
170206 12:30:59 InnoDB: Waiting for the background threads to start
170206 12:31:00 InnoDB: 5.5.54 started; log sequence number 9139235
170206 12:31:00 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170206 12:31:00 [Note] - '127.0.0.1' resolves to '127.0.0.1';
170206 12:31:00 [Note] Server socket created on IP: '127.0.0.1'.
170206 12:31:00 [Warning] 'user' entry 'root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 12:31:00 [Warning] 'proxies_priv' entry '@ root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 12:31:00 [Note] Event Scheduler: Loaded 0 events
170206 12:31:00 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)

Mysql Version ::
root@mudit-VirtualBox:~# mysql -V
mysql Ver 14.14 Distrib 5.5.54, for debian-linux-gnu (x86_64) using readline 6.3

Zabbix IP is internal.

Thanks
Mudit

[batchenr]

Hello batchenr

Cat /var/log/mysql/error.log

170206 12:30:58 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170206 12:30:58 [Note] Plugin 'FEDERATED' is disabled.
170206 12:30:58 InnoDB: The InnoDB memory heap is disabled
170206 12:30:58 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170206 12:30:58 InnoDB: Compressed tables use zlib 1.2.8
170206 12:30:58 InnoDB: Using Linux native AIO
170206 12:30:58 InnoDB: Initializing buffer pool, size = 128.0M
170206 12:30:58 InnoDB: Completed initialization of buffer pool
170206 12:30:58 InnoDB: highest supported file format is Barracuda.
170206 12:30:59 InnoDB: Waiting for the background threads to start
170206 12:31:00 InnoDB: 5.5.54 started; log sequence number 9139235
170206 12:31:00 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170206 12:31:00 [Note] - '127.0.0.1' resolves to '127.0.0.1';
170206 12:31:00 [Note] Server socket created on IP: '127.0.0.1'.
170206 12:31:00 [Warning] 'user' entry 'root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 12:31:00 [Warning] 'proxies_priv' entry '@ root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 12:31:00 [Note] Event Scheduler: Loaded 0 events
170206 12:31:00 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)

Mysql Version ::
root@mudit-VirtualBox:~# mysql -V
mysql Ver 14.14 Distrib 5.5.54, for debian-linux-gnu (x86_64) using readline 6.3

Zabbix IP is internal.

Thanks
Mudit

i need you to try to restart mysql&zabbix and try to connect to zabbix GUI and show me all of that in the log- i dont see there any mention to zabbix user.

[mudit.gupta]

Hello

I restarted mysql and Zabbix server then open Zabbix Server GUI and below is the out put of /var/log/mysql/error.log .


root@mudit-VirtualBox:~# tail -f /var/log/mysql/error.log
170206 13:16:56 InnoDB: Waiting for the background threads to start
170206 13:16:57 InnoDB: 5.5.54 started; log sequence number 9144641
170206 13:16:57 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170206 13:16:57 [Note] - '127.0.0.1' resolves to '127.0.0.1';
170206 13:16:57 [Note] Server socket created on IP: '127.0.0.1'.
170206 13:16:57 [Warning] 'user' entry 'root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:16:57 [Warning] 'proxies_priv' entry '@ root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:16:57 [Note] Event Scheduler: Loaded 0 events
170206 13:16:57 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
170206 13:19:45 [Note] /usr/sbin/mysqld: Normal shutdown

170206 13:19:45 [Note] Event Scheduler: Purging the queue. 0 events
170206 13:19:45 InnoDB: Starting shutdown...
170206 13:19:46 InnoDB: Waiting for 3 pages to be flushed
170206 13:19:46 InnoDB: Shutdown completed; log sequence number 9149344
170206 13:19:46 [Note] /usr/sbin/mysqld: Shutdown complete

170206 13:19:46 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170206 13:19:46 [Note] Plugin 'FEDERATED' is disabled.
170206 13:19:46 InnoDB: The InnoDB memory heap is disabled
170206 13:19:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170206 13:19:46 InnoDB: Compressed tables use zlib 1.2.8
170206 13:19:46 InnoDB: Using Linux native AIO
170206 13:19:47 InnoDB: Initializing buffer pool, size = 128.0M
170206 13:19:47 InnoDB: Completed initialization of buffer pool
170206 13:19:47 InnoDB: highest supported file format is Barracuda.
170206 13:19:47 InnoDB: Waiting for the background threads to start
170206 13:19:48 InnoDB: 5.5.54 started; log sequence number 9149344
170206 13:19:48 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170206 13:19:48 [Note] - '127.0.0.1' resolves to '127.0.0.1';
170206 13:19:48 [Note] Server socket created on IP: '127.0.0.1'.
170206 13:19:48 [Warning] 'user' entry 'root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:19:48 [Warning] 'proxies_priv' entry '@ root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:19:48 [Note] Event Scheduler: Loaded 0 events
170206 13:19:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)


Thanks
Mudit

[batchenr]

Hello

I restarted mysql and Zabbix server then open Zabbix Server GUI and below is the out put of /var/log/mysql/error.log .


root@mudit-VirtualBox:~# tail -f /var/log/mysql/error.log
170206 13:16:56 InnoDB: Waiting for the background threads to start
170206 13:16:57 InnoDB: 5.5.54 started; log sequence number 9144641
170206 13:16:57 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170206 13:16:57 [Note] - '127.0.0.1' resolves to '127.0.0.1';
170206 13:16:57 [Note] Server socket created on IP: '127.0.0.1'.
170206 13:16:57 [Warning] 'user' entry 'root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:16:57 [Warning] 'proxies_priv' entry '@ root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:16:57 [Note] Event Scheduler: Loaded 0 events
170206 13:16:57 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
170206 13:19:45 [Note] /usr/sbin/mysqld: Normal shutdown

170206 13:19:45 [Note] Event Scheduler: Purging the queue. 0 events
170206 13:19:45 InnoDB: Starting shutdown...
170206 13:19:46 InnoDB: Waiting for 3 pages to be flushed
170206 13:19:46 InnoDB: Shutdown completed; log sequence number 9149344
170206 13:19:46 [Note] /usr/sbin/mysqld: Shutdown complete

170206 13:19:46 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
170206 13:19:46 [Note] Plugin 'FEDERATED' is disabled.
170206 13:19:46 InnoDB: The InnoDB memory heap is disabled
170206 13:19:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
170206 13:19:46 InnoDB: Compressed tables use zlib 1.2.8
170206 13:19:46 InnoDB: Using Linux native AIO
170206 13:19:47 InnoDB: Initializing buffer pool, size = 128.0M
170206 13:19:47 InnoDB: Completed initialization of buffer pool
170206 13:19:47 InnoDB: highest supported file format is Barracuda.
170206 13:19:47 InnoDB: Waiting for the background threads to start
170206 13:19:48 InnoDB: 5.5.54 started; log sequence number 9149344
170206 13:19:48 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
170206 13:19:48 [Note] - '127.0.0.1' resolves to '127.0.0.1';
170206 13:19:48 [Note] Server socket created on IP: '127.0.0.1'.
170206 13:19:48 [Warning] 'user' entry 'root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:19:48 [Warning] 'proxies_priv' entry '@ root@mudit-virtualbox' ignored in --skip-name-resolve mode.
170206 13:19:48 [Note] Event Scheduler: Loaded 0 events
170206 13:19:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.54-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)


Thanks
Mudit

post my.cnf here please.

[mudit.gupta]

Here is the /etc/mysql/my.cnf

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/se...variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
skip-name-resolve
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/


Thanks
Mudit