Today my zabbix webpage was dead and after rebooting my zabbix server I realized Zabbix wasn;t starting.
After investigating I saw that it couldn't find the database.
Looking at the zabbix.conf file I see that the DB server is a remote server.
Had someone check that server and they could not find my database.
After some searching they located my database on another SQL server managed by the same group.
I changed the zabbix.conf file and the web conf file to point to the new database server and then rebooted my zabbix server.
I see the message [[ Zabbix supports only "utf8_bin" collation. Database "zep_1_zabbix" has default collation "utf8_general_ci" but it doesn't seem to be stopping it from starting. ]]
The web gui started working again but was very slow to populate after I logged in.
The first problem I've found after finally getting the GUI working is that when I go to Monitoring ---> Problems and select unacknowledged issues it seems to get stuck if I select more than 2 or 3 on the main page.
I seem to be able to select all on page 2 and 3 and the mass update worked without a hitch, but now page1 is stiuk and has been stuck for the past 30 minutes with the spinning busy icon right after clicking the "mass update" button.
What else should I expect to be a problem after having this database moved to a different server ?
I have to also figure out how to back up this remote server as I am not a db guy.
"mysqldump -u root -p zep_1_zabbix > zep_1_zabbix.sql.$NOW" is what i would use if the database was local, but it's on a remote DB server.
After investigating I saw that it couldn't find the database.
Looking at the zabbix.conf file I see that the DB server is a remote server.
Had someone check that server and they could not find my database.
After some searching they located my database on another SQL server managed by the same group.
I changed the zabbix.conf file and the web conf file to point to the new database server and then rebooted my zabbix server.
I see the message [[ Zabbix supports only "utf8_bin" collation. Database "zep_1_zabbix" has default collation "utf8_general_ci" but it doesn't seem to be stopping it from starting. ]]
The web gui started working again but was very slow to populate after I logged in.
The first problem I've found after finally getting the GUI working is that when I go to Monitoring ---> Problems and select unacknowledged issues it seems to get stuck if I select more than 2 or 3 on the main page.
I seem to be able to select all on page 2 and 3 and the mass update worked without a hitch, but now page1 is stiuk and has been stuck for the past 30 minutes with the spinning busy icon right after clicking the "mass update" button.
What else should I expect to be a problem after having this database moved to a different server ?
I have to also figure out how to back up this remote server as I am not a db guy.
"mysqldump -u root -p zep_1_zabbix > zep_1_zabbix.sql.$NOW" is what i would use if the database was local, but it's on a remote DB server.
Comment