Closed bertalanimre closed 3 months ago
Thank you for your advices. Please excuse me for being confused but I don't really get the first point of yours.
2; All clear, trying it now 3; I needed to do this because we use Grafana to display the data and Grafana couldn't use the Zabbix API to authenticate and receive the source. So we used this method as a workaround. Is this resolved in any way in Version 7 ?
4; Thanks, at leas I was able to figure out one thing.
- The proxy "zabbix-proxy-mysql" does not exist in Zabbix configuration
- './zabbix_server.conf:/etc/zabbix/zabbix_server.conf' - such mount is not allowed. Use env variables.
- You use custom / modified Zabbix frontend php file: './CUser.php:/usr/share/zabbix/include/classes/api/services/CUser.php'
Oh never mind me. I get it. I had to add the ZBX_PROXYMODE: 1
to the zabbix-proxy. Thanks. Thankfully, everything works now. :heart:
The only remaining issue was supposed to be Grafana, but it looks like it is working now out of the box.
Thank you for your help and have a great day ! :smiley:
SUMMARY
After pulling latest Zabbix images (previously on 6.4), the WebUI responds with HTTP 500 and complains about the PHP version. Did I forget to update anything else other than just pulling in the latest images? I haven't found anything specific task in the upgrade procedures I should be doing, tho to be fair, it is not about docker compose running environment at all so I am probably be at fault here.
OS / ENVIRONMENT / Used docker-compose files
Ubuntu 22.04 Docker version 27.0.3, build 7d4bcd8 Docker Compose version v2.28.1
CONFIGURATION
docker-compose.yml
Inside the container
STEPS TO REPRODUCE
I don't know who to exaclty reproduce the issue, but what I've done in order to upgrade to the lastest docker images were:
I have not changed any configuration line or executed any command before or after the docker image changes
EXPECTED RESULTS
I honestly just expected the WebUI to load in
ACTUAL RESULTS
The website comes back with a browser supplied HTTP 500. Uplon calling the URL, the following lines are coming to the docker compose logs: (I've hid the IP addresses and URLs, they are normal)
Oh wait, I might have found something. Turn out, the Proxy server dies during "boot".
Update
So what I've noticed is now in the logs the proxy server complains it cannot use the zabbix database as before. So I added a new database called "zabbix_proxy" in the compose file. However, even tho the proxy server does not fail now, it still spits out errors left and right along with the zabbix server
Is this normal?
Can I have a little help please? I am kinda feeling lost because the PHP is working, it is the proper version and NginX still refuses to see it. All this inside the container which is odd especially because I have not changed anything. I did not expect the images not working :disappointed: