Zabbix logon page error Solution

ZabbixLogin PageErrorThe specific solution is as follows!

After running Zabbix normally for a long time, I suddenly opened the zabbix homepage one day and found an error on the homepage.

[ERROR: Database upted, missed default user 'guest ']

Ignore the error and log on with the normal account and password. The page crashes.

Fatal error: Maximum execution time of 300 seconds exceeded in/var/www/admin_site/htdocs/zabbix/include/config. inc. php on line 342

The number of Zabbix serer processes remains unchanged (23). However, the number of connections generated by zabbix server is much less than that of the server, reducing the number of close wait links from about 200 time wait links to several close wait links.

Restart zabbix. the problem persists.

Solution Process

After investigation, I had restarted mysql at the time of the problem. I suspect that the database may be damaged due to the restart of MySQL.

Further Check: all databases and tables in the MySQL database are found to be disconnected from all innodb databases (not just the Zabbix database) and cannot be accessed. An error is returned: [ERROR]/usr/local/mysql/bin/mysqld: Incorrect information in file :'. /db/table. frm '. While MyISAM tables are good, basically locking is a problem caused by Innodb parameter adjustment.

Recalling the operation at that time, because the system was upgraded with 2 GB of memory, I had manually modified my. cnf and adjusted the innodb parameter.

# Before modification:

 
 

  
  
innodb_buffer_pool_size = 400M  
  
  
 
  
  
innodb_log_file_size = 40M  
  
  
 
 
 

# After modification:

 
 

  
  
innodb_buffer_pool_size = 1G  
  
  
 
  
  
innodb_log_file_size = 128M  
  
  
 
 
 

After searching for information on the Internet, find the reason because innodb_log_file_size has changed. The system finds the original log file and is overwhelmed, and the result fails.

The solution is also very simple. Just delete the ib_logfile * under the data Directory (I am here ib_logfile0 and ib_logfile1) and then start mysql and let it re-build on its own.

After reading the above article, I believe everyone has found out the cause of the error on the Zabbix login page. It will be difficult to encounter such an error in the future!